I'm running 2.4.3 - Latest Stable Version (Community Edition) at time of this post - and it took me over 3 weeks to get VLANs to work on my test network (real hardware, nothing virtualized). In desperation, I decided to use a separate ethernet port (read: physical cable into different NIC) for the VLAN and just like magic, everything worked. At work, I spent 2 days straight trying to get VLANs to work after I getting it to work on my test network. I disabled the OPT1 ethernet port (2nd LAN) and had configured my VLANs from that. Again, out of desperation, I deleted the OPT1 ethernet port in the Interface configurations and again, just like magic everything worked. The moral of the story: LAN and VLAN coming from the same cable to the switch does not work properly.
psychotic memories It sounds like you are configuring the vlan correctly in pfSense, but the switch port may not be setup correctly. You should be able to pass untagged traffic along with any number of vlans on the same port and NIC. Also, the switch must be able to have the vlan tags programmed in order to recognize the tagged traffic.
Greg Gorrell Awesome. What hardware? It's definitely doable without performance issues, as long as the other traffic from VMs isn't saturating the NICs. There can also be certain security implications of the firewall running on the same physical hardware as your VMs. Thanks for watching.
Can you show how to share or relay SSDP (simple service discovery protocol) across VLANs in pfSense? I want to allow my guest wifi vlan to cast to my roku in my home vlan. I have the firewall setup where I can enter the roku IP into the roku app on my phone while on guest wifi and it works, but Avahi doesnt seem to reflect the SSDP messages and the Roku is never discoverable in the UA-cam app. [Also, as many others have mentioned, your videos would greatly befefit from having an outline created before recording.]
Connect the network interface ports from the server to the network switches. I will make a quick video to demonstrate this shortly. Thanks for watching.
Why every lab setup uses 10.0.0.0 network. Like.. to look cool? Or... they really have potentially so much devices to manage which they will use pfSense?
In our area region, using a 10.0.0.0/x is the most common in corporate/office environments. 192.168.0.0/x is typically used at home. Thanks for watching!
Thanks sir, you helped me today!
I'm running 2.4.3 - Latest Stable Version (Community Edition) at time of this post - and it took me over 3 weeks to get VLANs to work on my test network (real hardware, nothing virtualized). In desperation, I decided to use a separate ethernet port (read: physical cable into different NIC) for the VLAN and just like magic, everything worked.
At work, I spent 2 days straight trying to get VLANs to work after I getting it to work on my test network. I disabled the OPT1 ethernet port (2nd LAN) and had configured my VLANs from that. Again, out of desperation, I deleted the OPT1 ethernet port in the Interface configurations and again, just like magic everything worked.
The moral of the story: LAN and VLAN coming from the same cable to the switch does not work properly.
psychotic memories It sounds like you are configuring the vlan correctly in pfSense, but the switch port may not be setup correctly. You should be able to pass untagged traffic along with any number of vlans on the same port and NIC.
Also, the switch must be able to have the vlan tags programmed in order to recognize the tagged traffic.
I've been running pfsense as a VM for over a year now with no issues at all with speed or reliability.
Greg Gorrell Awesome. What hardware? It's definitely doable without performance issues, as long as the other traffic from VMs isn't saturating the NICs. There can also be certain security implications of the firewall running on the same physical hardware as your VMs. Thanks for watching.
can you have multiple interfaces on the lan network?. im trying to do it with setting up a bridge, the attaching that to lan. is that correct?
Can you show how to share or relay SSDP (simple service discovery protocol) across VLANs in pfSense? I want to allow my guest wifi vlan to cast to my roku in my home vlan. I have the firewall setup where I can enter the roku IP into the roku app on my phone while on guest wifi and it works, but Avahi doesnt seem to reflect the SSDP messages and the Roku is never discoverable in the UA-cam app.
[Also, as many others have mentioned, your videos would greatly befefit from having an outline created before recording.]
Thanks! Really good explanation! :)
Max you’re welcome!
how do you connect the host to these VLANs?
Connect the network interface ports from the server to the network switches. I will make a quick video to demonstrate this shortly. Thanks for watching.
Check this out, I think it will answer your question: ua-cam.com/video/YhovEmL_8VU/v-deo.html
Thanks! I'll check it later. Your videos are very helpful.
Great video! I'm still a little confused about tagging. I understand the concept of VLAN's but when to tag is the question. New subscriber. Thanks.
notta3d Thanks for watching and glad to have you as a subscriber.
Why every lab setup uses 10.0.0.0 network. Like.. to look cool? Or... they really have potentially so much devices to manage which they will use pfSense?
In our area region, using a 10.0.0.0/x is the most common in corporate/office environments. 192.168.0.0/x is typically used at home. Thanks for watching!
The Pfsense VLAN "priority" instructions are NOT a thing. They just state "leave them at default"... sooo... there's that
just straight to the point bro hehehehe....
Definitely could have edited the 5 mins spent on VLAN priority into 15 seconds
Probably true.
good content, but good god man you can ramble. This should have been a 20min vid. Still, the content is good.
Haha, I try to include as much as possible for a more relaxed journey. Thanks for watching.