Weird ping timeout

[Simpleone71]

I have setup on my Freenas 11.1-u4 server a Ubunut 16.04LTS VM. I have it working, but have a weird problem with pinging the actual Freenas Server.

I have a static IP address setup and I can ping anything on my internal LAN and anything on my internal LAN can ping the Ubuntu machine. If I use SSH to the Ubuntu machine and ping my freenas box, it will resolve the name to the ip and then hang trying to ping. If I let it sit there long enough, it will sometimes just start pinging like normal. Even if I just try to ping directly the ip address of my freenas box, it will just sit there where it would normally tell you the bytes from etc, etc.

Sometimes on a reboot it will just instantly work and sometimes it takes forever to be able to ping the freenas box. I have gone over all my settings and do not see anything wrong. I'm fairly familiar with Ubuntu, but not Bhyve (am extremely familiar with VMWare ESXi) as this is my first attempt with using a virtual machine in freenas.

My biggest problem from this is that I'm trying to map a drive in this virtual machine on boot in fstab and since it sometimes can't get to the freenas box, it doesn't map.

Any suggestions?

 

[dlavigne]

Anything in /var/log/messages when the ping fails?

Also, paste the output of ifconfig within code tags.

 

[Simpleone71]

Nothing in the /var/log/messages. The ping doesn't fail so much as just hangs and is random and appears on startup. So if I reboot the Ubuntu server two times, the ping might work one time and not the other. I tried Ubuntu 17.10 and also Debian 9, both will randomly work after a reboot. This only happens with pinging the freenas box itself, but even then it does successfully resolve the ip address. It also does this regardless of if I use VirtIO or e1000 as my adapter type in the VM setup.

So here is a ping to something on the internal LAN:

Code:

ping s3300
PING s3300.rj.com (192.168.1.253) 56(84) bytes of data.
64 bytes from s3300.rj.com (192.168.1.253): icmp_seq=1 ttl=64 time=1.61 ms

Code:

ping freenas
PING freenas.rj.com (192.168.1.31) 56(84) bytes of data.
**THE CURSOR JUST SITS AT THE FAR LEFT OF THIS LINE AND DOES NOTHING, IF I HIT CTRL-C, THEN IT GIVES THE FOLLOWING**
--- freenas.rj.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2005ms

Here is my ifconfig

Code:

enp0s3	Link encap:Ethernet  HWaddr 00:a0:98:1e:53:56
		  inet addr:192.168.1.177  Bcast:192.168.1.255  Mask:255.255.255.0
		  inet6 addr: fe80::2a0:98ff:fe1e:5356/64 Scope:Link
		  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
		  RX packets:1747 errors:0 dropped:0 overruns:0 frame:0
		  TX packets:414 errors:0 dropped:0 overruns:0 carrier:0
		  collisions:0 txqueuelen:1000
		  RX bytes:459393 (459.3 KB)  TX bytes:40744 (40.7 KB)

lo		Link encap:Local Loopback
		  inet addr:127.0.0.1  Mask:255.0.0.0
		  inet6 addr: ::1/128 Scope:Host
		  UP LOOPBACK RUNNING  MTU:65536  Metric:1
		  RX packets:160 errors:0 dropped:0 overruns:0 frame:0
		  TX packets:160 errors:0 dropped:0 overruns:0 carrier:0
		  collisions:0 txqueuelen:1
		  RX bytes:11840 (11.8 KB)  TX bytes:11840 (11.8 KB)

virbr0	Link encap:Ethernet  HWaddr 52:54:00:ab:a7:c7
		  inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
		  UP BROADCAST MULTICAST  MTU:1500  Metric:1
		  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
		  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
		  collisions:0 txqueuelen:1000
		  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

 

[Simpleone71]

One additional note:

If I ping the freenas box and just let the ping sit, it eventually will start pinging (different amounts of time for it to start working each time). Once I'm able to ping, until I reboot it will work, but of course this keeps my mounts at bootup from working most times. Here is an example where it took around 1 minute to start working. Even though the pings are considered packets loss, the ping command doesn't show that they failed, it just sits there.

Code:

ping freenas
PING freenas.rj.com (192.168.1.31) 56(84) bytes of data.
64 bytes from freenas.rj.com (192.168.1.31): icmp_seq=65 ttl=64 time=0.139 ms
64 bytes from freenas.rj.com (192.168.1.31): icmp_seq=66 ttl=64 time=0.140 ms
64 bytes from freenas.rj.com (192.168.1.31): icmp_seq=67 ttl=64 time=0.160 ms
64 bytes from freenas.rj.com (192.168.1.31): icmp_seq=68 ttl=64 time=0.156 ms
64 bytes from freenas.rj.com (192.168.1.31): icmp_seq=69 ttl=64 time=0.088 ms
64 bytes from freenas.rj.com (192.168.1.31): icmp_seq=70 ttl=64 time=0.129 ms
64 bytes from freenas.rj.com (192.168.1.31): icmp_seq=71 ttl=64 time=0.113 ms
64 bytes from freenas.rj.com (192.168.1.31): icmp_seq=72 ttl=64 time=0.127 ms
^C
--- freenas.rj.com ping statistics ---
72 packets transmitted, 8 received, 88% packet loss, time 71352ms
rtt min/avg/max/mdev = 0.088/0.131/0.160/0.024 ms

 

[dlavigne]

Packet loss indicates that something in the network is blocking those packets (perhaps a firewall, proxy, some system/application overwhelming the bandwidth, etc.) Running a packet sniffer might help to locate the blocker.

 

[Simpleone71]

I checked and no firewall is running on the VM machine. As the VM is on Freenas, unless Freenas has any type of firewall that I'm not aware of, then I don't think it's a firewall issue. Thanks for the tips. I'm going to just go under the assumption that the Bhyve (VM) portion of Freenas isn't ready for prime time just yet. I loaded my Ubuntu machine on one of my lab ESXi servers and it's working perfect.

 

[Simpleone71]

Ok, well I wanted to come back here and post the solution to this issue. I'm not sure if it is a bug or by design. If you do not put a MAC address in the VM NIC device a new MAC address is created on each reboot. This forces you to have to manually clear the FreeNAS ARP cache manually for the VM to be able to ping the FreeNAS box. So I hard coded a MAC address in the NIC and it is working reliably after reboots.