VLAN's not working with pfSense and HP1810-24G Switch.

[Herman]

Hi Steve-scotter,

Thanks for your reply. I was thinking in that direction as well. The pfSense LAN and WAN port are Hyper-V switches connected to a physical NIC on the Hyper-V (Server 2016) host. De server has two physical nic's on board en a 4 port Intel server NIC interface card. So in total the server has 6 physical nic's on board. In another post I've read some info about some power shell command regarding the Hyper-V nics.

Kind regards,
Herman

[Herman]

Hello,

This is the thread I found regarding some powershell commands were @bobtheninja talks about. Does this make sense?

https://forum.netgate.com/topic/81161/pfsense-hyper-v-vlans/3

Any help appreciated
Herman

[Herman]

Hi Folks,

I tried the following command. Somehow something went wrong.

This is the solution @bobtheninja provides. Any ideas?

Regards Herman

[johnpoz]

I just went over this recently... Let me dig up the thread..

But yes you have to set trunk mode with powershell - not sure why messing with mac addresses? That thread is 2 years old..

BRB
edit: here you go
https://forum.netgate.com/topic/139891/solve-hyperv-2012-vlans-support-hn0/8

I walked through how to do tagged vlans, with pictures ;)

[Herman]

Hi @johnpoz,

Wow. That is a lot of information. I have to dig in there. You were right. I messed up things. Messing around with the mac address was indeed no good idea!!! Now I have to wait till I am home because my whole config isn't accessible anymore :-(

I have to figure out the exact power shell command to do your trick. I have 2 nic's in de pfsense vm. A LAN and WAN. So I presume that I only have to alter the LAN vlan settings right?

For now I am not able to connect to the network anymore! :-( I hope I can reverse the settings i've made...

Cheerz Herman

[Herman]

Hello Johnpoz,

I am back in business again. Was able to reverse my mes sup with the MAC address.

Let me show you what i Have done. That is after the restore :-)

Above you see the 2 virtual network adapters connected to my pfSense. one of them is the LAN and the other would be the WAN. cannot see that here. I think that is the reason why @bobtheninja was using the MAC address part???

Next I executed the following command.

After that evrything stops working. When setting the mode back to Untagged everything is working again.

My HP 1810 switch is configured this way;

Port 1 on the switch that is connected to the pfSense LAN interface is configured as a Trunk port

Any suggestions?

Kind regards Herman

[Herman]

@herman said in VLAN's not working with pfSense and HP1810-24G Switch.:

Hello Johnpoz,

I am back in business again. Was able to reverse my mes sup with the MAC address.

Let me show you what i Have done. That is after the restore :-)

Above you see the 2 virtual network adapters connected to my pfSense. one of them is the LAN and the other would be the WAN. cannot see that here. I think that is the reason why @bobtheninja was using the MAC address part???

Next I executed the following command.

After that evrything stops working. When setting the mode back to Untagged everything is working again.

My HP 1810 switch is configured this way;

Port 1 on the switch that is connected to the pfSense LAN interface is configured as a Trunk port

Any suggestions?

Kind regards Herman

Another screenshot how the interfaces are shown in pfSense;

[johnpoz]

You sure hp uses trunk in the same same with as cisco? WTF is static mode? Where are you tagging specific vlans?

[Pippin]

Yes, there is a difference between HP and Cisco:
https://networkingnerd.net/2011/02/02/when-is-a-trunk-not-a-trunk/

[johnpoz]

^ exactly!!! I thought they were different!

[Pippin]

On the old forum I posted a question few years ago and ran into this terminology problem myself, you where part of it too johnpoz , misunderstanding all around as same here, but cannot find the post...

[johnpoz]

I have not had to touch an HP switch for years and years - and to be honest have no desire to any time soon... But yeah I recall terminology is different that cisco ;)

[Herman]

@johnpoz said in VLAN's not working with pfSense and HP1810-24G Switch.:

You sure hp uses trunk in the same same with as cisco? WTF is static mode? Where are you tagging specific vlans?

When I read the document Pipin provided HP uses tagged ports to carry multiple vlans.

Under mode there are the multiple option;

Gr. Herman

[Herman]

@pippin said in VLAN's not working with pfSense and HP1810-24G Switch.:

On the old forum I posted a question few years ago and ran into this terminology problem myself, you where part of it too johnpoz , misunderstanding all around as same here, but cannot find the post...

Hi Pipin, I really hoping you will ... :-)

It seems that my HP 1810-24G is the pain in the ass here.

Gr. Herman

[Herman]

@johnpoz said in VLAN's not working with pfSense and HP1810-24G Switch.:

I have not had to touch an HP switch for years and years - and to be honest have no desire to any time soon... But yeah I recall terminology is different that cisco ;)

I have the feeling you are not a really big fan of HP switches

You are tending more to Cisco? Is Unify also a good product?

gr. Herman

[johnpoz]

Not that not a fan of them... Just much more experience with Cisco, and the few times I have had to deal with HP.. Not impressed with them compared to the cisco use to working with.

For the price of unifi - you could get a pretty much full featured L3 switch from cisco small business line. The sg300 or sg350 line.. I just saw a sg350-28 on amazon for $179.. Its feature set far exceeds the same sort of price point from unifi.

[Grimson]

@herman said in VLAN's not working with pfSense and HP1810-24G Switch.:

Those are LAGG modes, nothing to do with setting up VLANs.

[Herman]

@grimson said in VLAN's not working with pfSense and HP1810-24G Switch.:

@herman said in VLAN's not working with pfSense and HP1810-24G Switch.:

Those are LAGG modes, nothing to do with setting up VLANs.

Thanks for your reply @Grimson .

Gr. Herman

[johnpoz]

The link pippin gave calls out what you need to do

"In HPvania, the terminology used for a port that carries multiple VLANs is a tagged port. On an HP switch, the individual ports are rarely configured directly. Instead, the VLAN itself is configured and the ports are added to the VLAN configuration. "

[Herman]

Hi Guys,

Believe it or not, but my problem is solved. Thanks to all the expertise of you guys on here I finally get it going. There are still some issues regarding firewall rules but the VLAN part is working! Thanks to everybody who replied to this topic.

For the other users who might have a HP 18010-24G and a Hyper-V virtualized pfSense I write down what the solution is in my case:

1. On the pfsense box create a VLAN10 with ID 10. Assign the interface VLAN10 with the LAN (hn0) interface as parent interface.
2. on the Hyper-V host run in a elevated powershell the folowing line: Get-VMNetworkAdapter -VMName "name of vm" | Where-Object -Property MacAddress -eq "mac address of the LAN interface" | Set-VMNetworkAdapterVlan -Trunk -NativeVlanId 1 -AllowedVlanIdList "10". If you have more interfaces connected to the pfSense box for example LAN and WAN, the mac address will modify the right interface. In this case the LAN interface.
3. on the HP 1810-24G switch set the port that is connected to the LAN port of the pfSense box for both vlan's to Tagged! In this case VLAN1 and VLAN10 need to be marked as Tagged.
4. All the device you want to have in VLAN10 the physical switch port of that device need to be set to Untagged on VLAN 10. VLAN1 should then become Excluded automatically on that port.
5. Last but not least create a VLAN10 firewall rule. Tip. Copy the "Default allow LAN to any" and modify the rule from LAN to VLAN10 there were needed.
6. Voila! In my case all was working now.

In the above explanation I took VLAN10 and the networks 10.0.0.0/24 and 10.0.10.0/24 as example. Feel free to play around with other vlan's and subnets.

Take also a look at the info other members provided. For me it was a big help and learning curve.

Thanks again guys for all the help and patience.

Cheers Herman