NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
linutic
Aug 30, 2023Aspirant
Internal Server Error when hostname used
I have configured my RBR750 as an access point with the following IP addresses set as static DHCP addresses in my OpenWRT router. router: "mesh" 192.168.49.4 satellite: "mesh1" 192.168.4...
CrimpOn
Aug 30, 2023Guru - Experienced User
It appears that the DNS server in Open WRT is not resolving "mesh" to the correct IP address.
What happens if you do the command line command
ping mesh
- linuticAug 30, 2023Aspirant
Good thought, but the IP address in the query is correct. Here's what "wget" outputs when typed from the command line:
% wget mesh
--2023-08-30 12:09:08-- http://mesh/
Resolving mesh (mesh)... 192.168.49.4
Connecting to mesh (mesh)|192.168.49.4|:80... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2023-08-30 12:09:08 ERROR 500: Internal Server Error.% ping mesh
PING mesh.lan (192.168.49.4) 56(84) bytes of data.
64 bytes from mesh.lan (192.168.49.4): icmp_seq=1 ttl=64 time=0.322 ms
64 bytes from mesh.lan (192.168.49.4): icmp_seq=2 ttl=64 time=0.353 ms- linuticAug 30, 2023Aspirant
Here's some additional behavior. The satellites have no problem with wget queries.
% wget http://mesh1
--2023-08-30 14:02:14-- http://mesh1/
Resolving mesh1 (mesh1)... 192.168.49.5
Connecting to mesh1 (mesh1)|192.168.49.5|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 839 [text/html]
Saving to: ‘index.html.4’% wget http://mesh2
--2023-08-30 14:02:17-- http://mesh2/
Resolving mesh2 (mesh2)... 192.168.49.6
Connecting to mesh2 (mesh2)|192.168.49.6|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 839 [text/html]
Saving to: ‘index.html.5’- CrimpOnAug 30, 2023Guru - Experienced User
Thanks for providing the recording showing the DNS resolution.
Version V4.6.14.3 appears to have been out since 12/1/2022 (almost nine months). Unless this system was just recently updated, the firmware seems unlikely to be the cause of the change in behavior.
My Orbi requires authentication. (user, password) Do you have those parameters in a configuration file, rather than on the command line? It appears that more parameters are required to get the output in your post. All I get is this:
C:\Users\Dick>wget.exe 192.168.1.1 --user=admin --password=xxxxxxxxx --2023-08-30 16:13:45-- http://192.168.1.1/ Connecting to 192.168.1.1:80... connected. HTTP request sent, awaiting response... 401 Unauthorized Authentication selected: Basic realm="NETGEAR Orbi" Connecting to 192.168.1.1:80... connected. HTTP request sent, awaiting response... 200 OK Length: 531 [text/html] Saving to: 'index.html' index.html 100%[=================================================>] 531 --.-KB/s in 0s 2023-08-30 16:13:46 (7.90 MB/s) - 'index.html' saved [531/531]
One of the 'missing features' in Orbi is the ability to resolve local DNS entries, so I am unable to duplicate the entire situation. (Also testing on an RBR50 in router mode) It is interesting to note that on my Windows computer, wget connects to the IPv6 address of the web site when Orbi resolves http://orbilogin.net :
C:\Users\Dick>wget.exe http://orbilogin.net --user=admin --password=xxxxxxxxxx --2023-08-30 16:25:52-- http://orbilogin.net/ Resolving orbilogin.net (orbilogin.net)... 2603:8000:403:bd7c:a204:60ff:fe1c:239, 192.168.1.1 Connecting to orbilogin.net (orbilogin.net)|2603:8000:403:bd7c:a204:60ff:fe1c:239|:80... connected. HTTP request sent, awaiting response... 401 Unauthorized Authentication selected: Basic realm="NETGEAR Orbi" Connecting to orbilogin.net (orbilogin.net)|2603:8000:403:bd7c:a204:60ff:fe1c:239|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 531 [text/html] Saving to: 'index.html.1' index.html.1 100%[=================================================>] 531 --.-KB/s in 0s 2023-08-30 16:25:52 (5.56 MB/s) - 'index.html.1' saved [531/531]