|
|
|
so something is likely on .2, use an app like the one i mentioned above, or just ping .2 from a device
why are you allocating the AP an address that is part of the DHCP pool? static addresses should be outside the range of the DHCP pool
Because when setting up a router to use as a AP all the videos online saying how it's done say your main router should be set to 192.168.1.1 and second one that you plan to use as a AP should be 192.168.1.2
it doesnt matter what it is, it could be any of the other 253 IP addresses available (ie anything thats not the router). they likely say that to make things tidier. if assigning it a static IP address it should be outside the DHCP pool range of the Router. which yours isnt
My router is .1, and my 2 AP's are .8 and .9, my DHCP pool starts at .100-.200
you still havent answered if there is a device on .2. have you even checked this?

i believe that means something has that address already
3 options, change the DHCP pool range on the Asus, or put the AP on an IP address outside the DHCP pool or set the AP to get a DHCP address
What does the asus say on the General > Network Map tab under clients?
Starscream122 .... we are all trying to help you here, so bear with the questions please ![]()
What device (phone? PC?) did you use to ping 182.168.1.2?
Was it connected to your network at the time, either wifi or cable?
Rickles:
Starscream122 .... we are all trying to help you here, so bear with the questions please
What device (phone? PC?) did you use to ping 182.168.1.2?
Was it connected to your network at the time, either wifi or cable?
I used my Windows 10 PC Connected via Ethernet to my RT-AC86U
I used my Windows 10 PC Connected via Ethernet to my RT-AC86U
In theory, if your Asus is defined as 192.168.1.1, why not just fire up the access point, see what IP address has been assigned by the Asus, and simply accept that as appropriate?
Once you have that IP address, assign the AP/Ultra hub that IP as static, and that way your network works, and you'll always be able to access its interface as 192.168.1.x thereafter.
Even, as you say, 192.168.1.3 works OK, simply accept that and no further headaches ![]()
>I used my Windows 10 PC Connected via Ethernet to my RT-AC86U<
Then quite possibly the PC was assigned 192.168.1.2 ??
You may have to completely release and then renew all IP's before getting the Ultra Hub to grab/be assigned the one you want. The Hub or the Asus may also be holding 192.168.1.2 under lease (possibly 24 hours).
Rickles:
In theory, if your Asus is defined as 192.168.1.1, why not just fire up the access point, see what IP address has been assigned by the Asus, and simply accept that as appropriate?
Once you have that IP address, assign the AP/Ultra hub that IP as static, and that way your network works, and you'll always be able to access its interface as 192.168.1.x thereafter.
Even, as you say, 192.168.1.3 works OK, simply accept that and no further headaches
I will. I am happy with the ASUS router on .1 and the ultrahub on .3... everything is working all good!
>I will. I am happy with the ASUS router on .1 and the ultrahub on .3... everything is working all good!<
Good idea ... as you confirm, all is working pretty much as you want and in reality there is nothing wrong with any IP being assigned to a system device (that's how DHCP worls anyway). Because you occassionaly want to access the Ultra interface, then locking in the IP will do that for you.
I'm of the opinion that your PC has probably been assigned .2 by the Asus, and all your attempts to make the Ultra Hub that will require you to release and then renew the IP configurations ... something you could try at your leisure ![]()
I'm just going to jump in here and say that his client was not 1.2, i have been helping Starscream privately in discord chat and he has provided screenshots that show that his client is not 1.2, its been assigned 1.246 by DHCP
yep that was obvious by the ping above, but something has been allocted .2 and its not currently connected to the network.
|
|
|