Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 21 replies
  • Answers 3 answers
  • Subscribers 40 subscribers
  • Views 7377 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Clients don't receive an IP address from DHCP on newly created VLAN

dsurfer

Hi! I just created a new VLAN and DHCP server with firewall rule and clients are not able to get an IP address. My goal is to have my guest WIFI network (and if I can get this working, my IoT network) on a separate VLAN. I've restarted my switch, firewall, and DHCP server, removed and re-created everything a few times but no joy.

My newly created VLAN interface:

My new network IP host:

My newly created DHCP server on the firewall for the new VLAN:

The new firewall rule to allow traffic from the 192.168.200.0 network to the WAN (placed in top position):

I have a Unifi AP connected but have also tried a wired laptop to another dedicated VLAN port on the switch with the same results: can't get an IP address

Thanks for any help!



This thread was automatically locked due to age.
Parents
  • 0

    Please share a screenshot of your network topology (router/firewall, switches, clients / servers).
    Is the uplink from switch to firewall correctly tagged / untagged with the said VLAN?

    Also share informations with your interface settings - vlans, ips, ports on the firewall and switch.

    _______________________________________________________

    Sophos SG 210 with Sophos XG Home - 19.5 MR 2

    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to Thomas_XG

    The weird thing is that I have it set up pretty much exactly the same as another one of my sites and it still doesn't work. The same Sophos firewall system, same Datto switch manufacturer. All trunk ports on switch are tagged. I've tested this with a physically attached laptop and right now I'm testing it with a virtual machine (PC) on a Hyper-v server (which I did at my other site to confirm it worked). The VM network port is untagged as it should be.

    Pretty much the Sophos firewall connects the Datto switch, for that uplink port the VLAN is tagged, then I've tagged the port that goes to my Hyper-v server. Also I tagged the port that goes to the Unifi AP as well.

Reply
  • 0 in reply to Thomas_XG

    The weird thing is that I have it set up pretty much exactly the same as another one of my sites and it still doesn't work. The same Sophos firewall system, same Datto switch manufacturer. All trunk ports on switch are tagged. I've tested this with a physically attached laptop and right now I'm testing it with a virtual machine (PC) on a Hyper-v server (which I did at my other site to confirm it worked). The VM network port is untagged as it should be.

    Pretty much the Sophos firewall connects the Datto switch, for that uplink port the VLAN is tagged, then I've tagged the port that goes to my Hyper-v server. Also I tagged the port that goes to the Unifi AP as well.

Children
No Data
Unfiltered HTML