New, Fresh Install, Not able to ping router, LAN works fine

[eivl]

I'm brand new to unraid, but I would like to ask for some assistance. I have a fresh install, the only thing I have done is: activate disks, set a static IP for the server. 

 

I can ping the LAN, but I cannot ping the router: 192.168.0.1

I had FreeNAS installed on this server before, and it worked normally, Is there any settings I can change to figure this out?

Normally I have no issue with getting internet from the router on other systems, I also might have change something unknowingly while I have been debugging why a plugin didn't want to install (ofc if it does not have internet that is the reason, but at the time I did not know that)

 

I'm open to any suggestions. 

goliat-diagnostics-20180904-1106.zip

[Frank1940]

The one that that I saw was this:

 

DNS_SERVER1="192.168.0.4"

Most of the time, I would expect to see 

 

 DNS_SERVER1="192.168.0.1"  

 

In fact, with you specifying the Google DNS servers, I would  not know why you would want to use your ISP's DNS servers as the primary ones.  

[eivl]

192.168.0.4 is my domain controller, it also runs all network services. 192.168.0.1 is my router. 

I can ping localhost.mydomain.local, but not the router, and I have no idea why this is.

 

How should the routing table look? might it be something there?

 

Edit: added a ping to cnn.com Multiple sources

 

root@goliat:~# ping cnn.com
PING cnn.com (151.101.129.67) 56(84) bytes of data.
^C
--- cnn.com ping statistics ---
20 packets transmitted, 0 received, 100% packet loss, time 19464ms

root@goliat:~# ping deadpool.nof.local
PING deadpool.nof.local (192.168.0.197) 56(84) bytes of data.
64 bytes from deadpool.nof.local (192.168.0.197): icmp_seq=1 ttl=128 time=0.366 ms
64 bytes from deadpool.nof.local (192.168.0.197): icmp_seq=2 ttl=128 time=0.249 ms
64 bytes from deadpool.nof.local (192.168.0.197): icmp_seq=3 ttl=128 time=0.375 ms


root@goliat:~# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
^C
--- 192.168.0.1 ping statistics ---
14 packets transmitted, 0 received, 100% packet loss, time 13343ms

 

 

[ken-ji]

Not seeing an issue with your diagnostics.

Not being able to ping your router is worrying though.

I see you have 2 network interfaces, and they are bonded and both have cables plugged.

Can you unplug one those and see if it makes your network work?

 

And if this makes it work, you might need to disable bonding or change bonding mode to something else.

AFAIK FreeNAS uses bonding mode 4 aka 802.3ad aka LACP

[eivl]

5 minutes ago, ken-ji said:

Not seeing an issue with your diagnostics.

Not being able to ping your router is worrying though.

I see you have 2 network interfaces, and they are bonded and both have cables plugged.

Can you unplug one those and see if it makes your network work?

 

Removed bonding, only using one card and i unplugged the ethernet cable, It did not change anything.

 

Edit: this is my route settings. 

IPv4	default	192.168.0.1 via eth0	1	
IPv4	192.168.0.0/24	eth0	1	

 

[ken-ji]

I'll assume the cable left plugged in allowed you to reach the domain controller.

Did you try swapping cables? Can you post updated diagnostics again?

[eivl]

both cables are brand new Cat-7, but I will swap them out and post new diagnostics when it is done. hold on.

 

Edit: swaped cables and added diagnostics

goliat-diagnostics-20180905-0943.zip