High Packet Loss to Jail

[Richard Durso]

FreeNAS: 9.2.1.6-RELEASE

Hardware: Supermicro MB (MBD-X10SLM-F-O R) with Intel Core i3-4130 (Haswell), Dual Core 2.9 GHz, Intel HD graphics 4400 and 32GB DDR3 1600 Mhz ECC RAM. 4 x 4TB WD RED NAS Drives.

This is home installation, very light load (usually idle). The FreeNAS and my desktop are both on the same ethernet switch.

I have no packet loss between my desktop and the FreeNAS directly:

--- freenas.localdomain ping statistics ---
349 packets transmitted, 349 received, 0% packet loss, time 348000ms
rtt min/avg/max/mdev = 0.116/0.251/0.299/0.027 ms

However, if I ping the jail on FreeNAS from my desktop I have very high packet loss:

--- plexmediaserver_1.localdomain ping statistics ---
580 packets transmitted, 44 received, 92% packet loss, time 578999ms
rtt min/avg/max/mdev = 0.130/0.186/0.359/0.044 ms

The jail is up and running the entire time:
root@plexmediaserver_1:/ # uptime
7:44PM up 15 days, 7:15, 0 users, load averages: 0.06, 0.03, 0.00

I'm not sure how to troubleshoot this... suggestions?

 

[SweetAndLow]

You probably have an ip conflict on your network. What ip range is your jail configured for and what range does your router use for dhcp?

 

[Richard Durso]

pfSense handles my DHCP (disabled on router). DHCP Server Range is 192.168.0.10 - 192.168.0.50. All Server and desktop IPs are assigned statically outside this range. pfSense is configured to give static lease to the same IP address based on MAC address should the system make a DHCP request. Based on this I shouldn't have an IP address conflict.

Desktop: 192.168.0.246
FreeNAS: 192.168.0.250
Plex Jail: 192.168.0.239

I did a sustained ping to 3 other jails, no packet loss. But I can keep duplicating the packet loss to my plex jail.

I stopped the plex jail. Was no longer able to ping that IP address got "Destination Host Unreachable". If I had an IP conflict it should have still pinged.

Started the plex jail again, still have high packet loss:

--- plexmediaserver_1.localdomain ping statistics ---
351 packets transmitted, 127 received, 63% packet loss, time 349998ms
rtt min/avg/max/mdev = 0.115/0.185/0.378/0.049 ms

 

[Richard Durso]

I SSH'd into the FreeNAS and tried to ping the Plex Jail:

[rich@freenas ~]$ ping plexmediaserver_1
PING plexmediaserver_1.localdomain (192.168.0.239): 56 data bytes
^C
--- plexmediaserver_1.localdomain ping statistics ---
32 packets transmitted, 0 packets received, 100.0% packet loss

Should that work?

I then went into a different jail to ping the plex jail:

[root@freenas] ~# jexec 1 csh
root@headphones_1:/ # ping plexmediaserver_1
PING plexmediaserver_1.localdomain (192.168.0.239): 56 data bytes
64 bytes from 192.168.0.239: icmp_seq=0 ttl=64 time=0.040 ms
^C
--- plexmediaserver_1.localdomain ping statistics ---
13 packets transmitted, 1 packets received, 92.3% packet loss

I then had this jail ping itself:

root@headphones_1:/ # ping headphones
PING headphones.localdomain (192.168.0.238): 56 data bytes
^C
--- headphones.localdomain ping statistics ---
34 packets transmitted, 0 packets received, 100.0% packet loss

 

[SweetAndLow]

you can't ping the hostname unless you have dns configured for that hostname. Does the name resolve to an ip? What happens if you ping the IP?

EDIT: i take that back i see that you are resolving the hostname in the ping correctly. You have some kind of netmask or ip issues going on. Can you ping the gateway from the jail?

 

[Richard Durso]

From the jail I tested above:

root@headphones_1:/ # ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=0.268 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.095 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.109 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.124 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.139 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.147 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=0.163 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=0.177 ms
^C
--- 192.168.0.1 ping statistics ---
8 packets transmitted, 8 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.095/0.153/0.268/0.050 ms


From the Plex Jail:

root@plexmediaserver_1:/ # ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=0.245 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.209 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.094 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.116 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.121 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.137 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=0.156 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=0.165 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=0.180 ms
^C
--- 192.168.0.1 ping statistics ---
9 packets transmitted, 9 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.094/0.158/0.245/0.045 ms

Where would the default gateway be configured within a jail? Nothin in the "rc.conf" about it.

 

[Richard Durso]

As a follow-up, I can also ping the gateway (pfSense) via DNS:

root@plexmediaserver_1:/ # ping pfsense.localdomain
PING pfsense.localdomain (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=0.212 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.169 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.189 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.197 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.091 ms
^C
--- pfsense.localdomain ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss

And I can ping the router on the other side of pfSense gateway:

root@plexmediaserver_1:/ # ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=63 time=0.727 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=63 time=0.674 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=63 time=0.684 ms
^C
--- 192.168.1.1 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss

 

[SweetAndLow]

your gateway is probably 192.168.0.1(your router). It is good that you can ping that but strange that you can't ping the other jails.

 

[Richard Durso]

To add to the confusion. The plex jail can ping other jails:

root@plexmediaserver_1:/ # ping headphones
PING headphones.localdomain (192.168.0.238): 56 data bytes
64 bytes from 192.168.0.238: icmp_seq=0 ttl=64 time=0.035 ms
64 bytes from 192.168.0.238: icmp_seq=1 ttl=64 time=0.022 ms
64 bytes from 192.168.0.238: icmp_seq=2 ttl=64 time=0.023 ms
64 bytes from 192.168.0.238: icmp_seq=3 ttl=64 time=0.020 ms
64 bytes from 192.168.0.238: icmp_seq=4 ttl=64 time=0.035 ms
64 bytes from 192.168.0.238: icmp_seq=5 ttl=64 time=0.022 ms
64 bytes from 192.168.0.238: icmp_seq=6 ttl=64 time=0.022 ms
64 bytes from 192.168.0.238: icmp_seq=7 ttl=64 time=0.030 ms
64 bytes from 192.168.0.238: icmp_seq=8 ttl=64 time=0.022 ms
64 bytes from 192.168.0.238: icmp_seq=9 ttl=64 time=0.032 ms
^C
--- headphones.localdomain ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss

But the other jail can not ping the plex jail:

root@headphones_1:/ # ping plexmediaserver_1
PING plexmediaserver_1.localdomain (192.168.0.239): 56 data bytes
^C
--- plexmediaserver_1.localdomain ping statistics ---
10 packets transmitted, 0 packets received, 100.0% packet loss

Weird.

 

[Richard Durso]

I stumbled across a post about "Multiple nics on one subnet" https://forums.freenas.org/index.php?threads/multiple-network-interfaces-on-a-single-subnet.20204/ the discussion is more about load balancing.

But I do have 2 nics on a single subnet as lagg0 I simply unplugged one of ethernet wires and all my odd pinging issues outlined above went away.

No packet loss to the Plex Jail any more, from the FreeNAS it can ping the jails properly now.

Are 2 nics on 1 subnet an invalid configuration or is this something else?

BTW - nothing in the FreeNAS gui about the link being unplugged. Still have green "indicator". Nothing noted on the Network Settings > Interface or Link Aggregation screens.

 

[SweetAndLow]

You have a networking issues and you don't mention that YOU HAVE LAGG configured. To use lagg you you need switches that support it and and knowledge of how it works. Next you are going to tell me you are using wifi. Just delete everything you did with lagg and you can still have two nic just not joined.

 

[Richard Durso]

The LAGG has been in place since the initial setup on 9.2.0.0 when it came out. Not something recently added. No other issues from Windows, Linux, BSD desktops using CIFS / NFS, etc. Didn't know it was relevant to this issue. I'll remove it.