11th February 2013
|
|
Administrator
|
|
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 4,131
|
|
"Intel Packet of Death" not Intel's problem
From http://h-online.com/-1801537
Quote:
In the middle of last week, an engineer at a Californian provider of VoIP appliances made a disturbing observation. He discovered a network packet trace that reliably killed the software running on his company's Asterisk VoIP phone server. The packet does not crash the system though, instead it paralyses the network controller so much so that even a reboot will not return the interface to life. The system has to be powered down and disconnected from power for a short time to restore the network connection.
The network controller in question is the Intel 82574L which is mainly used on server boards.
[snip]
Shortly afterwards, Intel published a statement, which made it clear that the actual Ethernet controller was not to blame. Instead, the issue concerns only a motherboard from a specific manufacturer who programmed an EEPROM incorrectly.
|
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
|