Date: Mon, 17 Jun 2013 13:37:36 -0700 From: Brian Somers <brian@FreeBSD.org> To: "Li, Qing" <qing.li@bluecoat.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, Mack Nagashima <freebsd@mackn.org>, "qingli@freebsd.org" <qingli@freebsd.org> Subject: Re: Some routes no longer getting flagged with 'GATEWAY' in fbsd >=8 Message-ID: <5CD9527C-6B2E-42D9-A3F6-788522F6E14A@FreeBSD.org> In-Reply-To: <B143A8975061C446AD5E29742C53172335FF7AB4@PWSVL-EXCMBX-02.internal.cacheflow.com> References: <51BF591D.1050301@mackn.org> <B143A8975061C446AD5E29742C53172335FF7AB4@PWSVL-EXCMBX-02.internal.cacheflow.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Also relevant is this patch....
http://patchwork.diac24.net/patch/494/mbox/
I guess it seems like more of a workaround than a fix though.
On Jun 17, 2013, at 12:18 PM, "Li, Qing" <qing.li@bluecoat.com> wrote:
> Hi,
>=20
> I tried to keep the route messages to be legacy compatible due to =
reported=20
> breakage at the time. Let me revisit the code and get back to you.
>=20
> I haven't run the quagga code for years, so please don't mind me =
request
> some information from you offline.
>=20
> --Qing
>=20
>=20
> ________________________________________
> From: owner-freebsd-net@freebsd.org [owner-freebsd-net@freebsd.org] on =
behalf of Mack Nagashima [freebsd@mackn.org]
> Sent: Monday, June 17, 2013 11:44 AM
> To: freebsd-net@freebsd.org
> Subject: Some routes no longer getting flagged with 'GATEWAY' in fbsd =
>=3D8
>=20
> we're in the process of upgrading from fbsd 7 to 9 and noticed a =
change
> in behavior that might be problematic for us.
>=20
> We use quagga to establish bgp sessions with a router. We have it set
> to redistribute kernel routes.
> Zebra seems to drop anything that doesn't have the 'GATEWAY' flag set =
on
> a route.
>=20
> Prior to fbsd8 this wasn't a problem. Doing something like the
> following worked fine in fbsd7:
>=20
> ifconfig em0 inet 192.168.100.1/24
> ifconfig lo0 inet 192.168.100.100/24 alias
> route add -nostatic 192.168.100.100/32 192.168.100.1
>=20
> in fbsd7 this would yield a route with the flags <UP,GATEWAY> =
according
> to RTM_GET.
> in fbsd8+ the same would yield a route with <UP> without the GATEWAY =
flag.
>=20
> However the RTM_ADD for the 'route add' comes in with =
<UP,GATEWAY,DONE>
> on fbsd8+ so quagga does add if it's up before the route gets added =
but
> starting quagga after the route is added ignores it since it's missing
> the GATEWAY flag once in the routing table. (route delete also fails =
to
> propagate to quagga since the GATEWAY flag is missing)
>=20
> I assume this is all due to the networking overhaul in fbsd8 and =
perhaps
> it no longer flags any route who's gateway is bound to ANY interface =
on
> the box as a gateway.
>=20
> So the ultimate question is.. is there a way to get the legacy =
behavior
> and get them flagged with GATEWAY so zebra will see them or a better
> solution with the way networking now works... (i noticed that issuing =
a
> 'route change' of an existing route with the GATEWAY flag set seems to
> work as it doesn't drop the flag when the gateway changes under it...)
>=20
> Thanks in advance!
>=20
> -mackn
>=20
--
Brian Somers =
<brian@Awfulhak.org>
Don't _EVER_ lose your sense of humour ! =
<brian@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5CD9527C-6B2E-42D9-A3F6-788522F6E14A>