Wireless router as AP: how to access config UI?

[OsakaWebbie]

I followed some instructions for using a wired router (which I want as my perimeter firewall and for wired ports) and a wireless router (for the obvious reason of wireless connectivity) together. The instructions had me manually set the wireless router's WAN IP address to a number in the main router's subnet but outside its DHCP range, turn off its DHCP service and uPnP, and then connect it to the main router using its LAN port instead of WAN port. The instructions said that such a configuration makes it operate as an "access point" instead of a "router". It seemed counter-intuitive to me (but I'm not familiar with access points), but it worked - all my computers are now on the same subnet and can see each other (which was not working before). Hooray on that point. But now I can't figure out how to access the wireless router with my browser to change settings related to the wireless operations (like SSID etc.). My main router's DHCP range is from 192.168.11.2 to 192.168.11.16, so I set the IP of the wireless router to 192.168.11.17 (as far as I know). But it is not visible by browser URL or ping, by either a computer connected to it (wired or wireless) or a computer on the main router. What might I have done wrong? If I should be able to see it, how can I determine it's IP address? Or do I have to reconnect it as a "router" (using its WAN port) temporarily whenever I want to access its configuration interface?

 

[burtsbees]

You set the WAN ip to 192.168.11.17

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!

 

[OsakaWebbie]

That's what I did. And the fact that my PCs can see each other is evidence that my attempt to change that was successful, because the default address was 192,168.1.1, which would be on the wrong subnet and therefore wouldn't have allowed PCs on the wireless to do file sharing with PCs on the main router.

So from your statement, it sounds like you are confident that I should be able to access it by its IP. If I made a mistake and its IP is different than what I think, is there a way to determine it? For example, a way to query the subnet for what IPs are in use on it, short of pinging the 252 addresses that are not used by other devices? Or do I need to press the reset button on it and start over?

Oh, and one other thing: should I be able to access it from any PC on the subnet, or does it have to be a PC that is running through the WAP (i.e. wireless or wired to the WAP rather than the main router)?

 

[burtsbees]

You should be able to access the AP either through wired or wireless. The fact that the pc's are in the same subnet means that they communicate in layer 2, not routing (switched), so Ip addresses have nothing to do with that.

You can download Angry Ip Scanner for free to scan everything in the subnet. Now come to think of it, I cannot remember if you set the LAN or WAN ip address...can you even set the LAN IP address? I will chec mine at work---I will VPN into my work network and check how mine is set up...it has been a while...

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!

 

[OsakaWebbie]

Thanks for checking - this is definitely a point of possible confusion. At the time I configured mine, I never even considered that there could be a such thing as a LAN IP on a router, so I didn't look for one - it was definitely the WAN one that I set. Since then, I have read a number of internet pages that describe how to do this, and some call it the WAN IP and others the LAN IP. Perhaps it's just ambiguous terminology, because although WAN is the only IP that makes any sense for a router, it's running as an access point, so only LAN ports are being used. I'm totally new to the idea of access points, and I haven't found a satisfactory description of what they are yet (or more precisely, how a router can turn into one), so I'm fuzzy on the details.

When I was configuring the router (the last time I had access to the UI) it still had its WAN port connected. I suppose that it's possible that when it's running as an AP, it gives a different UI (configuration options more appropriate for an AP?) - after all, at least part of the device knows what's going on, because its MDI kicked in (I didn't have to use a crossover cable). If there is a special UI for its AP mode, too bad I can't see it...

 

[burtsbees]

It is the LAN IP address, not the WAN. It should give you the option somewhere around the DHCP settings. What model is this, anyway?

Did you ever get Angry IP Scanner?

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!

 

[OsakaWebbie]

It's a Corega CG-WLBARGPX, but I suspect it is not sold outside Japan, so you've probably never heard of it.

No, I did not get Angry IP Scanner - I try to avoid installing new software for one-time needs that can probably be solved without it.

I decided to start over. I unplugged all connections and pressed the reset button on the wireless router. Then I followed the order of instructions on this page because it seemed the most thorough and authoritative of the ones I had read. It turns out that I was mistaken - there IS an IP address setting in the LAN section (in fact, this time I didn't see one in the WAN section at first glance, although it might have been there if I had looked more). I changed it, which caused my PC to be disconnected until it was issued a new IP. Then I turned off DHCP, and then plugged in the router-to-router cable and switched my PC to using wireless instead of wired (in order to force a reissuing of an IP by my main router and also to test the normal way I would be connected). It was several minutes before I had internet access again, but it did come through eventually, as well as visibility to shared files on other PCs on the LAN. And now I think I am able to access the router's UI, although at the moment it refuses to let me in because it says someone is already logged in (me, from before I let the router give my PC a new IP). I assume that will time out in a day or so.