From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 14:53:15 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6748F1DE for ; Tue, 10 Mar 2015 14:53:15 +0000 (UTC) Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 387539A2 for ; Tue, 10 Mar 2015 14:53:15 +0000 (UTC) Received: by padet14 with SMTP id et14so2834638pad.0 for ; Tue, 10 Mar 2015 07:53:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5OB4DDNmSf39TeLEjQ3KBYEb54gmvK5bi5tNh8n4ZRU=; b=lhEa2QOzwFF7E+5M1JS3g36QENhLhHe4ea9LnbGRDgHEN28IlkY+sCqdD8LK+gKsqm IX/ToSOz0q0bNHwFXErAalaHeyoOz5ZXc7mzZtnbpymJXVoSz97BYrpJRQ3rAlAo7mLC ksF5YrdKvBpkyyfKPWNrc9OI3zkEOp7TufZuDFUNQPX7Bzwshx276pyxwDVwW3H0oScR MbDyhCHq3mxVBR6oftV0Lscko6D5bx5BLhlbzHBj3yWevbzKxBMQkhVSLwce45hI1Sw1 kBRi6Rn4cPEZy3PpcASLiypdwYanYIXD90r0rb7G7Vv+R80SYYpiGDx9pGq+fpoHmwV0 8o0A== X-Gm-Message-State: ALoCoQnJztL6aP1IQsrUxTgZs7+ycVfwiwMuw+gyD4H5+LkQ0oT6zvWXqT970O5yw8jCKVhZI0Wu X-Received: by 10.70.26.129 with SMTP id l1mr65774697pdg.163.1425999194138; Tue, 10 Mar 2015 07:53:14 -0700 (PDT) Received: from [192.168.1.149] ([118.179.177.178]) by mx.google.com with ESMTPSA id t5sm1402070pdn.58.2015.03.10.07.53.12 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Mar 2015 07:53:13 -0700 (PDT) Message-ID: <54FF0555.9070901@winterei.se> Date: Tue, 10 Mar 2015 23:53:09 +0900 From: "Paul S." User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: FreeBSD responding with wrong receiving interface IP References: <54FE566F.5030607@winterei.se> <54FF0266.3080106@m.jwh.me.uk> In-Reply-To: <54FF0266.3080106@m.jwh.me.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 14:53:15 -0000 Joe, That was it, thank you! I looked over net.inet.ip and ip6, icmp never crossed my mind. George, thank you as well. On 3/10/2015 午後 11:40, Joe Holden wrote: > On 10/03/2015 13:16, George Neville-Neil wrote: >> 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 > > sysctl net.inet.icmp.reply_from_interface=1 will probably do what you > expect. > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"