WNDR3400 and WDNR3700 Netgear routers with repeater

[Boneless]

I have both of these routers with the 3400 as my primary router and the 3700 as a bridge. I found out after setting it up that the 3700 will only support WEP. Is the only way to get more security by installing DD-WRT or Tomato firmware on it?

My other question is that I'm looking for the best option so that I can move from one end of my house using one Wifi, and seamlessly connect to the second Wifi when I walk into closer range to it. Is that possible or do I need to choose the network as I move away from the first and closer to the other?

[MaxRat]

if you set them with the same SSID and password it will do as you are wanting but the only issue is if problem arise it will be harder to trouble shoot...

I do this in my house but set different SSID for each... So far the range is good enough Windows based devices havent had to transfer but the Android ones automatically do to the stronger signal...

[Boneless]

Originally Posted by MaxRat if you set them with the same SSID and password it will do as you are wanting but the only issue is if problem arise it will be harder to trouble shoot... I do this in my house but set different SSID for each... So far the range is good enough Windows based devices havent had to transfer but the Android ones automatically do to the stronger signal...

So you're saying with the same SSID and password, the routers are basically seen as the same network, but it depends on the device whether they automatically switch to the stronger signal router? Security should be the same no matter which router is accessed I assume?

All you really had to do then, was make sure the second router have a distinct IP address and DHCP turned off correct?

I have tried the repeater setting in the 3700, but it disables WPA and I can't find a setting for WEP even though a google search says it should be supported. If I setup as you described above, I really don't need to use the repeater setting and can also get my security features?

[MaxRat]

Yes basically thats how it works... I dont have much faith in Netgear stuff as one of mine is a Netgear WNR2000v2 and it is working but not accessible...

there are many guides on how to do as you're wanting to do but the easiest is to just set it up and forget it.

I log in and turn OFF DHCP and then set the SSID and the Password and also the WiFi security....

You shouldnt have to set anything else other than the Device IP... the Default gateway will be the same beings both devices are the same maker...

The IP of the Access point should be just out of the range of the set 1st device... if the first device has the IP of 192.168.1.100 with DHCP being set at 101-199 you can set the access point device IP at 192.168.1.200 that way you can still log into it...

If you want you can also set the Access point as Static within the range and it will be seen via the first device and still work...

Hopefully you wont have issues like I did... netgear can be flaky at best sometimes..

EDIT: Here is the guide I followed... Keep in mind networking is not my specialty and can be a real hair pulling experience... this was pretty easy to follow and I got mine set up and working and its been a few months now...

http://www.speedguide.net/articles/h...ess-point-2556

[Boneless]

Originally Posted by MaxRat Yes basically thats how it works... I dont have much faith in Netgear stuff as one of mine is a Netgear WNR2000v2 and it is working but not accessible... there are many guides on how to do as you're wanting to do but the easiest is to just set it up and forget it. I log in and turn OFF DHCP and then set the SSID and the Password and also the WiFi security.... You shouldnt have to set anything else other than the Device IP... the Default gateway will be the same beings both devices are the same maker... The IP of the Access point should be just out of the range of the set 1st device... if the first device has the IP of 192.168.1.100 with DHCP being set at 101-199 you cant set the access point device IP at 192.168.1.200 that way you can still log into it... If you want you can also set the Access point as Static within the range and it will be seen via the first device and still work... Hopefully you wont have issues like I did... netgear can be flaky at best sometimes.. EDIT: Here is the guide I followed... Keep in mind networking is not my specialty and can be a real hair pulling experience... this was pretty easy to follow and I got mine set up and working and its been a few months now... SG :: How to set a Wireless Router as an Access Point

Above I think you meant "can" not "cant" right?

OT, Can I randomly assign IP's to devices outside of the router range without issues? Right now I just set static IP's for my most common devices just so I can identify what's on the network and out of habit when I used RealVNC before Logmein. Netgear Netgenie is pretty good about that.

Thanks for the link.

[MaxRat]

yes I meant Can.... sorry about that... I'm pretty sure you can statically set the IP outside the DHCP range and it will work... the range is just what the DHCP will auto-assign... I've always just set eveything inside the range and called it day...

I am sure someone more knowledgeable than me may have a better answer

[glc]

If you are assigning static IP's, you SHOULD assign them outside the DHCP scope (range), but they do have to be in the same subnet. I don't know what the default scope is with Netgear, but Linksys is usually 192.168.1.100 to 192.168.1.149 if I remember correctly. This can be adjusted and limited in the router setup.

You can only have ONE device providing DHCP services on a network, otherwise you will have conflicts.

[Boneless]

Originally Posted by glc If you are assigning static IP's, you SHOULD assign them outside the DHCP scope (range), but they do have to be in the same subnet. I don't know what the default scope is with Netgear, but Linksys is usually 192.168.1.100 to 192.168.1.149 if I remember correctly. This can be adjusted and limited in the router setup. You can only have ONE device providing DHCP services on a network, otherwise you will have conflicts.

I did not know about the importance of static IP being outside the range. In the netgear menu I assign static IP's to my devices so that I can see who's in the network and can easily identify who's not supposed to be there. I figured assigning a IP to the router would be just as easy and hassle-free but I can change it to outside the range if that's recommended.

[MaxRat]

if it is working I wouldn't mess with it. I think the whole reason to set the static IP outside the DHCP range is so you dont use up all the slots. On my DLink the DHCP is set 100-199 so I wont ever use all those and my media server is set inside that range and has been no issue....

[glc]

I *HAVE* had issues with that - I've seen routers that will want to assign an IP that's already in use by a static device.

[MaxRat]

On my netgear WNR2000 I would get that as well but not for the ones that were static... weird issue... not sure why the DHCP would assign the same IP to another machine on the same subnet but it did once in a while...

Thats a good tip to know though for future reference.