aMule Forum

English => aMule Help => Topic started by: levinas69 on March 03, 2010, 04:37:25 PM

Title: Help: "Client UDP-Socket discarded" with no connection
Post by: levinas69 on March 03, 2010, 04:37:25 PM

Hi Folks:

My motherboard on my FreeBSD board just died and I just slipped in an old motherboard while I do the RMA.  Started up first time and zfs came back no problems -- I'd like to see Windows do that!

However, when I start amuled I get the following error repeated again and again:  WARNING! Client UDP-Socket discarded packet due to errors (2) while sending.

1. I am running: aMuled 2.2.6 using wxGTK2 v2.8.10 (OS: FreeBSD)

2. I can connect into aMuled with my doze box no problems.  But, amuled doesn't seem to be connecting to either kad or ed2k. 

3. I suspected a firewall quirk but I flushed rules and I am now simply running: allow ip from all to all.

4. All other network functions work with lags or problems.  This includes: ssh, samba, etc.

Any thoughts? 

Thanks,
j.


 

Title: Re: Help: "Client UDP-Socket discarded" with no connection
Post by: Stu Redman on March 03, 2010, 09:41:13 PM

Quote from: levinas69 on March 03, 2010, 04:37:25 PM

I'd like to see Windows do that!

It usually does.  :P
Anyway, new mainboard, new network chip, new MAC address.Your router thinks it's a different computer and assigns a new IP address. And so the port forwarding set up there doesn't work anymore.
So just check/fix port forwarding in your router.

Title: Re: Help: "Client UDP-Socket discarded" with no connection
Post by: levinas69 on March 05, 2010, 02:01:32 AM

Hi,

Thanks for the reply. 

I set the IP manually not by DHCP.  Admittedly, the MAC is different.  But, I reset my  little Dlink Router, so the MACs should be flushed from the arp cache.  Port forwarding settings should remain intact since the same IP has been retained.

Am I missing something?  Any thoughts?

Best,
j.

Title: Re: Help: "Client UDP-Socket discarded" with no connection
Post by: Stu Redman on March 05, 2010, 10:08:12 PM

Maybe your OS assigned a new device node for the changed network device and that causes the problem? (I don't know much about PnP of network cards on BSD I admit.)