@Bob-Dig There is some info here: IEEE 802.1Q This shows an Ethernet frame both without and with VLANs. You can see where the tag goes. The size of the payload is what is determined by the MTU. If you run Wireshark you can examine the frames and see the VLAN tags and more.

@ciscokid Sorry, yes, you're right. You have to click with the mouse, or tap on my phrase, as it is a link to another forum post where you are told what to do. You have to create (copy and paste actually) a file. You have to install the pfSense 'cron' package. Etc.

[image: 1723071287440-screenshot-2024-08-07-at-15.53.57-resized.png]

No worries. I don't think anyone would argue that pfSense would benefit from built-in MFA. Unfortunately developer time is limited.

@viragomann @stephenw10 I appreciate you folk working with me on this thread. I think i ironed out all the issues and/or misunderstandings i was having here. Appreciate yall !

Same symptoms? No outbound state at all?

Aha, nice! Yup IPSec in policy mode can grab traffic and make it disappear like that.

@stephenw10 said in pfSense 2.7 crash when adding vnic: Yes I would definitely add it with the VM shutdown. If the PCI location changes, which it can, after the driver has attached that could cause issues like this. Also watch out if adding more NICs takes you to 5 or more. ESXi will reorder the NICs above 4. Yep, this worked fine thank you. My interfaces were slightly renumbered so had to reassign correctly, but otherwise I look to be up and running :) Cheers Eds

@stephenw10 Thanks a bunch for the tips! I fixed it. [image: 1722891637502-aff7692f-5ac3-4379-afe9-3fb52769b07d-image.png]

Yes. And it should just import directly and boot without issue since the 6100 has all interfaces the 4100 does. Steve

Discussion of this is here: https://forum.netgate.com/topic/189472/high-avail-secondary-node-ips-how-to-find-it

Yes, if the IP address exists on the firewall it should allow it. So that includes virtual IPs.

I agree, internal ticket opened.

@stephenw10 Problem solved. ABB wasn't properly terminating the previous connection. As soon as they unblocked the ports and kick me through their internal tools the connection was established again.

@Jsetive said in DHCP not pooling in interface with VLAN: connect the port in access with VLAN 200 and i still facing that issue. Well again - the port connected to pfsense port that is tagging that vlan would have to be setup as trunk (cisco term) where vlans are tagged, and the native vlan is not tagged.. Just connecting a port in access (not tagged) to that port where your tagging 200 wouldn't work - just like connecting your computer that doesn't understand the tag or use the tag wouldn't

@michmoor Solved!! There was another P2 active. So i think i know what happened. Whent he IPsec tunnel was first set up, it was in tunnel mode. Switched over to VTI but the other p2 was still there. Somehow there was a conflict. After deleting the old p2, things are looking good. Leaving this here for future me or anyone else

What bandwidth does it need to pass? Do you plan to run any packages or VPNs? Yes, that is possible. I would say there is always some risk that Windows decides to use those NICs before hyper-v sets them us to pass through. But there are many people doing exactly that. Probably better to ask about it in the Virualisation sub. Steve