Behind router with hub: Cannot set up manual port forwarding

Asked by grumpymrgruff

I have two PCs running behind a DSL router. One is a linux machine running verlihub and the other is a windows machine running the DC++ .709 client. I want to configure my DC++ client connection settings so that can use the "Firewall with manual port forwarding" option.

I have selected ports and forwarded them on my router and software firewalls. The problem is the external/WAN IP address required in the client. My LAN address is 192.168.1.64 while I have my external IP set up with No-IP. Here's the problem: If I specifiy my No-IP external address in the external/WAN IP field, my hub (sitting on my LAN and seeing my local address) finds an IP mismatch and boots me off the hub. If I supply my local IP address in the external/WAN IP field, I can connect to the hub but not my fellow users (who time out, unable to connect to my computer).

Question: How can I avoid being a passive user while still on the same LAN as my hub machine?

Thanks much!

Question information

Language:
English Edit question
Status:
Solved
For:
DC++ Edit question
Assignee:
No assignee Edit question
Solved by:
grumpymrgruff
Solved:
Last query:
Last reply:
Revision history for this message
Twilight2013 (twilight2013) said :
#1

What is your Windows OS as in XP or Vista? Are you using DC++ 0.709? If you are using DC++ 0.709, do you see a gray screen box on Settings of Personal Information? If so, upgrade to DC++ 0.7091.

See if this is related to the problem you are having with DC++ 0.709: https://answers.launchpad.net/dcplusplus/+question/53021

Revision history for this message
eMTee (realprogger) said :
#2

The only thing that you can do is to set up your hub so it does not need to check IPs of operators. Not sure if there is an option of this kind in your specific hub software/version. Check/ask about this at your hubsoftware's support forum.

Revision history for this message
grumpymrgruff (grumpy-mr-gruff) said :
#3

@Twilight2013
My mistake - I am running 0.7091. Mistyped in the original post. Same error message as in your linked post, but different reason.

@eMTee
Yeah, if there's no quick fix in the client, I'll have to dig around in the in the hub and see what I can do. The manual doesn't say anything about toggling IP spoofing (which is what it thinks I'm doing). Can anyone recommend their favorite hub software?

Revision history for this message
poy (poy) said :
#4

i could be mistaken, but i think ADCH++ <http://adchpp.sourceforge.net/> allows IP spoofing as long as it's a local IP.

most hub progs out there will disable this in order to prevent DDoS attacks <http://dcpp.wordpress.com/2009/01/14/dc-ctm-proof/>; however, some (like ADCH++ iirc) might still be allowing it exactly for your use case.
you're better off asking in each hub prog's forum.

Revision history for this message
grumpymrgruff (grumpy-mr-gruff) said :
#5

Turned out I grabbed an out of date version of verlihub via my package manager. I now have the latest version as of writing, 0.9.8d_RC2.

This version deprecates the "check_ctm" variable (toggles IP mismatch booting) and boots all users with mismatching IPs. For future reference, there is now a hub admin command:

"!r= <username> alternate_ip <alternate address>"

If you are an admin on the same LAN as your hub, you can specifiy your external address with this. The DC++ client's external/WAN IP field should be set to the local IP. I don't see any scripts allowing nonadmin LAN users to specify their IPs, but it could probably be set up.

Thanks for the help!