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