USG60W WiFi set up

Dovetail_MD

I'm now puzzling over the Wi-Fi setup.

At the moment all I've done is accepted the default with a Main SSID and a guest SSID and changed the passwords to something more complex

It looks to me like neither of these SSIDs has LAN access as default?

Our previous setup was to have two "always on" SSIDs - a guest with no LAN access and another SSID for those devices that are allowed access to the LAN.

The other issue is that there is an oddness in which devices are allowed to connect which not - my modern SamsungGalaxy Note mobile phone will connect to the main SSID but my administrators older Apple iPhone will not.  Why?

So how do I set up to always on SSID similar to the original that we had as described above?

Zyxel_Emily

Hi @Dovetail_MD,

Since you have DHCP supplied by Windows 2012 server, you can set DHCP relay on the lan interface.

Here is an example.

Go to the interface where the client is located.

Assume the DHCP server's IP is 192.168.7.10.

Then point the relay server to 192.168.7.10.

Last but not least

Please be nice and respectful to other community members.

We are encouraging community members to help each other and any offensive, abusive, obscene, hateful, political, religious, threatening, or discloses personal information about others will be prohibited.

Dovetail_MD

Sorry  - should have said - we have DHCP supplied by Windows 2012 server is also a DC of course and we do not use our subnet for the guest Wi-Fi as we cannot work out how to fix this

Dovetail_MD

No one?

I've changed the Guest to always on and now the bloody thing is not serving any WiFi at all.

Harska

Try to reset to factory defaults, then make the initial setup with basic settings.
Then create the home and guest WiFis, and do not use the DC as DHCP server.

These 2 WiFis should work fine; but only home can access LAN

If this is successfull then there are propably problems

with the DHCP settings of the DC, and the IP parameters do not match

with the IP settings of the router

Dovetail_MD

Thank you - I have just discovered that the DC running DHCP does not have Internet access for some reason.  Work in progress!

In the meantime I have put our previous gateway device back on the system as that has been reliable for two years.  

But are you suggesting turning on DHCP on the USG60W?

Oh no I forgot - this is what screwed up our domain controllers originally as it came on as a default, picked up the DHCP addresses on the iSCSI side of one of the DC's and  the domain failed because it could not authenticate - it's given us a month of difficulties as a result.

Dovetail_MD

Okay - DC that runs DHCP now has Internet access as well as network access.

Put the Zyxel back on the network and it is not dealing DHCP addresses from the DC

Is there any way of nominating the IP address of the DC that runs DHCP in this Zyxel so forcing it to use it?

Harska

ZyXEL either is dealing the IP adresses (=has DHCP server on);

or the DHCP is OFF (not dealing the IP adresses), and DC is acting as DHCP server.

There is no way to make ZyXEL to distribute the DHCP addresses of DC.

That is a communication protocol between the client and DHCP server.

In that scenario; the ZyXEL is only routing the IP traffic
(if setup correctly, ie. no FW rule blocking etc)

Dovetail_MD

"There is no way to make ZyXEL to distribute the DHCP addresses of DC" - really?

Dovetail_MD

Harska  - you are clearly talking rubbish - not the least since I have a mobile phone beside me now connected to the main USG60W Wi-Fi which is picking up DHCP from a Centos server.

And to get it to do this look at network resources inside the DMZ I had to go to the configuration and give that particular SSID lan access which it did not have as default.

I think this is one of the defaults on this box that I applaud - unlike at least two others being;

The default that means that when your Internet connection goes down it does not automatically redirect

The defaults that turns off the guest Wi-Fi after four hours as we use guest as a security device rather than something as though we were offering it to people coming to a hotel - not that we run a hotel you understand

Harska

Your sentence #1:
> Put the Zyxel back on the network and it is not dealing DHCP addresses from the DC

There was some problem or wrong config in the network

since you didn't get DHCP addresses from the DHCP server.

Your sentence #2:
> I have a mobile phone beside me now connected to the main
> USG60W Wi-Fi which is picking up DHCP from a Centos server

That is the way it works normally. So now you propably don't
have the earlier misconfiguration in the network anymore.

Your ZyXEL is doing normal routing of IP traffic, hence your phone gets
DHCP addresses over the wireless connection.

Your ZyXEL is not distributing (or dealing with) the DHCP addresses;

just doing normal routing of the traffic, between client and DHCP server.

I tried to help, but it's very difficult to solve other people's mess up
just by looking at the question; where many ot the key informations are missing.

From now on; I quit talking rubbish. You solve yourself your problems.

Zyxel_Emily

Hi @Dovetail_MD,

Since you have DHCP supplied by Windows 2012 server, you can set DHCP relay on the lan interface.

Here is an example.

Go to the interface where the client is located.

Assume the DHCP server's IP is 192.168.7.10.

Then point the relay server to 192.168.7.10.

Last but not least

Please be nice and respectful to other community members.

We are encouraging community members to help each other and any offensive, abusive, obscene, hateful, political, religious, threatening, or discloses personal information about others will be prohibited.