Xref: utzoo comp.protocols.tcp-ip:9413 comp.unix.wizards:19582 Path: utzoo!attcan!uunet!mailrus!purdue!mentor.cc.purdue.edu!pur-ee!ea.ecn.purdue.edu!housel From: housel@en.ecn.purdue.edu (Peter S. Housel) Newsgroups: comp.protocols.tcp-ip,comp.unix.wizards Subject: Re: What is INADDR_LOOPBACK for in sockets? Message-ID: <17748@ea.ecn.purdue.edu> Date: 2 Dec 89 15:15:27 GMT References: <29665@shemp.CS.UCLA.EDU> Sender: housel@ea.ecn.purdue.edu Reply-To: housel@en.ecn.purdue.edu (Peter S. Housel) Distribution: na Organization: Purdue University Engineering Computer Network Lines: 17 In article , mcgrath@paris (Roland McGrath) writes: >INADDR_LOOPBACK is 0x7f000001, Internet address 127.0.0.1, usually called >`localhost'. Talking to this address gets you back to where you started from, >without going through the network hardware. The nifty thing is that (on many systems with BSD-derived networking) you can disable the loopback-net, through which address 127.0.0.1 is routed. Running "ifconfig lo0 down" will disable the "loopback interface" and the machine will be unable to talk to itself. We once had cause to do this. Due to some kernel bug, packets were occasionally getting stuck in loops within the loopback. The system would get very sluggish, forwarding packets in tight little circles. Until the problem was fixed we just disabled the "interface" for 30 seconds or so until the offending packet timed out. -Peter S. Housel- housel@ecn.purdue.edu ...!pur-ee!housel Brought to you by Super Global Mega Corp .com