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

[Paul Stewart]

I'm not disagreeing with that at all ... just seemed implied somewhere that
this could have operational impact and I was questioning why/how?

As the private intercommunication within a Juniper box is in a private
table, I don't believe it should be viewed as "public vs private" as that IP
addressing can never been reached publicly anyways .... but as it does
belong to a "routing table" I can see a strong need to follow standards
based IP assignments instead of arbitrarily picking an IP range ....  

Best regards,

Paul




-----Original Message-----
From: Tarique A. Nalkhande - BMC [mailto:t.nalkhande.bmc at mobily.com.sa] 
Sent: Monday, October 10, 2011 3:44 PM
To: Paul Stewart; 'Daniel Roesen'; juniper-nsp at puck.nether.net
Subject: RE: [j-nsp] JUNOS and 128.0.0.0 martian (JFYI)

Keeping away technical constrains (needs to be evaluated, if any); in a
simple way, why would one want to use Public IP range for its Internal
addressing ?? 

Thanks & Regards
Tarique Abbas Nalkhande



-----Original Message-----
From: Paul Stewart [mailto:paul at paulstewart.org]
Sent: 10 October, 2011 10:19 PM
To: Tarique A. Nalkhande - BMC; 'Daniel Roesen'; juniper-nsp at puck.nether.net
Subject: RE: [j-nsp] JUNOS and 128.0.0.0 martian (JFYI)

Pardon me for asking this...

But those routes are in "private tables"... does this really mean that
Juniper is going to block the traffic when it doesn't seen it in inet.0 ?
If it does actually block it (meaning someone has proven this out) then
that's kinda scary...

Apologies if I missed something earlier in a thread and my questions were
already answered...;)

Paul


-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Tarique A.
Nalkhande - BMC
Sent: Monday, October 10, 2011 2:19 PM
To: Daniel Roesen; juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] JUNOS and 128.0.0.0 martian (JFYI)


So with 128/16 going live, Juniper may also additionally need to change
their internal addressing! 

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

Thanks & Regards
Tarique Abbas Nalkhande

This message (including any attachments) is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is non-public, proprietary, privileged, confidential, and exempt from
disclosure under applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified that any use,
dissemination, distribution, or copying of this communication is strictly
prohibited. If you have received this communication in error, notify us
immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this message
immediately if this is an electronic communication.

Thank you.

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


This message (including any attachments) is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is non-public, proprietary, privileged, confidential, and exempt from
disclosure under applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified that any use,
dissemination, distribution, or copying of this communication is strictly
prohibited. If you have received this communication in error, notify us
immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this message
immediately if this is an electronic communication.

Thank you.