Can't ping outside LAN

[Michael Campbell]

Hello friends - FreeNAS 9.3.1 on a Dell PowerEdge T100, Netgear FVS series router. I have a NAS4FREE set that I have been running for years, but want to replace it with a FreeNAS box.

I've diagnosed my problem to a routing issue; symptoms are:
- from SSH and the console, I can ping machines within the LAN, but I can't ping outside the LAN.
- NTP service can't find time servers - host names xxx.ntp.org can't be found.
- Email can't be sent; host not found
- FreeNAS updates failing
- Plugin list won't show; refresh ends with "syntax error" or "No entry has been found"

What I've done:
- Initial setup (before I had the problem diagnosed) - installed FreeNAS, set up zvol, set up CIFS share, transferred files to the share, all with no issues. Observing the console, I noticed that NTP wasn't finding the servers, so I changed the servers to other known servers, same issue. I tried to set up email, and the test email failed. I suspected bad nameservers, so I changed the nameservers from 75.75.75.75/75.75.76.76 to 8.8.8.8 / 8.8.4.4 as suggested in this forum, no change. I logged in via SSH and tried pinging (both names - google.com - and addresses). Was able to ping within the segment (10.0.1.x) but not outside (10.0.0.x, 8.8.8.8, etc). I made many changes and lost track of what I'd done (changed resolv.conf, changed rc.conf, etc), so...
- Reinstalled FreeNAS and started a log of changes and discovery (attached). Current state, resolv.conf, netstat report, etc can be found there
- I've searched the forums extensively (including a hand-over-hand of the Networking thread), and tried the remedies for similar problems.

My setup and relevant info:
- FreeNAS (10.0.1.11) by itself on a Dell PowerEdge T100. FreeNAS installed on a 500G hard drive, with a 9T zvol, CIFS with one share which works fine. I have no jails set up at this time (it's basically a fresh install with minor changes noted in the attached trouble log).
- Nas4Free server (10.0.1.8) with years of history; will be a backup volume for FreeNAS once established (it's slow and old, and typically runs at about a 40% CPU capacity constantly).
- Several Windows and Ubuntu machines with various purposes (MythTV server, Plex server, HDHomeRun server, movies, music, etc). All play well together.
- Netgear FVS318G router (10.0.1.1) / firewall, with port forwarding
- Motorola Cable Modem (10.0.0.1) forwarding all ports to router (not in the DMZ, but all ports are forwarded, so basically in the DMZ).
- It's a residential setup, so there is no time or mission critical needs (other than my need to itch my computer enthusiast scratch).
- There is no Active Directory in play. DHCP provided by the router, and reservations are made at router for all devices on network. DHCP range is small (10.0.1.200-10.0.1.220), and devices are manually assigned addresses below 10.0.1.180 once I see them in the DHCP range.
- A wireless access point bridges to the network. All devices mentioned above are hardwired, but this bridge is in play.
- There is no DNS in the network; all DNS is via gateway to the aforementioned nameservers.
- All devices ping and access the Internet without issue; FreeNAS is the only one with an issue.
- I am fluent in Windows, competent at Ubuntu/Linux, and new at the CLI with FreeBSD. I have extensive user interface familiarity with Nas4Free, but very little CLI experience (since I haven't needed it until now).

Any assistance or guidance will be appreciated.

Cheers, Mike.

 

[anodos]

Hello friends - FreeNAS 9.3.1 on a Dell PowerEdge T100, Netgear FVS series router. I have a NAS4FREE set that I have been running for years, but want to replace it with a FreeNAS box.

I've diagnosed my problem to a routing issue; symptoms are:
- from SSH and the console, I can ping machines within the LAN, but I can't ping outside the LAN.
- NTP service can't find time servers - host names xxx.ntp.org can't be found.
- Email can't be sent; host not found
- FreeNAS updates failing
- Plugin list won't show; refresh ends with "syntax error" or "No entry has been found"

What I've done:
- Initial setup (before I had the problem diagnosed) - installed FreeNAS, set up zvol, set up CIFS share, transferred files to the share, all with no issues. Observing the console, I noticed that NTP wasn't finding the servers, so I changed the servers to other known servers, same issue. I tried to set up email, and the test email failed. I suspected bad nameservers, so I changed the nameservers from 75.75.75.75/75.75.76.76 to 8.8.8.8 / 8.8.4.4 as suggested in this forum, no change. I logged in via SSH and tried pinging (both names - google.com - and addresses). Was able to ping within the segment (10.0.1.x) but not outside (10.0.0.x, 8.8.8.8, etc). I made many changes and lost track of what I'd done (changed resolv.conf, changed rc.conf, etc), so...
- Reinstalled FreeNAS and started a log of changes and discovery (attached). Current state, resolv.conf, netstat report, etc can be found there
- I've searched the forums extensively (including a hand-over-hand of the Networking thread), and tried the remedies for similar problems.

My setup and relevant info:
- FreeNAS (10.0.1.11) by itself on a Dell PowerEdge T100. FreeNAS installed on a 500G hard drive, with a 9T zvol, CIFS with one share which works fine. I have no jails set up at this time (it's basically a fresh install with minor changes noted in the attached trouble log).
- Nas4Free server (10.0.1.8) with years of history; will be a backup volume for FreeNAS once established (it's slow and old, and typically runs at about a 40% CPU capacity constantly).
- Several Windows and Ubuntu machines with various purposes (MythTV server, Plex server, HDHomeRun server, movies, music, etc). All play well together.
- Netgear FVS318G router (10.0.1.1) / firewall, with port forwarding
- Motorola Cable Modem (10.0.0.1) forwarding all ports to router (not in the DMZ, but all ports are forwarded, so basically in the DMZ).
- It's a residential setup, so there is no time or mission critical needs (other than my need to itch my computer enthusiast scratch).
- There is no Active Directory in play. DHCP provided by the router, and reservations are made at router for all devices on network. DHCP range is small (10.0.1.200-10.0.1.220), and devices are manually assigned addresses below 10.0.1.180 once I see them in the DHCP range.
- A wireless access point bridges to the network. All devices mentioned above are hardwired, but this bridge is in play.
- There is no DNS in the network; all DNS is via gateway to the aforementioned nameservers.
- All devices ping and access the Internet without issue; FreeNAS is the only one with an issue.
- I am fluent in Windows, competent at Ubuntu/Linux, and new at the CLI with FreeBSD. I have extensive user interface familiarity with Nas4Free, but very little CLI experience (since I haven't needed it until now).

Any assistance or guidance will be appreciated.

Cheers, Mike.

Go to "Network" -> "Global Configuration". Did you configure an IPv4 Default Gateway?

 

[Michael Campbell]

Did both (with and without), no change. current configuration:
Hostname: pmgfs
Domain: thepmgs.com
IPv4 Default Gateway: 10.0.1.1
Nameserver 1: 10.0.1.1
Nameserver 2: 75.75.75.75
Nameserver 3: 75.75.76.76

/etc/resolv.conf:
search thepmgs.com
nameserver 10.0.1.1
nameserver 75.75.75.75
nameserver 75.75.76.76

I also just ran a netstat -n (remotely via SSH), with the following output:

[root@pmgfs] ~# netstat -n
Active Internet connections
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp4 0 0 127.0.0.1.9042 127.0.0.1.18932 TIME_WAIT
tcp4 0 0 127.0.0.1.9042 127.0.0.1.48910 TIME_WAIT
tcp4 0 0 127.0.0.1.9042 127.0.0.1.11293 TIME_WAIT
tcp4 0 0 127.0.0.1.9042 127.0.0.1.33035 TIME_WAIT
tcp4 0 0 127.0.0.1.9042 127.0.0.1.60685 TIME_WAIT
tcp4 0 0 127.0.0.1.9042 127.0.0.1.11925 TIME_WAIT
tcp4 0 0 127.0.0.1.9042 127.0.0.1.64191 TIME_WAIT
tcp4 0 0 127.0.0.1.9042 127.0.0.1.31487 TIME_WAIT
tcp4 0 0 127.0.0.1.9042 127.0.0.1.17469 TIME_WAIT
tcp4 0 0 127.0.0.1.9042 127.0.0.1.64797 TIME_WAIT
tcp4 0 0 127.0.0.1.9042 127.0.0.1.18967 TIME_WAIT
tcp4 0 0 127.0.0.1.9042 127.0.0.1.53006 TIME_WAIT
tcp4 0 0 127.0.0.1.9042 127.0.0.1.60456 TIME_WAIT
... and many more like this - 69 total - then...
udp4 0 0 10.0.1.11.52571 10.0.1.1.53
udp4 0 0 10.0.1.255.138 *.*
udp4 0 0 10.0.1.11.138 *.*
udp4 0 0 10.0.1.255.137 *.*
udp4 0 0 10.0.1.11.137 *.*
udp4 0 0 127.0.0.1.123 *.*
udp6 0 0 fe80:5::1.123 *.*
udp6 0 0 ::1.123 *.*
udp4 0 0 10.0.1.11.123 *.*

not sure this helps, but it seems like an awful lot of loopback connections.

 

[Michael Campbell]

Hello and thank all who checked out this problem. I found the issue; at least I found a workaround if not the issue.

Since I was very early in installation, it wasn't a huge deal to wipe the OS and install a new one, so I installed NAS4FREE. Had the same problem. I installed Windows 7. Same issue. Installed Ubuntu 14.04... same issue. You get the theme...

I installed an old USB 10/100 adapter, and was able to ping out using that. I determined that the issue was with the NIC itself (odd), or it's configuration. I noted that there is a BMC in the BIOS, and despite disabling it (or trying to), that since I could get an external adapter working, I would just use the $10 solution instead of futzing around with an on-board peripheral.

Bottom line - using a discrete NIC solved this issue for me. I don't think that I've seen this solution anywhere, so hopefully anyone with this issue has $10 or a spare NIC laying around to try this . Would have saved me dozens of hours and frustration. It might not be everyone's option, but it worked for me.

 

[anodos]

Hello and thank all who checked out this problem. I found the issue; at least I found a workaround if not the issue.

Since I was very early in installation, it wasn't a huge deal to wipe the OS and install a new one, so I installed NAS4FREE. Had the same problem. I installed Windows 7. Same issue. Installed Ubuntu 14.04... same issue. You get the theme...

I installed an old USB 10/100 adapter, and was able to ping out using that. I determined that the issue was with the NIC itself (odd), or it's configuration. I noted that there is a BMC in the BIOS, and despite disabling it (or trying to), that since I could get an external adapter working, I would just use the $10 solution instead of futzing around with an on-board peripheral.

Bottom line - using a discrete NIC solved this issue for me. I don't think that I've seen this solution anywhere, so hopefully anyone with this issue has $10 or a spare NIC laying around to try this . Would have saved me dozens of hours and frustration. It might not be everyone's option, but it worked for me.

I hope your discrete NIC isn't the USB 10/100 adapter. ;)

 

[Michael Campbell]

Oh no... that would be horrible. I bought a discrete NIC. I just used the dongle to test.