On Wed, Oct 12, 2011 at 11:59:14AM +0400, Tima Maryin wrote:
>
> RIPE NCC was awared about this issue and now reallocate blocks to those
> who got addrs from 128.0.0.0/16
One more update on this topic: RIPE started debogonisation for
128.0.0.0/16, so it looks like this network will be allocated
We have a PSN( PSN-2011-10-393) released for this.
Thanks,
Siva
On Sat, Oct 15, 2011 at 12:42 AM, Nicholas Oas wrote:
> Tima, Siva-
>
> Thank you for bringing this to the attention of the community, and for all
> the updates!
>
> -Nicholas
>
> On Fri, Oct 14, 2011 at 12:18 AM, MSusiva wrote:
>
Hi All,
The PR was opened to alter the default martian table and also the PR is
public now. Even though we have workaround, customer wants the future junos
releases have the updated martian table.
Workaround:
set routing-options martians 128.0.0.0/16 orlonger allow
set routing-options martians 1
*The PR was opened to alter the default martian table and also the PR is
public now. Even though we have workaround, customer wants the future junos
releases have the updated martian table.
Workaround:
set routing-options martians 128.0.0.0/16 orlonger allow
set routing-options martians 191.255.0
Thanks for the update Tima, I'll distribute this internally - thank you.
On Thu, Oct 13, 2011 at 10:17 AM, Tima Maryin wrote:
> On 10.10.2011 17:17, Graham Brown wrote:
>
>> Hello Tima,
>>
>> Thank you for making me aware of this and raising this with JTAC, I am
>> sure that this would be deemed
On 10.10.2011 17:17, Graham Brown wrote:
Hello Tima,
Thank you for making me aware of this and raising this with JTAC, I am
sure that this would be deemed as critical and an easy fix. If you get
allocated a PR, could you please share this with the group so we can
monitor the progress and get a h
On 10.10.2011 16:39, Tima Maryin 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
skip
p.s. set routing-options martians 128.0.0.0/16 orlonger allow
fixes it.
Couple u
On Tuesday, October 11, 2011 03:49:33 AM Paul Stewart wrote:
> 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
That's where I don't hav
On Tuesday, October 11, 2011 04:59:54 AM Vladimir Blazhkun
wrote:
> +1. I guess nobody cares about intersecting address
> spaces in typical BGP L3VPNs, why to discuss router's
> internals then?
See my previous post.
That's why even with l3vpn's in our environment, we still
stick to private add
+1. I guess nobody cares about intersecting address spaces in typical
BGP L3VPNs, why to discuss router's internals then?
Just my .02$.
With best regards,
Vladimir Blazhkun.
On Mon, Oct 10, 2011 at 23:59, Tima Maryin wrote:
> I don't see any problem with it since it's different routing table.
On 10.10.2011 22:43, Jonas Frey (Probe Networks) wrote:
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 b
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
om: Tarique A. Nalkhande - BMC [mailto:t.nalkhande@mobily.com.sa]
Sent: Monday, October 10, 2011 3:44 PM
To: Paul Stewart; 'Daniel Roesen'; juniper-nsp@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
ober, 2011 10:19 PM
To: Tarique A. Nalkhande - BMC; 'Daniel Roesen'; juniper-nsp@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 b
Roesen; juniper-nsp@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 ProtoLocal
So with 128/16 going live, Juniper may also additionally need to change their
internal addressing!
re0> show interfaces em1 terse
Interface Admin Link ProtoLocal Remote
em1 upup
em1.0 upup inet
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>
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) blo
* Tima Maryin [2011-10-10 14:41]:
> Hello!
>
>
> 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
On 10/10/11 23:39, Tima Maryin wrote:
> Hello!
>
>
> 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
> inet.0:
> 128.0.0.0/16 orlonger -- disallowed
It's only the
Hello Tima,
Thank you for making me aware of this and raising this with JTAC, I am sure
that this would be deemed as critical and an easy fix. If you get allocated
a PR, could you please share this with the group so we can monitor the
progress and get a heads up on what releases contain the fix. I
Hello!
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:
> show route martians
inet.0:
0.0.0
22 matches
Mail list logo
