[bnam]

I have an Asus RT-N66U as my main router. For a couple of years now, I had been using a Netgear WNDR3300 as a bridge router. But moved to a new house and decided to install the Netgear as a repeater bridge. I was on the old firmware 13064 (IIRC) and upgraded via GUI to a newer firmware.

The problem is within a few minutes of turning on the WNDR3300 (which is upstairs), my ASUS router stops working -- both wifi and ethernet stop working.

I initially thought it was the ACT internet issue, but the ACT techs came over and their optical fiber connection is fine. They noticed the Asus was hot. I turned off the WNDR3300 and let the Asus stay off for a minute. Turned the Asus back on. It works with no issues.

I'll try turning on the WNDR again after I post this, in case I get disconnected. Is it possible that the WNDR is somehow overloading the ASUS? The TX power on the WNDR (I happened to notice while setting it up) is at 71mw.

Any other possibilities?

Thanks!
Byas

[jwh7]

[bnam]

I'm using SVN revision 23919 from this thread

http://www.dd-wrt.com/phpBB2/viewtopic.php?t=257862&highlight=wndr3300

Only on the Netgear. Asus is running stock FW (latest rev).

Here's a pic from a an app called NetSpot that shows my Asus and Netgear Bluenet SSIDs. A



I just turned it on for a moment to get this. The network and even the bridge worked for about 30secs. After that Wifi and Ethernet connection at the Asus was lost and my ipad would not even show a wifi icon on top.

So, have turned the Netgear off for now. Would like to fix it though.

I followed the Wiki to a T while setting up the repeater bridge. I first copied the settings from Bluenet for mode, security, channel, etc and replicated them on the RB and the virtual interface.


Byas

[bnam]

If there is some conflict (that's perhaps causing 100% cpu on the asus and shutting it down), how do I go about identifying this?

Thx!
Byas

[nolimitz]

[bnam]

I reset (had to do it twice) and reconfigured. First disabled WAN, disabled DHCP, set IP/Gateway/DNS, then applied and rebooted. Logged into new IP, set Wireless Physical and Virtual, Wireless security, and Firewall.

Applied and rebooted. This time it booted up and did not crash my Router. Wifi was working on the repeater bridge, but the bridge router was not connecting to the main router (so no internet).

Did it all over again -- this time it crashed the Asus again.

Got fed up and threw it in the closet. Will probably buy a repeater/extender.

Frustrated!!

Byas

[Per Yngve Berg]

Here is dd-wrt dor RT-N66U: ftp://ftp.dd-wrt.com/betas/2017/06-01-2017-r32170/broadcom_K3X/dd-wrt.v24-32170_NEWD-2_K3.x-big-RT-N66U.trx

What CFE version does your RT-N66U have?

Some are shipped with 1.0.1.2. this one is bad. 1.0.1.3-9 is OK

Don't use 1.0.2.x as it have the new lock-down as required by the FCC.

[bnam]

The Asus is stock. The Bridge repeater is Netgear WNDR3300 on dd-wrt.

Byas

[mrjcd]

What local IP / subnetmask and DHCP range does the ASUS have set?
What IP do you have set for the Netgear Repeater Bridge?

[bnam]

ASUS - main router
IP 192.168.1.1
Subnet mask 255.255.255.0
IP pool starting 192.168.1.2, ending @254

WNDR3300 on dd-wrt as bridge repeater
IP 192.168.1.200
subnet mask 255.255.255.0
gateway 192.168.1.1
dns 192.168.1.1

Does the repeater bridge IP have to be outside the DHCP pool of the main router (but on same subnet)? i.e. should I be setting the DHCP pool say starting from 192.168.1.2 to 135 and set the repeater bridge to a number between 136 and 255?

Thanks!
Byas

[egc]

Yes, static addresses have to be outside the DHCP pool. Normally you start the pool at 100 and end at 150. adresses below 100 are used for static leases.
Other routers and server are usually 2 to 10. So set your second router at 192.168.1.2 (and of course start DHCP at 100)

[bnam]

So, did that. ASUS ip range 192.168.1.15 to 254. Repeater bridge 192.168.1.2

Did the setup page and applied. Logged back in with 192.168.1.2.

Did all the other changes. And applied. I kept the Asus router running. The repeater bridge was running but still not connecting.

I tried connecting back to the repeater bridge (first turned the Asus off, and rebooted my PC, turned my Wifi off and connected via ehternet). It would not now connect at 192.168.1.2. When I did ipconfig in the cmd box, it showed me a 169.x.x.x IP (I did not write it down) for Ethernet.

So, did a 30/30/30 reset, rebooted laptop and tried again. Since the last thing I did was the Security page, I thought I try chaging that first. So, changed the Setup page settings, applied. Logged into 192.168.1.2 and went to security and unchecked everything except multicast and disabled spi. saved. Applied. No longer able to log back into 192.168.1.2.

Though it maybe something on that page. So left that page alone. next try. Did the setup page again. Then the wireless settings. Saved and Applied. Still able to connect at 192.168.1.2. Then went to wireless security. I only set wireless security on one of the radios wl1 (left security disabled for wl0). Saved, applied. Now not able to connect with 192.168.1.2.

I can see 2 Netgear radios on -- one with security and other open when I use Netspot on another computer. But, I'm no longer able to connect back to repeater bridge gui thru 192.168.1.2. IPCONFIG shows Ethernet connected to 169.254.246.205. If I ping it, I get host unreachable. (BTW, this is with Asus router back on). BUT, I am NOW CONNECTED to the INTERNET.

I just need to be able to log back into the repeater bridge and set security for WL0. But, how do I log back in?

Thanks!
Byas

[mrjcd]

I have no idea that the build you are using will even support repeater bridge.
What I would do:
Install mini 25974 or mini 26125
ftp://ftp.dd-wrt.com/betas/2015/

Do not create a VAP until you have a working connection between the main and your netgear router.
You should have a static IP set on your computer and only have the repeater bridge router plugged to it.
You can easily see in wireless status if it is connected to main.
If it shows connected then you can set computer back to DHCP and get IP from your main router and should then be able to have internet access.
If that is working then create a VAP for wireless clients to connect. You will probably have to reboot after makeing the VAP and creating ths password.....may take a few minutes after reboot before all connects.

[nolimitz]

Or use an old Build, i use 14929 on two devices as repeater bridges and no complaints.

[hubermania]