From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 13:16:37 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B543642F for ; Tue, 10 Mar 2015 13:16:37 +0000 (UTC) Received: from vps.hungerhost.com (vps.hungerhost.com [216.38.53.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8D3B69E7 for ; Tue, 10 Mar 2015 13:16:37 +0000 (UTC) Received: from [101.110.58.226] (port=65002 helo=[10.1.10.186]) by vps.hungerhost.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1YVK1U-0007d1-4R; Tue, 10 Mar 2015 09:16:36 -0400 From: "George Neville-Neil" To: "Paul S." Subject: Re: FreeBSD responding with wrong receiving interface IP Date: Tue, 10 Mar 2015 22:16:24 +0900 Message-ID: In-Reply-To: <54FE566F.5030607@winterei.se> References: <54FE566F.5030607@winterei.se> MIME-Version: 1.0 Content-Type: text/plain; format=flowed Content-Transfer-Encoding: quoted-printable X-Mailer: MailMate (1.9r5066) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - neville-neil.com X-Get-Message-Sender-Via: vps.hungerhost.com: authenticated_id: gnn@neville-neil.com Cc: freebsd-net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2015 13:16:37 -0000 On 10 Mar 2015, at 11:26, Paul S. wrote: > Hi, > > I've been deploying FreeBSD as customer edge routers for customers = > with sites that do not require high throughput (>1g/s). > > Each site has two ISPs (Mostly Telstra + Verizon/Optus), and take full = > routes via OpenBGPd and BIRD. I use next-hop self on all received = > routes. > > The FreeBSD boxes have static routes delegating the announced IP = > blocks to a L3 switch down the road. i.e: route add -net 10.100.1.0/24 = > 10.0.0.1, and then that /24 is originated via BGP to both upstreams. > > Things in general work fine, but I've been receiving reports of 'weird = > traceroute results' from my customers. > > Examples of this would be, > > 1 some.random.isp (...) (...) > 2 gigabitethernet3-3.exi1.melbourne.telstra.net (203.50.77.49) 0.309 = > ms 0.284 ms 0.227 ms > 3 bundle-ether3-100.exi-core10.melbourne.telstra.net (203.50.80.1) = > 1.966 ms 1.675 ms 1.852 ms > 4 bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124) 16.707 = > ms 15.917 ms 16.360 ms > 5 customer-gw.syd.ALTER.net (...) (...) > > This traceroute seems to claim that the packet was received over the = > Verizon gateway, which in reality it was not -- it was received = > directly over the Telstra interface, but my outbound AS-PATH towards = > some.random.isp uses Verizon. > > So FreeBSD replies back with the Verizon address. Another person = > having the same issue (mostly, but on OpenBSD) can be found at = > http://openbsd.7691.n7.nabble.com/BGP-responding-with-wrong-IP-address-= td90264.html > > I would love to know if there's a way to fix this, or if I've missed = > something, or if there's something wrong in the way I set it up. > > Thank you for taking the time to read. I wonder if we could see some routing tables? That might help. Best, George