Sorry, this one here http://www.amazon.co.uk/Zoom-Wireless-Range-Extender-Access/dp/B007SU05SW/ref=sr_1_2?ie=UTF8&qid=1348350406&sr=8-2
Model number 4403
It seems that device has several options of how it can be used - as a router, a client bridge or a repeater.
It sounds like you are trying to set it up as a repeater. (BTW, that will at least half your wi-fi bandwidth (ever erroneously referred to as "speed") and introduce a bit more latency (lag.))
Most wi-fi devices don't need an IP address in order to "work" - the IP addres is only there so you can connect to the device to administer it. And that IP address will need to be in the same range as your SuperHub - what IP address doe this have...?
Wi-fi repeaters listed out to the airwaves, grab the packets out of the air, wait for the airwaves to go quiet, then broadcast a verbatim copy of the original transmissions. As such, they are probably "invisible" to client devices (and possibly their parent routers) and thus shouldn't need much in the way of setting up apart from telling it which router to "repeat." ie. repeater don't have their own SSID, passphrase, etc. etc. as they are simply echoing what the SuperHub broadcasts.
I suggest you grab the Zoom's manual and carefully work through the section on configuring it as a repeater.
Don't forget that a repeater will need to be "in range" of the router and the relevant client devices so that it can "hear" the relevant transmissions.
However, because of the bandwidth clobbering, I wouldn't use repeating unless I had no other choice. Much better would be to use multiple Access Points to create a "cellular" coverage pattern and to achieve that, the outpost AP's need to be cabled back to your main router, either using "proper" UTP network cables, or tunnelled over the mains using HomePlugs.
Yes, that's what option I was going for but it should still have kept the LAN ports available going by the manual
In my original post, 192.168.2.1, the superhub is 192.168.0.1 with DHCP range 192.168.0.2 to 254
It was hybrid mode which should have kept the LAN's available. It can go in WDS, AP or hybrid and hybrid should keep the ports open.
I worked through the manual, it's on a cd, but I looked on Virgin's forums and they seem to say the superhub doesn't support WDS, which might be the issue. Looks like I'm going to have to go down the homeplug route, thanks for taking a look for me.
That's probably why you cannot "talk" to both devices to configure them - presuming the subnet mask of your LAN is 255.255.255.0 (most SOHO's are) then the AP is on the "wrong" subnet compared to everything else. Change your AP to 192.168.0.X where X is not in use by anything else, and not within the DHCP range server out by your SuperHub (which might mean you have to change the SuperHub DHCP range a little.)
I can't really comment on the "AP" versus "hybrid" mode and whether LAN ports should or shouldn't be working as I don't know your device.
A "pure" wi-fi repeater would disable the LAN ports as they are irrelevant in such a configuration, hence would have no use for them. If they are being left active, then (I'd argue) your device isn't "repeating" it's doing something else.
If "hybrid" mode is something designed to avail both AP mode and/or "bridge" mode as well as "repeating," then maybe the LAN ports should work, but I'd have to read the manual for you to check that, and my altruism does have some limits!
Maybe it would be worth you setting up your AP in each of it's various modes (AP, repeater, router, etc.) so you can gain an understanding of how each works, then use that knowledge to determine what the various "hybrid" modes are all about.
Hi, I changed it to 192.168.0.254 which is the last address in the DHCP range, should be far enough out not to conflict any other devices but then I couldn't access the router using the new IP.
Hybrid appears to be a mix of the WDS (repeater) and AP. according to the manual, when I get home tonight I can post up the section on setting the device in repeater mode which is where this hybrid mode is mentioned.
I lose wifi signal when I go from my living room (downstairs) to the bedroom (upstairs) data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7
If I run an ethernet cable from the sky router downstairs to the spare sky router somewhere upstairs and follow the guide on the first page then I should get wifi reception upstairs?
Yes. It will certainly be better, though obviously one cannot make absolute predictions without seeing your home.
After trawling through the wise words of this thread, I'm still unsure as to the best way forward. So, if I may...
Setup is this -
OFFICE
Cisco Linksys router, through which I'm running two PC's within the office, connecting via a Devolo dLAN 500. There is also a Devolo dLAN Highspeed II plug on a separate ringmain. The former of the Devolo plugs is actually powered via my primary ringmain, in order for it to be on the same ringmain as its companion dLAN 500, which is located in my lounge.
LOUNGE
Samsung smart TV, Home Cinema and Laptop, all hooked up to the Net via a Devolo dLAN 500.
Secondary Office
PC linked to Linksys router via Devolo dLAN Highspeed II plug, on separate ringmain to the Devolo dLAN 500.
Dining Room
Laptop linked to Linksys router via Devolo dLAN Highspeed II plug, on separate ringmain to the Devolo dLAN 500.
Problem -
While the above works very well, I would ideally like to regain the use of wifi in my lounge. I'm using powerline products because the insulation makes wif-fi impossible. I'm hoping that I can add something that will gain wi-fi access for tablets, etc.
Is there an uncomplicated way to do this? I gather that with effort I could add a secondary router? But, I'm wondering if there is another bit of kit that would, of necessity, plug in to theDevolo dLAN 500, and make life easier. Any recommendations appreciated.
Hey Buddy thanks for the info.. you saved me a few bucks ;p
Hey Buddy, so nice of you to paste the all important info over here, i was scratching my head from last 6 hours.. Thanks for the cool info.. the one thing i was missing was the similar ssid for both networks data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7 you solved it .. thanks a lot data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7 data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7