On Tue, Jan 22, 2013 at 07:54:25PM -0300, Roberto Scattini wrote: > ~# route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > XX.220.XX.176 0.0.0.0 255.255.255.255 UH 0 0 0 eth3 > YY.20.YY.0 0.0.0.0 255.255.255.255 UH 0 0 0 eth4 > XX.220.XX.176 0.0.0.0 255.255.255.252 U 0 0 0 eth3 > 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 > YY.20.YY.0 0.0.0.0 255.255.255.0 U 0 0 0 eth4 > 0.0.0.0 XX.220.XX.177 0.0.0.0 UG 0 0 0 eth3 I just noticed here, that your YY traffic is being routed over your default gateway, that should probably have a next hop specific to that network. You also probably want to remove the YY.20.YY.0 host route. This might not solve the whole problem, but it will get some of it out of the way. Cheers, Tom -- Fess: Well, you must admit there is something innately humorous about a man chasing an invention of his own halfway across the galaxy. Rod: Oh yeah, it's a million yuks, sure. But after all, isn't that the basic difference between robots and humans? Fess: What, the ability to form imaginary constructs? Rod: No, the ability to get hung up on them. -- Christopher Stasheff, "The Warlock in Spite of Himself"
Attachment:
signature.asc
Description: Digital signature