On Sat, Apr 27, 2002 at 10:25:24AM +0200, Arthur van Leeuwen wrote: > On Fri, 26 Apr 2002, Adrian Chung wrote: > > > When you add a route that sets a src like: > > > > ip route add table <table> 192.168.1.0/24 src 192.168.1.11 dev eth0 > > > > The "src" doesn't specify the source IP to put in the packet (it's not > > network address translation, like SNAT in iptables), it just specifies > > which local source IP the routing mechanisms should use to determine > > where to route the packet. > > Actually, it is more subtle than that. The 'src' *does* specify the source > IP to put in the packet *if* the packet doesn't have a source IP yet. This > only holds true for packets generated locally. Ah okay, that makes sense... But I think in both our cases the packets were generated locally, so the 'src' flag should have set the source IP. Is it possible for the application (telnet in my case) to explicitly bind to a socket and set it's source IP? That could explain why the rule has no effect since by the time the packet reaches the routing system, it already has a source IP set. -- Adrian Chung (adrian at enfusion-group dot com) http://www.enfusion-group.com/~adrian GPG Fingerprint: C620 C8EA 86BA 79CC 384C E7BE A10C 353B 919D 1A17 [toad.enfusion-group.com] up 34 days, 17:14, 17 users
