IP - Revision history

Pbug: let the macro expand RFC links

2009-08-13T15:05:56Z

let the macro expand RFC links

← Older revision		Revision as of 08:05, 13 August 2009
Line 1:		Line 1:
	Internet Protocol. [[RFC]] 791. It is also called IPv4 (IP version 4) as compared to the new IPv6. Without IPv4 you would not read this.		Internet Protocol. RFC 791. It is also called IPv4 (IP version 4) as compared to the new IPv6. Without IPv4 you would not read this.

Pbug at 15:05, 13 August 2009

2009-08-13T15:05:14Z

← Older revision		Revision as of 08:05, 13 August 2009
Line 1:		Line 1:
	Internet Protocol. [[RFC]] 791. Without it you would not read this.		Internet Protocol. [[RFC]] 791. It is also called IPv4 (IP version 4) as compared to the new IPv6. Without IPv4 you would not read this.

Pbug: /* Exhausting IP addresses */

2009-08-13T14:48:42Z

Exhausting IP addresses

← Older revision		Revision as of 07:48, 13 August 2009
Line 75:		Line 75:

	With 1.5 billion internet users today and more coming the IP address space is getting exhausted. We have a maximum of 4.5 billion Internet addresses in the 32 bit space of which 0.5 billion are reserved for multicasting and research. Also, some organizations have entire /8 space for themselves and hardly use it. We're expected to run scarce on IPv4 address space in the 2010's. A replacement for IPv4 is already in operation called [[IPv6]]. It offers a lot more address space (128 bits).		With 1.5 billion internet users today and more coming the IP address space is getting exhausted. We have a maximum of 4.5 billion Internet addresses in the 32 bit space of which 0.5 billion are reserved for multicasting and research. Also, some organizations have entire /8 space for themselves and hardly use it. We're expected to run scarce on IPv4 address space in the 2010's. A replacement for IPv4 is already in operation called [[IPv6]]. It offers a lot more address space (128 bits).

			At the time of this writing it is estimated that there are 687 days left until IPv4 address exhaustion [http://www.potaroo.net/tools/ipv4/index.html Source].

Pbug: /* Obtaining an IP manually or with DHCP */

2009-08-13T11:35:45Z

Obtaining an IP manually or with DHCP

← Older revision		Revision as of 04:35, 13 August 2009
Line 3:		Line 3:

	== Obtaining an IP manually or with DHCP ==		== Obtaining an IP manually or with DHCP ==

			Often a home connection is provided with a home [[router]] which provides DHCP protocol for connecting workstations or laptops.

	[[Windows]]:		[[Windows]]:
	In Network Configuration under TCP/IP and then Properties, you can choose to either to either request your IP or specify it manually.		In Network Configuration under TCP/IP and then Properties, you can choose to either to either request your IP or specify it manually.
Line 68:		Line 71:

	You should be ready to try to [[Connect]] somewhere now.		You should be ready to try to [[Connect]] somewhere now.


	== Exhausting IP addresses ==		== Exhausting IP addresses ==

	With 1.5 billion internet users today and more coming the IP address space is getting exhausted. We have a maximum of 4.5 billion Internet addresses in the 32 bit space of which 0.5 billion are reserved for multicasting and research. Also, some organizations have entire /8 space for themselves and hardly use it. We're expected to run scarce on IPv4 address space in the 2010's. A replacement for IPv4 is already in operation called [[IPv6]]. It offers a lot more address space (128 bits).		With 1.5 billion internet users today and more coming the IP address space is getting exhausted. We have a maximum of 4.5 billion Internet addresses in the 32 bit space of which 0.5 billion are reserved for multicasting and research. Also, some organizations have entire /8 space for themselves and hardly use it. We're expected to run scarce on IPv4 address space in the 2010's. A replacement for IPv4 is already in operation called [[IPv6]]. It offers a lot more address space (128 bits).

Pbug at 11:19, 13 August 2009

2009-08-13T11:19:59Z

← Older revision		Revision as of 04:19, 13 August 2009
Line 2:		Line 2:


	== Obtaining ==		== Obtaining an IP manually or with DHCP ==
	[[Windows]]:		[[Windows]]:
	In Network Configuration under TCP/IP and then Properties, you can choose to either to either request your IP or specify it manually.		In Network Configuration under TCP/IP and then Properties, you can choose to either to either request your IP or specify it manually.
Line 68:		Line 68:

	You should be ready to try to [[Connect]] somewhere now.		You should be ready to try to [[Connect]] somewhere now.


			== Exhausting IP addresses ==

			With 1.5 billion internet users today and more coming the IP address space is getting exhausted. We have a maximum of 4.5 billion Internet addresses in the 32 bit space of which 0.5 billion are reserved for multicasting and research. Also, some organizations have entire /8 space for themselves and hardly use it. We're expected to run scarce on IPv4 address space in the 2010's. A replacement for IPv4 is already in operation called [[IPv6]]. It offers a lot more address space (128 bits).

Franks: Added windows, need to start taking screenshots.

2006-03-17T02:11:32Z

Added windows, need to start taking screenshots.

← Older revision		Revision as of 19:11, 16 March 2006
Line 3:		Line 3:

	== Obtaining ==		== Obtaining ==
			[[Windows]]:
			In Network Configuration under TCP/IP and then Properties, you can choose to either to either request your IP or specify it manually.

			[[UBO]]:
	To obtain a standard IPv4 address, you can either specify it manually, or request one if you have a [[dhcpd]] server on your [[subnet]]. We'll assume in this example that your ethernet interface is "eth0". You should be able to find your interface by typing		To obtain a standard IPv4 address, you can either specify it manually, or request one if you have a [[dhcpd]] server on your [[subnet]]. We'll assume in this example that your ethernet interface is "eth0". You should be able to find your interface by typing
	$ /sbin/ifconfig		$ /sbin/ifconfig

Franks at 01:58, 17 March 2006

2006-03-17T01:58:19Z

← Older revision		Revision as of 18:58, 16 March 2006
Line 1:		Line 1:
	Internet Protocol. [[RFC]] 791. Without it you would not read this.		Internet Protocol. [[RFC]] 791. Without it you would not read this.


			== Obtaining ==

			To obtain a standard IPv4 address, you can either specify it manually, or request one if you have a [[dhcpd]] server on your [[subnet]]. We'll assume in this example that your ethernet interface is "eth0". You should be able to find your interface by typing
			$ /sbin/ifconfig
			otherwise you will have to find your [[NIC]].

			To request an IP you will require the application called dhclient, it should be as simple as that

			# dhclient eth0
			Internet Software Consortium DHCP Client 2.0pl5
			Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
			All rights reserved.
			Please contribute if you find this software useful.
			For info, please visit http://www.isc.org/dhcp-contrib.html
			sit0: unknown hardware address type 776
			sit0: unknown hardware address type 776
			Listening on LPF/eth0/00:0f:1f:df:4e:39
			Sending on LPF/eth0/00:0f:1f:df:4e:39
			Sending on Socket/fallback/fallback-net
			DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
			receive_packet failed on eth0: Network is down
			DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
			DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
			DHCPOFFER from 192.168.1.1
			DHCPREQUEST on eth0 to 255.255.255.255 port 67
			DHCPACK from 192.168.1.1
			bound to 192.168.1.11 -- renewal in 30000 seconds.

			Now to verify it's up and working:
			# ifconfig eth0 \| grep inet
			inet addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0

			Looks good. Time you try to [[connect]] somewhere.

			Although dhcp is the more popular and easier of the two, you can also specify an IP address using ifconfig. You typically will need to know the [[NIC]] and your IP, although you can add subnet and many other options in the [[Manual]] if you want a non-standard configuration.

			# ifconfig eth0 192.168.1.11

			should be as simple as that. Now to verify it's working:

			# ifconfig eth0 \| grep inet
			inet addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0

			Excellent! The one difference with setting your IP is that dhcpd usually also defines your default gateway. Your gateway is typically the host of your ISP that your internet traffic will go through. Your gateway or router will be one [[traceroute\|hop]] away from you. To set a default gateway of 192.168.1.1 you will do the following. Note that many [[UBO]]s use a different route command, so you will likely use one of the following three:

			# route add default gw 192.168.1.1

			# route add default 192.168.1.1

			# route add default gateway 192.168.1.1

			but really, you're not going to run a command as [[root]] without reading the [[Manual]] page first to ensure you're using the proper syntax, right?


			Finally, we will check our routing:

			$ netstat -rn
			Kernel IP routing table
			Destination Gateway Genmask Flags MSS Window irtt Iface
			192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
			0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

			You should be ready to try to [[Connect]] somewhere now.

Pbug at 12:41, 13 October 2005

2005-10-13T12:41:55Z

← Older revision		Revision as of 05:41, 13 October 2005
Line 1:		Line 1:
	Internet Protocol. Without it you would not read this.		Internet Protocol. [[RFC]] 791. Without it you would not read this.

Pbug at 12:29, 13 October 2005

2005-10-13T12:29:05Z

New page

Internet Protocol. Without it you would not read this.