Client IP address is not automatically refreshed

[bluemax]

Hey,

I'm wondering if you ever experienced the same as me with MLDonkey 2.9.0 for Windows:
I'm running the core with run_mldonkey.exe with all the necessary ports forwarded in my SMC router to my PC.
My WAN IP address is correctly recongnized and is written to the Client_ip field of the core settings.
However sometimes after my router gets new IP address on its WAN interface, the client_ip does not refresh itself and so I'm not able to download anything from this point, I loose all incoming and outgoing connections. I think this is understandable because the IP that is in the client_ip field does not match my client any more.
I tried to give a discover_ip command in console to resolve this, without success.

I guess the core has some functionality to renew the IP address that is in the client_ip field by doing some kind of re-discover the external IP address from time to time. I didn't find any parameter where I could see what the periodicity of this process would be.

My problem is, that it happens from time to time that after the IP change, there is no more connectivity due to the above facts and my client_ip never gets renewed, so I have to restart the core to solve this problem.

I'm wondering if any of you did see tha same thing and came up with a solution of any kind.

By the way, are my assumptions correct above regarding the auto-re-discovery issue?

Thanks for your attention...
Balazs

[pango]

MLdonkey should update client_ip when it connects to an edonkey server again.
On Unix, you can send MLdonkey a SIGHUP signal to immediately close all connections and force an IP discovery.

[spiralvoice]

Do you get a high ID from EDK servers?
_________________
Link overview and precompiled cores here: http://mldonkey.sourceforge.net/DownloadLinks

[ais77]

I've got the same situation - after IP change (I'm on the ADSL modem which reconnects periodically, once or twice a day) MLD sends and recieves no data at all - it's not connected to any servers.

I didn't check if there is difference between current IP and stated in MLD at that moment one (will do next time), but only solution is to kill core and start it over.

It's impossible via web-interface (i mean start over - kinda feature requst to spiralvoice ) - so I have to connect to MLD machine by Radm...

Donkey servers allways give me high ID.