phyiscal pfsense trunk to vSwitch esxi

kiokoman

@daddygo
it does not matter if it's virtual or not, if you want all vlan to pass you need to set the portgroup where pfsense send traffic to 4095

DaddyGo

@kiokoman said in phyiscal pfsense trunk to vSwitch esxi:

@daddygo
it does not matter if it's virtual or not

true, but...
but is that really the question?
not a connecting a pfSense physical interface to a VM switch...pure or cleanly

I quote...
@lugwitz "Is there a way to trunk traffic from physical interface on pfsense(physical machine) to ESXi vSwitch?"

+++edit:
correct me if I misunderstand the OP
don't fool anyone with the "trunk" word

kiokoman

the physical interface of pfsense is always a trunk interface(vlan must be configured on pfsense) , and there is nothing to do there, only the switch or the vswitch can filter or block the vlan traffic

DaddyGo

@kiokoman said in phyiscal pfsense trunk to vSwitch esxi:

the physical interface of pfsense is always a trunk interface

I think the question is how to connect a physical and a virtual interface

of course, the nature of the pfSense interface is what:
therefore, it can be used for segmentation without VLANs

kiokoman

@daddygo
connect a cable from pfSense to the nic of esxi and assign it to a portgroup with vlan id 4095?

lugwitz

@daddygo PF is not a vm. I'd prefer to not have a router as a VM. I'm trying to cut on CPU cycles and other resources if i can just trunk all of it to a physical router.

DaddyGo

@kiokoman said in phyiscal pfsense trunk to vSwitch esxi:

connect a cable from pfSense to the nic of esxi

I love you bro

lugwitz

@kiokoman I've read that, ESXi doesn't seem to take that effect when you make the change. A bug maybe? my build is 6.7.0 Update 1 (Build 10302608)

DaddyGo

@lugwitz said in phyiscal pfsense trunk to vSwitch esxi:

PF is not a vm

that's the point

+++edit:
I'll get out of this, now

DaddyGo

@lugwitz said in phyiscal pfsense trunk to vSwitch esxi:

I'd prefer to not have a router as a VM

it's a smart idea

lugwitz

@daddygo Sorry, I've made edit to correct grammar. I'm still awaiting up lol

DaddyGo

@lugwitz said in phyiscal pfsense trunk to vSwitch esxi:

I'm still awaiting up lol

it's not an ESXi issue or pfSense - it's just networking

lugwitz

@daddygo

Here is another thing I've noticed. I've edit the network to correct port group that the machine show be on but I doesn't change and shows at disconnected. Samething vlan vlan tagging is working but its accepting the wrong network when it receives an IP. I've tried to reboot the Hypervisor but its still doing this. While writing this I think I solve the issue. I've delete vNIC to the VM and re-added it. And I'm seeing my network get re-assigned, connected and receiving the IP it should be getting. This VM was imported but I don't understand why redoing the vNIC need to make the change. It really sound like a bug with ESXi to me.

DaddyGo

@lugwitz said in phyiscal pfsense trunk to vSwitch esxi:

Here is another thing I've notice

Please, my darling, please. note that

lugwitz

I've found the issue. My tagged traffic is not working with pfsense. I don't see that vlans are supported with it.

https://ark.intel.com/content/www/us/en/ark/products/50495/intel-pro-1000-pt-quad-port-low-profile-server-adapter.html

DaddyGo

@lugwitz said in phyiscal pfsense trunk to vSwitch esxi:

I don't see that vlans are supported with it.

it’s hard to imagine, as it is supported in principle by PHY ....(
Intel 82571EB)

but then I found this:

https://social.technet.microsoft.com/Forums/ie/en-US/11584256-b924-4945-a2f4-aefca0c3a43a/intel-1000pro-vlan-not-working-any-idea?forum=winserverhyperv