If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
^wrong. if you're connected to a wireless router or a switch, IPconfig doesn't show your external address... it only shows the address that only your home can see.
mercuryengine.com imo
Exactly. Most broadband users are going to come from one public IP address. Never thought of proxies, but that certainly explains why you'd be getting more than one address.
to communicate with another computer. the reason most p2p software doesn't work behind firewalls is because your computer thinks your external IP is your local IP. you (the host) send a message to the client saying "connect to me at this IP on x port for this file," but you send the local IP instead, which is an internal address that is impossible to connect to from the Internet cloud.
Dude, I use all kinds of p2p programs behind a router and have no idea what my external IP is. Ever heard of port forwarding??
If you turn on port forwarding it can improve download/upload performance.
Why would you need to know your IP? Normally you don't, even for p2p. For p2p, you just need to setup a port forwarder for which port you set the p2p program to use.
If someone wanted to allow you through their firewall, they'd need to know your public IP.
Dude, I use all kinds of p2p programs behind a router and have no idea what my external IP is. Ever heard of port forwarding??
The reason you are forwarding your port is to bind the external IP's address and port to an internal IP's address and port. You may not *need* to know what your external IP is for connections being initiated from inside only but if you had say a web server hosted and were coming in from the outside you would need to.
"They who would give up an essential liberty for temporary security, deserve neither liberty or security." -Benjamin Franklin
The reason you are forwarding your port is to bind the external IP's address and port to an internal IP's address and port. You may not *need* to know what your external IP is for connections being initiated from inside only but if you had say a web server hosted and were coming in from the outside you would need to.
Right, got all that. My point is that the original poster has no need or use for his external IP. That's it.
MercuryServer uses account information, forum content, cookies and technical records to operate the community. Our privacy notice explains public posts, private communications, the TOTM connection and your choices.
Please read the notice before using member features. This acknowledgement does not waive your privacy rights or authorise unrelated tracking.
Comment