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

[Jonas Frey (Probe Networks)]

To whomever opened a PR about this:

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).
Please add this to the PR so it gets fixed.


re0> show interfaces em1 terse              
Interface               Admin Link Proto    Local                 Remote
em1                     up    up  
em1.0                   up    up   inet     10.0.0.1/8      
                                            10.0.0.4/8      
                                            128.0.0.1/2   <<--  
                                            128.0.0.4/2   <<--

MX96-01_re0> show interfaces em0 terse    
Interface               Admin Link Proto    Local                 Remote
em0                     up    up  
em0.0                   up    up   inet     10.0.0.1/8      
                                            10.0.0.4/8      
                                            128.0.0.1/2    <<-- 
                                            128.0.0.4/2    <<--

re0> show route 128.0.0.0/2 table __juniper_private1__.inet.0 
__juniper_private1__.inet.0: 6 destinations, 10 routes (4 active, 0
holddown, 2 hidden)
+ = Active Route, - = Last Active, * = Both

128.0.0.0/2        *[Direct/0] 31w6d 05:05:46
                    > via em0.0
                    [Direct/0] 31w6d 05:05:46
                    > via em0.0
                    [Direct/0] 31w6d 05:05:46
                    > via em1.0
                    [Direct/0] 31w6d 05:05:46
                    > via em1.0


Am Montag, den 10.10.2011, 16:26 +0200 schrieb Daniel Roesen:
> On Mon, Oct 10, 2011 at 03:23:48PM +0200, Sebastian Wiesinger wrote:
> > > Recently RIPE NCC started to allocate addresses from 128/8 to end
> > > users, example:
> > > 
> > > https://apps.db.ripe.net/whois/lookup/ripe/inetnum/128.0.0.0-128.0.7.255.html
> > > 
> > > Junos software (upto and including 11.1) blocks those address by default:
> > 
> > If you have a case open with JTAC tell them to remove 191.255.0.0/16
> > as well. That block is no longer reserved.
> 
> Same goes for 223.255.255.0/24
> 
> Reference: RFC5735
> 
> Best regards,
> Daniel
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20111010/ac29f17b/attachment.pgp>