@NaNook1971

 

Hey

 

Hopefully be able to help you with this, sounds like a common enough networking issue..  few questions if you don't mind!

 

I then found tht the default IP for the unit is in the 192.168.0 range.  My network is in the .1 range.  So fine, I changed my router to .0, logged in to the EAP, set it up with the correct IP range, then set my router back to the .1 range.

 

Can you give us the IP addresses in use?   Namely the router and Access Point..   192.168.1.21  and 192.168.1.125 for example

 

 

Now I can log in to the EAP fine, from the web browser.  Omada still doesnt work, but im not too fussed about that.

 

What do you mean by Omada doesnt work?

 

 

I have set the EAP up with the same SSIDs as my Sky router, as I want seamless roaming.

 

Seamless roaming doesn't work like this, this setup wont give you seamless roaming sadly...  You would need a controller to get seamless roaming, the Sky hub doesnt do seamless

 

 

I can see from the web interface that the EAP is passing traffic over wireless.

 

So, I moved my EAP outside, connected it directly to a TPLink POE+ switch, and all lights come on as expected.

 

The problem now is, when I connect to the EAP, i.e. out of range of Sky router, I get a perfect wifi signal, but no internet access.  The POE+ switch is connected by TPLink powerline to the main network.

 

What IP address are you getting when connected to the Sky device, then connected to the AP?   when on the AP can you ping the sky router?    paste any screenshots you have.. that might help :)

 

Any idea what the problem may be?

Got a few, but need the IP details and any screens you can mate :)