phyiscal pfsense trunk to vSwitch esxi
-
Is there a way to trunk traffic from physical interface on pfsense(physical machine) to ESXi vSwitch? This isn't currently working for me and the guides that I'm looking at assume that pfsense is a VM but in my case its not what I'm trying to do. Also vmwares guide to vlan assumes that cisco switch are involed but this is also not what we're trying to do here.
-
@lugwitz said in phyiscal pfsense trunk to vSwitch esxi:
Is there a way to trunk traffic from physical interface on pfsense(physical machine) to ESXi vSwitch?
Hi,
Yes...
Pls. look from the other side...philosophy...
The pfSense does not care what the switch is on the physical interface...
-we use several types of virtual switches in our systems without any problems, - with our pfSense installations
it should be known that in VM these units are virtual
, but their output have to is physical (a non-VM environment requires an exit(?) on a physical port), ergo in ESXi a physical interface must be assigned to the upstream pfSense portsan intermediate Cisco switch is a good idea, not in vain marked
-
@lugwitz
on esxi you need to Set the VLAN ID to 4095. A VLAN ID of 4095 represents all trunked VLANs.
̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
Please do not use chat/PM to ask for help
we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
Don't forget to Upvote with the 👍 button for any post you find to be helpful. -
@kiokoman said in phyiscal pfsense trunk to vSwitch esxi:
on esxi you need to Set the VLAN ID to 4095
@lugwitz " I'm looking at assume that pfsense is a VM but in my .............
if it is only a VLAN
Cats bury it so they can't see it!
(You know what I mean if you have a cat) -
@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̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
Please do not use chat/PM to ask for help
we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
Don't forget to Upvote with the 👍 button for any post you find to be helpful. -
@kiokoman said in phyiscal pfsense trunk to vSwitch esxi:
@daddygo
it does not matter if it's virtual or nottrue, but...
but is that really the question?
not a connecting a pfSense physical interface to a VM switch...pure or cleanlyI 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" wordCats bury it so they can't see it!
(You know what I mean if you have a cat) -
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
̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
Please do not use chat/PM to ask for help
we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
Don't forget to Upvote with the 👍 button for any post you find to be helpful. -
@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 VLANsCats bury it so they can't see it!
(You know what I mean if you have a cat) -
@daddygo
connect a cable from pfSense to the nic of esxi and assign it to a portgroup with vlan id 4095?
̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
Please do not use chat/PM to ask for help
we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
Don't forget to Upvote with the 👍 button for any post you find to be helpful. -
@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.
-
@kiokoman said in phyiscal pfsense trunk to vSwitch esxi:
connect a cable from pfSense to the nic of esxi
I love you bro
-
@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)
-
@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 -
@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
-
@daddygo Sorry, I've made edit to correct grammar. I'm still awaiting up lol
-
@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
-
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.
-
@lugwitz said in phyiscal pfsense trunk to vSwitch esxi:
Here is another thing I've notice
Please, my darling, please. note that
-
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
-
@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
