From owner-freebsd-net@freebsd.org  Tue Dec 20 01:16:09 2016
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A04FC87C67
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Tue, 20 Dec 2016 01:16:09 +0000 (UTC)
 (envelope-from mail@m.jwh.me.uk)
Received: from mail.zorins.co.uk (mail.zorins.co.uk [91.121.236.227])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 17BBC1FE7
 for <freebsd-net@freebsd.org>; Tue, 20 Dec 2016 01:16:08 +0000 (UTC)
 (envelope-from mail@m.jwh.me.uk)
Received: from [172.21.88.190]
 (cpc82705-staf9-2-0-cust342.3-1.cable.virginm.net [81.108.23.87])
 (Authenticated sender: mail@m.jwh.me.uk)
 by mail.zorins.co.uk (Postfix) with ESMTPA id 3tjK3h5MfVz4Kfd
 for <freebsd-net@freebsd.org>; Tue, 20 Dec 2016 00:51:28 +0000 (UTC)
Subject: Re: Avoid using RFC3927 outside of the link
To: freebsd-net@freebsd.org
References: <20161219184617.7yph7isgtgjy4mja@kaiminus>
 <58582C25.7090806@grosbein.net> <20161219190506.kc32q7sz3okekup7@kaiminus>
 <58583645.3090502@grosbein.net> <20161219210150.mf4cwx3k33x2qbbe@kaiminus>
From: Joe Holden <mail@m.jwh.me.uk>
Message-ID: <eb570498-d8a3-27d5-9fac-369d3902187a@m.jwh.me.uk>
Date: Tue, 20 Dec 2016 01:10:29 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <20161219210150.mf4cwx3k33x2qbbe@kaiminus>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Dec 2016 01:16:09 -0000

On 19/12/2016 21:01, Alarig Le Lay wrote:
> On Tue Dec 20 02:34:29 2016, Eugene Grosbein wrote:
>> Well, you can always use brute force instead:
>>
>> ipfw nat 169 config reset ip 89.234.186.1 && \
>> ipfw add 60 nat 169 ip from 169.254.0.0/16 to any out xmit igb0
>>
>> That's ugly but works.
>
> I will work just by side effect: by doing this, I will send BGP packets
> from 89.234.186.1, which is an IP than the peer learned by BGP. This will
> create a recursive loop, and the session will be shut. So, no more
> traffic will transit through this interface, and this IP will not be
> displayed anymore :p
>
Use valid addressing and optionally, working config, there is no problem 
here.