IPv6 Question

johnpoz

This is a curious situation you have discovered!

For sure... there has to be a piece of the puzzle we are missing. Since it makes zero sense that untagged traffic coming into 3/20 on his switch could somehow make it to pfsense tagged vlan 11. When clearly on his port connected to ix0 on pfsense also shows untagged as 1..

From his 2 switch port configs, the untagged or native vlan is clearly shown as vlan 1

Is there any other ports connected to this server.. That could somehow put untagged traffic on vlan 11 on the switch?

johnnybinator

@johnpoz Not that I'm aware of.

stephenw10

It's the fact you have two way traffic that is most confusing. It's relatively common to see something incorrectly stripping tags. Some misbehaving switch or hardware offloading on a NIC for example. But that would only ever expose an untagged host to traffic that should be on a VLAN. It would not re-tag it the other way.
You could try running packet captures on the interfaces in question to see if that traffic is in fact tagged or untagged as expected.

Steve

johnnybinator

@stephenw10 I will do some testing later. I cannot do it now.

johnnybinator

@johnnybinator Actually I was able to spin up a VM & everything now works as intended. I appreciate you sticking with me and helping to eliminate possibilities.

johnpoz

@johnnybinator said in IPv6 Question:

I was able to spin up a VM & everything now works as intended

huh.. Dude you can not leave us hanging like that ;) There has to be a actual reason, so before the vm was tagging the traffic that you didn't think it should be tagging?

johnnybinator

@johnpoz I guess I could put the switch back the way it was and see if that makes things go back to what was happening. This is at him and I'm working. Kind of a hectic week. When originally posted this, I thought someone was going to just say "yeah, just click here, etc..."

stephenw10

The change you made though was to remove the IPv6 IP from the switch?

johnnybinator

@stephenw10 The change was ipv6 addres on vlan 11, which is where the switch's IPv4 is, instead of VLAN 1 which is where the IPv6 address assignment went when I put it in via the GUI, which doesn't give you a choice of interface.

stephenw10

So assigning it in the switch sing the CLI you were able to put it on VLAN11 and everything started working as expected? That's some interesting behaviour.

johnnybinator

@stephenw10 Yes, exactly. These are not the highest-end switches I've ever worked with. I went for silence, remember?

stephenw10

Mmm, fun*. I'll have to watch out for that.