NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DeeDee123
Jan 03, 2020Tutor
Devices on VLAN do not get IP from DHCP
Dear NETGEAR community, I have been banging my head for a long time now and seek advice from you folks that are much more experienced than me. Please if you need additional info or clarification,...
- Jan 19, 2020
Hi DaneA,
Thanks for getting back to me! I think i found the issue to my problem. It was my DHCP server now being able to route back to my pfsense box because I removed the default gateway from the dhcp server's nic interface.
I think I should be able to get it working now!
Thanks agani!
DaneA
Jan 07, 2020NETGEAR Employee Retired
For me, I think DHCP L2 Relay is not needed because when you configured the 10.1.8.0 network on the Windows DHCP Server (the current setup), it works.
Kindly post a detailed diagram of your network setup showing how everything is connected. I'm sorry for I'm kinda confuse in laying out how is everything connected following what you have stated on your posts.
Regards,
DaneA
NETGEAR Community Team
schumaku
Jan 07, 2020Guru - Experienced User
Very confusing, agree with DaneA that some additional and ideally complete design sheet might help.
Two points:
Suspect there is an inconsistency between the VLAN config for VLAN 2 on the pfsense (dedicated port) and the switch port - for thes VLAN 2 connection, it either has to be run tagged on both ends of the link, or untagged. If it's untagged, the VLAN ID 2 must be reflected in the same PVID 2.
As you seem to establish dedicated links for the two VLANs, I can't see why you think about enabling routing on the switch, or on enabling any DHCP helpers. You should have to complete independent L2 netwrks implemented as VLANs.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!