Mldonkey too old? LowID?

[Zach]

One other outside possibility is that ISPs may be antagonistic of
people who are doing p2p filesharing. Since 4662 TCP, and 4672 UDP are
extremely common for edonkey clients, your isp might have draconian
port blocking policies, and are not allowing incoming traffic on
common p2p ports.  Maybe try configuring your client to listen on
something far outside that range like 34662 and 34672.  Be sure to set
up the proper forwarding in your nat as well.

Here's a troubleshooting technique you can try.
Turn off your mldonkey/edonkey/whatever program.
Install openssh-server
Configure your ssh server to listen on the port (TCP only for ssh) in
question.  This is in /etc/ssh_config.
Restart the ssh server
Ensure your port forwarding is set up properly
Get a friend with linux or using PuTTy on windows to attempt to ssh in
to your computer.
get your ip address at http://checkip.dyndns.org/
Note you don't have to even give them a username/password.  If they
receive a password prompt, then the connection was successful, and
they can cancel.  If their client just sits there or refuses to
connect then something is going on either with your ISP or with your
router/port forwarding.
(They can also run nmap against that port.)
Reconfigure ssh to use a different port and try again
Rinse
Repeat.

On 2/1/06, Zach <uid000 at gmail.com> wrote:
> As of breezy, there are no iptables rules configured by default, so
> there shouldn't be any problem with any service attempting to listen
> on any port.
>
> Many NAT routers have a stateful firewall in addition to their NAT
> functionality.  I'm assuming that when you say "On my router, I have
> opened the ports 4662 TCP, 4672 UDP", you mean not just configuring
> the router's firewall to allow incoming traffic on those ports, but
> also actually forwarding the ports to the appropriate internal IP?  Do
> you use DHCP?  Is it possible that your machine's IP is changing, or
> not what you thought?
>
> Perhaps the the "client is too old" error is related afterall.  Where
> did you get your mldonkey?  From one of Ubuntu's repositories, or a
> third party?  Are you running breezy?  If it's not a matter of the
> ports being forwarded properly, then perhaps the edonkey protocol has
> changed, and out of date clients are being penalized.  However other
> posters indicated they are running mldonkey from Ubuntu universe and
> are not having problems.
>
> These two possibilities notwithstanding, I can't guess what the
> problem could be.  Personally, I'm not that familiar with mldonkey.
>
> One other suggestion would be to give amule a try.  I'm fairly certain
> it's in Universe or Multiverse.
>
> On 2/1/06, Dave M G <martin at autotelic.com> wrote:
> > Zach wrote:
> >
> > >Your performance will suffer significantly with a low id ...you need to forward
> > >the ports that your client is configured to use.  Generally this is
> > >4662 TCP & 4672 UDP,
> > >
> > I have only one computer, and it accesses the net via a router connected
> > to a fibre optic modem. On my router, I have opened the ports 4662 TCP,
> > 4672 UDP, and 6346 TCP and UDP (for Gnutella networks).
> > I had done this since the beginning.
> >
> > Yet I still see the "lowid" error.
> >
> > Is there some kind of firewall or port blocking in Ubuntu/Linux that I
> > need to open as well?
> >
> > --
> > Dave M G
> >
> > --
> > ubuntu-users mailing list
> > ubuntu-users at lists.ubuntu.com
> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>


--
If you reply to a message I posted to a mailing list,
and you want me to see your reply, be sure to put my
address in the 'To:', or I might not see the message.