Re: [j-nsp] DHCPv6 client on SRX210 - IPv6 forwarding breaks at lease expiration

On 02/08/15 02:28, Chris Woodfield wrote: TL;DR: IPv6 forwarding breaks when my DHCPv6 client lease expires, even though CLI output claims it’s been renewed. I have an SRX210 as my home gateway, running 12.1X46-D35.1. This is running dual stack to Comcast, receiving a /56 DHCPv6 delegation and

[j-nsp] DHCPv6 client on SRX210 - IPv6 forwarding breaks at lease expiration

TL;DR: IPv6 forwarding breaks when my DHCPv6 client lease expires, even though CLI output claims it’s been renewed. I have an SRX210 as my home gateway, running 12.1X46-D35.1. This is running dual stack to Comcast, receiving a /56 DHCPv6 delegation and RA’ing a /64 to my home LAN. I’ve noticed

Re: [j-nsp] Juniper vMX limitations

Has anyone gotten VMX running on a non-Ubuntu KVM machine (ex. RHEL/CentOS)? -C > On Jul 30, 2015, at 6:11 AM, Chris Adams wrote: > > Once upon a time, Phil Bedard said: >> I’m sure they’ve had it running in VMWare, but it’s a little more difficult >> and you need the Enterprise Plus version

Re: [j-nsp] l2circuit between ASR9k and MX80

On (2015-08-01 12:21 +0200), Marcin Kurek wrote: Hey Marcin, > Thanks for your reply. This is strange, even if it is pushing 3101 again, > there should be two VLAN tags in a frame received by MX - outer 3101 and > inner dummy tag. What dummy tag? Is there [ SVLAN CVLAN ] stack coming to the CSCO

Re: [j-nsp] l2circuit between ASR9k and MX80

Hi Saku, So what happens here is Cisco somehow dynamically determines what is required. In 7600 with this config 3101 _Will be popped_ and _internal VLAN_ will be pushed, before sending it out to MPLS network. But as it works with you, it is probably pushing 3101 again. Magically same con