|
|
#1 |
|
Senior Member
|
server and cluster dilema
Is their any way to block your main server from being listed in the shoutcast directory but have the relays still listed? reason being is that I want to have my main server holding only 2 listeners, while my relay will be a 100 listener one. but if the 100 listener were to suddenly drop and come back online the main server would be filled already with listeners since there are only 2 spots. This would make the relay server impossible to connect back since it needs to have an open spot right? So basically I don't want any listeners connecting to my main server. Reason my main server is so small is cause the I want to use the relay server which is in Sweden as my big server (much more affordable) and I don't trust my ISP streaming that far. my pings get over 300 ms at times. I want the sweden server to relay off a server in north america.
|
|
|
|
|
|
#2 |
|
Alumni
Join Date: Sep 2001
Location: Maui, Hawaii
Posts: 14,109
|
I was doing a relay serach earlier in the day and found an exact match for your question.
I don't remember the post ID nor the response and I'm too tired to dig through query results. It's there though. |
|
|
|
|
|
#3 |
|
Senior Member
|
I know you can do it with SAM2 (www.spacialaudio.com) by hiding the relay from being posted, or perhaps using a different encoder, other than that Im not sure =\ sry
|
|
|
|
|
|
#4 |
|
Senior Member
|
i do use SAM2 to broadcast, but I never heard of an option of hiding your main server and still have your relays show up. Fester are u aware of this?
|
|
|
|
|
|
#5 |
|
Senior Member
|
wait just thought of something. What if I were to add the IP of the relay server on the reserve IP list?
|
|
|
|
|
|
#6 |
|
Junior Member
Join Date: Apr 2003
Posts: 31
|
I've done that and it works. But... according to the docs, when the machine with the reserved ip reconnects, it supposedly kicks the listener that's been connected the longest. So, if you're running more than one relay, it will likely kick the other relay. That one should try and reconnect and then kick the listener (assuming both relays are have reserved ips). Just something to think about.
|
|
|
|
|
|
#7 |
|
Moderator Alumni
Join Date: May 2000
Location: Next Door
Posts: 8,888
|
easier way,
The main (Small) server: sc_serv.ini/conf set PublicServer=Never The big (public) server or any other relaying server you want publicized that is relaying that main server: set PublicServer=Always -Jay | Radio Toolbox.com |
|
|
|
|
|
#8 |
|
Alumni
Join Date: Sep 2001
Location: Maui, Hawaii
Posts: 14,109
|
|
|
|
|
|
|
#9 |
|
Senior Member
|
cool, thanks guys.
|
|
|
|
|
|
#10 |
|
Senior Member
|
just read that post that festerhead pointed out and started to get confused. KXRM do i just need to make those 2 changes you listed?
so if in the main server: set PublicServer=Never and in the relay server(s): set PublicServer=Never This will cause the main server not to get listed and all my relays to get listed. In my SAM2 station details I still in list in "public listing" normally right? |
|
|
|
|
|
#11 |
|
Major Dude
Join Date: Feb 2003
Location: ATL, of course.
Posts: 724
|
I've never done this, but I'm guessing you need to set the relay to "Always." This will show your relay, but not your main server (right?)
rg. |
|
|
|
|
|
#12 |
|
Junior Member
|
How to set main server private and relay public
Just use the RIP only function on the main server's .conf file, much easier.Then add the IP's of the relays to your RIP list through the web admin.Blamo private 1 listener main source.
|
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|