I don't think MTU would be the issue. If the endpoint has a 1500 byte
MTU then it will send IP packets up to 1500 bytes long. IPv6 header is
a little longer, but that means the data portion will just have to be a
little shorter. So if you had an MTU issue with v6 you'd have an MTU
issue with v4 also.
On 2/14/2021 5:27 PM, Steve Jones wrote:
The ip6 traffic is encapsulated in the vlan? Ip6 headers I'm assuming
are larger because the number itself is longer, mtu. But I'm just now
learning to use vlans and I lick the tasty windows so I dont know a lot
On Sun, Feb 14, 2021, 3:00 PM Adam Moffett <dmmoff...@gmail.com
<mailto:dmmoff...@gmail.com>> wrote:
Unless you've defined it as a protocol based VLAN then no it
shouldn't
matter.
On 2/14/2021 3:12 PM, Nate Burke wrote:
> I have a P2P circuit plugged into a CRS317-1G-16S+ and setting
> PVID3000 on that bridge interface. A Mikrotik CCR1009 is plugged
> into another port on the CRS317 set for trunked VLan3000. I can
move
> IPv4 traffic on Vlan3000 and to the other end of the P2P circuit
just
> fine, but I cannot move any IPv6 traffic on Vlan3000.
>
> The Vlan shouldn't care about IP4 vs IP6 traffic, right? I just
want
> to make sure I'm not causing my own problem before pointing my
finger
> at the Circuit.
>
> The IPv6 package is not installed on the CRS317, because it's just
> acting as a switch, it's not doing any routing. That shouldn't
> matter, right?
>
--
AF mailing list
AF@af.afmug.com <mailto:AF@af.afmug.com>
http://af.afmug.com/mailman/listinfo/af_af.afmug.com
<http://af.afmug.com/mailman/listinfo/af_af.afmug.com>
--
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com
