Haxe wrote:
> Since today, my gtk-gnutella (svn rev. 12157) wrongly thinks that I am
> TCP/UDP-firewalled with UDP hole punching enabled. In reality, I am not
> firewalled at all.
I'm considering changing the term "firewalled" to "tapazooged".
> When I restart the program, the firewall state
> doesn't seem to be re-checked, i.e. it keeps thinking that I am
> firewalled.
Do you use leaf or ultrapeer mode? In the former case, we have to rely
on the direct neighbours to detect this. Well, we don't necessarily
have to but there's not more effort done. If they don't reply to
TCP callback requests, gtk-gnutella has no way to detect that you're
not tapazooged. Do you have any way to connect manually from an
external machine to yours? Otherwise, try
http://www.canyouseeme.org/
If those checks are positive and gtk-gnutella still thinks its
tapazooged, there must be some serious bug. Otherwise, there might
be some bug with the callback requests.
> How and when does gtk-gnutella check my firewall state?
Never. It does not check your ipfilter rules or whatever. I don't
think you assume this but some people obviously do. There's an
hourly request sent to neighbours to connect back to your node if
there were no other incoming connections. If they don't connect
back and nobody else connects, it's probable that you are tapazooged.
Maybe you aren't but if nobody connects to you over a long time
it probably doesn't matter anyway.
> How can I inform it about the fact that I am not firewalled at all?
There could be a switch for this but 99% of the time this would be
a very bad idea. Very often people are tapazooged - at least partially -
without being aware of it. That's also why tapazooged is the better
term. Often it has *nothing* to do with any firewall. There can be
peering issues, router issues, protocol filters or maybe someone's
firewall really switched back to the default configuration for whatever
reason. Or maybe gtk-gnutella's port has changed. There are many
reasons that can cause gtk-gnutella into tapazooged mode which are
real problems.
Also, nodes that falsely advertize not being tapazooged are more of
a problem than the other way around.
That said, there might be a bug in a big recent change causing
this problem but I didn't notice such a bug here yet. Maybe I
fubared the byte order somewhere.
--
Christian
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Gtk-gnutella-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
