Kent Borg said: > > It appears that though the kernel naturally wants to send response packets > back from whence they came, there had better be a "route" > thataway before it can.
the kernel will send the response packets out the default gateway. on a typical machine, there is only 1 default gateway, if someone adds a second gateway the 2nd gateway is ignored. Unless the first gateway is deleted then it will be used. so if eth1 is on a 2nd network, and it recieves a packet the response will get sent out eth0, resulting in failure since the source address is incorrect. you can work around this by playing with I think the command is iproute2, to configure the system to send the response packets out the correct interface. one of my former co workers did this on his machine which was multihomed between 2 T1s from different ISPs, and it worked pretty well, I don't know what his exact setup was since he ran 2.4.x and my systems run 2.2.x, his setup was not compatible with my kernel. But it is possible, he did recieve several complaints over the ~6 months or so he had it configured from time to time people thought one or the other interfaces wasn't reachable. I don't think he looked into it much. so in the end, it is possible, but from what I gather from his setup, it was rather complicated and not worth me investigating further for my own use. We both did significant testing using the standard 'route' command to no avail. He of course tested on a hacked up redhat system running 2.4.x and I tested on my debian systems running 2.2.19. So I reccomend against this unless it's REALLY important and your prepared to spend some time learning the iproute documentation. I've never used this command myself. nate -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
