[Stach]

All the previous versions I've used Kad worked perfectly, with port forwarding set up correctly. But ever since I upgraded to the newest version, Kad is nonfunctional. I've tried assigning different ports to no avail, even though I connect to the ed2k network just fine, with HighID and all that. Right now, Kad's status is open. UDP status is firewalled for some reason.. the port forwarding test page confirms this. Any way to alleviate this? Or is there some additional functionality I'm unaware of?

[torpon]

What server, name and ip, are you connected to?
Problem is your UDP port is not reachable, not the eMule version you are using. Recheck rules in firewall and router for UDP Port.

Cheers

[Stach]

Doesn't matter which server I connect to, all the same results (Razorback 3.x, eDonkeyServer No#, etc)

Yes, my UDP port is unreachable, like I've already said.. I don't know the reason. My firewall is already configured to allow the specified open ports through. Like I said before, this was working perfectly before 0.49a.

(my router is my firewall: wrt54g w/ latest dd-wrt firmware, winxp firewall is disabled)

This post has been edited by Stach: 05 June 2008 - 10:36 PM

[niclights]

Did you try [recheck firewall]? It might take more than one attempt - enable verbose log to see if successful & result.

Another option is to try UPnP just in case there is something wrong about forwarding.

[Stach]

niclights, on Jun 5 2008, 03:05 PM, said:

Did you try [recheck firewall]? It might take more than one attempt - enable verbose log to see if successful & result.

Another option is to try UPnP just in case there is something wrong about forwarding.

Recheck? I know my router's config like the back of my hand

But yeah, no matter what I try, it's firewalled.

Funny though, once emule starts, Kad status claims ports are opened (but unverified). After a minute, it's firewalled.

Are you nothings changed between 0.48 and 0.49a? It just seemed like such a coincidence...

[niclights]

[recheck firewall] is a button on the Kad window.

Yes, many things relating to Kad have changed in the new version. It was the main focus. See the release notes for details.

'open (unverified)' means just that. When it is later checked it is apparently firewalled. This is just part of the new handling.

So, like I said, enable verbose log and use the recheck button and see what it reports.

This post has been edited by niclights: 06 June 2008 - 02:05 AM

[Stach]

6.5.08 23:02:20: Received proper magic value after DH-Agreement from Serverconnection IP: 77.247.178.245
6.5.08 23:02:21: My public IP Address is: 67.180.x.xxx
6.5.08 23:02:21: Possible IP Change - Checking for expired Server UDP-Keys: 27 UDP Keys total, 0 UDP Keys expired, 0 immediate UDP Pings forced, 0 delayed UDP Pings forced
6.5.08 23:02:34: Starting Kademlia
6.5.08 23:02:34: Read 0 source, 0 keyword, and 2 load entries
6.5.08 23:02:34: Terminating CIndexed::CLoadDataThread - finished loading data
6.5.08 23:02:35: Starting NODEFWCHECKUDP Kad Search
6.5.08 23:02:35: Set external Kad Port to 6110
6.5.08 23:02:35: Selected client for UDP Firewallcheck: 89.186.13.14
6.5.08 23:02:35: Selected client for UDP Firewallcheck: 80.104.71.20
6.5.08 23:02:45: Ignored kad contact (IP=212.225.136.27) - IP filter (Bogon)
6.5.08 23:02:45: Cleaned up Kad Incoming Requests Tracklist, entries before: 0, after 0
6.5.08 23:02:45: Client UDP socket: prot=0xe4 opcode=0x50 sizeaftercrypt=6 realsize=6 ***NOTE: Received wrong size (4) packet in Kademlia::CKademliaUDPListener::Process_KADEMLIA_FIREWALLED_REQ: 83.50.229.99:4672
6.5.08 23:02:48: Ignored kad contact (IP=88.153.61.229) - IP filter (Bogon,)
6.5.08 23:02:58: Ignored kad contact (IP=139.19.142.1:4500) - IP filter (Max-Pl)
6.5.08 23:02:58: Ignored kad contact (IP=75.158.135.250:7560) - IP filter (IANA R)
6.5.08 23:03:05: Ignored kad contact (IP=77.27.4.148:26677) - IP filter (Bogon,)
6.5.08 23:03:05: Ignored kad contact (IP=190.226.84.146:59940) - IP filter (Bogon)
6.5.08 23:03:05: Ignored kad contact (IP=129.47.129.2:4662) - IP filter (Bogon,)
6.5.08 23:03:18: Kad UDP firewalltest from 89.186.13.14 result: Firewalled, continue testing
6.5.08 23:03:32: New KAD Firewallstate (UDP): Firewalled

---- changed ports to something else; retried ------

6.5.08 23:07:41: Deleted public IP
6.5.08 23:07:42: Received proper magic value after DH-Agreement from Serverconnection IP: 77.247.178.245
6.5.08 23:07:42: Possible IP Change - Checking for expired Server UDP-Keys: 27 UDP Keys total, 0 UDP Keys expired, 0 immediate UDP Pings forced, 0 delayed UDP Pings forced
6.5.08 23:07:48: Ignored kad contact (IP=205.200.238.211) - IP filter (Teledi)
6.5.08 23:07:59: Ignored kad contact (IP=77.27.16.166:49736) - IP filter (Bogon,)
6.5.08 23:08:10: Kad UDP firewalltest from 151.65.35.135 result: Firewalled, continue testing
6.5.08 23:08:13: New KAD Firewallstate (UDP): Firewalled
6.5.08 23:08:46: Starting NODEFWCHECKUDP Kad Search
6.5.08 23:08:47: Starting NODEFWCHECKUDP Kad Search
6.5.08 23:08:47: Set external Kad Port to 8135
6.5.08 23:08:47: Selected client for UDP Firewallcheck: 220.239.220.137
6.5.08 23:08:47: Selected client for UDP Firewallcheck: 83.81.70.60
6.5.08 23:08:47: Starting NODEFWCHECKUDP Kad Search
6.5.08 23:08:48: Starting NODEFWCHECKUDP Kad Search
6.5.08 23:08:48: Kad UDP firewalltest from 83.81.70.60 cancelled
6.5.08 23:08:48: Ignored kad contact (IP=93.156.91.91:64939) - IP filter (Bogon,)
6.5.08 23:08:48: Starting NODEFWCHECKUDP Kad Search
6.5.08 23:08:49: Client UDP socket: prot=0xe4 opcode=0x50 sizeaftercrypt=6 realsize=6 ***NOTE: Received wrong size (4) packet in Kademlia::CKademliaUDPListener::Process_KADEMLIA_FIREWALLED_REQ: 151.32.215.83:5666
6.5.08 23:08:50: Kad UDP firewalltest from 220.239.220.137 cancelled
6.5.08 23:09:02: Ignored kad contact (IP=190.244.48.232:4672) - IP filter (Bogon)
6.5.08 23:09:02: Set external Kad Port to 8135
6.5.08 23:09:02: Selected client for UDP Firewallcheck: 85.87.85.131
6.5.08 23:09:05: Selected client for UDP Firewallcheck: 78.4.36.159
6.5.08 23:09:16: Ignored kad contact (IP=119.122.70.35:5624) - IP filter (IANA R)
6.5.08 23:09:45: Kad UDP firewalltest from 85.87.85.131 result: Firewalled, continue testing
6.5.08 23:09:50: Ignored kad contact (IP=79.109.178.3:42664) - IP filter (IANA R)
6.5.08 23:09:51: New KAD Firewallstate (UDP): Firewalled

----

no juice.

This post has been edited by Stach: 06 June 2008 - 06:21 AM

[PacoBell]

Stach, on Jun 5 2008, 11:20 PM, said:

---- changed ports to something else; retried ------

When you say "changed ports", does that entail changing both eMule's settings as well as creating the forwarding rule in NAT and/or punching the appropriate hole in the firewall?

[Some Support]

Quote

Right now, Kad's status is open. UDP status is firewalled for some reason..

The UDP check is new and its very well possible that your UDP port was never reachable but Kad didn't knew before. Your Kad still works fine and its an advantage for the network that its aware of your firewalled UDP port. You do not have the disadvantages of a LowID because of this neither (but of course you still shoudl try to forward your UDP port properly).

[niclights]

And, with this in mind, have you tried UPnP?

[Stach]

niclights, on Jun 6 2008, 05:35 AM, said:

And, with this in mind, have you tried UPnP?

Yes (but I have it disabled for now).

So Kad is working but not? lol?

I have my ports forwarded correctly, thanks (for the 3rd time).

Are there other ways to know you're connecting to Kad properly?

[niclights]

If, by 'properly', you mean in a non-firewalled state. You keep saying they're forwarded correctly but it is clear Emule does not agree. It is well known that some routers just don't like the UDP packets. Maybe that's the reason. As SS has confirmed it is possible it was always this way but the changes in checking only now show the true status.

[Stach]

That's wierd then. TCP gets reported as open and UDP as closed, even when both are forwarded correctly. I even swapped the TCP with the UDP port number with the same effect.

[Wulp]

I don't think it's weird. As niclights pointed out, the problem is probably not the port forwarding but your router that just cannot handle the amount of UDP packets created by Kad. If this is the case, then there's not much you can do about it, except for buying a new router.
But if I've understood this correctly, you shouldn't have any problems with UDP status firewalled. As TCP is open, you can still connect to all users (high+low id), it just means that you can't index information from other Kad users and thus you don't "help" the network.

P.S.: Try the port test again before you connect to Kad. Do you get negative result then, too?

This post has been edited by Wulp: 08 June 2008 - 05:47 PM

[niclights]

Exactly. And if you want 'weird', then I always get firewalled status with my router when manually forwarded, but with UPnP on latest version I get confirmed Open. It makes no sense. I went through this in Beta with SS but all seems correct, including repeated rechecks & related verbose log. So there!

[darro53]

Stach, on Jun 5 2008, 09:47 AM, said:

All the previous versions I've used Kad worked perfectly, with port forwarding set up correctly. But ever since I upgraded to the newest version, Kad is nonfunctional. I've tried assigning different ports to no avail, even though I connect to the ed2k network just fine, with HighID and all that. Right now, Kad's status is open. UDP status is firewalled for some reason.. the port forwarding test page confirms this. Any way to alleviate this? Or is there some additional functionality I'm unaware of?

[Stach]

Instead of continuing to be software firewall-free, I've installed an older version of ZoneAlarm (6.1.744.001) on my tower. On the main tab of "firewall", I've set custom rules to allow my assigned UDP in/out port to be open and guess what.. it works. Kad reports status: open, UDP status: open.

Now this is beginning to make less sense. I'm gonna' try reconfiguring dd-wrt again without the software firewall running.. hope this works.

--

Followup:

Same results without a software firewall.. WTF.

This post has been edited by Stach: 12 June 2008 - 06:46 AM