Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 4 Oct 2012 12:12:30 -0400
From:      Dominic Blais <dblais@interplex.ca>
To:        John-Mark Gurney <jmg@funkthat.com>, "Alexander V. Chernikov" <melifaro@freebsd.org>
Cc:        "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Subject:   RE: Default route destination changing without warning follow-up
Message-ID:  <2DE61B0869B7484997BCA012845482C7EBE8E28133@WIN2008.Domnt.abi.ca>
In-Reply-To: <20121004160240.GA1967@funkthat.com>
References:  <2DE61B0869B7484997BCA012845482C7EBE8E280DB@WIN2008.Domnt.abi.ca> <5068AC17.8020704@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE8E280DC@WIN2008.Domnt.abi.ca> <5068ADCC.5030105@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE8E280DD@WIN2008.Domnt.abi.ca> <5068B48E.2070303@FreeBSD.org> <20121004160240.GA1967@funkthat.com>

next in thread | previous in thread | raw e-mail | index | archive | help
There's never 2 default route... it's always a single default route. Since =
route monitor shows nothing, I guess it's the same route that gets its gate=
way changed for some reason... I guess the effective and appearing change c=
ould be due to a pointer changing somewhere or the memory space where is lo=
cated the default gateway is replaced with new stuff... I don't know how it=
's coded but it looks like that kind of stuff since nothing is triggered on=
 the route monitor radar...

The default route always exists and there's no trace of it deleted prior to=
 what my script does so we may be quite sure it's the same route that's bru=
talized ;)

Since mpd creates new interfaces for each new connection I see some route b=
eing added/replaced from time to time. I first thought it was mpd's fault b=
ecause it was the only thing playing with routes but Krzysztof Barcikowski =
doesn't use MPD and shares the use of IPFW and PF like me and has the same =
default route gateway changing behaviour...


--



-----Message d'origine-----
De=A0: John-Mark Gurney [mailto:jmg@funkthat.com]=20
Envoy=E9=A0: 4 octobre 2012 12:03
=C0=A0: Alexander V. Chernikov
Cc=A0: Dominic Blais; freebsd-net@freebsd.org
Objet=A0: Re: Default route destination changing without warning follow-up

Alexander V. Chernikov wrote this message on Mon, Oct 01, 2012 at 01:07 +04=
00:
> On 01.10.2012 00:59, Dominic Blais wrote:
> >It's all about IPv4 in my case.
>=20
> It will be great to supply some more details (e.g. like FreeBSD=20
> version, interfaces configuration, netstat -rn output).
>=20
> How often does this happen ?
> (e.g. while true; do echo -n `date` ; route -n get default | grep=20
> gate; sleep 1; done can help)
>=20
> If this is reproducible, what actions precedes this change?
> Maybe some ARP traffic on that interface, or interface=20
> creation/deletion, or.. ?
>=20
> Is route monitor completely silent when the change happens?

Just for refernece, Dominic brought this up in an earlier thread:
http://www.freebsd.org/cgi/mid.cgi?2DE61B0869B7484997BCA012845482C7EBE62DDD=
88@WIN2008.Domnt.abi.ca

and at least on other person seems to have the same issue...

quick question for you Dominic, do you see the correct number of routes, bu=
t a new wrong one appear?  or does the route just simply disapear? or does =
a new one seem to replace the old one?

The reason I ask is that if a new wrong one appears, it could be memory cor=
ruption, but if a new one replaces the old one, for some reason when alloca=
ting a new route, it could accidentatlly be replacing the default route...

Just some thoughts...

--=20
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2DE61B0869B7484997BCA012845482C7EBE8E28133>