NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jamestx10
Mar 23, 2017Aspirant
6.6.1 on Ultra 6 Loses DNS lookup after a few days
I have my router configured as the DNS server in the network settings. It can reach the router fine but it fails to resolve addresses after a few days. I reboot the NAS and it is good to go again for...
jak0lantash
Mar 26, 2017Mentor
Firstly, you should download the logs, at least for reference.
If you want to check via SSH, you could try to:
- ping google.com
- ping 8.8.8.8
- ping your default gateway
- ping what's supposed to be the DNS server
If you want to check via SSH, you could try to:
- ping google.com
- ping 8.8.8.8
- ping your default gateway
- ping what's supposed to be the DNS server
jak0lantash
Mar 26, 2017Mentor
You can also dump the current status of all network connections:
for a_service in $(connmanctl services | awk '{ printf $3" " }'); do connmanctl services $a_service; done- jamestx10Mar 26, 2017Aspirant
This time the unit locked up so I had to reboot it. I set the IP back to DHCP. Running your other command I noticed that I had not updated my NTP address and that the 2nd ethernet connection had a router and DNS entry set that it cannot connect to. I have Eth1 directly connected to a PC with a cross over cable. I removed the router and DNS entries from that connection. I am wondering if that was the issue??? How are the network connections weighted? Which link will it try by default? I see they are both listed as favorite.
/net/connman/service/ethernet_001f33ea8125_cable Type = ethernet Security = [ ] State = ready Favorite = True Immutable = False AutoConnect = True Name = Wired Ethernet = [ Method=auto, Interface=eth0, Address=00:1F:33:EA:81:25, MTU=1500 ] IPv4 = [ Method=dhcp, Address=10.10.10.20, Netmask=255.255.255.0, Gateway=10.10.10.1 ] IPv4.Configuration = [ Method=dhcp ] IPv6 = [ ] IPv6.Configuration = [ Method=off ] Nameservers = [ 10.10.10.1 ] Nameservers.Configuration = [ ] Timeservers = [ 10.10.10.26, time-a.netgear.com, 10.10.10.1 ] Timeservers.Configuration = [ 10.10.10.26, time-a.netgear.com ] Routes = [ ] Routes.Configuration = [ ] Domains = [ NULEAF ] Domains.Configuration = [ ] Proxy = [ Method=direct ] Proxy.Configuration = [ ] Provider = [ ] /net/connman/service/ethernet_001f33ea8124_cable Type = ethernet Security = [ ] State = ready Favorite = True Immutable = False AutoConnect = True Name = Wired Ethernet = [ Method=auto, Interface=eth1, Address=00:1F:33:EA:81:24, MTU=1500 ] IPv4 = [ Method=manual, Address=10.101.1.3, Netmask=255.255.255.0 ] IPv4.Configuration = [ Method=manual, Address=10.101.1.3, Netmask=255.255.255.0 ] IPv6 = [ ] IPv6.Configuration = [ Method=off ] Nameservers = [ ] Nameservers.Configuration = [ ] Timeservers = [ 10.10.10.26, time-a.netgear.com ] Timeservers.Configuration = [ 10.10.10.26, time-a.netgear.com ] Routes = [ ] Routes.Configuration = [ ] Domains = [ ] Domains.Configuration = [ ] Proxy = [ Method=direct ] Proxy.Configuration = [ ] Provider = [ ]
Once I removed that Router and DNS entry from Eth1 I could no longer resolve DNS So it really seems like it wants to use that link
root@NAS:~# ping google.com ping: bad address 'google.com' root@NAS:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: seq=0 ttl=46 time=9.523 ms 64 bytes from 8.8.8.8: seq=1 ttl=46 time=9.473 ms
So next I disconencted Eth1 and then I could ping again. Any ideas on how to have the two connections used but favor Eth0 for internet and DNS?
- jamestx10Mar 28, 2017Aspirant
Is there a service on the NAS I can restart that should correct this?
- Retired_MemberMar 28, 2017
The nas is not the problem, but the way you have setup your network topology.
The only way to solve this I see in having two completely separated networks and that also means addresswise. eth0 should be on one network together with your router. eth1 should be on a second isolated network holding only eth1 and the workstation.
I assume you only have one nic in your workstation and that directly connects to eth1 via the crossover cable. In this case give the workstation a static ip address and do the same to eth1. Make the workstation the router and gateway of eth1. Make eth1 the router and gateway of the workstation. Make sure both ip addresses of eth1 and the workstation are not on the same network than the router and eth0.
For example: If you router is on 192.168.0.1 and the eth0 is on 192.168.0.2 the static ip addresses for the workstation could be 192.168.1.1 and for the eth1 192.168.1.2
Should you have 2 nic in your workstation, one of them directly going to the nas and one going into the router's network, disable the one into the router's network while trying to implement the proposed solution.
- jamestx10Mar 28, 2017Aspirant
That is how I have it connected.
Eth0 goes to the router where it has a DHCP reserved IP of 10.10.10.20
Eth1 goes directly to the workstation with a crossover cable and static IP of 10.101.1.3
Workstation has 2 eth ports with one going to the router and one going to the NAS with an IP of 10.101.1.2
- jak0lantashMar 28, 2017Mentor
jamestx10 wrote:/net/connman/service/ethernet_001f33ea8125_cable Ethernet = [ Method=auto, Interface=eth0, Address=00:1F:33:EA:81:25, MTU=1500 ] IPv4 = [ Method=dhcp, Address=10.10.10.20, Netmask=255.255.255.0, Gateway=10.10.10.1 ]
/net/connman/service/ethernet_001f33ea8124_cable Ethernet = [ Method=auto, Interface=eth1, Address=00:1F:33:EA:81:24, MTU=1500 ] IPv4.Configuration = [ Method=manual, Address=10.101.1.3, Netmask=255.255.255.0 ]Your configuration is correct.
Eth0: 10.10.10.20/24, GW 10.10.10.1, DNS 10.10.10.1
Eth1: 10.101.1.3/24, no GW, no DNS
This is exactly the configuration I have on my NAS and it's working OK.
You could try to restart connmand, but it's just easier to reboot the NAS.
After the reboot, double check that both NICs still have the same configuration, from the GUI and using the command I give you.
Try again to resolve google.com with a ping.
- jak0lantashMar 29, 2017Mentor
jak0lantash wrote:
jamestx10 wrote:/net/connman/service/ethernet_001f33ea8125_cable Ethernet = [ Method=auto, Interface=eth0, Address=00:1F:33:EA:81:25, MTU=1500 ] IPv4 = [ Method=dhcp, Address=10.10.10.20, Netmask=255.255.255.0, Gateway=10.10.10.1 ]
/net/connman/service/ethernet_001f33ea8124_cable Ethernet = [ Method=auto, Interface=eth1, Address=00:1F:33:EA:81:24, MTU=1500 ] IPv4.Configuration = [ Method=manual, Address=10.101.1.3, Netmask=255.255.255.0 ]Your configuration is correct.
Eth0: 10.10.10.20/24, GW 10.10.10.1, DNS 10.10.10.1
Eth1: 10.101.1.3/24, no GW, no DNS
This is exactly the configuration I have on my NAS and it's working OK.
You could try to restart connmand, but it's just easier to reboot the NAS.
After the reboot, double check that both NICs still have the same configuration, from the GUI and using the command I give you.
Try again to resolve google.com with a ping.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!