Scenario: I run behind a NAT linux gateway, which has the internal IP of 192.168.0.1 as the gateway, and an internet IP (obviously). However, yesterday, I changed which linux gateway I route through, not by changing the 192.168.0.1, but changing it so the *new* linux server actually has the 192.168.0.1 IP address. This is when the problems started.

Now, eMule continually "recognizes" some other user as being at MY router's internet address, and says the userhash changed, and they are banned. It then spews out some more banned messages, saying that my router's IP address is banned for a hash change, and then just a bunch of banned messages. This stops me from keeping HIGH id's... I'd really like to find out what causes this, and how to fix it.

If its something on my new linux router that needs changing, I can do that as well. But I think in general, it should work, I'm using the same firewall script that includes port forwarding the ports I use for eMule, to my desktop, so really, nothing the only thing that has changed, is the INTERNET ip address I now connect to the internet with, and a different version of linux (2.6 kernel versus 2.4 kernel).

I can troubleshoot a bit.. I've tried already deleting *everything* ... including my hashfile, crypt file, clients, etc.. the only files i didn't delete was the known.met, my preferences files, server.met, statistics, and staticservers. Still no luck.

please help.. heh, i'm stumped.

I'm thinking there should either be code to stop eMule from banning its own IP (the same IP as reported in the server window, when you connect to a server, or to kademlia network), or a bug fixed somewhere so it doesn't think my "internet" ip is other clients, thinking their hash changed, and banning them.. in the same swipe, killing my HIGH ID's.

Options -> Extended



Did you disable this ?


Do you have your LAN IP range in the ipfilter.dat ?
If yes, remove it !

Yes, I already tried deleting/clearing the entire ipfilter file and reloading it.

hi

you should try a forum search (on both bug reports and support sub-forums, for at least the last 180 days), you should find at least one other topic on the same subject. I don't know if you will find a solution in it, though, but it's worth the try.

I think he was also talking about this option:



May it helps if you show your pc's ipconfig, your emule ports and your "firewall script". Also never delete your cryptkey.dat & preferences.dat. If you do that your secure identification/hash WILL change.

I've tried that setting both ways, resulting in no difference to this problem. However, I think I may have some more information as to why this could be happening, and possibly that it is still a bug, or something that just needs a work around of some kind.

I forgot that one difference between the "old" and the "new" linux server that I am using for my router, is that the new server only has one ethernet card, the eth0 having the dynamic ip address my isp gives me through my dsl modem, and then eth0:1 has 192.168.0.1 for my internal network address. Just to be thorough with the description of my network(s), my dsl modem is plugged into a 16-port 10/100 switch, the same switch that all my computers in the house are hooked up to. The way this works, is that I only set my linux server to get an IP via dhcp, plus I set an internal IP as an IP alias, and all the other computers in the house are set for static ip (internal network IP ... 192.168.0.xx). This allows me to use a single network card/cable to my linux server, and it also allows me the extra option of setting any of my other computers to an ISP dynamically assigned IP if I really want to, simply by changing its ip configuration to use DHCP.

Anyways, so as it stands, the linux server has multiple IP's on its one network card, an ISP DHCP address, and two internal network IP's (192.168.0.1 and 192.168.0.49), one being the "gateway" address, and the 0.49 because thats what this server was before I made it the router, so I just wanted to keep the .49 around for posterity. Once again, I believe this is probably whats *causing* the problems with emule detecting that all the incoming requests are from my linux servers DHCP (internet) IP, and banning all requests, and also it shows the clients as failing the secure id check:

10/17/2005 1:45:20 AM: Rejecting connection attempt of banned client 216.86.xx.xx
10/17/2005 1:45:20 AM: '306vermell' has failed the secure identification, V2 State: 0

the xx.xx is my linux servers internet address... so its banning all incoming clients, because it thinks that they are all coming from the linux servers IP, instead of their actual IP, hence why the secure identification check fails, because their IP doesn't match what it should.

blah... heh.

Any more help?

here's another snippet from a fresh start of emule:

10/17/2005 2:16:37 AM: Starting Kademlia
10/17/2005 2:16:37 AM: Read 0 source, 0 keyword, and 20 load entries
10/17/2005 2:16:37 AM: Cleaning up TrackedClientList, 0 clients on List...
10/17/2005 2:16:37 AM: ...done, 0 clients left on list
10/17/2005 2:16:38 AM: Server, Sendlist: Packet size:168
10/17/2005 2:16:38 AM: My public IP Address is: 216.86.xx.xx
10/17/2005 2:16:50 AM: AICHSyncThread finished
10/17/2005 2:16:51 AM: SXSend: Local server source request; File="mountain.jpg"
10/17/2005 2:16:53 AM: Clients: Maverick (216.86.xx.xx), Banreason: Userhash changed
10/17/2005 2:16:53 AM: Banned: Aggressive behaviour; 216.86.xx.xx 'Maverick' (eMule v0.46c,None/None/None)
10/17/2005 2:16:53 AM: Clients: grifindor (216.86.xx.xx), Banreason: Userhash changed (Found in TrackedClientsList)
10/17/2005 2:16:53 AM: Clients: grifindor (216.86.xx.xx), Banreason: Userhash changed
10/17/2005 2:16:53 AM: Rejecting connection attempt of banned client 216.86.xx.xx 7217969@194.30.160.41 (216.86.xx.xx) 'grifindor' (eMule v0.46a,None/Banned/None)
10/17/2005 2:16:53 AM: Rejecting connection attempt of banned client 216.86.xx.xx 7217969@194.30.160.41 (216.86.xx.xx) 'grifindor' (eMule v0.46a,None/Banned/None)
10/17/2005 2:16:53 AM: Rejecting connection attempt of banned client 216.86.xx.xx 7217969@194.30.160.41 (216.86.xx.xx) 'grifindor' (eMule v0.46a,None/Banned/None)
10/17/2005 2:16:53 AM: Rejecting connection attempt of banned client 216.86.xx.xx 7217969@194.30.160.41 (216.86.xx.xx) 'grifindor' (eMule v0.46a,None/Banned/None)
10/17/2005 2:16:54 AM: Rejecting connection attempt of banned client 216.86.xx.xx 7217969@194.30.160.41 (216.86.xx.xx) 'grifindor' (eMule v0.46a,None/Banned/None)


the 216.86.xx.xx is my internet IP of my linux server, yet it thinks all the clients IP's are that... the above was shown after disabling secure check, and restarting emule.

thats probly the problem + the router

why can't the DSL modem goto linux then network as that is the norm way as you say it picks it up via the hub so there is no resen for it not to pick it up if the modem is pluged into the linux box strate in the have it get routed tho an other network card on the box (if not one fitted it only £$10)

other simple linux router softs are like www.ipcop.org (open source as well) i use that my self on mine simple to set up in 5 mins