strange Log for WAN interface "can't handle af183"
-
Apr 20 20:11:06 kernel re0: can't handle af183
Apr 20 20:11:06 kernel re0: can't handle af182
Apr 20 20:11:05 kernel re0: can't handle af117
Apr 20 20:11:01 kernel re0: can't handle af213anyone a hint ?
thx NP
-
Most likely, the interface is receiving corrupted frames with invalid packet headers. It could be a wiring or hardware problem.
-
F@#&* not what I was hoping for....
Your best guess wire or hardware?
Your beer s on me!
BrNP
-
Kind of a toss-up there. Could be on either end of the wire (switch/modem/CPE/etc or your NIC). Wire is the cheapest and easiest thing to swap, so always try that first. Replace with a clean patch that has factory ends.
-
Yes I used a brand new out of the bag cable
Pluged from the modem NIC to the Onboard NIC
So 2 things I ve to check if the modem port is a VLAN tag port but shouldn't matter
This will be fun!
-
@noplan said in strange Log for WAN interface "can't handle af183":
re0The 're0' is an important indication. It means Realtek - and you have a NIC based on that chip set.
Just for the kicks, use the forum search function, and enter "realtek".I've a box with 22 dead NIC's : 18 are realteks ...
-
if that IF dies idont care 1out of 5 ;)
the others are intel :)
do i really wanna know what realtek NICs are for .....
I've a box with 22 dead NIC's : 18 are realteks ...
-
@noplan said in strange Log for WAN interface "can't handle af183":
do i really wanna know what realtek NICs are for .....
So you knew it already : non-important connections, with "best-effort" performance.
-
yessssss and a pain in the a*%&§ when u ignored that uu knowed it
