NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
R7000 in Bridge mode
Hello I am trying to setup my Nighthawk R7000 ac1900 in bridge mode, but I am running into some issues. Here is my setup: Arris TG4482A Gateway -wifi-> R7000 Router(bridge) -ethernet-> Computer ...
Ok, loaded v.136 FW file on to R7000 while in bridge mode. It came back to ready and working.
I powered it OFF for 30 seconds then back ON. Still going:
Will monitor.
Thank you for trying all those tests!
I wanted to change my channel, but it looks like its not an option on my gateway anymore…(thanks to a sneaky firmware update on their end..)
I downgraded the firmware to v126 to see if it helped, no luck.
Is there any settings I would need to do on my gateway part maybe?
Also, when re-doing a “fresh” install, comparing to your “status”, it said that the DHCP Client was still On, i thought it would automatically go off once its in bridge mode no?
I am pretty much a beginner in those kind of things, thank you for your help!
I wanted to change my channel, but it looks like its not an option on my gateway anymore…(thanks to a sneaky firmware update on their end..)
I downgraded the firmware to v126 to see if it helped, no luck.
Is there any settings I would need to do on my gateway part maybe?
Also, when re-doing a “fresh” install, comparing to your “status”, it said that the DHCP Client was still On, i thought it would automatically go off once its in bridge mode no?
I am pretty much a beginner in those kind of things, thank you for your help!
So after I upgraded to v.136, I came to find my one wired PC connected to the R7000 in bridge mode had no internet.
I found the I could still access the web UI and debug page.
Connection rate reports zero:
The RAXE500 reported it being a connected device but no IP address. I saw this even when the R7000 was working. Probably the static IP set instead of Dynamic.
Seem to fail in about 19 hours:
I did a power cycle on the R7000 and it came back to ready. I noticed the connection rate isn't displayed properly:
Should be 1300.
So after the R7000 was power cycled, I re-loaded v.126 back on the router and did another power cycle. It may not be stable either. After it was back online, I had to switch my one wired PC to a different router and connection to check something there. It was disabled from the router using the ethernet enable or disable option. It was disabled for about 30 minutes when I came back to enable the connection with the R7000 bridge mode and the PC didn't get internet. I logged into the R7000 and found the Internet status was Disconnected again. I power cycled the R7000 and it's now back. I need to try a factory reset and setup from scratch to see if this cleares this behavior or not. Going to give this 1 hour with the PC connected to see if the R7000 stop working. IF not, then FR. Wondering if something stops working if nothing is connected or there is no internet traffic happening.
As of now 1300Mpbs is seen and DHCP reports being OFF with v.126 loaded:
jfg2 wrote:
Thank you for trying all those tests!
I wanted to change my channel, but it looks like its not an option on my gateway anymore…(thanks to a sneaky firmware update on their end..)
Can you ask the ISP to change the channels? Try 40 or 48 or 149 on the ISP modem
I downgraded the firmware to v126 to see if it helped, no luck.
Did you factory reset and setup from scratch after you installed the FW?
Is there any settings I would need to do on my gateway part maybe?
Be sure any Smart Connect is disabled.
Also, when re-doing a “fresh” install, comparing to your “status”, it said that the DHCP Client was still On, i thought it would automatically go off once its in bridge mode no?
I am pretty much a beginner in those kind of things, thank you for your help!>If the FW isn't stable, the router is of age now and not sure if NG will do anything to fix it.
Just to let you know I've left my R7000 up over the weekend. Been almost 4 days, still up and running good in brige mode. FW v.126 seems to be the most stable. Not sure what's wrong with v.13x versions.