Wake On lan ; how to avoid "nfe0 up and down"

[Blanche]

Hello all;

I would like to wake on line my freenas (freebdd 11.1), it works but after wake up I always have to go in the shell and type
ifconfig nfe0 down
ifconfig nfe0 up
before i can connect to the server. I have this message :
"discard frame w/o leading ethernet header (len 0 pkt len 0) in loop

There is few setup files :

Code:

# ifconfig
nfe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
		options=82008<VLAN_MTU,WOL_MAGIC,LINKSTATE>
		ether 00:17:31:83:9c:57
		hwaddr 00:17:31:83:9c:57
		inet 192.168.1.101 netmask 0xffffff00 broadcast 192.168.1.255
		nd6 options=9<PERFORMNUD,IFDISABLED>
		media: Ethernet autoselect (100baseTX <full-duplex>)
		status: active

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
		options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
		inet6 ::1 prefixlen 128
		inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
		inet 127.0.0.1 netmask 0xff000000
		nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
		groups: lo

Code:

dmesg | grep nfe0
nfe0: discard frame w/o leading ethernet header (len 4294967295 pkt len 4294967295)
nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0)
....
nfe0: link state changed to DOWN
nfe0: link state changed to UP
nfe0: link state changed to DOWN
nfe0: link state changed to UP

I try this :
https://forums.freebsd.org/threads/...-frame-without-leading-ethernet-header.28475/
but without success.

Anyone have an idea of what to do ?

 

[kdragon75]

Wake on LAN is supported in freebdd 11.1 FreeBSD 11.1 but not in freenas FreeNAS. FreeNAS is intended to be treated as a server. The normal workarounds may not survive reboots or updates as FreeNAS works like an appliance. you are not intended to make changes to the underlying system.

With all of that said, you can write a script to configure things at boot time. The script could add configurations to UDEV and run if up/if down on an event triggered by WOL. I dont to bash scripting but its doable. Also...

The nfe(4) driver is buggy, I have seen similar behaviour on a machine I built for a friend. Sometimes just replugging the cable cured the problems.

The nVidia NIC drives are indeed buggy and unreliable. You may be better off getting a better supported NIC, ideally one built into a server grade motherboard.

 

[Blanche]

Thanks a lot for your reply.
As you notice, i'm even not able to retype simple words without faults, so... script bashing !... i must forget for sure or my script 'll works when "hens 'll have teeth"...
I found an old network card in my attic i'll try it and cross my fingers ...
Thank you again kdragon75 !