>From what I understand of how routing works the table for the other interface is sort of redundant. If the gateway in the table for the first interface matches the gateway in the main table, then I don't see any point. None the less, I decided to humor the idea of creating another table for the first interface, and, as I suspected, it did not fix the problem. To clarify, connections which properly bind to NIC2 will work. For example, apache, which is running on both NICs has no problem handling requests from either NIC. The real issue is that the kernel is not recognizing that the UDP packet is part of a related series of packets coming in on NIC2. So instead it's choosing the ip associated with default route, which is IP1. Obviously this is the way it's suppose to work, since it's just following a simple routing table. I'm just looking for a workaround. ----- Original Message ----- From: Peter Surda <shurdeek@xxxxxxxxxxxx> Date: Thursday, September 9, 2004 3:55 am Subject: Re: UDP routing issues with multiple NICs > On Thu, Sep 09, 2004 at 03:24:20AM -0600, Matthew Lowe wrote: > > Ok, the story is this, I'm running an Unreal Tournament 2004 > server. It's > > running on a system that has two external NICs that are > connected to > > different ISPs. I would like players to be able to connect to > the server > > from either link. My default gateway goes through NIC1. For > traffic through > > NIC2 to work I simply added an extra routing table and rule. The > extra> routing table has the default gateway for NIC2 in it and is > triggered by > > packets that have a source address that matches the IP of NIC2. > You have to have a separate table for either nic. Adding one for > nic2 isn't > enough. Follow the instructions in the LARTC HOWTO. > > > Thanks, > > Matt > Bye, > > Peter Surda (Shurdeek) <shurdeek@xxxxxxxxxxxx>, ICQ 10236103, > +436505122023 > -- > Failure is not an option. It comes bundled with your Microsoft > product._______________________________________________ > LARTC mailing list / LARTC@xxxxxxxxxxxxxxx > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ > _______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
