@CrimpOn wrote:
The Advanced Setting on page 10 do not have anything resembling "Block Sites"?
https://www.bt.com/content/dam/bt/help/legacy-ug/new-pdf/BT%20Smart%20Hub%20(Type%20B)%20Fibre%20to%...
Alas not no 😞
@CrimpOn wrote:
There are only two methods to prevent the Orbi from auto-updating firmware:
- Put a router between the Orbi and the Internet and use it to block access to the Netgear update web sites.
(Shame that the BT Advanced Settings will not do that.)
Because this will create a Double (or Triple) NAT, the Orbi will probably be better off in AP mode.
In your case, this leaves you with a Double NAT to get around. Does the BT Hub offer a DMZ? - Use telnet to change the file firmware_version in the Orbi root directory to begin with a number larger than the latest firmware.
V2.7.3.22 is the latest, so my personal practice is to load a previous version, such as V2.7.2.104 and change the first 2 to something BIG, such as V5.7.2.104.
Then, keep the Orbi from rebooting, which will cause it to reset the version number and promptly update firmware.
I use a substantial UPS so that minor power outages do not cause my Orbi to reboot.
This topic is really awkward because I have no Synology NAS and cannot investigate the primary issue. I am unable to come up with any reason how the Orbi's handling of DNS could impact the NAS. If the NAS can be set with a static IP, then surely it can be set to entirely bypass the Orbi DNS process????
[Sorry I can't get the quote funcion to work on copied in content]. Option 1 is out, I don't have the funds to buy another router. The BT Hub does have the facility to assign a DMZ IP.
I have a small UPS here as well so 2. might well be viable.
The problem is that when the issue occurs if one looks to test outgoing traffic from the NAS to the outside world e.g. DDNS then test results show that communication gets as far as the Orbi and then stops (My Orbi has IP of 192.168.1.254) as you can see below. The NAS does have a static IP and is set to use it's own DNS servers (Cloudflare) but the Orbi blocks the communication:
root@mynas:~# ping 192.168.1.254
PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.
64 bytes from 192.168.1.254: icmp_seq=1 ttl=64 time=0.357 ms
64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=0.327 ms
64 bytes from 192.168.1.254: icmp_seq=3 ttl=64 time=0.423 ms
64 bytes from 192.168.1.254: icmp_seq=4 ttl=64 time=0.323 ms
64 bytes from 192.168.1.254: icmp_seq=5 ttl=64 time=0.233 ms
^C
--- 192.168.1.254 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 0.233/0.332/0.423/0.064 ms
root@mynas:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.1.254 icmp_seq=1 Destination Port Unreachable
From 192.168.1.254 icmp_seq=2 Destination Port Unreachable
From 192.168.1.254 icmp_seq=3 Destination Port Unreachable
From 192.168.1.254 icmp_seq=4 Destination Port Unreachable
From 192.168.1.254 icmp_seq=5 Destination Port Unreachable
From 192.168.1.254 icmp_seq=6 Destination Port Unreachable
From 192.168.1.254 icmp_seq=7 Destination Port Unreachable
^C
--- 8.8.8.8 ping statistics ---
7 packets transmitted, 0 received, +7 errors, 100% packet loss, time 8ms
root@mynas:~# ping www.google.com
PING www.google.com (142.250.187.196) 56(84) bytes of data.
From 192.168.1.254 (192.168.1.254) icmp_seq=1 Destination Port Unreachable
From 192.168.1.254 (192.168.1.254) icmp_seq=2 Destination Port Unreachable
From 192.168.1.254 (192.168.1.254) icmp_seq=3 Destination Port Unreachable
From 192.168.1.254 (192.168.1.254) icmp_seq=4 Destination Port Unreachable
From 192.168.1.254 (192.168.1.254) icmp_seq=5 Destination Port Unreachable
^C
--- www.google.com ping statistics ---
5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 7ms
root@mynas:~# nslookup www.google.com
Server: 81.139.57.100
Address: 81.139.57.100#53
Non-authoritative answer:
Name: www.google.com
Address: 142.250.200.36
Name: www.google.com
Address: 2a00:1450:4009:81f::2004
root@mynas:~# nslookup www.google.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: www.google.com
Address: 142.250.200.36
Name: www.google.com
Address: 2a00:1450:4009:820::2004
root@mynas:~# traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 0.352 ms 0.392 ms 0.403 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
root@mynas:~#
