On Tue, Apr 25, 2006 at 12:25:26PM +0200, Otto Moerbeek wrote: > On Tue, 25 Apr 2006, Toni Mueller wrote: > > > Hello Otto, > > > > On Tue, 25.04.2006 at 10:46:37 +0200, Otto Moerbeek <[EMAIL PROTECTED]> > > wrote: > > > Does it work when you force the source address to the desired address? > > > With ping, use -I address, with ssh use -b address. > > > > yes, it does work when I specify the correct address with ping, but > > doesn't when I don't specify an address. > > > > > 3.7 contains some route caching that might play a role. Forcing a > > > source address might have the effect of clearing that cache. > > > > Nope. I did it in this sequence: > > > > 1. ping with forced source address -> success > > 2. ping without forced source address -> failure > > > > Some important programs don't have an option to specify a source > > address... > > Indeed, I looked up what changed and that was a case of caching a > route used with forwarding, which does not apply here. > > > > > > Also, double check the routing table with route -n show, to rule out > > > wrong reverse lookups and remaining route entries for the old address. > > > > I always use -n because I don't have DNS on that network anyway, and it > > goes faster, and is more true, too. > > > > The routing table does not show any appearance of the wrong address, > > only some mac addresses for hosts, and some "link#n" entries for > > directly attached networks. > > I'm out of suggestions. >
Upgrade from 3.7 to 3.9. It may be fixed in 3.9 (I remember stuff that was fixed where packets where sent out with the wrong source address if you had more than one network configured (alias with a different network than the main address)). -- :wq Claudio
