 What a difference a day makes ... or... a little TCP/IP knowledge is dangerous!
Yesterday: only TCP port 6346 was being forwarded by my firewall. (MY BAD!)
Today: both TCP and UDP port 6346 is being forwarded. (Yeah, I fixed it!? Maybe...)
SO, the firewall uses NAT (Network Address Translation) and port numbers to map an external, dynamic, PUBLIC IP addr to an internal, STATIC, PRIVATE IP addr.
The internal LAN addr starts with 172....
My external, public IP addr changes only if I reboot my DSL modem. It may look like 64... or 67... or ... but never 172... My ISP assigns that addr via DHCP when I reboot my DSL modem.
LimeWire remote peer should always use the EXTERNAL addr like
67.124.63.161:6346 and never the internal addr like
172.1*.**.**:6346.
SOMETIMES, LimeWire remote peers use the INTERNAL 172... addr, while others are using the EXTERNAL 64... addr. this a bug in LimeWire, or a config problem, or a design problem for a future version of LimeWire so it can support NAT routers/ Firewalls???
More details below... later...
Last edited by Lord of the Rings; April 28th, 2005 at 02:26 AM.
|