From owner-freebsd-net@FreeBSD.ORG Mon Jun 17 19:26:21 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8C64DA3D; Mon, 17 Jun 2013 19:26:21 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from plsvl-mailgw-02.bluecoat.com (plsvl-mailgw-02.bluecoat.com [199.91.133.12]) by mx1.freebsd.org (Postfix) with ESMTP id 6A0D91A75; Mon, 17 Jun 2013 19:26:21 +0000 (UTC) Received: from pwsvl-exchts-03.internal.cacheflow.com (pwsvl-exchts-03.bluecoat.com [10.2.2.160]) by plsvl-mailgw-02.bluecoat.com (Postfix) with ESMTP id A657420591; Mon, 17 Jun 2013 12:18:26 -0700 (PDT) Received: from PWSVL-EXCHTS-06.internal.cacheflow.com (10.2.2.166) by pwsvl-exchts-03.internal.cacheflow.com (10.2.2.160) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 17 Jun 2013 12:18:26 -0700 Received: from PWSVL-EXCMBX-02.internal.cacheflow.com ([fe80::81ba:dd3c:2f44:2eff]) by pwsvl-exchts-06.internal.cacheflow.com ([fe80::8554:761:8def:a2e1%12]) with mapi id 14.03.0123.003; Mon, 17 Jun 2013 12:18:26 -0700 From: "Li, Qing" To: Mack Nagashima , "freebsd-net@freebsd.org" Subject: RE: Some routes no longer getting flagged with 'GATEWAY' in fbsd >=8 Thread-Topic: Some routes no longer getting flagged with 'GATEWAY' in fbsd >=8 Thread-Index: AQHOa4uIH4lG6JKH1U+cypzkUhXiMJk6RqPB Date: Mon, 17 Jun 2013 19:18:25 +0000 Message-ID: References: <51BF591D.1050301@mackn.org> In-Reply-To: <51BF591D.1050301@mackn.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [199.91.133.85] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "qingli@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jun 2013 19:26:21 -0000 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 according=0A= to RTM_GET.=0A= in fbsd8+ the same would yield a route with without the GATEWAY flag.= =0A= =0A= However the RTM_ADD for the 'route add' comes in with =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=