what does the address 127.0.0.1 stand for ? And what happens when we ping the address ..
i know its for self pinging ...but could u tell me what actually happens......
Printable View
what does the address 127.0.0.1 stand for ? And what happens when we ping the address ..
i know its for self pinging ...but could u tell me what actually happens......
127.0.0.1 is the loopback address, it's not a 'real' ip, it's used to check that local set-up is working. (ie: ping 127.0.0.1 should always work even without a NIC)
Do a google search for more info.
:)
J>
Hrms..i'm freaked out. I pinged 127.0.0.1 and the request timed out. I thought it loops back and i'd get a reply?
Quote:
It does and you will....do you have the incoming ping request permanently blocked by your firewall?
127.0.0.1 is the same thing as localhost... So try to ping localhost it might work
127.0.0.1 is simply an alias for the local server on your computer (usually 'localhost' although sometimes it can be 'linux'). You can usually use any 127.*.*.* address as well. If you don't have a local server installed it merely acts as a loopback address.
If the request times out either you have a firewall blocking incoming packets or you could try localhost (although this shouldn't make any difference as they point to the same thing).
If it times out, there could also be a problem with your ethernet card. Depends on what OS you are running. In linux, if you ping 127.0.0.1, and it times out, that means that either networking is disabled, lo is down, or a firewall is blocking you pings. In windows, it means either a firewall is blocking, or networking is disabled.
a remark:
The localhost can be whatever name you want on home boxes. One of my linux boxes, for instance, now has "VictorKaum" as localhost, it's not a usual config and I'am going to change it back to the original, but with some little "tweaks" you can play with all the networking stuff...
However: I'am not responsible when you do something bad to your box as root ;)
Normally a ping to 127.0.0.1 should work.
It is possible to change the name from localhost, but it often doesn't work properly with some servers and it's really not worth the hassle. The only time you'll need to change the alias is if you are running a website and want to point the address 'www.whatever.com' to your local IP.Quote:
Originally posted here by VictorKaum
a remark:
The localhost can be whatever name you want on home boxes. One of my linux boxes, for instance, now has "VictorKaum" as localhost, it's not a usual config and I'am going to change it back to the original, but with some little "tweaks" you can play with all the networking stuff...
However: I'am not responsible when you do something bad to your box as root ;)
Normally a ping to 127.0.0.1 should work.
Like everyone said 127.0.0.1 is the local loopback address. 127.* is reserved specifically for this. The only good thing about pinging yourself is it can tell you if tcp/ip is properly configured on your network card. So, if you can't ping yourself and you don't have a firewall, something might be off in your tcp/ip settings. THats not to say it won't work....it just means that something may be misconfigged.
Yep I know, it's not worth the hassle, cause when you don't run a website you do get troubles with for instance your sendmail or other network related stuff... My point was that it could easily be done... but it has no use on home boxes (only trouble).Quote:
Originally posted here by pwaring
It is possible to change the name from localhost, but it often doesn't work properly with some servers and it's really not worth the hassle. The only time you'll need to change the alias is if you are running a website and want to point the address 'www.whatever.com' to your local IP.
its actually not for "self pinging" because like jcdux said you dont need access to the internet for this to work. its for testing services on your box(win/*nix/whatever). like if you wanted to see if your welcome message for your telnet daemon was working you can telnet yourself and see.
Bios's comment is right, the loopback adress is also for using services on your own computer. This is usefull in many ways, for example, you with ssh you can set up tunnels, to use this tunnel with the client, you would usually use the loopback adress(es).
One difference to using your other address (for example 192.168.0.1, or 1.2.3.4), is that you could bind a service that you only want accessible from the server itself to a loopback address, for example, the administrative server of IIS.
The loopback is also used in routing tables; check out your routing table with "route print" in a command promt (in windows). You'll see that your local interface is routed to 127.0.0.1.
Ammo
Another thing:
The loopback address(es) should always work AS LONG AS you have TCP/IP setuped on your computer...Quote:
A windows box with no modem and no NICs (ie, nothing to bind TCP/IP to, ie as no IP stack) will no answer to ping 127.0.0.1...
About the firewalls: a well configured firewall should (usually) allow everything on 127.0.0.0/8... you're looking for troubles otherwise...
Ammo
hahah
whoa..even though this aint my thread, looks like i've got everyone answering my question! thanks... i think it's just my network card that may be temp. stuffed.
:(
thankx guys !!! Needed to know .......this stuff