Networking issue

[yesthattom]

I have a developer that doesn’t know that 127.0.0.1 is his own machine.

Comments

[rainbear.livejournal.com]

...of course not..that's a networking issue..

*duck* ;-D

[ckd]

127.0.0.1, the infamous warez site.

(Of course, one of my favorite uses of it was sending a fake IRC DCC chat request asking the other user's client to connect to 127.0.0.1:19...heh.)

[king-tirian.livejournal.com]

http://linuxfire.dhis.org/~xceals/blog/archives/2005/06/i_hacked_127001.html

[porcinea.livejournal.com]

Ow! OW! Can't. Stop. Laughing.

[king-tirian.livejournal.com]

So much for laughter being the best medicine.

[grendelgongon.livejournal.com]

*collapses in a fit of laughter* Awesome!

How can it be?

[mrfantasy.livejournal.com]

My machine's at home! Turned off!

[barking-iguana.livejournal.com]

Is there any reason he especially *should* know it? I wouldn't expect someone who designs car interiors to necessarily know which brand radio receivers deal well with getting signal from an antenna attached to a large hunk of moving metal. S/he'd figure out where the radio needed to go and someone else would decide which music fixture whent in the slot. The situations seem comparable to me.

[yesthattom.livejournal.com]

Yes. If you are any kind of a Unix programmer you should know this.

[jss]

Well, any kind of a Unix programmer who cares about any network-based traffic at all. If you only programmed for a local Unix system with (pseudo)local disks/tapes (i.e., local i/o or faux local a la NFS), who cares about the IP stack? If you've got multiple processes you could be using IPC instead of a network (IP) socket to 127.0.0.1.

But I'm being pedantic.

[ninaf.livejournal.com]

what about 127.0.0.2

[yesthattom.livejournal.com]

neighbor of the beast

[ninaf.livejournal.com]

so very true.

[xthread.livejournal.com]

This begs the question:

Do you still have a developer who doesn't know that 127.0.0.1 is his own machine?

[cpj.livejournal.com]

True, but the automounter should never use NFS pointing back to itself. In that case, revert to the Loopback File System.

At least, I'm guessing that this started out as a NFS issue. It could be anything I guess.

I met a Sun installer the other day who didn't know how to count rack-unit holes. But then again, he's much more used to the big stuff that's pre-racked.

[porcinea.livejournal.com]

There's no place like 127.0.0.1!