Multiple IP Addresses Hitting One Server

NightAire · 8th January 2006, 20:43

OK, I think I generally have the idea: binding two cards together gives the single machine more bandwidth, and if one card goes down data continues on the other card.

I'm not sure that's really solving the problem I'm having, though... my machine seems plenty stable, it's my connection to the internet that's the problem.

Just to complicate things, what I thought was originally going to be the setup, looks like isn't going to be the setup. Originally I thought I'd just be hosting the encoder here and we'd hit my provider's Shoutcast server. Apparently, though, I'll have the server on my machine locally (like it is currently) and they will simply "relay" the stream. What I DON'T know is how they'll be relaying it... guess I oughta ask.

Here's part of what they said in a recent email to me:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The only way to make your dual connection work in a redundant fasion with shoutcast, that I can think of, would be to use a Windows 2000 Pro, Windows XP Pro or Server 2003 machine with dual NIC's, each obtaining an IP from different ISPs.

For the failover to work properly, you would need to "push" the stream to us, rather than us "pull" or "relay" the stream off of you. Shoutcast "pushes" by default, in otherwords, connects "out" from your end to the server.

When an interface fails, the stream will continue to push out through another interface, seamlessly to us, as the IP of the outgoing stream will not change, regardless of which interface fails. There may be a few seconds of lag as things fail over, but it should be pretty quick.

The problem with setting up servers on multiple IP addresses, is that if something fails, the server on this end would need to be manually reconfigured to "pull" the stream from an alternative IP. There is no automatic way about this, without alot of custom code.

If you want redundancy with two connections, the only way to do so is to "push" the stream to us.

Otherwise if you decide to run your own DNAS and have us relay it, it would require a static IP, and if you had two connections, it would not be redundant.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

8th January 2006, 20:43	#1
NightAire Junior Member Join Date: Jan 2001 Location: Owasso, Oklahoma USA Posts: 20	OK, I think I generally have the idea: binding two cards together gives the single machine more bandwidth, and if one card goes down data continues on the other card. I'm not sure that's really solving the problem I'm having, though... my machine seems plenty stable, it's my connection to the internet that's the problem. Just to complicate things, what I thought was originally going to be the setup, looks like isn't going to be the setup. Originally I thought I'd just be hosting the encoder here and we'd hit my provider's Shoutcast server. Apparently, though, I'll have the server on my machine locally (like it is currently) and they will simply "relay" the stream. What I DON'T know is how they'll be relaying it... guess I oughta ask. Here's part of what they said in a recent email to me: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The only way to make your dual connection work in a redundant fasion with shoutcast, that I can think of, would be to use a Windows 2000 Pro, Windows XP Pro or Server 2003 machine with dual NIC's, each obtaining an IP from different ISPs. For the failover to work properly, you would need to "push" the stream to us, rather than us "pull" or "relay" the stream off of you. Shoutcast "pushes" by default, in otherwords, connects "out" from your end to the server. When an interface fails, the stream will continue to push out through another interface, seamlessly to us, as the IP of the outgoing stream will not change, regardless of which interface fails. There may be a few seconds of lag as things fail over, but it should be pretty quick. The problem with setting up servers on multiple IP addresses, is that if something fails, the server on this end would need to be manually reconfigured to "pull" the stream from an alternative IP. There is no automatic way about this, without alot of custom code. If you want redundancy with two connections, the only way to do so is to "push" the stream to us. Otherwise if you decide to run your own DNAS and have us relay it, it would require a static IP, and if you had two connections, it would not be redundant. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~