Quoting rick james <rj196...@gmail.com> from ml.softs.gtk-gnutella.devel: :But gtk-gnutella seems to insist on using the public 76.* IP adress :and not seeing the the current portforwared 192.* adress or that's :the impression i'm getting because gtk-gnutella keeps saying I'm :firewalled even though I'm telling it to use the opened port if you :understand what I'm saying.
Maybe I'm not understanding your issue fully but you need to know how things work to properly diagnose whether there is a problem in your configuration or whether there is a problem in the way GTKG works currently. The IP address that GTKG wants to use is the IP address that remote peers report you have when you connect to them. The "firewalled" status is computed by looking at whether you do get incoming connections to the advertised port or not, on your external IP address. The proper configuration therefore is to make sure the public IP router will have a rule to forward your listening port to your local machine. For instance, imagine your LAN address is 192.168.0.1 and your external IP address is 76.0.0.1, with your local listening port set to 12345. Locally, GTKG listens to 192.168.0.1:12345 but it is going to advertise 76.0.0.1:12345 to the world. Therefore, on your 76.0.0.1 box, you need to forward port 12345 to 192.168.0.1 and everything will work fine. Raphael ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ gtk-gnutella-devel mailing list gtk-gnutella-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
