Problems with Network Connection..?

Status
Not open for further replies.

Sty

Dabbler
Joined
Jun 2, 2015
Messages
16
I have recently been suffering many network troubles with my FreeNAS mini box. I wonder if this has some to do with it? I did recently find that no "network interface" was set up and added igb0 (I'm not using igb1) which according to ifconfig was setup and working with an IP address. However this hasn't seemed to fix anything. Could someone explain to me what epair1a and epair1b are and maybe what's going on?

Thank you.

Code:
athena.local kernel log messages:
> epair1a: link state changed to DOWN
> epair1b: link state changed to DOWN
> epair1a: Ethernet address: 02:ff:20:00:06:0a
> epair1b: Ethernet address: 02:ff:70:00:07:0b
> epair1a: link state changed to UP
> epair1b: link state changed to UP
> epair1a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair1b
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (240 items). Lost 24 pages of memory.
> Freed UMA keg (udpcb) was not empty (2171 items). Lost 13 pages of memory.
> Freed UMA keg (tcptw) was not empty (900 items). Lost 20 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (290 items). Lost 29 pages of memory.
> Freed UMA keg (sackhole) was not empty (1625 items). Lost 13 pages of memory.
> Freed UMA keg (tcpcb) was not empty (108 items). Lost 36 pages of memory.
> Freed UMA keg (ripcb) was not empty (60 items). Lost 6 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> arp: 192.168.75.23 moved from 02:ff:20:00:06:0a to d0:50:99:2d:fb:8e on epair1b
> epair1a: link state changed to DOWN
> epair1b: link state changed to DOWN
> epair1a: Ethernet address: 02:ff:20:00:06:0a
> epair1b: Ethernet address: 02:ff:70:00:07:0b
> epair1a: link state changed to UP
> epair1b: link state changed to UP
> epair1a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair1b
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (240 items). Lost 24 pages of memory.
> Freed UMA keg (udpcb) was not empty (2171 items). Lost 13 pages of memory.
> Freed UMA keg (tcptw) was not empty (765 items). Lost 17 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (290 items). Lost 29 pages of memory.
> Freed UMA keg (sackhole) was not empty (1625 items). Lost 13 pages of memory.
> Freed UMA keg (tcpcb) was not empty (99 items). Lost 33 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> arp: 192.168.75.23 moved from 02:ff:20:00:06:0a to d0:50:99:2d:fb:8e on epair1b
> epair1a: link state changed to DOWN
> epair1b: link state changed to DOWN
> epair1a: Ethernet address: 02:ff:20:00:06:0a
> epair1b: Ethernet address: 02:ff:70:00:07:0b
> epair1a: link state changed to UP
> epair1b: link state changed to UP
> epair1a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair1b
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (210 items). Lost 21 pages of memory.
> Freed UMA keg (udpcb) was not empty (1837 items). Lost 11 pages of memory.
> Freed UMA keg (tcptw) was not empty (765 items). Lost 17 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (240 items). Lost 24 pages of memory.
> Freed UMA keg (sackhole) was not empty (1375 items). Lost 11 pages of memory.
> Freed UMA keg (tcpcb) was not empty (99 items). Lost 33 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> arp: 192.168.75.23 moved from 02:ff:20:00:06:0a to d0:50:99:2d:fb:8e on epair1b
> epair1a: link state changed to DOWN
> epair1b: link state changed to DOWN
> epair1a: Ethernet address: 02:ff:20:00:06:0a
> epair1b: Ethernet address: 02:ff:70:00:07:0b
> epair1a: link state changed to UP
> epair1b: link state changed to UP
> epair1a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair1b
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (210 items). Lost 21 pages of memory.
> Freed UMA keg (udpcb) was not empty (1837 items). Lost 11 pages of memory.
> Freed UMA keg (tcptw) was not empty (630 items). Lost 14 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (290 items). Lost 29 pages of memory.
> Freed UMA keg (tcpcb) was not empty (99 items). Lost 33 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> arp: 192.168.75.23 moved from 02:ff:20:00:06:0a to d0:50:99:2d:fb:8e on epair1b
> epair1a: link state changed to DOWN
> epair1b: link state changed to DOWN
> epair1a: Ethernet address: 02:ff:20:00:06:0a
> epair1b: Ethernet address: 02:ff:70:00:07:0b
> epair1a: link state changed to UP
> epair1b: link state changed to UP
> epair1a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair1b
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (240 items). Lost 24 pages of memory.
> Freed UMA keg (udpcb) was not empty (2171 items). Lost 13 pages of memory.
> Freed UMA keg (tcptw) was not empty (900 items). Lost 20 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (240 items). Lost 24 pages of memory.
> Freed UMA keg (sackhole) was not empty (625 items). Lost 5 pages of memory.
> Freed UMA keg (tcpcb) was not empty (99 items). Lost 33 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> arp: 192.168.75.23 moved from 02:ff:20:00:06:0a to d0:50:99:2d:fb:8e on epair1b
> ifa_del_loopback_route: deletion failed: 48
> igb0: link state changed to DOWN
> igb0: link state changed to UP
> epair1a: link state changed to DOWN
> epair1b: link state changed to DOWN
> epair1a: Ethernet address: 02:ff:20:00:06:0a
> epair1b: Ethernet address: 02:ff:70:00:07:0b
> epair1a: link state changed to UP
> epair1b: link state changed to UP
> epair1a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair1b
> arp: 192.168.75.23 moved from 02:ff:20:00:06:0a to d0:50:99:2d:fb:8e on epair1b
> epair0a: link state changed to DOWN
> epair0b: link state changed to DOWN
> epair0a: Ethernet address: 02:ff:20:00:05:0a
> epair0b: Ethernet address: 02:ff:70:00:07:0b
> epair0a: link state changed to UP
> epair0b: link state changed to UP
> epair0a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair0b
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (240 items). Lost 24 pages of memory.
> Freed UMA keg (udpcb) was not empty (2171 items). Lost 13 pages of memory.
> Freed UMA keg (tcptw) was not empty (900 items). Lost 20 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (270 items). Lost 27 pages of memory.
> Freed UMA keg (tcpcb) was not empty (99 items). Lost 33 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (240 items). Lost 24 pages of memory.
> Freed UMA keg (udpcb) was not empty (2171 items). Lost 13 pages of memory.
> Freed UMA keg (tcptw) was not empty (1530 items). Lost 34 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (930 items). Lost 93 pages of memory.
> Freed UMA keg (tcpcb) was not empty (117 items). Lost 39 pages of memory.
> Freed UMA keg (ripcb) was not empty (120 items). Lost 12 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> arp: 192.168.75.23 moved from 02:ff:20:00:05:0a to d0:50:99:2d:fb:8e on epair0b
> epair1a: link state changed to DOWN
> epair1b: link state changed to DOWN
> epair1a: Ethernet address: 02:ff:20:00:06:0a
> epair1b: Ethernet address: 02:ff:70:00:07:0b
> epair1a: link state changed to UP
> epair1b: link state changed to UP
> epair1a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair1b
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (240 items). Lost 24 pages of memory.
> Freed UMA keg (udpcb) was not empty (2171 items). Lost 13 pages of memory.
> Freed UMA keg (tcptw) was not empty (900 items). Lost 20 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (270 items). Lost 27 pages of memory.
> Freed UMA keg (sackhole) was not empty (375 items). Lost 3 pages of memory.
> Freed UMA keg (tcpcb) was not empty (99 items). Lost 33 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> epair1a: link state changed to DOWN
> epair1b: link state changed to DOWN
> epair1a: Ethernet address: 02:ff:20:00:06:0a
> epair1b: Ethernet address: 02:ff:70:00:07:0b
> epair1a: link state changed to UP
> epair1b: link state changed to UP
> epair1a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair1b
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (240 items). Lost 24 pages of memory.
> Freed UMA keg (udpcb) was not empty (2171 items). Lost 13 pages of memory.
> Freed UMA keg (tcptw) was not empty (765 items). Lost 17 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (270 items). Lost 27 pages of memory.
> Freed UMA keg (tcpcb) was not empty (99 items). Lost 33 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> epair1a: link state changed to DOWN
> epair1b: link state changed to DOWN
> epair1a: Ethernet address: 02:ff:20:00:06:0a
> epair1b: Ethernet address: 02:ff:70:00:07:0b
> epair1a: link state changed to UP
> epair1b: link state changed to UP
> epair1a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair1b
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (240 items). Lost 24 pages of memory.
> Freed UMA keg (udpcb) was not empty (2171 items). Lost 13 pages of memory.
> Freed UMA keg (tcptw) was not empty (765 items). Lost 17 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (240 items). Lost 24 pages of memory.
> Freed UMA keg (tcpcb) was not empty (99 items). Lost 33 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> epair1a: link state changed to DOWN
> epair1b: link state changed to DOWN
> epair1a: Ethernet address: 02:ff:20:00:06:0a
> epair1b: Ethernet address: 02:ff:70:00:07:0b
> epair1a: link state changed to UP
> epair1b: link state changed to UP
> epair1a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair1b
> arp: 192.168.75.23 moved from 02:ff:20:00:06:0a to d0:50:99:2d:fb:8e on epair1b
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (240 items). Lost 24 pages of memory.
> Freed UMA keg (udpcb) was not empty (2171 items). Lost 13 pages of memory.
> Freed UMA keg (tcptw) was not empty (765 items). Lost 17 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (270 items). Lost 27 pages of memory.
> Freed UMA keg (sackhole) was not empty (1625 items). Lost 13 pages of memory.
> Freed UMA keg (tcpcb) was not empty (99 items). Lost 33 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> epair1a: link state changed to DOWN
> epair1b: link state changed to DOWN
> epair1a: Ethernet address: 02:ff:20:00:06:0a
> epair1b: Ethernet address: 02:ff:70:00:07:0b
> epair1a: link state changed to UP
> epair1b: link state changed to UP
> epair1a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair1b
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (210 items). Lost 21 pages of memory.
> Freed UMA keg (udpcb) was not empty (1837 items). Lost 11 pages of memory.
> Freed UMA keg (tcptw) was not empty (765 items). Lost 17 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (270 items). Lost 27 pages of memory.
> Freed UMA keg (tcpcb) was not empty (99 items). Lost 33 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> arp: 192.168.75.23 moved from 02:ff:20:00:06:0a to d0:50:99:2d:fb:8e on epair1b
 

DrKK

FreeNAS Generalissimo
Joined
Oct 15, 2013
Messages
3,630
Can you tell us more about what problems you're having? What are the symptoms? "I am having network problems" doesn't tell us anything.

Looking at this, I'd be concerned that it seems your Mini doesn't have an IP address, which (if correct) means you won't be able to do anything at all with it, until we solve it.
 

Sty

Dabbler
Joined
Jun 2, 2015
Messages
16
The problems tend to be with FreeNAS plug-ins dying over time. Especially Transmission. All of a sudden the network will cease to have connection unless I restart the jail.

I do not see any problems with the FreeNAS master itself, and honestly have just been trying to figure out what it may be. When I poked around in the Web interface I saw that it said no network interfaces were set up, yet ssh and the like has never been a problem. I confirmed via ifconfig which interface needed setup and that seems good.

Since doing that yesterday I received that email. I have not fixed the jail connection problems and have not observed connection issues with the FreeNAS (network shares both samba and AFS have been stable). So I guess, what exactly am I seeing on that email is the first question.

Sorry, full-time grad student makes finding troubleshooting time hard.
 

DrKK

FreeNAS Generalissimo
Joined
Oct 15, 2013
Messages
3,630
OK, well one thing that (believe or not) has worked for people experiencing strange network issues vis-a-vis jails, is go into the jails screen, and for the jail in question, toggle the state of VIMAGE. If it's off, turn it on, and vice versa.

One thing that I personally notice: if my main DHCP server/gateway drops off for any reason, when it comes back up, the FreeNAS itself will reestablish networking, but I may have jails that require a restart before the network sorts itself out.
 

Sty

Dabbler
Joined
Jun 2, 2015
Messages
16
I just tried switching VIMAGE from on to off. I'll report back after I try for a little while. What exactly is that setting?

Another interesting fact... In the Web-UI I show IPs for all my jails but in the shell, if I run jls I see no IP for the ones that are working fine... I just don't know what's going on.
 
Last edited by a moderator:

DrKK

FreeNAS Generalissimo
Joined
Oct 15, 2013
Messages
3,630
Basically, the VIMAGE thing is a bit mysterious. I am not a BSD-master, so take what I'm saying with a grain of salt, but what it apparently does is this:

If the VIMAGE is on, then, the jail has its very own network stack. If it is off, it shares the stack of the host. So for example, let's say your jail is 192.168.1.200, and your host is 192.168.1.10. Let's suppose that the host is running a web server on port 80, but the jail is not. If VIMAGE is *not* checked, then if you visit http://192.168.1.200:80/, you *will actually get* the daemon listening on 192.168.1.10. If both are running web servers, then it works as you imagine. Other things you will notice: there is no DHCP to obtain the IP address on a non VIMAGE'd jail (you'll see you can't select it if VIMAGE is off), it just sort of is a "second" IP address for the host. So that for example, in most modern routers, you won't see the jail IP listed as one of the connections in your router's list of connections. If you run something like "fing" on Android (which I *highly* recommend), you see it would list 192.168.1.10 (+1), meaning, there is another IP address associated to this host, etc.

If, on the other hand, VIMAGE is on, then the jail is its own dude, will be listed as its own connection, will have its own (non-sensical/random) MAC address, and will be independently resolved in ARP.

Now, functionally, for Joe Blow user running some jails, it doesn't really matter, for 90% of things. That's why I used to just turn off VIMAGE. But, as of 9.10, especially, a few of us have been noticing that VIMAGE being on, or off, seems to cause things to either do weird network stuff, or not, and I (at least) have no cogent explanation. e.g., my Plex is not properly discoverable, and acts weird, if VIMAGE is off. My UniFi from Ubiquiti software acts weird, if VIMAGE is off. But my other jail, that has the ZNC bouncer, the DNS server, the web server, and a bunch of other stuff, doesn't seem to care that VIMAGE is off.

So basically: if your jail is acting weird vis-a-vis network, try turning the VIMAGE on if it's off, and off if it's on. It has a 75% chance of resolving the problem.

It is unsatisfactory, I agree, that a cogent explanation for what's going on is not obvious---it is certainly not the BSD way to just say "yeah, click it off, then it works, I have no idea why". But, that's where I'm at, at least.

Maybe one of the other guys has some insight.
 
Status
Not open for further replies.
Top