Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On 11/17/2009 05:31 PM, Jerry Natowitz wrote: > Somewhere in my past I ran into a problem where the outgoing packets=20 > went out one interface, but the incoming packets came in the other=20 > interface. Some process or service did not like this, it required the = > same interface be used for both directions. I don't remember any more = > details. I think it was Solaris rather than Linux, but I'm not certain= =2E > > You might get around the problem by advertising route costs to coax the= =20 > next hop to use the desired IP address for the box. > =20 I understand that. In TCP, you are bound to ports and ip addresses, so outgoing and incoming packets SHOULD all go out and come in via the same interface as the IP address is assigned to the interface. I've had interesting problems with unterminated coax and connecting to multiple subnets on the same physical wire (John Chambers remember Alek :-) --=20 Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org> Boston Linux and Unix PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |