Sophos XGS 126w connecting wireless ssid dhcp dont work

Hello Chi Hing Chi Hing,

Thank you for reaching out to the community, On the CLI, press 5 to select 5. Device management, press 3 to select 3. Advanced shell, and change to the log directory using the command cd /log. Can you share the dhcpd.log when a client is trying to connect to the internal ssid...
For the live logs, you can check - tail -f dhcpd.log  
For the olderlogs if you know the time frame you can use the following cmd: less dhcpd.log 

there you go, the internal ssid interface is wlet1 

XGS126w_XN01_SFOS 18.5.0 GA-Build264# tail -f dhcpd.log

Multiple interfaces match the same subnet: Port1 wlnet1
Multiple interfaces match the same shared network: Port1 wlnet1
Listening on LPF/Port1/7c:5a:1c:ab:68:80/wlnet1
Sending on LPF/Port1/7c:5a:1c:ab:68:80/wlnet1
Listening on LPF/wlnet2/f2:50:bd:a6:b1:cc/wlnet2
Sending on LPF/wlnet2/f2:50:bd:a6:b1:cc/wlnet2
Listening on LPF/wlnet1/7c:5a:1c:ab:68:92/wlnet1
Sending on LPF/wlnet1/7c:5a:1c:ab:68:92/wlnet1
Sending on Socket/fallback/fallback-net

Can you upgrade the v18.5.0 GA to v18.5.4 Build ?
as GA is declared EoL on 30-JUN-2022

it is in SFOS 18.5.0 GA-Build264, shall i upgrade to the following ? 

You can go for SFOS 18.5.4 MR4-Build418 and check the status once again regarding the dhcp for the internal ssid !!

ok will try to upgrade and let you know the result, thanks

firmware upgraded and still the same with below log 

XGS126w_XN01_SFOS 18.5.4 MR-4-Build418# tail -f dhcpd.log

Multiple interfaces match the same subnet: Port1 wlnet1
Multiple interfaces match the same shared network: Port1 wlnet1
Listening on LPF/Port1/7c:5a:1c:ab:68:80/wlnet1
Sending on LPF/Port1/7c:5a:1c:ab:68:80/wlnet1
Listening on LPF/wlnet2/f2:50:bd:a6:b1:cc/wlnet2
Sending on LPF/wlnet2/f2:50:bd:a6:b1:cc/wlnet2
Listening on LPF/wlnet1/7c:5a:1c:ab:68:92/wlnet1
Sending on LPF/wlnet1/7c:5a:1c:ab:68:92/wlnet1
Sending on Socket/fallback/fallback-net

firmware upgraded and still the same with below log 

XGS126w_XN01_SFOS 18.5.4 MR-4-Build418# tail -f dhcpd.log

Multiple interfaces match the same subnet: Port1 wlnet1
Multiple interfaces match the same shared network: Port1 wlnet1
Listening on LPF/Port1/7c:5a:1c:ab:68:80/wlnet1
Sending on LPF/Port1/7c:5a:1c:ab:68:80/wlnet1
Listening on LPF/wlnet2/f2:50:bd:a6:b1:cc/wlnet2
Sending on LPF/wlnet2/f2:50:bd:a6:b1:cc/wlnet2
Listening on LPF/wlnet1/7c:5a:1c:ab:68:92/wlnet1
Sending on LPF/wlnet1/7c:5a:1c:ab:68:92/wlnet1
Sending on Socket/fallback/fallback-net

are any clients connected from that dhcp server at all ? 

No it’s doesn’t obtain ip when connecting the internal ssid, I really don’t have idea 

Hi,

Please post a copy of your DHCP server configuration.

Ian

Hello there,

You would need to change the IP range of your Separate Zone SSID to not overlap with your Bridge to AP LAN subnet.

Regards,

please find below dhcp setting for internal ssid, and i found that it could connect to this ssid, but its take around one min to connect and after connected, it doesnt access internet and also can not reaching the LAN segment like as the FW, do i need to create a bridge on this ssid ?

Can you change the subnet of chihing from 192.168.0.2/24 to 192.168.2.0/24 and define the range accordingly ?

i create a new zone to assign public ssid into it, and create a bridge for port 1 and zone wifi (ssid interenal) and its start working well, but i still found the internal and external ssid can still reaching each other, in this case i need to create a rule to restrict these 2 subnet ?

With the separate zone, separate subnet - a separate rule would be better !!

when creating public ssid i have chosen seperate zone already, suppose this ip segment will already seperate to lan and internal ssid, but i dont know why these segement is still able to accessible ? 

Hello,

When using the community, please insert the image directly, don't share 3rd party links.

As mentioned, I would recommend you to create a new DHCP range for your Wireless Guest.

Regards,