[j-nsp] JUNOS and 128.0.0.0 martian (JFYI)

[Tarko Tikan]

hey,

> It has been posted on the amsix mailing list that juniper also needs to
> change internal addressing because of the issue with 128.0.0.0/16 as
> addresses of this space are used internally within JunOS (see below).

It's worse. Example from SRX cluster:

show interfaces terse | match "^(fab|fxp1).*inet"
fab0.0                  up    up   inet     30.17.0.200/24  
fab1.0                  up    up   inet     30.18.0.200/24  
fxp1.0                  up    up   inet     129.16.0.1/2    

Luckily none of the routes in __juniper__private__ tables interferes with transit traffic. Same cannot be said for martians.

-- 
tarko