It needs at least two if it's acting as a router.
t scrolls back up to read the router discussion
Ah, gotcha. Thanks again, guys.
Fred: Oh my God! Angel, you're…cute! Angel: Fred, don't! Fred: Oh, but the little hands! And the hair! Angel: Hey! You're fired.
'Smile Time'
Buffistechnology 2: You Made Her So She Growls?
Got a question about technology? Ask it here. Discussion of hardware, software, TiVos, multi-region DVDs, Windows, Macs, LINUX, hand-helds, iPods, anything tech related. Better than any helpdesk!
Dana - Jan 31, 2005 9:33:16 am PST #1481 of 10003
I'm terrifically busy with my ennui.
NoiseDesign - Jan 31, 2005 9:34:25 am PST #1482 of 10003
Our wings are not tired
Each interface eats an IP address. If you've got a computer with wired and wireless connections each one will use it's own IP.
Dana - Jan 31, 2005 10:52:15 am PST #1483 of 10003
I'm terrifically busy with my ennui.
Yes, but they are all likely to start "192.168."
Because addresses in that range are designated for private use, right? I'm learning.
§ ita § - Jan 31, 2005 10:54:48 am PST #1484 of 10003
Well not canonically, no, but this is transformative fiction.
Yes -- from the RFC (1918):
The Internet Assigned Numbers Authority (IANA) has reserved the following three blocks of the IP address space for private internets:
10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
thegrommit - Jan 31, 2005 3:21:30 pm PST #1485 of 10003
Um.
Because addresses in that range are designated for private use, right? I'm learning.
Home routers (the boxes you see in Best Buy) will translate between public IP and private IP addresses. So you can have a little network behind the router that only has one public IP address. This process is known as NAT - Network Address Translation.
Gandalfe - Jan 31, 2005 3:22:52 pm PST #1486 of 10003
The generation that could change the world is still looking for its car keys.
192.168.0.0 - 192.168.255.255
This is the one that seems to be most commonly used for standard networking. FYI, any (Windows?) machine out there can be pinged locally, even if it's not hooked up to anything (except the power, obviously. And the keyboard. And the monitor.) at 127.0.0.1. Or localhost.
Which is really just another way of saying . . . . I dunno. Something.
§ ita § - Jan 31, 2005 3:32:23 pm PST #1487 of 10003
Well not canonically, no, but this is transformative fiction.
Oh, and those addresses are nicely safe, since routers won't route their traffic across networks.
amych - Jan 31, 2005 3:42:15 pm PST #1488 of 10003
Now let us crush something soft and watch it fountain blood. That is a girlish thing to want to do, yes?
any (Windows?) machine
Any machine, not just windows -- 127.0.0.1 is the local machine, for any machine that recognizes the IP protocol. Not just useful for pinging when bored, but handy knowledge for lots of "develop on the local machine before uploading to a real server" type work.
Dana - Jan 31, 2005 5:41:42 pm PST #1489 of 10003
I'm terrifically busy with my ennui.
127.0.0.1 is the local machine, for any machine that recognizes the IP protocol.
Right, I learned that too.
I'm going to be bummed if this writing sample doesn't at least get me a round further.
Gandalfe - Feb 01, 2005 4:42:32 am PST #1490 of 10003
The generation that could change the world is still looking for its car keys.
Any machine, not just windows -- 127.0.0.1 is the local machine, for any machine that recognizes the IP protocol. Not just useful for pinging when bored, but handy knowledge for lots of "develop on the local machine before uploading to a real server" type work.
I thought it might be any machine, but wasn't completely certain, and I was too tired to try to really remember. It's also useful if you're having connectivity issues - try pinging yourself. If you can't, well, you're completely and totally hosed.