I have a DSL-500T router of Dlink and I notice that when I run the Emule software the dproxy process aborts.
When dproxy aborts, the last message that appears in debug log is "Lotsa answers".
Take a look in the tailed file: http://hstein.trix.net/lotsa_answers.txt
I guess that the router has the following dproxy packages intalled:
dproxy-nexgen_1.0-10_18_02.diff.gz
dproxy-nexgen_1.0.orig.tar.gz
dproxy-timeout-init.diff.gz
Best Regads,
Sumo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The problem occurs between 3-6 hours of modem activity. Someone got the same problem?
PS. To see the modem debug log is required to kill the original dproxy process (in telnet console), then start it again - all DNS requests will then shown in the terminal.
The command arguments are in the list of processes (ps command). Mine is: /sbin/dproxy -c /etc/resolv.conf -d
("-d" is required).
Ty
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I have a DSL-500T router of Dlink and I notice that when I run the Emule software the dproxy process aborts.
When dproxy aborts, the last message that appears in debug log is "Lotsa answers".
Take a look in the tailed file:
http://hstein.trix.net/lotsa_answers.txt
I guess that the router has the following dproxy packages intalled:
dproxy-nexgen_1.0-10_18_02.diff.gz
dproxy-nexgen_1.0.orig.tar.gz
dproxy-timeout-init.diff.gz
Best Regads,
Sumo
The problem occurs between 3-6 hours of modem activity. Someone got the same problem?
PS. To see the modem debug log is required to kill the original dproxy process (in telnet console), then start it again - all DNS requests will then shown in the terminal.
The command arguments are in the list of processes (ps command). Mine is: /sbin/dproxy -c /etc/resolv.conf -d
("-d" is required).
Ty