topic Re: ASUS Access point with SKY Fibre Router issus in Broadband

ASUS Access point with SKY Fibre Router issus

grumpy+baker — Tue, 06 May 2025 19:24:49 GMT

I have just got my SKY fibre installed but have some issues.

I have a ASUS router set up as an access point (hardwired to Sky router) but I cannot find a way to access the admin page of the access point. I know its workin as i can wireless connect to the ASUS access point and get internet access but I cant find a way to connect to the admin page of the access point.

If I look at the list of connected devices on the Sky admin page the MAC adress of the access point is not even listed which is odd.

I do see a couple of devices marked as UNKNOWN but cant connect to any of the URLS (eg 192.168.0.9)

Sometimes I get an error "connection refused"

This is annoying as I want to change to wifi password on the access point but cannot

Any help much appreciated

Re: ASUS Access point with SKY Fibre Router issus

JimM1 — Tue, 06 May 2025 20:16:41 GMT

@grumpy+baker You more than likely are going to have an issue trying to admin the Asus router connection via the Sky Hub, even with the known IP that the Sky unit assign's it, Asus will block the reverse transfer, it is easy to Asus down to sky but just not the other way.

You could try 192.168.50.1 and as a http:// in front to see if it lets you in.

Re: ASUS Access point with SKY Fibre Router issus

ADozer — Tue, 06 May 2025 20:31:19 GMT

Download asus device

Re: ASUS Access point with SKY Fibre Router issus

ADozer — Tue, 06 May 2025 20:32:17 GMT

Download the Asus device discovery app from the play store if you have an android phone. It will find the sky assigned IP address.

Re: ASUS Access point with SKY Fibre Router issus

grumpy+baker — Wed, 07 May 2025 06:06:09 GMT

Thanks for replies but neither worked. Before I got the new sky fibre hub I was using an ASUS ADSL router as main router connected to sky and then another ASU's router as a hardwired access point. I had assigned a fixed ip address to the access point (192.168.1.200) and all was fine.

using ASU'S discovery it is still telling me that it adress is still 192.168.1.200 which I don't understand as it's working as an access point ok to the new sky fibre router.

As it's all working may just leave it but it's odd.

i could reset the access point back to factory and start again or try and get the old main router running on sky which is a bit more complicated as it don't have a WAN port

Re: ASUS Access point with SKY Fibre Router issus

JimM1 — Wed, 07 May 2025 06:24:23 GMT

@grumpy+baker The error "Sometimes I get an error "connection refused" is the puppy, you need to take a look at the IP assigned and what is doing it, Asus in AP mode will be refusing the connection back from the sky, if you do not believe connect a Ethernet device direct on the Asus, and you will be able to admin it fine. Once you know the true IP for the Asus write it down somewhere so you have it.

Re: ASUS Access point with SKY Fibre Router issus

Chrisee — Wed, 07 May 2025 07:45:16 GMT

@grumpy+baker it is likely that the Asus unit is simply acting as an ethernet to. WiFi bridge which doesnt require an IP address to work. It would need an address in the Skyhub's range of 192.168.0.2 to 192.168.0.254 for you to be able the change the settings while connected.

Re: ASUS Access point with SKY Fibre Router issus

ADozer — Wed, 07 May 2025 06:51:48 GMT

I'd recommend factory resetting and starting again. That way you would have a clean restart and you wouldn't encounter any bugs.

Re: ASUS Access point with SKY Fibre Router issus

grumpy+baker — Wed, 07 May 2025 07:48:12 GMT

Thanks all goons do a factory reset on the access point and start again. Will assign it a fixed in of 192.168.0.200 so I can admin it via the sky network

will let you know if this works

Re: ASUS Access point with SKY Fibre Router issus

grumpy+baker — Wed, 07 May 2025 13:03:57 GMT

Ok a factory reset and setting a fixed ip of 192.168.0.200 fixed the issue

can now happily access the asus access point admin page

i think the issue was caused by the access point having a fixed ip of 192.168.1.200 from my previous set up