Wireless access point -> Powerline -> Router -> Internet, should this work?

My network at home used to be a laptop and desktop connected wirelessly to a single Wireless ADSL router, a Cisco 877W.

Wireless reception around the house with this setup was quite unreliable, so I've gone about looking to improve it.

I purchased some Belkin Gigabit powerline adapters and I've got these working fine. I can hook a computer up to one of the powerline adapters, and with the other one plugged into the ADSL router the computer has internet access.

Additionally I can hook a Netgear DG834G Wireless ADSL router into it with the adsl not plugged in, and after turning off DHCP can RJ45 a computer up to the network.

Everything works fine.

However, if I setup a wireless network on the Netgear then any computer that connects wirelessly to it cannot access the internet. It gets an IP address very slowly via DHCP which is a good one, but it cannot access the internet. It can however communicate with the RJ45'd computer also connected to the Netgear.

I wondered whether this could be a problem with the Netgear so I've borrowed a Cisco Aironet 1200 and got this working fine when it's attached directly to the primary ADSL router. I can connect to it wireless and get onto the internet.

However, if I then plug it into the Netgear I can communicate with other devices attached to the Netgear, but can't get any further than the Netgear.

All the while though the other devices RJ45'd to the Netgear are communicating with the internet just fine.

I'm starting to suspect it's one of two things causing the problem:

1) For some reason the belkin powerline adapters don't like carrying wireless-originating signals. Could this be possible?

2) The primary Cisco ADSL router doesn't want to communicate with other devices on my network more than one hop away from it. I'm making an assumption here that within the Netgear box the wireless and wired sides are handled differently. Could this be true?

Has anyone successfully setup something similar to what I'm trying, with a wireless device on the otherside of a pair of powerline connectors?

Update 06/07/2010 - Response to irrational John 28 June

Thanks for the answer John - and for clearing up some of my questions. The model number of the belkin powerline adapters are F5D4076. Security was apparently enabled by default on them, and I didn't change them from their default setting. The network diagram in your answer shows exactly what I'm trying to setup:

enter image description here

I've followed that guide and I'm still not able to get things working properly. The thing that perplexes me is that wired network traffic works just fine - it's only the wireless traffic that doesn't. This is with the same laptop, and the same DHCP or static IPs.

"1. What IP addresses did you assign to each router? What subnet masks are you using?" - subnet is 255.255.255.0, the router connected to the adsl is 192.168.153.1 and that has the DHCP server. The access point on the other side of the powerline adapters I've tried both a static IP of 192.168.153.110, same subnet, and a DHCP-assigned IP. The other devices are DHCP, although I also tried manually entering IP settings.

"2. Have you correctly enabled DHCP on only one of the routers and disabled it on all the others?" Yes I have - only the internet-connected router has DHCP enabled. The IP range for the DHCP is from 192.168.153.11 -> 192.168.153.200. The strange thing is that wired connections work fine on the LAN, plugged into any router, work fine - it's only the wireless connections that aren't working when they're plugged into the non-primary AP.

"Since the routers you are using appear to integrate an ADSL modem I'm assuming there is no WAN port on them." There's no NAT within the LAN, and all wired connections are connected to LAN ports. It's something wrong with the wireless - wired works fine throughout the whole LAN.

Update 06/07/2010 - Response to irrational John 29 June

The diagram you've drawn in your answer shows pretty much exactly what I'm trying to do. I've spent another evening trying different things and made some progress but I'm still scratching my head. I've borrowed a Netgear access point and been trying with this, and the strange thing is that my PC is working now - this is a Windows 7 PC connected to the access point in the position of where the DG834G is in the diagram. Meanwhile, however, I have an old Powerbook G4 12" I use for music, and while that has a DHCP-assigned IP address, it's not getting any network throughput to either LAN or internet addresses.

To make matters more strange, my phone appears to be intermittently working when it's on the wifi. The access point is a Netgear WPN802v1, DHCP, NAT both switched off, running firmware 2.0.9.0. Last night I set it up with exactly the same settings, and similar to tonight I could get a couple of devices to work, and a couple not to. By the morning, however, everything had stopped working - nothing could get a DHCP IP address. I rebooted the 877W earlier this evening and I'm wondering whether this is why a few things are working now.

"Could it be possible that the issue could be with the 877W?" I didn't configure this - is it possible that the DHCP server only likes assigning devices that are immediately attached to it? Or similar, could a firewall be stopping too many addresses that are coming through one device? (ie. the Access Point) This could explain why devices are working at the start but then not by the end.

In reply to your questions, "1. I looked at the Netgear DG834G support page. There are five versions of this router. Which version do you have? Netgear usually lists this on the label on the bottom of the router. What version of the firmware does it have?" It's a DG834Gv3, and the firmware is the last on the netgear site version 4.01.40.

"3. Not knowing which version you have, I glanced at the reference manual for the DG834G v3. In the section for Wireless Settings under the subsection Wireless Access Point there is a check box for a Wireless Isolation setting. If you have this setting it should be off/unchecked. If it is checked then any device connected via wireless would not be able to talk to any other device on the LAN. This sounds like your problem so maybe this is the cause?" I've checked this and it's switched off.

I've made a change to the IP of the access point to something outside the DHCP range - it's now 192.158.153.5, with DHCP starting at 11 and going up to 254. Thanks for the tip about this - I only have a few devices so wouldn't anticipate the DHCP server assigning up to 110, but better safe than sorry. Finally one more thing I thought I should add, is with the Powerbook G4 that's not working - it's getting a DHCP IP address and it can communicate with the WPN802 as I can visit the administration page. Anything further than this, however, it can't reach; I can't administrate the 192.168.153.1 (877W router). Strangely, however, when I open Finder on the same powerbook it's detecting my NAS which is attached directly via wire to the 877W. If I try to browse it, it says connection failed.

RE: "Perhaps the problem with your Powerbook is with DNS?.." The IP settings on the powerbook are identical to that of the PC with the exception of the IP address; the PC is 192.168.153.17 and the powerbook is 192.168.153.12. Subnets are the same, 255.255.255.0 and default gateway is the same, .1, and the DNS servers are the same. I administrate the 877W by going to 192.168.153.1 in the browser. This is what isn't working from the Powerbook, despite the PC working fine when I do the same. Meanwhile, however, I can administrate the AP on 192.168.153.5 from both PC and Powerbook

Update 06/07/2010 - FINAL RESOLUTION of sorts:

First off, sorry for the length of this question. I need start to practice a more concise writing style, so I'm going to try to keep this bit brief.

After much fiddling, and with the hugely-appreciated help of irrational John, I have come to the conclusion that it's something wrong with the powerbook.

I believe that this was perhaps the reason I doubted things worked at the very beginning.

I now have the original DG834Gv3 running both wirelessly and wired, and both wired devices and wireless devices get internet connectivity. The only anomaly is the powerbook which I've had to keep wired, as no matter what I do it refuses to work wirelessly.

I still have suspicions that the 877W isn't quite right; I'm fairly sure that if I RJ45 the powerline adapter into a different LAN port on it then everything will break. I've just about run out of patience to test this further, and I think I need to go into the 877W's config to match the 877w's lan port's settings.

I'm accepting irrational John's answer as he's been enormously helpful, way above the call of duty, and for this line he wrote:

Beats the heck out of me.

which in the midst of great frustration made me chuckle, and for a sentence in one of his comments to the same answer:

If it is specific to the Powerbook I would put that issue aside until after you feel you have the rest of your LAN and the additional WAP all working together correctlyt

It was this second sentence that made me put the powerbook aside and concentrate on the other devices that ultimately led me to getting things working.


Solution 1:

1) For some reason the belkin powerline adapters don't like carrying wireless-originating signals. Could this be possible?

No. This is not possible, at least not the way you asked the question. Powerline adapters try to come as close as is reasonable given their limitations to being a substitute for a length of Cat 5e ethernet cable. They would not care about the source of the ethernet packets they are exchanging. Indeed, I can not think of a way they could detect where a packet originated.

If you've done a simple verification test by directly connecting a computer to each powerline adapter to verify they can talk to each other then I would not suspect the powerline ethernet adapters.

A BTW which is not connected to your problem: You did enable the security on these adapters, yes? Also, it might possibly be helpful if you included the model number of your Belkin powerline adapters so people could look at their specs.

2) The primary Cisco ADSL router doesn't want to communicate with other devices on my network more than one hop away from it. I'm making an assumption here that within the Netgear box the wireless and wired sides are handled differently. Could this be true?

While as Hello71 suggested in his comment, some routers can filter wired and wireless traffic differently, I doubt this is the default behavior. So unless you have configured your router's behavior to limit connectivity, this is not the first place I would look.

Since what you are trying to do is add another Wireless Access Point to your existing network perhaps this guide on how to add a WAP to a LAN might be helpful to you. I believe the guide's network diagram matches the gist of what you are trying to do, no?


Update To Try to Figure Out What Works & What Does Not Work

Anthony, I'm afraid I may be lost. For this edit I'm mostly trying to get in synch. I discarded a lot of the questions I asked earlier because they no longer seemed pertinent. Also, the questions are repeated & answered in your comments below.

I kept the text diagram (below). It was also edited both to update it based on your comments and to correct a (stupid) mistake I noticed.

( Internet )
    |
 ( ISP )
    |
 [Cisco 877W ADSL modem]
    |
  ?.?.?.?  (external IP from ISP's DHCP)
 [Cisco 877W router] (NAT device, LAN DHCP: 192.168.x.11 to .254)
  192.168.x.1 (877W's fixed internal LAN IP)
    |___________________________________|
       |                           |
       |                           |
    [Belkin F5D4076]               |
      /|\                       [ PC1 ] 192.168.x.111
   powerline
      \|/
    [Belkin F5D4076]
       |
       |
 [Netgear DG834G v3 (4.01.40)] (WAP, NAT & DHCP disabled)
  192.168.x.5 (fixed LAN IP)
    |___________________________________|
       |                           :
       |                         Wi-Fi
       |                           :
    [ PC2 ] 192.168.x.112       [ PC3 ] 192.168.x.113


Here's where I think we're at with adding another WAP to your LAN.

  1. When you connect your Netgear DG834G v3 as shown in the diagram above, then you have wired LAN & WAN connectivity to the DG834G. But you are unable to access the LAN when using the wireless in the DG834G.

  2. When you substitute a Netgear WPN802 v1 for the DG834G and use the same configuration as above then you are able to connect to both LAN & WAN using both wired & wireless connections to the WPN802.

  3. Wireless access using the Cisco 877W works correctly.

  4. In the DG834G's Wireless Settings section you have

    • Enable Wireless Access Point enabled/checked.
    • Allow Broadcast Name (SSID) enabled/checked.
    • Wireless Isolation disabled/unchecked.

I hope the above is a correct summary.

If it is, then the remaining unanswered part of you question seems to me to be why you can't get wireless to work when using the DG834G. After all, the whole point of this was to use the DG834G as a WAP, no?

Beats the heck out of me.

But if the network configuration above allows wireless to "work" when using the WPN802 then it should also work when using the DG834G. It's just a matter of tracking down what it is about the DG834G that is keeping wireless from working for you.

Does your DG834G configuration have an Advanced Wireless Settings section? If it does make sure that WDS Mode, Enable Wireless Bridging & Repeating is not enabled/checked.

A request. If you have an update that is longer than a sentence or two, please add it by updating your original question. The comments section is not really well suited to or meant for an extended discussion. :-)


Update responding to FINAL RESOLUTION of sorts:

I now have the original DG834Gv3 running both wirelessly and wired, and both wired devices and wireless devices get internet connectivity.

&deity. be praised!!

The only anomaly is the powerbook which I've had to keep wired, as no matter what I do it refuses to work wirelessly.

It should work. I suggest either asking a new question here or trying another PowerPC Mac related discussion board. FWIW, you might try asking about this on the G-Group.

I still have suspicions that the 877W isn't quite right; I'm fairly sure that if I RJ45 the powerline adapter into a different LAN port on it then everything will break.

I don't see how this could happen. All the LAN ports on the 877W should be equivalent from a network access perspective. But at this point I can understand you reluctance to change anything.

Solution 2:

I have a very similar setup in my 3000 sq feet home. My cable modem and Cisco wireless router are in a corner office. With an ethernet cable, I run a Belkin Powerline adapter off the router to a nearby outlet. I have two other Belkin powerline connectors in other areas of the house connected via Ethernet cable to two other D-link access points.

Initially, I had both wireless connection and maintaining wireless connection problems. The only solution I found was to change the SSID of each D-link access point to a unique one (different than the main routers SSID); This means I had a total of three unique wireless access points from which I could connect to in my home.

I suspected that since both the router and the access points were set to roam to find the least used channels that they would often overlap by using the same SSID. I also found that by setting fixed channels for each access point and router was problematic as my neighborhood is congested with WiFi signals set to roaming channels.

I then switched to the 5 GHz spectrum. Most importantly, by configuring the access points to unique SSIDs, all my home wireless network problems were solved. My home is very well connected now with three iPads, four laptops, three iPods, three smart phones, two wireless home theater systems (AV receivers, TIVO, Blu-rays, Plasma TVs, all with wireless connections), X-box, PS3, PSP, wii, kindle, nook.

I merely programmed the passwords to each of the mobile devices for the router and two access points. The only minor inconvenience is switching to the strongest signal, depending on which area of the home that the mobile device is in. I find this is well worth the cost of having a wireless home network that actually works. I hope this solution works for you.