/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! /* ALSO: Don't quote this header. It makes you look lame :-) */
Jamin W.Collins <[EMAIL PROTECTED]> wrote: > > Silly question, but why are you trying to use a different port on the > second IP? IIRC, since this is a different IP (even though it is > aliased), it has it's own set of ports thus 1720 isn't used on eth0:0. It depends on how the application binds to the listen socket. Most applications bind to the IP address INADDR_ANY, or 0.0.0.0, which causes the application to receive traffic from all interfaces on the machine. If the application indeed binds to 0.0.0.0:1720, then another application would not be permitted to bind the same address, which I assume is why the original poster binds a second port. However, if there is some control over the address that the application binds to, then you are correct, the application could be written so that one instance binds itself to <eth0-IP>:1720, and another instance binds to <eth0:0-IP>:1720, and the two instances would not interfere with each other at all. This is the best solution in this scenario, if available. -- [EMAIL PROTECTED] (Fuzzy Fox) || "Good judgment comes from experience. sometimes known as David DeSimone || Experience comes from bad judgment." _______________________________________________ Masq maillist - [EMAIL PROTECTED] Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES UNSUBSCRIBING! or email to [EMAIL PROTECTED] PLEASE read the HOWTO and search the archives before posting. You can start your search at http://www.indyramp.com/masq/ Please keep general linux/unix/pc/internet questions off the list.
