I have a fios router in my basement with wires that connect to it running all throughout my house. At the ends of each of these wires are ethernet outlets (not sure if that's the technical term, but I mean this) where I can plug in an ethernet cable and then connect my computer. I want to set up a second router (Linksys ea3500) as a wireless access point. Meaning I want the network to look something like this:
===cable===[fios box]~~~~[ethernet outlet]~~~ethernet cable~~~>[linksys] <))) wifi
I hope that ascii diagram was clear enough. Anyway, I started by connecting my linksys router with my laptop, and at this point neither were connected to the internet. I opened up the linksys router settings at 192.168.1.1 and selected Bridge Mode. Just after that I was booted off the page and it said that I can access the router settings via its network IP (presumably the one the fios router will give it). Fine. Then I connect my linksys router to my ethernet outlet and pop open the Fios router page 192.168.1.1 and view my network. I see that my linksys router has been given the IP 192.168.1.9 but it is offline and ping does not work. I tried connecting the ethernet cable both to the WAN port on my Linksys and to the first LAN port. Nothing seemed to help to bring it online.
So my two questions:
What am I missing here / how can I bring it online?
I understand that in a simple one-router setup the WAN port is for the cable bringing internet into the house and then the other devices connect on the LAN ports. What about for this second Linksys router? Should the ethernet cable connected to the outlet that is connected to Fios be plugged in to the WAN port on the Linksys or a LAN port on the Linksys? I would like a clear explanation on this, but for the purposes of the first question, neither worked.
Bridge your linksys and connect the two routers using the LAN interface on each device. The WAN port serves as a NAT interface - connecting two different networks. Ie, an external ip address from your isp and your internal network.
Ensure that NAT (network address translation) is turned OFF on the 2nd router
Ensure that your 'wireless' devices can conntect with your 2nd router (SSID, password - if you use one, all devices in same workgroup, etc.)
I have a Netgear router that is the main router/gateway in and out of the network. Then I have a Linksys 54g router with WiFi that we use as are main WiFi access point
The Cat5 runs from the router to the WiFi routers LAN port (not WAN). And then if you connect to that WAP you are basically on the network.
I want to be able to find out what the IP address of that WAP is but so far I can't figure out how to:
Any ideas on how I can figure out how to administer it? (I do have limited physical access but my attempt to plug into it came back with a faulty IP (in the 169 range where the rest of the office is 192.168...).
I never set this router up to begin with so I'm reluctant to just kill it with the reset button because I can't get into see what the settings are set to.
Use Angry IP Scanner to see which devices on your subnet are listening on port 80.
Most routers do not show IP addresses for attached devices that are statically assigned, or are not assigned by their DHCP server.
It's also entirely possible that your Wifi is on a different subnet. This wouldn't have caused an issue previously, since your router is doing DHCP. Have you replaced or reset your modem since you had the Wifi put in? If so, try to manually set a computer to an IP address on that subnet, and run Angry again.
First, is your Wifi on another IP subnet than your "main" router? In other words, does the AP route between wireless and wired network or does it bridge the traffic?
To me it sounds like the latter - your AP is just a bridge between wifi and cable. Therefore, it does not use it's IP in the forwarding process - it's a layer2 device.
If it were a router, you would
If as you say, Tracert returns nothing, it pretty much means you are using a bridged gateway type device and without further information of the network, you are not going to find it remotely.
If you have physical access over the network, I would go to the machine that is your gateway, and see how that is set up, then go to that machines gateway and so on... Short of that, I do not think you will find it.