Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[BlogThis2009]

How about allowing Amule to connect using an external IP that is not the hosts's machine's IP. In the case of port forwarding for example, using the forwarded IPs machine. Currently Amule doesn't seem to be able to do this, but there must be a way. All that needs to be done is to tell everyone else that its IP is the forwarded IP/port, and just listen on the local IP/port itself.

This would then allow using openssh to reverse port-forward from behind NAT networks, to obtain a HIGH-ID, I assume?

[lfroen]

what is "external IP"??

[Morse]

you cannot obtain high-id being behind NAT, and no feature will change that.

[BlogThis2009]

Well, currently you open up a port on your router, and forward that to your NAT'd machine right?

What is different about using SSH to forward a port?

Basically, the port 4662 (or whatever) could be accessed On the remote machine, via port 4662 on another machine - and it would forward it to the NAT's machine (using reverse port forwarding)...

But how can you get amule to work like that?

[Morse]

if your NAT server forvards ports 4662 TCP and 4665 4672 UDP then your amule should work fine (with highid and KAD), if not - then not.

anyway - it's not an amule issue.

[wuischke]

If you use a ssh (-Dport) connection only, you may need to set it as socks proxy. If you use a tunnel (-Lport:server:port) you can treat it like a local connection, I think.

[BlogThis2009]

Basically, the situation is:

The external IP through which my connection goes is firewalled, and there is no way of port forwarding on that address.

Short of doing a full VPN to another machine, and routing through that and getting that to port-forward, couldn't the method I request work?

Surely all aMule would need to do is tell the server it connects to, the clients etc, that when they are to send it data, to send it to the external IP address that has a valid listening port, and to accept that it will send data from its own IP address that does not have a listening port?

Basically, listen on one IP address, and send on another.

[skolnick]

Basically, listen on one IP address, and send on another.

It is already doing that. Look for NAT and PAT and how they work. That's what your aMule is currently doing. It most probably have a private IP, but all computers on the internet see it with your public IP. The problem is not aMule listening on a different IP. The problem is what does your firewall do with the requests of the other computers around the world. It should pass them to your aMule. If it doesn't, then you get lowID. It's an issue with your firewall, nothing to do with aMule.

Regards.