Help with Vlan
-
you don't need an AP that supports vlans unless you want to have different wireless networks based up ssid that want to control access between.. For example if you wanted a guest wifi network and a work wifi network using the same AP that on work you all them to talk to your desktops and other wired network devices, and guest you just let use the internet for example.
I would recommend one of the unifi AP.. The new AC line is very reasonable priced.. $89 for the lite model and highend pro model $149 I believe..
https://www.ubnt.com/unifi/unifi-ap-ac-lite/
You can have 4 different SSIDs with different vlans each… I run a ssid that requires eap-tls to auth, this is my normal wlan, I then have a guest wlan as you saw and also run a wlan-psk that is for my devices that do not support enterprise wpa2.. My nest thermostat for example, and my harmony hub.. Consumer grade electronics that are wifi quite often do not support wpa2 enterprise and only psk mode.
Yes once you put separate your network into multiple segments/vlans then it is very easy to control access between them via psfsense.
-
you don't need an AP that supports vlans unless you want to have different wireless networks based up ssid that want to control access between.. For example if you wanted a guest wifi network and a work wifi network using the same AP that on work you all them to talk to your desktops and other wired network devices, and guest you just let use the internet for example.
I would recommend one of the unifi AP.. The new AC line is very reasonable priced.. $89 for the lite model and highend pro model $149 I believe..
https://www.ubnt.com/unifi/unifi-ap-ac-lite/
You can have 4 different SSIDs with different vlans each… I run a ssid that requires eap-tls to auth, this is my normal wlan, I then have a guest wlan as you saw and also run a wlan-psk that is for my devices that do not support enterprise wpa2.. My nest thermostat for example, and my harmony hub.. Consumer grade electronics that are wifi quite often do not support wpa2 enterprise and only psk mode.
Yes once you put separate your network into multiple segments/vlans then it is very easy to control access between them via psfsense.
we are using switch HP ProCurve 1810G - 24 GE .
and those Linksys AP.the idea is to provide two SSID one for Guest and one for office including the cables.
Guest SSID need to be on VLAN 10
Office SSID and Wired to be on Vlan 20switch has 24 ports. seen I can thrink the vlans on the switchs ports.
How does the AP understands which IP to provide when the users are connected?
-
The AP needs to place traffic from one SSID onto one VLAN and the other SSID onto the other VLAN.
From there you will probably be running DHCP on each VLAN on pfSense and it will be responsible for leasing IP addresses and settings on each network.
It will look something like this:
https://forum.pfsense.org/index.php?topic=88942.msg491727#msg491727
-
The AP needs to place traffic from one SSID onto one VLAN and the other SSID onto the other VLAN.
From there you will probably be running DHCP on each VLAN on pfSense and it will be responsible for leasing IP addresses and settings on each network.
It will look something like this:
https://forum.pfsense.org/index.php?topic=88942.msg491727#msg491727
Thank you so much,
so tag the vlan on the switch port and plug the AP on the taged port . enable dhcp on the VLANS NIC.
is the Linksys AP gonna work with this settings ?i have esxi 6.0 using pfsense as a vm on it.
I've created vlan 20 on the hp physical switch and also in pfsense .
tagged port 20 for Vlan 20.
do i need a physical NIC of the host to be connect to the physical tagged port on the switch or it will works out of the box when i plug the AP to the switch ?please see attached i tried to design the idea.
much appreciate it .
 -
No idea about the linksys. Sorry. If it supports multiple SSIDs with VLAN tags, it should work fine. If not, no.
-
No idea about the linksys. Sorry. If it supports multiple SSIDs with VLAN tags, it should work fine. If not, no.
thank you,
do I have to trunk a port on the switch ? create vlan on the switch port ? -
To send multiple VLANs over one switch port, yes, you need it to be a tagged port. "trunk" has at least two meanings when it comes to switch ports and is kind of vendor-specific so I like to avoid the term.
-
To send multiple VLANs over one switch port, yes, you need it to be a tagged port. "trunk" has at least two meanings when it comes to switch ports and is kind of vendor-specific so I like to avoid the term.
do you mean create just a VLAN on the physical switch port no thrunk ?
-
You typically don't create a VLAN on a port. You create a VLAN on a switch or a network of switches. Ports are either tagged or untagged on that VLAN. Tagged ports can carry multiple VLANs and are sometimes referred to as trunk ports.
All of this information is available in places like wikipedia and is not pfSense-specific. I don't know why you want someone to take the time to re-explain that which is already explained elsewhere and is general networking knowledge.
-
keep in mind if your going to be running vlans on your vswitch you need to set it to 4095
-
keep in mind if your going to be running vlans on your vswitch you need to set it to 4095
thanks john,
creating a vlan 4095 on the vswitch , creating vlan on the pfsense , and vlan on the physique switch and I am set to go ?thank you
-
John can you please help ?
i am stuck here.
i've bought the VLAN WLAN device
http://www.peplink.com/products/enterprise-access-point/pepwave-ap-one/#enterpriseVLAN is configured on the pfsense
VLAN 20 is configured on the switch on port 20
the AP is attached on port 20 on the switch.
VLAN 20 on the pfsense is having DHCP enabled
On the vSwitch i've created a port group with ALL (4095 ) but can't get it work**when a use is connected to the AP they don't receive IP of VLAN 20 but of Default VLAN
what i am doing wrong ?
thank you**
-
Sounds like the AP is sending traffic to the switch untagged. Change your switch port to an untagged port on VLAN 20 and connect the AP to it.
That's fine but you can only do one SSID. Else you have to figure out how to tell the AP to tag the traffic from that SSID with VLAN 20 and leave the switchport like it is.
I notice you did not specify whether you made port 20 tagged or untagged on VLAN 20. It matters.
-
Sounds like the AP is sending traffic to the switch untagged. Change your switch port to an untagged port on VLAN 20 and connect the AP to it.
That's fine but you can only do one SSID. Else you have to figure out how to tell the AP to tag the traffic from that SSID with VLAN 20 and leave the switchport like it is.
I notice you did not specify whether you made port 20 tagged or untagged on VLAN 20. It matters.
thank you so much for your answer.
the port 20 is untagged on the VLAN20 on the physical switch.
attached is a picturePS : there is no cable right now just had to disaconnect it .
from the vswitch is the settings correct ?
-
The settings on the switch are wrong or it would be working. The switchport going to the AP needs to be configured to match whatever the AP is configured to do. Sorry, I don't have time to research your AP. You'll need to find out its capabilities.
A VLAN with only one port on it can't talk to anything else. Where is your tagged port going to pfSense?
-
A VLAN with only one port on it can't talk to anything else. Where is your tagged port going to pfSense?
sorry I didn't get the question,
can you ask it again ? -
The fastest way to solve your issues is probably to find a networking text written in your native language that explains all this.
-
The fastest way to solve your issues is probably to find a networking text written in your native language that explains all this.
thank you for your answer.
the idea is to configure VLAN20 and VLAN 30 using pfsense as VM in the ESXI 6.0
on the physical switch configure two ports for VLAN 30 and 20
Connect the AP 20 in VLAN 20 on the physical switch and AP 30 In VLAN 30 port on the switch.
each VLAN is delivering a DHCP server .thank you
-
Right. And I am in no mood to write up exactly how to configure all that for someone who apparently doesn't know the difference between tagged and untagged switch ports.
I hate to be harsh, but no. Maybe someone else.
-
Right. And I am in no mood to write up exactly how to configure all that for someone who apparently doesn't know the difference between tagged and untagged switch ports.
I hate to be harsh, but no. Maybe someone else.
thank you for your answer,
the issue here is not knowing the different between tag and untag is the explanation .
hopefully someone can be kind and help me here out .
