OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: 3.7: weird IP address problem

From: Otto Moerbeek (ottodrijf.net)
Date: Tue Apr 25 2006 - 05:25:26 CDT


On Tue, 25 Apr 2006, Toni Mueller wrote:

> Hello Otto,
>
> On Tue, 25.04.2006 at 10:46:37 +0200, Otto Moerbeek <ottodrijf.net> 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.

        -Otto