RBR50 + satellite randomly disconnecting specific devices from internet

Hi, all,

I confirmed the following with tech support this AM:

- DST and TM interact and crash dnsmasq, killing DHCP and DNS relay

- the current recommended fix is to disable either DST or TM and appears to be stable

- a firmware fix is in the works and will be posted when ready

I also noted the following two issues:

1. IPv6 DNS override does not work; the address entered is not correctly saved in /tmp/resolv.conf as it is for IPv4

2. IPv6 DNS override fields are too narrow (3 characters), though you can just type 4 characters in the fields

3. DNS override on Orbi devices sets the DNS for the router; the DNS for clients (provided in DHCP) is always the IP of the router, not the IP of the DNS; this is a widely-known deficieny in the Netgear graphical interface (there are ways to override via the debug console)

Did support mention that this DST fiasco appears to only effect those with latest firmware?  I'm on a older version and never blinked an eye 

There are reports of this affecting other firmware versions too.

---

l8nc wrote:

There are reports of this affecting other firmware versions too.

 

---

Not mine 

It does appear the 104 version is much more predictable in how it fails.

If you're running an earlier version, can you please post the following:

- which version of RBR50? (v1 has USB ports; v2 does not)

- which version of firmware on both router and satellite?

- is DST set?

- is TM set?

---

l8nc wrote:

It does appear the 104 version is much more predictable in how it fails.

 

If you're running an earlier version, can you please post the following:

- which version of RBR50? (v1 has USB ports; v2 does not)

- which version of firmware on both router and satellite?

- is DST set?

- is TM set?

 

v2.5.2.4

v1

 

yes

 

no

If you set DST=yes and TM=no, you're using the fix that we already know works with v104 too.

I.e., your example of using old firmware is NOT shown as an alternate sollution; it uses the same fix.

---

l8nc wrote:

If you set DST=yes and TM=no, you're using the fix that we already know works with v104 too.

 

I.e., your example of using old firmware is NOT shown as an alternate sollution; it uses the same fix.

 

---

Nice

but my firmware never needed a fix for it was never broken 

it sounds what you're trying to say is the latest wizbang firmware couldn't handle TM 

or....if I set TM on my old firmware there would be hell to pay ???

---

vajim wrote:

---

l8nc wrote:

If you set DST=yes and TM=no, you're using the fix that we already know works with v104 too.

 

I.e., your example of using old firmware is NOT shown as an alternate sollution; it uses the same fix.

 

---

Nice

 

but my firmware never needed a fix for it was never broken 

 

it sounds what you're trying to say is the latest wizbang firmware couldn't handle TM 

 

or....if I set TM on my old firmware there would be hell to pay ???

---

I don't know; the more recent firmware does protect you better against cyber attacks though.

The only way to know if this woud happen with DST+TM on your firmware is to test; the worst that happens is you lose DNS and DHCP; you can always login to your router, change the settings back, and reboot it to fix.

---

l8nc wrote:

---

vajim wrote:

---

l8nc wrote:

If you set DST=yes and TM=no, you're using the fix that we already know works with v104 too.

 

I.e., your example of using old firmware is NOT shown as an alternate sollution; it uses the same fix.

 

---

Nice

 

but my firmware never needed a fix for it was never broken 

 

it sounds what you're trying to say is the latest wizbang firmware couldn't handle TM 

 

or....if I set TM on my old firmware there would be hell to pay ???

---

I don't know; the more recent firmware does protect you better against cyber attacks though.

 

The only way to know if this woud happen with DST+TM on your firmware is to test; the worst that happens is you lose DNS and DHCP; you can always login to your router, change the settings back, and reboot it to fix.

---

No to the TM. Not interested 

still waiting on the cyber attack 

I might honestly just roll it back again. What firmware are you using?

I'm on the latest firmware right now, with DST on and TM off and the disconnects are constant, not intermittent but basically constant on my wifi devices.

---

CaptainPing wrote:

I might honestly just roll it back again. What firmware are you using?

 

I'm on the latest firmware right now, with DST on and TM off and the disconnects are constant, not intermittent but basically constant on my wifi devices.

 

---

im on 2.5.2.4 but i doubt you can find it available

unless you have a copy of a older version, you might check the download area, enter your model number and see what is listed.

v4 doesn't have any new security updates and was deemed insecure to use. 

Thought it's still up on NG download site. 

Thought downgrading might not help. 

Good Luck. 

---

CaptainPing wrote:

I might honestly just roll it back again. What firmware are you using?

 

I'm on the latest firmware right now, with DST on and TM off and the disconnects are constant, not intermittent but basically constant on my wifi devices.

 

---

---

FURRYe38 wrote:

v4 doesn't have any new security updates and was deemed insecure to use. 

Thought it's still up on NG download site. 

Thought downgrading might not help. 

 

was that one you pushed?

---

 

---

What version did you end up with? 

V2.5.2.4

---

CaptainPing wrote:

V2.5.2.4

---

same as me...nice work