well, it's just a guess ?( but i suspect it's first amule hanging your modem
i experienced similar problems when switching from a precompiled rpm package to self compiled versions of amule:
- modem losing connection 30 min - 8 h after amule has been started
- amule crashes in some versions, keeps running in others (i tried 1.2.4-1.2.6 and 2.0.0rc2
on SuSE 8.2 and Fedora Core 1)
- modem does not reconnect in most cases without being resetted
- in those few cases when modem reconnects by itself, it reconnected at ISDN speed or less
i didn't experience these problems with other apps (browser, download manager) when not running amule, nor with the rpm package; on the other hand, with self compiled amule running, in many cases my connection was gone when the browser started loading a page, so i suspect amule is somehow confusing the modem (the changelog of 2.0.0rc3 mentions something about the possibility of amule hanging up modems)
i tried the following workarounds:
(1) using very conservative settings, reducing max connections to 100 or less, reducing max connection per 5 sec to 10 --> little improvement
(2) compiling amule with --disable-optimise --> the connection stays up significantly longer, but nor forever (in fact, the rpm i had been using and which had been running without those problems had consumed up to 70-95%(!) of my 1300 MHz CPU)
(3) running "ping some.server.com" in the background - seems to help keeping the connection alive for some time longer
(4) swapping modems & network cards --> wouldn't help
i finally tried a cvs amule - voila, problem gone:
cvs 2004-06-22 has been up & running without problems for 40 (forty) hours now without crash & without losing connection, so i recommend you try that one (indeed very close to rc4 !!!)
