Avoid using RFC3927 outside of the link

[Alarig Le Lay]

Hi,

I have a router that is mutli-homed with BGP. One of my peers is using
an RFC3927 address for the connection. If I traceroute to host behind
that route where we use a route via this peer to reply, the ICMP reply
display that link-local IP:

  1. AS12876 195-154-86-1.rev.poneytelecom.eu (195.154.86.1)     0.0%    10    0.9   0.8   0.6   1.1   0.0
  2. AS12876 a9k2-49e-s46-3.dc3.poneytelecom.eu (195.154.1.86)   0.0%    10    0.8   1.1   0.7   2.2   0.5
  3. AS12876 pni-th2-a9k2.th2.poneytelecom.eu (195.154.1.75)     0.0%    10    1.2   1.5   1.1   3.5   0.6
  4. AS???   equinix-th2.quantic-telecom.net (195.42.144.192)    0.0%    10    1.1   1.0   0.9   1.2   0.0
  5. AS198507185.132.75.33                                       0.0%    10    7.3   7.4   7.2   7.9   0.0
  6. AS???   169.254.1.2                                         0.0%    10    7.6   7.6   7.4   7.9   0.0
  7. AS204092kaiminus.swordarmor.fr (89.234.186.26)              0.0%    10    8.1  11.4   7.8  41.5  10.6

Is it possible to avoid this behaviour and reply with the public IP
(89.234.186.1) instead? What I am looking for is an equivalent of `ip
addr change 169.254.1.2/30 scope link` on Linux.

Thanks,
-- 
alarig
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-net/attachments/20161219/2f7ddde6/attachment.sig>