Network constantly reconnecting

[xmicks]

looks like my networking is constantly doing the whole dhcp thing

this is what the error logs are telling me

Code:

FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b

i have an x10slm-f motherboard with an intel i217 nic and an i210 nic. on both nics its throwing this error


here a feed of my error logs: (its not the whole feed. if i need to post that, let me know)

Code:

Apr 30 23:43:06 FreeNAS devd: Executing '/etc/pccard_ether epair2a start'
Apr 30 23:43:06 FreeNAS devd: Executing '/etc/pccard_ether epair2b start'
Apr 30 23:43:06 FreeNAS devd: Executing '/etc/rc.d/dhclient quietstart epair2a'
May 1 01:43:06 FreeNAS epair2a: Ethernet address: 02:ff:20:00:07:0a
May 1 01:43:06 FreeNAS epair2b: Ethernet address: 02:ff:70:00:08:0b
May 1 01:43:06 FreeNAS kernel: epair2a: link state changed to UP
May 1 01:43:06 FreeNAS kernel: epair2a: link state changed to UP
May 1 01:43:06 FreeNAS kernel: epair2b: link state changed to UP
May 1 01:43:06 FreeNAS kernel: epair2b: link state changed to UP
May 1 01:43:06 FreeNAS kernel: epair2a: promiscuous mode enabled
May 1 01:43:06 FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
May 1 01:43:06 FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
May 1 01:43:11 FreeNAS kernel: arp: 10.0.8.12 moved from 02:ff:20:00:07:0a to 00:25:90:59:ef:ef on epair2b
May 1 01:44:20 FreeNAS kernel: ifa_del_loopback_route: deletion failed: 48
May 1 01:44:20 FreeNAS Freed UMA keg (udp_inpcb) was not empty (120 items). Lost 12 pages of memory.
May 1 01:44:20 FreeNAS Freed UMA keg (udpcb) was not empty (1169 items). Lost 7 pages of memory.
May 1 01:44:20 FreeNAS Freed UMA keg (tcptw) was not empty (540 items). Lost 12 pages of memory.
May 1 01:44:20 FreeNAS Freed UMA keg (tcp_inpcb) was not empty (120 items). Lost 12 pages of memory.
May 1 01:44:20 FreeNAS Freed UMA keg (tcpcb) was not empty (27 items). Lost 9 pages of memory.
May 1 01:44:20 FreeNAS hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
May 1 01:44:20 FreeNAS hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required

 

[joeschmuck]

Did you have a question? If you do, what version of FreeNAS are you running, what hardware are you using, are you also running FreeNAS on a VM system, what problems are you experiencing with FreeNAS, do you have any jails/plugins, and then ask your question. You might also consider doing a Google search (something the forum rules tell you to try) to see if you can look up this problem you might be having. I did so and found the following link, not sure it applies to you since I don't have any details but if it does, then all is okay. https://bugs.freenas.org/issues/7413

 

[xmicks]

okay i might have given a bit to less information. im using freenas 9.10-stable now, previously(like last week, i was using 9.3-stable. on a supermicro x10slm-f motherboard which has 2 intel nics: a i210-AT and a i217-LM. and freenas is not running of a vm. i'm also using 3 plugins: sabnzbd, emby and plex.

ive done quite a lot of research and ive learnt that this might be an issue releated to the driver support of freebsd for my particular intel nics. i dont actually experience any connectivity issues. as some people have. when sabnzbd is running i get download speeds up til 140 mbps, so speeds are okay i have a incomming line of 150mbps. till this day my server is always been online and i could always connect to it. but i do notice that my plugins, especially sabnzbd(because thats the first plugin ive installed and been working with.) is a lot down, cant start or retrieve treemenu. one time i can ping to 8.8.8.8 the other time the jail has no internet) or it has and in the sabnzbd gui it says no internet. also tried static and dhcp ip on the jais networking. the other plugings, emby and plex, i didnt use much yet.

i do see my normal network interfaces(ithink the i210 is emo and i217 is the igb0) constantly changing its link from up to down and doing the whole dhcp thing. then theres the epairXa and epairXb (where X is 1,2,3,...) what are those epair interfaces? and why do the constantly reconnect?

now what do i do about this? is this a 'simple' update the driver and its fixed? his is my first option and tried that but i cant extract the tar.gz file.

i did this, following the readme notes of the driver https://downloadmirror.intel.com/17509/eng/README.txt
using this driver https://downloadcenter.intel.com/download/17509/Network-Adapter-Gigabit-Base-Driver-for-FreeBSD-?v=t

Code:

[root@FreeNAS ~]# cd /usr/local/emxx
[root@FreeNAS /usr/local/emxx]# fetch https://downloadcenter.intel.com/downloads
/eula/17509/Network-Adapter-Gigabit-Base-Driver-for-FreeBSD-?httpDown=https%3A%2
F%2Fdownloadmirror.intel.com%2F17509%2Feng%2Fem-7.6.1.tar.gz -o em-7.6.1.tar.gz
em-7.6.1.tar.gz 100% of 15 kB 218 MBps 00m00s
[root@FreeNAS /usr/local/emxx]# ls
em-7.6.1.tar.gz
[root@FreeNAS /usr/local/emxx]# tar -xf em-7.6.1.tar.gz
tar: Error opening archive: Unrecognized archive format
[root@FreeNAS /usr/local/emxx]# tar xvfz em-7.6.1.tar.gz
tar: Error opening archive: Unrecognized archive format

i always get that error "tar: Error opening archive: Unrecognized archive format"

what is wrong with my network interfaces and is it possible that plugins like sabnzbd are not working properly due my main network connectivity issues?

this are some errors i get on sabnzbd

Code:

May 1 19:08:13 FreeNAS devd: Executing '/etc/pccard_ether epair3a start'
May 1 19:08:13 FreeNAS devd: Executing '/etc/pccard_ether epair3b start'
May 1 19:08:13 FreeNAS devd: Executing '/etc/rc.d/dhclient quietstart epair3a'
May 1 21:08:13 FreeNAS epair3a: Ethernet address: 02:ff:20:00:08:0a
May 1 21:08:13 FreeNAS epair3b: Ethernet address: 02:ff:70:00:09:0b
May 1 21:08:13 FreeNAS kernel: epair3a: link state changed to UP
May 1 21:08:13 FreeNAS kernel: epair3a: link state changed to UP
May 1 21:08:13 FreeNAS kernel: epair3b: link state changed to UP
May 1 21:08:13 FreeNAS kernel: epair3b: link state changed to UP
May 1 21:08:13 FreeNAS kernel: epair3a: promiscuous mode enabled
May 1 21:08:13 FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b
May 1 21:08:13 FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b
May 1 21:08:13 FreeNAS kernel: pid 6886 (Plex Media Server), uid 972: exited on signal 11
May 1 21:55:31 FreeNAS manage.py: [freeadmin.navtree:576] Couldn't retrieve http://10.0.8.12/plugins/emby/5/_s/treemenu: timed out
May 2 00:00:00 FreeNAS syslog-ng[1459]: Configuration reload request received, reloading configuration;
May 2 18:11:16 FreeNAS manage.py: [freeadmin.navtree:576] Couldn't retrieve http://10.0.8.12/plugins/sabnzbd/6/_s/treemenu: timed out
May 2 18:11:36 FreeNAS manage.py: [freeadmin.navtree:576] Couldn't retrieve http://10.0.8.12/plugins/sabnzbd/6/_s/treemenu: timed out
May 2 18:33:42 FreeNAS manage.py: [freeadmin.navtree:576] Couldn't retrieve http://10.0.8.12/plugins/sabnzbd/6/_s/treemenu: timed out
May 2 20:00:00 FreeNAS autosnap.py: [tools.autosnap:61] Popen()ing: /sbin/zfs snapshot "Volume1/SharedSet@auto-20160502.2000-2w"
May 2 20:53:47 FreeNAS manage.py: [freeadmin.navtree:576] Couldn't retrieve http://10.0.8.12/plugins/sabnzbd/6/_s/treemenu: timed out
May 2 23:59:46 FreeNAS manage.py: [freeadmin.navtree:576] Couldn't retrieve http://10.0.8.12/plugins/sabnzbd/6/_s/treemenu: timed out
May 3 00:00:00 FreeNAS syslog-ng[1459]: Configuration reload request received, reloading configuration;
May 3 00:00:00 FreeNAS autosnap.py: [tools.autosnap:61] Popen()ing: /sbin/zfs snapshot "Volume1/SharedSet@auto-20160503.0000-2w"
May 3 01:06:19 FreeNAS manage.py: [freeadmin.navtree:576] Couldn't retrieve http://10.0.8.12/plugins/sabnzbd/6/_s/treemenu: timed out
May 3 01:06:40 FreeNAS manage.py: [freeadmin.navtree:576] Couldn't retrieve http://10.0.8.12/plugins/sabnzbd/6/_s/treemenu: timed out
May 3 01:07:17 FreeNAS manage.py: [plugins.utils:91] Couldn't retrieve http://10.0.8.12/plugins/sabnzbd/6/_s/status: No JSON object could be decoded
May 3 01:07:36 FreeNAS manage.py: [plugins.utils:91] Couldn't retrieve http://10.0.8.12/plugins/sabnzbd/6/_s/status: No JSON object could be decoded

what does this mean: "kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b"?