Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Last revision Both sides next revision | ||
|
soc:2011:pcmattman:notes:start [2011/07/04 04:16] pcmattman rfc for network boot dhcp6 options |
soc:2011:pcmattman:notes:start [2011/07/31 18:11] pcmattman updates to the basic documentation already written |
||
|---|---|---|---|
| Line 30: | Line 30: | ||
| ==== Setting up IPv6 on your network ==== | ==== Setting up IPv6 on your network ==== | ||
| - | To work with IPv6 in gPXE on your network, you will need both an IPv6 prefix and a router advertisement daemon. DHCPv6 support is coming soon! | + | To work with IPv6 in gPXE on your network, you will need both an IPv6 prefix and a router advertisement daemon. If you like, you can set up DHCPv6 for your network for address assignment. A router advertisement daemon will still be required for routing, but in the future DHCPv6 will offer boot filenames and other boot-related options. |
| - | The best place to get an IPv6 is your ISP, but if your ISP does not offer IPv6, [[http://www.tunnelbroker.net|Hurricane Electric]] offers a fairly stable and easy-to-use tunnel. HE also provides configuration commands for a wide range of operating systems. | + | The best place to get an IPv6 is your ISP, but if your ISP does not offer IPv6, [[http://www.tunnelbroker.net|Hurricane Electric]] offers a fairly stable and easy-to-use tunnel. HE also provides configuration commands for a wide range of operating systems. These should be able to be copied and pasted into a terminal on your workstation to set up IPv6 connectivity quickly and easily. There are a variety of tutorials on the internet that will cover adding router advertisements and/or DHCPv6 to an IPv6 tunnel. |
| - | Once your network is IPv6-enabled, you will need a router advertisement daemon to advertise the prefix you have been assigned. These router advertisements allow hosts to autoconfigure themselves where a DHCPv6 server is not present. | + | Booting over IPv6 in gPXE is quite simple: instead of using the 'dhcp' command (ala IPv4), you use the 'ipv6' command. This obtains an address and sets up routing for IPv6 so that you can use IPv6 servers. |
| - | + | ||
| - | Note that currently IPv6 in gPXE will not work properly on IPv6 networks with DHCPv6 servers. | + | |
| You can use the following script to test gPXE's HTTP boot over IPv6: | You can use the following script to test gPXE's HTTP boot over IPv6: | ||
| Line 42: | Line 40: | ||
| #!gpxe | #!gpxe | ||
| ipv6 any | ipv6 any | ||
| - | kernel http://ipv6.theiselins.net/gpxe/bz2bzImage root=100 | + | kernel http://flash6.etherboot.org/gpxe/bz2bzImage root=100 |
| - | initrd http://ipv6.theiselins.net/gpxe/initrd.bz2 | + | initrd http://flash6.etherboot.org/gpxe/initrd.bz2 |
| boot | boot | ||
| </code> | </code> | ||
| + | |||
| + | (note: flash6 may need these image files uploaded - TODO!) | ||
| This should boot a Linux kernel. | This should boot a Linux kernel. | ||
| + | |||
| + | If you don't have a DNS name for an IPv6 host, you can boot from an IPv6 address using the following syntax: | ||
| + | <code> | ||
| + | http://[2001:ab:cd:ef::1]:1234/file.bin | ||
| + | </code> | ||
| + | |||
| + | Note that [[http://msdn.microsoft.com/en-us/library/aa921042.aspx|zero compression ("Compressing Zeroes" section)]] can be used for all IPv6 addresses. | ||
