I presume you have setup your WA901ND as a DHCP client, in which case it may have received some IP address from your building's gateway. Please notice: it may, it need not to. If it has an IP address, issue the following command (you may have to install the program nmap, which is absolutely necessary to solve networking problems):
nmap -p80 192.168.112.0/24
This assumes that your home network is 192.168.112.0/24, replace it with your real home network. This command will display all pcs listening on port 80, which is where a Web page is served. Some machines will reply: 'port closed', which means they do not have a Web server. The others will reply either port open
or port filtered
; most likely, the WA910ND will have this port open, so that the output of nmap will narrow down the number of IP addresses you will have to try in your Web Browser.
If this fails, you should try
nmap -p443 192.168.112.0/24
which does the same thing for the encrypted (SSL) port 443. If your WA910ND is up, has a valid IP and it has a Web Server running, it will be listed in either of these two outputs.
If, after trial and error, you have not located it, it means it has not been dished out a valid IP address. This can happen, if it bridges the mon.wlan0 and eth0 interfaces (if you do not understand this, don't worry, just read on). In this case, your only choice is to disconnect it from the building's wifi, and attach yourself directly with a cable.
Please also notice that you should not change the Wifi channel it is operating on, because this must match the channel of your building's wifi, so you have no freedom there.
I'm assuming you didn't set an IP for the bridged device before putting it in bridged mode. If you didn't you can guess at the IP it defaulted to, otherwise, you'll have to restart the process of bridging that device again I'd imagine. – Andrew – 2014-08-11T11:10:14.420