Virtualization problem between Pfsense and switch manageable

Mediane

Hi,

Software :
VMware worksation 11
PfSense version 2.1.5 Release

Hardware :
two specifics network card EXP19301XTBLK (Bridge with VMware)
Switch HP ProCurve J9028B manageable

Setup :
WAN -le1 /dhcp
LAN -le0 /192.168.1.1/24

VLAN2 - le0 / 192.168.2.1 /24
VLAN3 - le0 / 192.168.3.1 /24
VLAN4 - le0 / 192.168.4.1 /24
VLAN5 - le0 / 192.168.5.1 /24

VLAN does not work at all. I've LAN on 192.168.1.1 and WAN works fine.

Any computer that are on the ports of the switch that are automatically set to 192.168.1.1.
In order to clarify the set up, LAN from PfSense is connected to the manageable switch. From Switch, I can get 4 VLANs (VLAN1 to VLAN4) and computers are connected on the ports of the switch. But I've 192.168.1.1 with all outputs from manageable switch. So, the switch did not get any information VLAN configuration from PfSense. Maybe problem is about virtualization with VMware but I do not know…

I want to clarify that it is a migration so I have a fully functional server PfSense as I am just after virtualizing, so I installed a new PfSense then import most of the settings and recreate the map settings WAN / LAN / VLAN ... then I end up with this problem ...
I've a specific computer with PfSense without virtualization to test PfSense with the switch. The set up works fine. I want to virtualize this on my server with VMware. So I installed PfSense with VMware, apply same configurations and import parameters for WAN/LAN/VLAN. Switch did not reveive any information about configuration from PfSense, so what's wrong between PfSense and VMWare ?

I want to clarify that I build a smaller network to test vlan then nothing changes, same addresses for all VLANs. Definitely, there's a problem between VMWare and PfSense, and I can not find a way to resolve that issue.

Thank you for your help.

johnpoz

And what did you set on the vswitch

0 is untagged, 4095 would be like trunk mode and enable tags

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004074

Mediane

Thanks for your answer, but I don't use a virtual manageable switch, I've a physical one.

So I bridged a physical network card for WAN, virtualize PfSense, bridged a network card for my physical manageable switch. PfSense is not able to configure this manageable switch via VMware. So I'm looking to find a way to resolve that issue.

Right now, I've a physical computer with PfSense and all things work fine, but I need to virtualize PfSense with VMware.

johnpoz

"but I don't use a virtual manageable switch"

Yeah you do.. You stated you have vmware, I read it as esxi vs workstation - my bad. Because normally this sort of thing would be done with esxi.

You have a vswitch/port group to connect to the physical nic once you use virtualization from vmware. To be honest I don't think workstation supports tagging of vlans. You would need to use esxi to do what you want with vlans unless you had more physical nics in the box so you could use physical separation for your segments.

pan_2

Make sure what switch port, to which pfsense LAN interface is connected, is in a trunk mode and have all needed VLANs set on it.
Other ports (to which other computers are connected) should be in "access" mode and in one specific VLAN (port can't be in access mode and be in multiple VLANs).

Refer to HP documentation on how to do that.