Date: Mon, 19 Dec 2016 22:01:51 +0100 From: Alarig Le Lay <alarig@swordarmor.fr> To: Eugene Grosbein <eugen@grosbein.net> Cc: freebsd-net@freebsd.org Subject: Re: Avoid using RFC3927 outside of the link Message-ID: <20161219210150.mf4cwx3k33x2qbbe@kaiminus> In-Reply-To: <58583645.3090502@grosbein.net> References: <20161219184617.7yph7isgtgjy4mja@kaiminus> <58582C25.7090806@grosbein.net> <20161219190506.kc32q7sz3okekup7@kaiminus> <58583645.3090502@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--qlo3tw4cmxg455lw Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue Dec 20 02:34:29 2016, Eugene Grosbein wrote: > Well, you can always use brute force instead: >=20 > 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 >=20 > That's ugly but works. I will work just by side effect: by doing this, I will send BGP packets =66rom 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 --=20 alarig --qlo3tw4cmxg455lw Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJYWEq7AAoJEK84SsFrICuI9rIIAIq610fOw3KUonFG+lSBK2Qk bwu/DysUzJXLWc+0KrfDbuAxb0gtYeQSx/DcRBS234jWbruH1eDd8ODE9zirz88s PL8FGNA+kiMazUzPucMN+1flqySrS4UL1mPaL4IsO2C5An5jTAa7TciGD4Wlwan+ GZIJm9W/2UZrdg0RI6BZAtdAuaZwOqKhuWmSjL3IuyJh+ATQh5xyCjDFZIezq7MD 5gljHVJiQzwY9rGvSkvvy02Dux3CNvLLrhV5L07K50vchIf0We1pjkuOT4SQwnw0 lok/b8ny/moQv+TVcCMQHM3hPczArMH3h3K5jBjheZwW2h+YkKKRB09M2q2gVKs= =FfkW -----END PGP SIGNATURE----- --qlo3tw4cmxg455lw--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161219210150.mf4cwx3k33x2qbbe>