====== Differences ====== This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
wirelessboot [2009/08/11 15:14] rwcr |
wirelessboot [2009/11/29 12:30] (current) rwcr wireless_settings.gpxe => wireless.gpxe |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| //**Note:** the contents of this page rely on some features that are not yet present in mainline gPXE, but hopefully they should be there soon.// | //**Note:** the contents of this page rely on some features that are not yet present in mainline gPXE, but hopefully they should be there soon.// | ||
| + | |||
| + | For the curious, some [[:wirelessboot:implementation|implementation details]] are available. | ||
| ===== Supported hardware ===== | ===== Supported hardware ===== | ||
| Line 66: | Line 68: | ||
| Could not configure net0: Connection timed out (0x4c106035) | Could not configure net0: Connection timed out (0x4c106035) | ||
| suggests the same, especially if ''iwstat net0'' shows a line like | suggests the same, especially if ''iwstat net0'' shows a line like | ||
| - | [TXE: 4 x "Packet decryption error (0x1c1f6602)"] | + | [RXE: 4 x "Packet decryption error (0x1c1f6602)"] |
| For any other error, consult us on the Etherboot-discuss mailing list or the ''#etherboot'' IRC channel; especially remember to specify the eight-digit error code(s) beginning with ''0x''. | For any other error, consult us on the Etherboot-discuss mailing list or the ''#etherboot'' IRC channel; especially remember to specify the eight-digit error code(s) beginning with ''0x''. | ||
| Line 74: | Line 76: | ||
| Unlike DHCP on a wired network, connecting to wireless requires that some settings be provided before any network services can be accessed at all. Specifically, you need to specify the SSID and encryption key (as above) before you can run DHCP. These are set per network device, and have the gPXE setting names ''net//X///ssid'' and ''net//X///key'' respectively, where ''//X//'' is the number of your network device. | Unlike DHCP on a wired network, connecting to wireless requires that some settings be provided before any network services can be accessed at all. Specifically, you need to specify the SSID and encryption key (as above) before you can run DHCP. These are set per network device, and have the gPXE setting names ''net//X///ssid'' and ''net//X///key'' respectively, where ''//X//'' is the number of your network device. | ||
| - | Currently no wireless NIC has support for gPXE's NVRAM settings support, but if you have a wired NIC with such support you may be able to use the ''config'' command at the gPXE prompt to set the settings permanently. Otherwise, you'll need to create a small gPXE script and embed it. For example, put this in a file named ''wireless_settings.gpxe'': | + | Currently no wireless NIC has support for gPXE's NVRAM settings support, but if you have a wired NIC with such support you may be able to use the ''config'' command at the gPXE prompt to set the settings permanently. Otherwise, you'll need to create a small gPXE script and embed it. For example, put this in a file named ''wireless.gpxe'': |
| #!gpxe | #!gpxe | ||
| set net0/ssid mynetwork | set net0/ssid mynetwork | ||
| set net0/key seeecret | set net0/key seeecret | ||
| autoboot | autoboot | ||
| - | Compile gPXE with ''EMBEDDED_IMAGE=wireless_settings.gpxe'' on your ''make'' command line, and boot it; it should boot off the wireless network automatically. | + | Compile gPXE with ''EMBEDDED_IMAGE=wireless.gpxe'' on your ''make'' command line, and boot it; it should boot off the wireless network automatically. |
| Congratulations on successfully booting gPXE over wireless! | Congratulations on successfully booting gPXE over wireless! | ||
