NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
How to avoid subnet with JWNR2010v5
hello, I have now read countless threads about this, but this seems to not work whatever I do.
I have bought a JWNR2010v5 and I would like to use it as a second access point to extend my wireless signal in a far away portion of the home, where the wireless signal from my main router is weak but where I was able to carry an ethernet cable.
I cannot seem to be able to avoid creating a subnet with the JWNR2010v5.
I have tried both:
CASE A)
main router connected to WAN port of Netgear.
Netgear is happy because it sees internet, gets a DHCP address from my main router, creates a subnet.
everything works but I would like to get rid of the Netgear subnet and have everything on the LAN created by my main router.
CASE B)
main router connected to LAN port of Netgear, DHCP for Netgear disabled.
Netgear is NOT happy since it does not see internet access.
wired computers connected to the other LAN ports of Netgear are switched on the main router's network and work great.
wireless computers connected to the Netgear wifi do NOT get an IP address, thus are stuck in a limbo.
how can I accomplish a simple no DHCP, no NAT mode for my Netgear router?
I only want a single subnet!
thanks. bye
downgraded firmware to v54 -- everything works as expected now!
the 403 Forbidden bug was quite annoying and, I guess, was what made me stray from the suggested steps in the tutorial.
16 Replies
> [...] I have now read countless threads about this, [...]
Think, for a moment, about how little useful information that
non-description conveys to the non-psychics in your audience.> I have bought a JWNR2010v5 and I would like to use it as a second
> access point [...]Ok. You need to configure your JWNR2010v5 as a wireless access
point. According to its User Manual, it doesn't have a convenient
option to do that.> CASE A)
It's still a router, which is not what you want.
> CASE B)
> main router connected to LAN port of Netgear, DHCP for Netgear
> disabled.
That's closer.> Netgear is NOT happy since it does not see internet access.
What, exactly, does "NOT happy" mean to you, and how, exactly, did
you decide that "does not see internet access" (whatever that means) is
the reason?It's not obvious to me why your "CASE B)" does not work.
There's a detailed procedure for configuring (almost?) any wireless
router as a WAP here:https://community.netgear.com/t5/x/x/m-p/1463500
That's written for a Netgear C6300-as-WAP, but the steps are about the
same for any other router (any make/model) which lacks a one-step WAP
option. But the essence is disable the DHCP server, and use a LAN port.
I know nothing, but I can imagine that the JWNR2010v5 firmware has
some defect/quirk which affects only its wireless client devices.> Think, for a moment, about how little useful information that
> non-description conveys to the non-psychics in your audience.my first sentence was only to say that I am not a complete newbie who comes to the forums for easy help without having tried anything first, but rather I've spent several days reading through any thread I could find and I've wasted a full day trying to make it work.
sorry if that was not clear.> Ok. You need to configure your JWNR2010v5 as a wireless access
> point. According to its User Manual, it doesn't have a convenient
> option to do that.that's fine, I am willing to painstakingly set up everything as needed.
> What, exactly, does "NOT happy" mean to you, and how, exactly, did
> you decide that "does not see internet access" (whatever that means) is
> the reason?since the ethernet cable going to my main router is connected to the LAN port, the WAN port is empty.
the Netgear complains a lot about that, and insists quite often that I re-do the entire setup wizard.
I do not think the Netgear is happy about having an empty WAN port.
also, with an empty WAN port, the Netgear does not pick up an IP address from my main router's DHCP server.> It's not obvious to me why your "CASE B)" does not work.
> There's a detailed procedure for configuring (almost?) any wireless
> router as a WAP here:that's exactly what I have read and followed.
> But the essence is disable the DHCP server, and use a LAN port.
I thought so too, but there are a couple of issues:
- the Netgear does not pick up an IP address from my main router, which might be expected but is certainly weird to me (no Netgear dashboard in this config),
- the wired clients are correctly switched to the DHCP of the main router and pick up an address,
- the wireless clients are not switched to the DHCP and never pick up an address.> I know nothing, but I can imagine that the JWNR2010v5 firmware has
> some defect/quirk which affects only its wireless client devices.for the record, I bought this Netgear and it had firmware V1.1.0.62_1.0.1 by default, while online the official Netgear product page says the last version is v54.
anyway, I fear there might be some bug in the firmware preventing this operation at all!it feels like the Netgear still advertises itself as DNS even though I disabled the DHCP, and therefore, since it has no knowledge of the main router's DHCP or network, cannot do anything at all and gets stuck in limbo.
I did post another reply but it got lost somehow.
anyway, thanks for helping out!> [...] sorry if that was not clear.
I got the opposite impression.
> [...] with an empty WAN port, the Netgear does not pick up an IP
> address from my main router's DHCP server.That's to be expected. On the models/versions which offer the
one-step WAP option, using DHCP is the default ("Get dynamically from
existing router"). With the ad-hoc scheme, you need to assign its LAN
interface a static IP address, which is the primary complicating factor
in that procedure.> it feels like the Netgear still advertises itself as DNS even though I
> disabled the DHCP, and therefore, since it has no knowledge of the main
> router's DHCP or network, cannot do anything at all and gets stuck in
> limbo.Ask a client device what it's using? I know nothing, but I wouldn't
be amazed if it intercepted DNS requests, and then mishandled them.
> anyway, thanks for helping out!Wish I could do more. I've seen scheme this work on more than a few
old-junk routers, but it can be defeated by quirky firmware. And, in my
book, at least, works-for-wired and fails-for-wireless qualifies as
quirky.