VLan Set up/Network segregation setup
-
I need to set up a 2100 with three (3) separate LAN networks with unique IP Ranges distributed by DHCP.
I WILL have three (3) switches and thought the best way to set this up was to connect Port 1 (LAN) to one switch, Port 2 (called one department name) to the second and Port 3 (another department name) to the third.
I’ve been testing setting up the VLAN on Port 2 and I can’t seem to get DHCP to work on Port 2.
I’ve been attaching a computer to Port 2 and it won’t get a DHCP address that is assigned to that VLAN and Port.
Rules are set to allow any traffic to propagate.Now, I think, as I continue to read documentation, that I first have to configure one of the Managed Switches to support that VLan and then connect devices to them.
Is that true?Previously, on a 3100, I was able to configure the OPT 1 port as a separate LAN interface and create two networks fairly easily, kinda thought creating a VLAN (which by default is called OPT 1) would accomplish the same thing.
Any help, suggestions appreciated.
-
@AimHigh Did you look here?
https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/configuring-the-switch-ports.html -
Thank you.
I didn’t go to that document directly, however, I did complete those steps from other documentation for Port 2.
Not getting DHCP from that Port, nor can I pass traffic (or see an ARO entry) when I set a device connected to that Port using a static IP in the assigned IP range. -
@AimHigh Best bet is to post screen shots of the config in pfSense and your switch.
-
@Jarhead yes, that is my next step. Thanks.
I just wanted to be sure that I don’t have to have a managed switch configured on the VLAN port.
Will post in a few. -
@Jarhead Color me confused.
Before doing the screen shots, I rebooted the 2100 and plugged a device into Port 2 (which) is where I had set up the VLAN.
Still no DHCP, then, set a Static address on the device in the range and it worked! I could get to the 2100 on the primary IP for that VLAN.
Switched the device BACK to DHCP and, then, DID get an IP.
When in doubt, reboot, eh?
Thanks for your responses, they did help my thinking process and confirmed I was not completely crazy.