Network issues Freenas 11.3 U2

[Bjureus1]

Code:

root@freenas[~]# ifconfig
igb0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=6002bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO6,RXCSUM_IPV6,TXCSUM_IPV6>
ether d0:50:99:1b:65:11
hwaddr d0:50:99:1b:65:11
inet 192.168.0.200 netmask 0xffffff00 broadcast 192.168.0.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
ether d0:50:99:1b:65:12
hwaddr d0:50:99:1b:65:12
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect
status: no carrier
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
groups: lo
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 02:04:3a:7b:2f:00
nd6 options=1<PERFORMNUD>

?

 

[Basil Hendroff]

This looks a little different to what I have, but before I comment, I just want to check that your other client devices have no problems accessing the internet. Are you running Windows? If so, can I have a look at the equivalent of this dialogue box:

 

[Bjureus1]

This looks a little different to what I have, but before I comment, I just want to check that your other client devices have no problems accessing the internet. Are you running Windows? If so, can I have a look at the equivalent of this dialogue box:

View attachment 37618

 

[Basil Hendroff]

It looks to me like you've got both ipv4 and ipv6 enabled on your network. I don't have ipv6 enabled so I'm not sure if this is having an impact somewhere. Would anyone else care to comment?

I'll include this just for comparison.

Code:

root@freenas-l:/mnt/tank/nfs/freenas-iocage-nextcloud # ifconfig
bge0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: bge0
        options=c0099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,VLAN_HWTSO,LINKSTATE>
        ether 94:18:82:38:36:58
        hwaddr 94:18:82:38:36:58
        inet 10.1.1.20 netmask 0xffffff00 broadcast 10.1.1.255
        nd6 options=9<PERFORMNUD,IFDISABLED>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
bge1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=c019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>
        ether 94:18:82:38:36:59
        hwaddr 94:18:82:38:36:59
        nd6 options=1<PERFORMNUD>
        media: Ethernet autoselect
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: lo

 

[Bjureus1]

Noone had the same problem?????

 

[no_connection]

can you ping the address from FN shell?
what happens if you connect both NIC?

 

[Yorick]

Noone had the same problem?????

Not really. This looks like a basic networking issue. I'd check that DNS is reachable from FreeNAS (ping to DNS IP), and that it can resolve names (ping to something like www.google.com). Then, for good measure, manually create a jail and do the same checks inside the jail.

Basic network troubleshooting isn't hard - you just move up the OSI stack, checking at each layer - and, it's beyond tedious to try and walk someone through it remotely, because there are so many possible steps to take.

 

[Brad_S]

I too am experiencing the same issue. I have the default gateway set and DNS is set to default gateway and Google DNS. Still cannot name resolve through shell. I upgraded from 11.3-U2.1 to 11.3-U3.1, but the issue still exists.

 

[Samuel Tai]

I too am experiencing the same issue. I have the default gateway set and DNS is set to default gateway and Google DNS. Still cannot name resolve through shell. I upgraded from 11.3-U2.1 to 11.3-U3.1, but the issue still exists.

Have you checked /etc/nsswitch.conf, to make sure the hosts: line reads "files dns"?

Code:

#
# nsswitch.conf(5) - name service switch configuration file
# $FreeBSD$
#


group: files
hosts: files dns
networks: files
passwd: files
shells: files
services: files
protocols: files
rpc: files
sudoers: files

This tells the shell to first try /etc/hosts, and then DNS.

Next, make sure /etc/resolv.conf lists all the DNS servers you've configured in the GUI.

Then, run netstat -rn, see if your default gateway is configured. Run ping <default gateway IP> to make sure the shell has connectivity to the default gateway.

If you still can't resolve names after this, then something upstream of the default gateway is either not passing on your DNS queries, or is actively blocking the DNS responses from reaching your FreeNAS installation.

 

[Brad_S]

Have you checked /etc/nsswitch.conf, to make sure the hosts: line reads "files dns"?

Code:

#
# nsswitch.conf(5) - name service switch configuration file
# $FreeBSD$
#


group: files
hosts: files dns
networks: files
passwd: files
shells: files
services: files
protocols: files
rpc: files
sudoers: files

This tells the shell to first try /etc/hosts, and then DNS.

Next, make sure /etc/resolv.conf lists all the DNS servers you've configured in the GUI.

Then, run netstat -rn, see if your default gateway is configured. Run ping <default gateway IP> to make sure the shell has connectivity to the default gateway.

If you still can't resolve names after this, then something upstream of the default gateway is either not passing on your DNS queries, or is actively blocking the DNS responses from reaching your FreeNAS installation.

I've checked these files and they are fine. netstat -nr My firewall/default gateway device appears to be blocking traffic for FreeNAS, and I do not know why.
1. Other devices can ping/DNS resolution to default gateway
2. Changed FreeNAS IP address (192.168.1.102, 192.168.1.101, 192.168.1.5) but the problem followed
3. Tried creating a specific rule to allow ICMP to the default gateway, but this failed as well
4. Upgraded from FreeNAS 11.3-U2.1 to 11.3-U3.1
5. I can ping other devices within VLAN1 (192.168.1.0 network); I only have one VLAN. Servers are connected via an unmanaged switch, the switch is connected to the firewall

Everything I've tried so far has not worked.

 

[Yorick]

Sounds like a simple fix then, figure out your firewall. Some firewalls, for example, can be configured to be very suspicious of anything with a fixed IP. You’ll have a medium learning curve to figure out what your firewall is and how it behaves.

 

[Samuel Tai]

Is the gateway device expecting tagged packets or untagged?

 

[Samuel Tai]

Also, does your gateway have an ARP entry for your FreeNAS box, and does that ARP MAC match the MAC on the FreeNAS box?

 

[Samuel Tai]

Are you using jumbo frames on FreeNAS? The gateway may not like it, if it doesn't also have jumbo frames enabled.

 

[Brad_S]

Well, I rebooted my firewall and that appears to have resolved the issue with ping and name resolution.

There was another thread I was reading where this resolved this specific issue as well.

So I am wondering to myself, "Why do some people have issues with fresh installs where 'something' happens to their default gateway that causes this issue?"

Thanks to everyone and their advice. I truly appreciate you.

Stay safe!