aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Client UDP-Socket: Packet discarded due to error while sending.  (Read 3784 times)

HKM

  • Jr. Member
  • **
  • Karma: 4
  • Offline Offline
  • Posts: 77
  • You don't know enough to know that you don't know.
Client UDP-Socket: Packet discarded due to error while sending.
« on: December 19, 2015, 01:41:10 AM »
Now what would cause these below?

Code: [Select]
2015-12-18 18:33:05: WARNING! Client UDP-Socket: Packet to 188.152.25.22:14273 discarded due to error (2) while sending.
 2015-12-18 18:33:05: WARNING! Client UDP-Socket: Packet to 123.243.240.34:1534 discarded due to error (2) while sending.
 2015-12-18 18:33:05: WARNING! Client UDP-Socket: Packet to 80.86.50.187:63440 discarded due to error (2) while sending.
 2015-12-18 18:33:05: WARNING! Client UDP-Socket: Packet to 82.53.7.53:4672 discarded due to error (2) while sending.
 2015-12-18 18:33:05: WARNING! Client UDP-Socket: Packet to 175.0.192.131:16223 discarded due to error (2) while sending.
 2015-12-18 18:33:06: WARNING! Client UDP-Socket: Packet to 87.3.72.35:4672 discarded due to error (2) while sending.
 2015-12-18 18:33:06: WARNING! Client UDP-Socket: Packet to 2.138.246.137:58497 discarded due to error (2) while sending.
 2015-12-18 18:33:06: WARNING! Client UDP-Socket: Packet to 78.235.116.34:23351 discarded due to error (2) while sending.
 2015-12-18 18:33:06: WARNING! Client UDP-Socket: Packet to 90.71.201.175:38241 discarded due to error (2) while sending.
 2015-12-18 18:33:06: WARNING! Client UDP-Socket: Packet to 2.224.162.121:5509 discarded due to error (2) while sending.
 2015-12-18 18:33:06: WARNING! Client UDP-Socket: Packet to 209.209.210.82:7153 discarded due to error (2) while sending.

From MuleUDPSocket.cpp:

Code: [Select]
AddLogLineN((wxT("WARNING! ") + m_name + wxT(": Packet to "))
   << Uint32_16toStringIP_Port(ip, port)
   << wxT(" discarded due to error (") << error << wxT(") while sending."));
 sent = true;

I can see UDP socket error returned when its busy and can't send data currently so it resent when socket is ready. Which is odd since the system aMuleD is hosted on custom ITX box with 3GHZ P4 with 2GB DDR2 PC2700 with Gbit dual NIC with enough resources as its only running modified nginx and aMuleD as FServ for local and remote. The unit is behind FVS318v3 hardware firewall but on open DMZ. As its using CentOS6.7i396 the tx/rx transmission packets is handled via IPTables. I have currently modified the default timeout and set it as 60s UDP/180s TCP session so it does not have problem with unable to free TCP/UDP port. Since I have custom IPTables loggin chain enabled via kernel.panic bind to Rsyslog /var/log/iptables.log if I CAT then I just mostly basic routing filters like these for aMuleD.

Code: [Select]
Fri, 2015-12-18 19:24:34 - ICMP packet - Source: 192.168.0.3 - Destination: 190.235.108.130 - [ICMP Type: 3 Code: 10    Icmp error message received for uninitiated connection. Orginal Src 190.235.108.130 Dst 192.168.0.3 TCP Src:55204 Dst:54662, dropping packet from LAN]
Logged