Re: [j-nsp] Junos and single IPv6 link-local address per IFL

2019-01-25 Thread Martin T
Hi Charles,

> fe80:0001::::/64 is not valid as a link-local address and I've run 
> into vendors that have issues with such addresses.

Oh, ok. I understand now what you meant. Good to know.


Martin
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Junos and single IPv6 link-local address per IFL

2019-01-24 Thread Anderson, Charles R
On Fri, Jan 25, 2019 at 12:02:55AM +0200, Martin T wrote:
> Hi Charles,
> 
> > Link-Local addresses should be in fe80::/64, not fe80::/10.
> 
> As Eldon already mentioned, then I actually used /64 prefix in my
> examples. However, any address from address block fe80::/10 should be
> fine. The point is, that for some reason, Junos allows to have only
> one link-local address per IFL.

Yes, I see that Junos only allows one link-local.  But I stand by my 
comment--you should not be creating link locals outside of 
fe80:::::/64.  

> root@vmx1# show | compare
> [edit interfaces ge-0/0/9 unit 0 family inet6]
> address fe80::206:aff:fe0e:fffa/64 { ... }
> +   address fe80:1::206:aff:fe0e:fffa/64;

fe80:0001::::/64 is not valid as a link-local address and I've run into 
vendors that have issues with such addresses.  See RFC 4291 Section 2.5.6.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Junos and single IPv6 link-local address per IFL

2019-01-24 Thread Martin T
Hi Charles,

> Link-Local addresses should be in fe80::/64, not fe80::/10.

As Eldon already mentioned, then I actually used /64 prefix in my
examples. However, any address from address block fe80::/10 should be
fine. The point is, that for some reason, Junos allows to have only
one link-local address per IFL.


Martin
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Junos and single IPv6 link-local address per IFL

2019-01-22 Thread Eldon Koyle
He showed fe80::206:aff:fe0e:fffb/64 in his second example with the same
result.

-- 
Eldon

On Tue, Jan 22, 2019, 07:11 Anderson, Charles R  Link-Local addresses should be in fe80::/64, not fe80::/10.  Try
> configuring a second one that meets this criteria, such as:
>
> > +   address fe80::206:aff:fe0e:fffb/64;
>
> On Tue, Jan 22, 2019 at 03:42:43PM +0200, Martin T wrote:
> > Hi,
> >
> > looks like Junos allows to have only a single IPv6 link-local address.
> > For example, here I tested with Junos 18.2R1.9:
> >
> > root@vmx1# show | compare
> > [edit interfaces ge-0/0/9 unit 0 family inet6]
> > address fe80::206:aff:fe0e:fffa/64 { ... }
> > +   address fe80:1::206:aff:fe0e:fffa/64;
> >
> > [edit]
> > root@vmx1# commit check
> > [edit interfaces ge-0/0/9 unit 0 family inet6]
> >   'address fe80:1::206:aff:fe0e:fffa/64'
> >  Link Local address exists
> > error: configuration check-out failed
> >
> > [edit]
> > root@vmx1#
> >
> > ..or:
> >
> > root@vmx1# show | compare
> > [edit interfaces ge-0/0/9 unit 0 family inet6]
> > address fe80::206:aff:fe0e:fffa/64 { ... }
> > +   address fe80::206:aff:fe0e:fffb/64;
> >
> > [edit]
> > root@vmx1# commit check
> > [edit interfaces ge-0/0/9 unit 0 family inet6]
> >   'address fe80::206:aff:fe0e:fffb/64'
> >  Link Local address exists
> > error: configuration check-out failed
> >
> > [edit]
> > root@vmx1#
> >
> > Just out of curiosity, why there is this limitation? For example
> > FreeBSD 11, which Junos 18.2R1.9 is based on, does not have this
> > limitation:
> >
> > root@FreeBSD-11:~ # ifconfig em0 inet6
> > em0: flags=8843 metric 0 mtu
> > 1500
> >
>  options=209b
> > inet6 fe80::fc69:d3ff:feec:7741%em0 prefixlen 64 scopeid 0x1
> > inet6 fe80::fc69:d3ff:feec:7740%em0 prefixlen 64 scopeid 0x1
> > nd6 options=21
> > root@FreeBSD-11:~ #
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Junos and single IPv6 link-local address per IFL

2019-01-22 Thread Anderson, Charles R
Link-Local addresses should be in fe80::/64, not fe80::/10.  Try configuring a 
second one that meets this criteria, such as:

> +   address fe80::206:aff:fe0e:fffb/64;

On Tue, Jan 22, 2019 at 03:42:43PM +0200, Martin T wrote:
> Hi,
> 
> looks like Junos allows to have only a single IPv6 link-local address.
> For example, here I tested with Junos 18.2R1.9:
> 
> root@vmx1# show | compare
> [edit interfaces ge-0/0/9 unit 0 family inet6]
> address fe80::206:aff:fe0e:fffa/64 { ... }
> +   address fe80:1::206:aff:fe0e:fffa/64;
> 
> [edit]
> root@vmx1# commit check
> [edit interfaces ge-0/0/9 unit 0 family inet6]
>   'address fe80:1::206:aff:fe0e:fffa/64'
>  Link Local address exists
> error: configuration check-out failed
> 
> [edit]
> root@vmx1#
> 
> ..or:
> 
> root@vmx1# show | compare
> [edit interfaces ge-0/0/9 unit 0 family inet6]
> address fe80::206:aff:fe0e:fffa/64 { ... }
> +   address fe80::206:aff:fe0e:fffb/64;
> 
> [edit]
> root@vmx1# commit check
> [edit interfaces ge-0/0/9 unit 0 family inet6]
>   'address fe80::206:aff:fe0e:fffb/64'
>  Link Local address exists
> error: configuration check-out failed
> 
> [edit]
> root@vmx1#
> 
> Just out of curiosity, why there is this limitation? For example
> FreeBSD 11, which Junos 18.2R1.9 is based on, does not have this
> limitation:
> 
> root@FreeBSD-11:~ # ifconfig em0 inet6
> em0: flags=8843 metric 0 mtu
> 1500
> 
> options=209b
> inet6 fe80::fc69:d3ff:feec:7741%em0 prefixlen 64 scopeid 0x1
> inet6 fe80::fc69:d3ff:feec:7740%em0 prefixlen 64 scopeid 0x1
> nd6 options=21
> root@FreeBSD-11:~ #
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


[j-nsp] Junos and single IPv6 link-local address per IFL

2019-01-22 Thread Martin T
Hi,

looks like Junos allows to have only a single IPv6 link-local address.
For example, here I tested with Junos 18.2R1.9:

root@vmx1# show | compare
[edit interfaces ge-0/0/9 unit 0 family inet6]
address fe80::206:aff:fe0e:fffa/64 { ... }
+   address fe80:1::206:aff:fe0e:fffa/64;

[edit]
root@vmx1# commit check
[edit interfaces ge-0/0/9 unit 0 family inet6]
  'address fe80:1::206:aff:fe0e:fffa/64'
 Link Local address exists
error: configuration check-out failed

[edit]
root@vmx1#

..or:

root@vmx1# show | compare
[edit interfaces ge-0/0/9 unit 0 family inet6]
address fe80::206:aff:fe0e:fffa/64 { ... }
+   address fe80::206:aff:fe0e:fffb/64;

[edit]
root@vmx1# commit check
[edit interfaces ge-0/0/9 unit 0 family inet6]
  'address fe80::206:aff:fe0e:fffb/64'
 Link Local address exists
error: configuration check-out failed

[edit]
root@vmx1#

Just out of curiosity, why there is this limitation? For example
FreeBSD 11, which Junos 18.2R1.9 is based on, does not have this
limitation:

root@FreeBSD-11:~ # ifconfig em0 inet6
em0: flags=8843 metric 0 mtu
1500

options=209b
inet6 fe80::fc69:d3ff:feec:7741%em0 prefixlen 64 scopeid 0x1
inet6 fe80::fc69:d3ff:feec:7740%em0 prefixlen 64 scopeid 0x1
nd6 options=21
root@FreeBSD-11:~ #


thanks,
Martin
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp