Ok, you didn't answer my questions, but i found a little about your ip
The ISP you are using for dialup seams to be a cable-provider.
Cable-provider often using line discipline like a proxy- or dhcpserver.
This means for P2P, in this case - ed2k - all needed ports, client and/or
server can't be forwarded by router, you might have LowID.
Ok, some more little help.
..."My home LAN is on 192.168 subnet and the WAN is on 10.x.x.x network. My
LAN has a connection both the internet (my ip is 83.xxx) and the WAN
Ip-ranges like 10.x.y.z, 192.168.x.y are used by (L)ocal (A)rea (N)etworks.
In your case, look at your debian-box "vi /etc/network/interfaces"
iface eth0 inet static
When your NIC is configured like this, your eserver have to know your
public IP. 83.x.y.z
In this case a dyndns-client like ddclient, inside debian, might be
have to be changed to:
thisIP=83.x.x.x (or like thisIP=$var and var is found by a little script
with the help of ddclient e.x.)
should be left blank. configured by eserver itself.
your tcpport is set to 58130 by donkey.ini, eserver sets automatically
udpport=58134, portTCPOBF=58130, portUDPOBF=58144. (might be seen with
"screen -r" and "print")
should left blank or in your case set false. (with "screen -r" and
eserver will swap your ram and harddisk with useless information very
At the end the same question, why do you use or need a router???
If you have a debian-box you have several helpful tools inside to configure
your debian-box as a router, too. apt-get, aptitude or synaptic will be
your friends installing little tools like, pppoeconf, iproute and more.
ipkungfu or arno-iptables - inside your debian-box - you might setup a
little firewall-script using NAT and so on for security and nating your
hm, ... more questions???
Server: maxx1462 macht urlaub