Skip to main content
Minor formatting
Source Link
AdminBee
  • 23.6k
  • 25
  • 56
  • 77

Packet Dropped seen from ifconfigifconfig could be due to many reasons, you should dig deeper into NIC statistics to figure out real reason. Below are some general reasons

  • NIC ring buffers getting full and unable to cope-up with incoming bursts of traffic
  • CPU receiving NIC interrupts is very busy and unable to process
  • some cable/hardware/duplex issues
  • some bug in NIC driver

Look at ethtool -S wlan0, iwconfig wlan0the output of

  • ethtool -S wlan0
  • iwconfig wlan0

and look atthe content of /proc/net/wireless/proc/net/wireless for any further information.

Packet Dropped seen from ifconfig could be due to many reasons, you should dig deeper into NIC statistics to figure out real reason. Below are some general reasons

  • NIC ring buffers getting full and unable to cope-up with incoming bursts of traffic
  • CPU receiving NIC interrupts is very busy and unable to process
  • some cable/hardware/duplex issues
  • some bug in NIC driver

Look at ethtool -S wlan0, iwconfig wlan0 and look at /proc/net/wireless for any further information

Packet Dropped seen from ifconfig could be due to many reasons, you should dig deeper into NIC statistics to figure out real reason. Below are some general reasons

  • NIC ring buffers getting full and unable to cope-up with incoming bursts of traffic
  • CPU receiving NIC interrupts is very busy and unable to process
  • some cable/hardware/duplex issues
  • some bug in NIC driver

Look at the output of

  • ethtool -S wlan0
  • iwconfig wlan0

and the content of /proc/net/wireless for any further information.

Source Link
VenkatC
  • 2.2k
  • 18
  • 12

Packet Dropped seen from ifconfig could be due to many reasons, you should dig deeper into NIC statistics to figure out real reason. Below are some general reasons

  • NIC ring buffers getting full and unable to cope-up with incoming bursts of traffic
  • CPU receiving NIC interrupts is very busy and unable to process
  • some cable/hardware/duplex issues
  • some bug in NIC driver

Look at ethtool -S wlan0, iwconfig wlan0 and look at /proc/net/wireless for any further information