Dear Voxel,There could be some incompatibility if flashing from 2.3.x.
Do not worry, I had to flash my internal versions about 20 times. And only one brick
Voxel.
I was able to reflash the router using Windows TFTP to 192.168.1.1 on latest stock firmware, then updated to your latest firmware. All seems good now. Was scared, thought I bricked it somehow.
Did you tried this one?How did you do that? I have the same problem. I cant connect to 192.168.1.1, reset doesnt help.
Please check with Ookla speedtest next time you face such degradation.
https://www.speedtest.net/
Voxel.
I'm not sure what I'm doing wrong, but I had my rbr50 go down after an hour on the custom firmware and won't start back up. When I follow these instructions, I get "Connect request failed" and a red blinking power led on the back of the orbi... these directions don't seem to be specific to the orbi, is there something different that I need to be doing?
Sorry I do not quite understand what you need. Guest network?There was a possibility to create multiple SSIDs with multiple network ranges. Is there a possibility with Voxel to archive this?
Thank you for your effort customised firmware
May be RBR will brick if we dont revert back to IP default (192.168.1.1) before flash your firmware or still keep connect with internet thought modem.
I my case was brick went flash your firmware but not yet disconnect to modem and IP not 192.168.1.1.
Another thing can we change connect to AX200 with 5G 1.73gbps (I mean exchange backhauls to another 5G transmission)
Sorry but I do not think it is because of using my version. I am still using my versions.I'm not sure what I'm doing wrong, but I had my rbr50 go down after an hour on the custom firmware and won't start back up. When I follow these instructions, I get "Connect request failed" and a red blinking power led on the back of the orbi...
these directions don't seem to be specific to the orbi, is there something different that I need to be doing?
This may be off topic but is there a way to do custom routing with this firmware? Basically I want to set up VPN client on the router and have only specific ports route through the VPN and everything else route normally.
I have a plex server running on a Mac Mini. I want the Mac Mini to connect to the internet using the VPN client running on the router but the Plex server to not use the VPN client on the router. All other devices on the network will not route through the VPN client running on the router.
Just curious if this is even an option with this firmware.
In running the netstat command I noticed that the Orbi is listening on port 3333. The process running is potval, which is related to the potd daemon. I looked online and apparently it is normal for this port to be open on the LAN side in Netgear routers. Port 3333 is closed on the WAN side. Any idea what this service is doing? I killed the process with no ill effects.
I'm not sure, but I will suggest to look specifically at item #22 in the support article - which is holding down the reset while powering back on. There is another NG article floating around on the web that is almost the same except that it omits holding down the reset while powering on, which is what was screwing me up for the longest time. I followed the article to the letter and it worked so not sure what else it could be.I'm not sure what I'm doing wrong, but I had my rbr50 go down after an hour on the custom firmware and won't start back up. When I follow these instructions, I get "Connect request failed" and a red blinking power led on the back of the orbi... these directions don't seem to be specific to the orbi, is there something different that I need to be doing?
Yes ussually they will not connecttion.I'm not sure what I'm doing wrong, but I had my rbr50 go down after an hour on the custom firmware and won't start back up. When I follow these instructions, I get "Connect request failed" and a red blinking power led on the back of the orbi... these directions don't seem to be specific to the orbi, is there something different that I need to be doing?
If it not work you can do another way:
- Turn router OFF for 10 seconds.
- Hold down the reset button on the back of router with a paper clip.
- Power ON the router while holding down the reset button.
- Watch the Power LED. It starts with an orange color, and then start flashing.
- Count at least 10 flashing power LED and release the reset button.
- Press Enter to execute the TFTP command. Wait for a few minutes (be patient, do not reboot the router). When the upload is successful, the Power LED will turn solid. The rest of LED’s on the router will also turn ON indicating that the router has booted up properly.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!