User talk:127.0.0.1

From Wikipedia, the free encyclopedia

I was going to joke about banning this "vandal", but I just noticed that somehow actual contributions have been made through this IP. Wow. That blew my mind. --Nintendorulez talk 00:37, 23 March 2006 (UTC)

-- Wow, that's hilarious, maybe an ip spoofer? —The preceding unsigned comment was added by 68.3.229.131 (talk • contribs) 07:24, 26 November 2006 (UTC)

Someone spoofing their IP would not be able to establish a TCP handshake, which means they would not be able to establish a connection to Wikipedia's HTTP server. They would just send the SYN packets and never receive a reply (in fact the packets would likely never reach their intended destination in this case, as well-configured routers along the way would drop a packet with a source in 127.0.0.0/8). Capi 07:29, 27 November 2006 (UTC)

How the hell...? Does this mean some guy at Bomis installed a browser on one of the servers and made contributions with it? BigBlueFish 08:33, 1 April 2006 (UTC)

Perhaps. --Nintendorulez talk 19:12, 2 April 2006 (UTC)
I bet it's a normal user who just happened to have registered this nick. —Michiel Sikma, 12:18, 4 May 2006 (UTC)
Supposedly it is impossible to register a username that looks like an IP address. Ardric47 02:27, 7 May 2006 (UTC)
You mean it's impossible to "_________________________" is an IP adress. But yeah, it is impossible to [insert what I said before here]. ~ Ghelæ talkcontribs 15:34, 2 June 2006 (UTC)
Wikipedia:Bad Jokes and Other Deleted Nonsense/127.0.0.1 Vandalism. –Gunslinger47 00:36, 20 August 2006 (UTC)
I heard a rumor that this is simply a sockpuppet of *.*.*.* --Nintendorulez talk 22:07, 10 September 2006 (UTC)
See Ghelae's comment above. "You mean it's impossible to 'confirm that' is an IP address. But yeah, it is impossible to [confirm that]." I inserted what you said, or what you most likely wanted to say. It's not impossible.--75.26.13.197 00:34, 18 September 2006 (UTC)
This is probably the most confusing talk page in the history of the Wikipedia... ~ Ghelæ talkcontribs 18:09, 21 September 2006 (UTC)
Someone got to this before me I see...ah well --WikiSlasher 13:53, 16 October 2006 (UTC)

[edit] IP for Localhost

This is, in fact, an IP address. The difference is, each computer has 127.0.0.1 until a DHCP assigns you an IP address. 127.0.0.1 cannot be acessed from the outside internet. The only purpose of that address is for your own usage. Technically. 127.0.0.1 gets used throughout the internet, such as:

  • Installation of internet software by the server, not by remote.
  • The forum test post you see after an installation. The IP responsible for that is 127.0.0.1

So it is a private IP address, not meant for general public connection. —The preceding unsigned comment was added by AOL Alex (talk • contribs) 21:59, 25 September 2006 (UTC).

Almost correct. 127.0.0.1 is indeed a valid IP address, and each computer with a working TCP/IP stack does indeed have that address, but not just "until a DHCP [server] assigns you an IP address". Actually, what happens is that each computer has, alongside its real physical network interfaces, a "loopback interface", which is a virtual interface that echoes back any data sent to it. This interface is typically assigned the IP address 127.0.0.1. In fact, any address in the range 127.0.0.0/8 block would be correct as per IANA reserved addresses (see RFC 3330), but 127.0.0.1 is the de facto standard (and some implementations only allow 127.0.0.1 anyway). So yes, each computer can reach itself through the IP address 127.0.0.1, but no, this address does not depend on DHCP leases, nor will it cease to exist if/when the computer obtains a DHCP lease on one of its physical interfaces.
As to the question of whether 127.0.0.1 can be accessed externally, it is actually not as straightforward as it might sound. It is possible to manipulate the fields in an IP packet's header; in particular, it is possible to send an IP packet through a physical interface with a source IP of 127.0.0.1, and a target IP set to the IP of another machine's physical interface. If the destination is on the same subnet as the sender, the packet will indeed reach the target computer, on its physical interface (if it's in a different subnet, e.g. if it's somewhere on the Internet, it will most likely never reach its target as most routers will be configured not to forward packets with a source in 127.0.0.0/8). Once the target system receives the packet, what it does with it depends on how the system is configured (whether it is set up to forward packets or not, whether it has a firewall on it, etc). It is entirely possible for the system to be configured (intentionally or otherwise) in a way such that it will accept the packet and pass it to the protocol stack as though it had come from within. Capi 02:34, 29 September 2006 (UTC)

[edit] Whois

OrgName: Internet Assigned Numbers Authority

OrgID: IANA

Address: 4676 Admiralty Way, Suite 330

City: Marina del Rey

StateProv: CA

PostalCode: 90292-6695

Country: US


NetRange: 0.0.0.0 - 0.255.255.255

CIDR: 0.0.0.0/8

NetName: RESERVED-1

NetHandle: NET-0-0-0-0-1

Parent:

NetType: IANA Special Use

Comment: Please see RFC 3330 for additional information.

RegDate:

Updated: 2002-10-14


OrgAbuseHandle: IANA-IP-ARIN

OrgAbuseName: Internet Corporation for Assigned Names and Number

OrgAbusePhone: +1-310-301-5820

OrgAbuseEmail: abuse@iana.org


OrgTechHandle: IANA-IP-ARIN

OrgTechName: Internet Corporation for Assigned Names and Number

OrgTechPhone: +1-310-301-5820

OrgTechEmail: abuse@iana.org


  1. ARIN WHOIS database, last updated 2006-10-31 19:10
  1. Enter ? for additional hints on searching ARIN's WHOIS database.

Now we know. --24.187.50.132 22:41, 1 November 2006 (UTC)

What's to know? We already knew this, it's just repeating what I said above, that it's a reserved address... Incidentally, this is a whois on 0.0.0.0, not on 127.0.0.1. Capi 13:36, 2 November 2006 (UTC)
Retrieved from "http://en.wikipedia.org../../../1/2/7/User_talk%7E127.0.0.1.html"