RBK53 - Clarification on Ethernet Backhaul Set-Up

Well I am about to have to give up again having spent another night at it.  family going made at me for WiFi being down :-(

i am positive I am missing something stupid but I don’t know what it is.

i factory reset everything in, went through the normal set up process with the router.  Added only one satellite wirelessly during the setup process.

switched the set up to AP mode which you have to do after the initial set up process.

i then tried to unplug the satellite, plug in Ethernet and then power back up the satellite.

i then sit there watching the attached devices in the desperate hope satelite may appear in attached satellites field as backhaul, but it only appears in attached devices and the IP address keeps changing from 192.168.1.4 and 192.168.1.250

the moment I unplug the Ethernet cable the ip goes back to 192.168.1.4 and it shows as an attached satellite with 5g connection.

i have tried the cables through my switch and I have tried daisy chain from on router to the next.  I have tried with yellow port, without yellow port, if I had a blue port I would try that too but I dont🤫.  I really don’t know what else to try.

interestingly, even when the address shows as 250 in attached devices I can still connect to .4 on a browser.  I am convinced it is still trying to connect wirelessly and gets its knickers in a complete twist.

any ideas......

Well you don't have to turn OFF the Satellite before you plug in the ethernet cable. I didn't and mine set up in about 2 minutes after I plugged in the cable.

Can you use the Orbi in router mode and see if the operation is different? Set up the DMZ on the ISP modem for the routers IP address. Disable uPnP and wireless if any, on the modem.

Other features disabled? Im only using Beamforming. 40feet between router and satellite.

Does the system run ok with out using the ethernet cable. Ensure LAN cables are of good quality and CAT6.

I tried all sorts to be honest. What is interesting to me is that I get the same experience no matter how I do it or it what order.  The satellite gets mixed up with the 250 ip address.

i may give router mode a go although I wanted to avoid messing with my broadband router if possible.

the cables are cat6 or cat 5e, tried different ones.  My WiFi on the modem router is off.

thanks for the support on this, I am sure eventually I will get it working, perhaps...maybe....

you asked about in wireless set up, I have had some issues which is why I am trying Ethernet.  I am trying to isolate the issue when in wireless mode, it seems related to a DFS radar issue in the log, I feel that may have something to do with being close to my Sonos system, so I have moved the satellite away to see if that makes a difference.

i am seriously thinking of returning and just trying another make and model of the same sort of thing.

FFS!!!!  

i was just reading a few posts and noticed that Ethernet Backhaul is supported on version 2.1.xxx

i am on version 2.0.14

is this the problem?  I just assumed as I updated the firmware on install that it would pick up the latest version!!!!

can anyone advise what version is stable and that works and I will give that a go!

i knew it may be a simple problem.

doh!

Lets try with out the Sonos being online or ON. Turn it OFF. these have there own wifi broadcast.

I would try router mode and use input the IP address it gets into the modems DMZ. Set up the router first. I would do this, just run the router alone for a bit. See if you notice any issues with any if your devices.

What neighbors are near by and what channels are they using? If any?

You can try the new beta firmware since quite a few users have posted that it is stable.

https://community.netgear.com/t5/Orbi/Orbi-MR-2-1-Update-3-23-18/m-p/1533584#M26234%C2%A0

Quick reply.

updated to 2.1.3.4

wired backhaul appears to have worked ok.  Am still testing the setup but things looking ok so far.

both satellites had a little trouble initially after plugging in cable, flicking between IP address of .3 or .4 (depending on the device) and .250.  However full reboots of each have stopped this for the time being.

will continue to test over the next few days then come back and report this closed and resolved.

Apologies for making the mistake on the firmware, I just assumed that when you auto update it would install the latest and greatest.  Thanks for all your support.

oh by the way....router plugged into yellow WAN port ;-)

Glad it seems to be working better. Ya, I thought you had already updated. hehe. 

Keep us posted. Should be good now. 

---

ElCapowrote:

Quick reply.

 

updated to 2.1.3.4

 

wired backhaul appears to have worked ok.  Am still testing the setup but things looking ok so far.

 

both satellites had a little trouble initially after plugging in cable, flicking between IP address of .3 or .4 (depending on the device) and .250.  However full reboots of each have stopped this for the time being.

 

will continue to test over the next few days then come back and report this closed and resolved.

 

Apologies for making the mistake on the firmware, I just assumed that when you auto update it would install the latest and greatest.  Thanks for all your support.

 

oh by the way....router plugged into yellow WAN port ;-)

---

Glad you got it working well. Enjoy. :smileywink:

---

ElCapo wrote:

OK..

 

Just touching base after a couple of weeks of testing.

 

As soon as I changed to Firmware 2.1.3.4 I was able to set up the Ethernet Backhaul.  A quick check with IPERF3 showed good speeds across the network both wireless and wired.  So far since last update everything has been stable.

 

Couple of points:

 

- My Orbi Router (in AP Mode) is connected to my Broadband Router via Ethernet into the Yellow WAN port

- My 2 x Orbi Satellites are connected to the Broadband Router via daisy chained un-managed switches

- After setting up the two satellites wirelessly first, then moving one by one to Ethernet I did see their IP addresses on the Router Conntection Page flick between 192.168.1.x (x being the actual address) and 192.168.1.250.  Once I restarted each device this ceased to happen and they settled on the 192.168.1.x address.

 

Thanks to all support on this post.

---