No internet access

[longcanadianwinter]

Hi … I know this is a simple question but I have been working on it for hours now. I have read and re-read the documentation and many threads. My problem is simple: I can access my freenas web interface (so it's accessing my home network fine) but I can not get access to the internet. Every ping test returns no packets received. I tried a number of configurations based on reading other threads here and for an hour it worked. Then in the middle of installing a plugin it failed again. I know some may suggest a NIC failure as the cause but I don't think so - I suspect I was making changes trying to get the plug in to work as I was having challenges and mucked up a setting. I have gone back and retried but from what I see this should be fairly simple - under global config make sure you have a default gateway pointing to your router and that you have DNS names set. I have posted a screenshot - don't judge if there is something stupid in there, I have tried many different configs and rebooted in between each. Thanks for any help and apologies if it's something dumb!

 

[longcanadianwinter]

To add... I guess one thing I am confused about is the interface, whether I need to go through the web interface and add one? I have tried both ways. I have also tried through the console on the freenas doing a reset of the interface network config.

 

[melloa]

To confirm are you using the version listed on your signature?? FreeNAS 9.2.1.5??

Also ... You are using a private IP address as gateway, so assume your freenas is on 192.168.1.xxx (?) Your name servers are OpenDNS ... Why don't you just let your router take care of all of that? Configure your FreeNAS for DHCP and problem should be fixed.

 

[melloa]

To add... I guess one thing I am confused about is the interface, whether I need to go through the web interface and add one? I have tried both ways. I have also tried through the console on the freenas doing a reset of the interface network config.

No ... from the manual:

Code:

Typically, the interface used to access the FreeNAS® administrative GUI is configured by DHCP. This interface does not appear in this screen, even though it is already dynamically configured and in use.

 

[kdragon75]

What is your FreeNAS IP? Can you ping your gateway from FreeNAS?

 

[longcanadianwinter]

To confirm are you using the version listed on your signature?? FreeNAS 9.2.1.5??

Also ... You are using a private IP address as gateway, so assume your freenas is on 192.168.1.xxx (?) Your name servers are OpenDNS ... Why don't you just let your router take care of all of that? Configure your FreeNAS for DHCP and problem should be fixed.

No my bad … I will update. I am now using 11.2 BETA3. I have been running 9.3 without issues for a number of years. My freeNAS is on 192.168.86.35 so the gateway is the IP of my router ….? I have tried setting up with DHCP but possibly I didn't have other things set properly. Will try again

 

[longcanadianwinter]

What is your FreeNAS IP? Can you ping your gateway from FreeNAS?

Thanks for the reply. FreeNAS IP is 192.168.86.35 and I can ping my gateway on 192.168.86.1 without any issues

 

[longcanadianwinter]

No ... from the manual:

Code:

Typically, the interface used to access the FreeNAS® administrative GUI is configured by DHCP. This interface does not appear in this screen, even though it is already dynamically configured and in use.

Like this?

 

[longcanadianwinter]

Just tried pinging Google nameservers and came back good - I think when I am trying the different settings I am mixing up different pieces and getting a bad result. Saving the config file now! Still though when I try to load 'available plugins' I get an error that it can not resolve the hostname. I have seen some other threads on that so will search and post back if there is nothing on this issue out there already. Thanks.

 

[melloa]

Like this?

No. Unless you've added, it should not be there. I never changed (until today to set mtu) my network configuration after installation.

Try to remove and configure from the console the interface for DHCP.

 

[melloa]

Just tried pinging Google nameservers and came back good - I think when I am trying the different settings I am mixing up different pieces and getting a bad result. Saving the config file now! Still though when I try to load 'available plugins' I get an error that it can not resolve the hostname. I have seen some other threads on that so will search and post back if there is nothing on this issue out there already. Thanks.

Did you ping IP or FQDN ?

 

[longcanadianwinter]

No. Unless you've added, it should not be there. I never changed (until today to set mtu) my network configuration after installation.

Try to remove and configure from the console the interface for DHCP.

Got it will try that, thanks!

 

[longcanadianwinter]

Did you ping IP or FQDN ?

IP

 

[longcanadianwinter]

IP

And when I try the FQDN it gives me a hostname lookup failure …. thanks for the catch. It is not resolving hostnames clearly

 

[longcanadianwinter]

So … deleted interface that I had added on the web interface. Went into freeNas local console. Removed the interface, reset network config and configured for DHCP. Routing and network come back as ok on console. Running a ping from web console to FQDN of Google still gives hostname lookup error. Will try to remove name servers based on early reply.

 

[longcanadianwinter]

Still nothing. Does not seem to matter what I put for name servers or default gateway (as my original screenshot or all removed) … I can ping 8.8.8.8 no issues but not www.google.com ….. help?

 

[kdragon75]

http://doc.freenas.org/11.2/network.html#global-configuration
What are you setting for the name server?

 

[longcanadianwinter]

http://doc.freenas.org/11.2/network.html#global-configuration
What are you setting for the name server?

I am using the OpenDNS name servers. I also tried the google ones 8.8.8.8 and 8.8.4.4

 

[longcanadianwinter]

As an add.... when I go into global configuration and remove the default gateway (since the manual says this is not typically set) I get a 'no route to host' error when I try to ping. When I add it back in I can ping IP but not FQDM … thanks everyone

 

[longcanadianwinter]

As an add.... when I go into global configuration and remove the default gateway (since the manual says this is not typically set) I get a 'no route to host' error when I try to ping. When I add it back in I can ping IP but not FQDM … thanks everyone

Also I have nothing under host name database …. should I?