I do have a loopback filter on input, but it should be clear (and took it off just to double-check - no change). Even if it had been that, it wouldn't have prevented the outbound packets that I'm not seeing.
Once upon a time, Rolf Hanßen via juniper-nsp <[email protected]> said: > Hello Chris, > > do you have a loopback filter applied that could drop the packets? > > kind regards > Rolf > > On 25/01/2022 20:51, Chris Adams via juniper-nsp wrote: > >I'm trying to add VRRP for IPv6 to a pair of MX150s (that are already > >running VRRP for IPv4). I've switched from VRRPv2 to VRRPv3, and the v4 > >VRRP switched over, but both routers think they are master for the v6 > >side. Looking at "show vrrp interface" on each router, the > >"Advertisement sent" count is increasing, but if I do a "monitor > >traffic", I only see the VRRP packets for the v4 IP. > > > >Config I've set (from first router, second just has a different address > >and priority): > > > >interfaces { > > ae1 { > > unit 101 { > > vlan-id 101; > > family inet6 { > > address <block>::2/64 { > > vrrp-inet6-group 26 { > > virtual-inet6-address <block>::1; > > priority 110; > > no-preempt; > > accept-data; > > } > > } > > } > > } > > } > >} > >protocols { > > router-advertisement { > > interface ae1.101 { > > virtual-router-only; > > } > > } > > vrrp { > > version-3; > > } > >} > > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp -- Chris Adams <[email protected]> _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
