Sign in with
Sign up | Sign in
Your question
Solved

Can I wifi connect to an AP wired to the main modem/router?

Tags:
  • Routers
  • Wireless
  • LAN
  • Cable
  • Networking
Last response: in Networking
Share
November 10, 2011 12:43:04 AM

My room is at the far end of the house and doesn't have a LAN cable so I have to use wireless but I don't have a great signal. I get about half the rated speed. The other rooms do have LAN cables. I have cable internet on a modem/wireless N router Motorola Surfboard SBG6850.

Is it possible to hook up an access point to the LAN cable in the other room so that I can connect wirelessly to that AP and increase my speed and signal that way? The main router's wireless is also being used btw.

If not what other options can I do? I know there's a wireless repeater but I hear that cuts your speed in half, which I'm already getting.

More about : wifi connect wired main modem router

a b F Wireless
a b X LAN
November 10, 2011 12:50:22 AM

Yes, you can just drop a wireless access point at the nearest available ethernet port. In fact, many ppl grab an old router to save a few bucks. Just disable its DHCP server, assign it an IP address in the same subnet as the primary router (but not being hand-out by the primary router's DHCP server), and patch its LAN port to the ethernet port.
m
0
l
November 10, 2011 1:02:40 AM

Can you go into a little more detail about how to do that? I understand disabling the DHCP on the AP. What do you mean assign an IP address in the same subnet as the primary router?

m
0
l
Related resources
a b F Wireless
a b X LAN
November 10, 2011 1:19:53 AM

Let's assume your primary router has the IP address 192.168.1.1 (very common). Then your network is using the 192.168.1.x subnet, so you have the ability to assign additional IPs from 192.168.1.2 thru 192.168.1.254 (192.168.1.255 is reserved for broadcasts). But some of those IPs are "pooled" and being handed-out by the primary router's DHCP server, so don't use any from the pool.
m
0
l
November 10, 2011 1:31:38 AM

By pooled you mean an IP that's already in use? So pick something near the end of the subnet?

m
0
l
a b F Wireless
a b X LAN
November 10, 2011 1:58:23 AM

By pool I mean, a predefined range, perhaps 192.168.1.100 thru 192.168.1.199. You need to check w/ the primary router’s configuration to verify exactly what that range is. So you can use anything outside that range (lower or higher) except 192.168.1.1 (the primary router), 192.168.1.255 (the broadcast IP), and of course, any other devices that might be using a static IP (like you're about to do). You’re just trying to avoid IP conflicts and make sure no two devices are using the same IP.
m
0
l
November 10, 2011 2:28:47 AM

I looked everywhere in my router's page and I think this is what we're looking for

http://www.imagebam.com/image/0667ea158454040

Does CPE mean the pool of addresses the router will use? If so, it doesn't list the range so how will I know which address I can pick?

Also do I enter the static IP on the access point or the primary router or both?

I don't see a LAN port on the router. I see a WAN port, the 4 ethernet ports and an uplink port. Do I use the WAN?

thanks for the help btw. sorry this isn't going as easy as you or I hoped :/ 

m
0
l

Best solution

a b F Wireless
a b X LAN
November 10, 2011 2:50:12 AM

Sometimes they use a starting IP address, then a count (CPE). So your primary router starts @ 192.168.0.2 and goes up to 192.168.0.254, which is basically everything except the router (192.168.0.1) and the broadcast IP (192.168.0.255). That' overkill, and leaves you NOTHING available for a static IP assignment for the second router. You could easily reduce the count (CPE) to say 100, or even 50. Then use any IP above the new range. Or you could just change the starting IP to 192.168.0.3 and use 192.168.0.2 for the second router. Whichever you prefer.

You enter the static IP on the second router, the one you intend to use as a WAP (wireless access point), NOT the primary router. You’re only looking at the primary router to determine what IPs are available for static assignment (if any) to second router/WAP. There should be a webpage on the second router for setting the router’s IP.

You do NOT use the second router’s WAN in this configuration, only a LAN port (take your pick).
Share
November 10, 2011 3:05:29 AM

Ok I think I got it. I'll report back if I have any problems. Thanks again for the help!
m
0
l
November 12, 2011 3:04:45 PM

Ok after some frustration I was able to successfully set up the router as an access point and get connected. The part that I wasn't aware of was that I needed to create a static IP on MY computer. When you said to create a static IP on the second router I was looking at the broadband connections in the router where it says DHCP, Static IP, PPPoE, etc. and trying to set that up as the static ip.

And then everytime I disabled the DHCP my Windows Network Connections would get that yellow triangle that said Limited or No Connectivity and then I couldn't get back into the router and had to do a factory reset. But after reading many tutorials, most of which also didn't say to create a static IP on my computer (they basically said the same thing you did, change 2nd router ip to range outside main router's pool, disable dhcp, plug into lan port), I finally came across one telling me to create a static IP in my TCP/IP properties.

So I have a few more questions: when creating the static IP in TCP/IP properties should I set the DNS server's addresses to the 2nd router's IP address or to my ISP's DNS address?

And does the other person who is connecting to the AP through a LAN cable also need to create a static IP on his computer?
m
0
l
a b F Wireless
a b X LAN
November 12, 2011 5:33:45 PM

You do NOT have to use a static IP on your computer! The reason we disabled the DHCP server on the second router was precisely so that when your computer made a DHCP request on the network, it would bypass the second router's DHCP server (since it's not running) and move to the primary router (who's DHCP server is running). The only way I can imagine DHCP not working (assuming you did everything else correctly) is if you mistakenly connected the second router's WAN port to the LAN cable in the other room. As I said in my initially response, you connect them LAN to LAN, you never use the second router's WAN port in this configuration. You're only interested in the switch portion of the second router, which is defined as the LAN ports. The WAN port is for routing, which doesn't come into play here.

[primary router (192.168.1.1, dhcp enabled)](lan)<-- wire -->(lan)[second router (192.168.1.2, dhcp disabled)]<-- wireless -->[your computer]
m
0
l
November 12, 2011 5:56:43 PM

Hmm I don't know what is wrong. After I factory reset the router I connect a LAN cable from my computer to the LAN port on the 2nd router. I log in and change the router ip address to 192.168.0.200 and disable DHCP and UPNP. I save the setting. Then a few seconds later I get the yellow triangle Limited or No Connectivity. I can't get back in or do anything else with the router so I have to factory reset again

I don't know what I could have possibly messed up on in such a few steps. I have a D-Link DIR-601 router. I can show you with screenshots of what I'm doing if you need to see.
m
0
l
November 12, 2011 6:39:20 PM

Ok lemme ask something. If the 2nd router has DHCP disabled and I don't have a static ip set on my pc and the 2nd router is not connected to the primary router yet should I still be able to login into the 2nd router? Or do I have to wait until after I connect the 2nd to the 1st and then it will give me access to the 2nd router again?

Because after I disable DHCP on the 2nd router, if I don't set a static IP on my computer for the ethernet or the wireless device I won't be able to log back into the router to make anymore changes.
m
0
l
a b F Wireless
a b X LAN
November 12, 2011 6:46:37 PM

You're basically correct. If the second router is not connected to the primary router, then you don't have access to a DHCP server. And if your client is making DHCP requests, they go unanswered, and then your client isn't configured at all. And then you can't talk to even the second router. Yeah, a pain.

That's just part of the hassle in getting these things setup. Until the second router is talking to the first, you'll just have to manually configure your IP address. For example, if the second router is 192.168.1.2, then just make your computer 192.168.1.3 for now. You don't need anything else except the netmask (255.255.255.0), no gateway IP, no DNS, no nothing, just IP and mask.
m
0
l
November 12, 2011 8:23:04 PM

Alright I tested it all out and it works great. I was able to connect wirelessly and with LAN cable to the AP without assigning a static IP to my computer. Now next time I'll know if I set up another AP the very last thing I should do is disable DHCP! That had me confused!

So if I need to forward ports do I do it on the 2nd router or the primary router?
m
0
l
a b F Wireless
a b X LAN
November 12, 2011 8:46:13 PM

The second router is now just a bridge. Once it’s working, you can pretty much forget about it, it's just seamlessly passing data back and forth. Think of it as a "virtual wire". You do all your port forwarding where you've always done it, on the primary router.
m
0
l
November 12, 2011 9:04:13 PM

eibgrad said:
The second router is now just a bridge. Once it’s working, you can pretty much forget about it, it's just seamlessly passing data back and forth. Think of it as a "virtual wire". You do all your port forwarding where you've always done it, on the primary router.



Sweet man thanks so much for the help! I really appreciate it.

Oh one last thing, I promise. If I do decide to assign a static IP for my pc what do I enter for the DNS address? Do I have to put the AP's IP address or can I put my ISP's or google's DNS?

m
0
l
a b F Wireless
a b X LAN
November 12, 2011 9:16:37 PM

If you want to assign a static IP, I strongly suggest you stick w/ DHCP. Most DHCP servers allow you to bind a specific IP address to the MAC address of your network adapter. So even though you're using DHCP, you're assured you’ll always receive the same IP address, which is important for port forwarding (and why I believe you're asking). It's a lot better in the long run than manually assigning a static IP on the client for the very issue you're asking about; you get all the other stuff as usual (gateway IP, DNS servers, etc.). And if any of that changes (let’s say the ISP changes their DNS servers), those changes are propagated to your client thanks to DHCP.

But if you insist on manually assigning a static IP (or perhaps your router doesn't support static IP assignments in DHCP), then you can use whatever DNS server(s) you like, including Google's DNS, OpenDNS, or just take note of what DHCP returns and use that (probably your ISP's DNS server(s), or possibly the router itself).
m
0
l
November 12, 2011 9:31:46 PM

Ok I think I know how to do the static in dhcp. Thanks again for all the help! :hello: 
m
0
l
November 19, 2011 11:01:07 PM

Best answer selected by flyz.
m
0
l
!