On Thu, Jul 12, 2007 at 11:21:53PM +0200, Frank van Maarseveen wrote: > On Thu, Jul 12, 2007 at 10:51:55PM +0200, Bernd Eckenfels wrote: > > In article <20070712163603.GA12582@janus> you wrote: > > > a TCP connection is created originating from 172.17.2.93 instead of > > > from 172.17.1.48 > > > > Well, this might be because you get a "magical" interface self route, check > > for example "route -Cn". > > After some playing I see these: > > Source Destination Gateway Flags Metric Ref Use Iface > 172.17.1.48 172.17.255.255 172.17.255.255 bl 0 0 4 eth0 > 172.17.1.48 172.17.255.255 172.17.255.255 bl 0 0 0 eth0 > 172.17.1.48 172.17.1.48 172.17.1.48 l 0 0 7 lo > 172.17.1.48 172.17.1.48 172.17.1.48 l 0 0 3 lo > > 172.17.2.93 172.17.2.93 172.17.2.93 l 0 0 3 lo > 172.17.2.93 172.17.2.93 172.17.2.93 l 0 0 1 lo But I think this is a symptom rather than the cause. It is from a cache after all. I tried flushing routes + adding various src= routes to both devices but the problem persists: apparently the src= is ignored for traffic to a secondary IP address of the same box. -- Frank - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
