projects / network.git / blame
| Commit | Line | Data |
|---|---|---|
| ec63256a MT |
1 | .TH network-device 8 "6 Jun 2012" "@VERSION@" "network man page" |
| 2 | ||
| 3 | .SH NAME | |
| 4 | network-device \- Network Configuration Control Program | |
| 5 | ||
| 6 | .SH SYNOPSIS | |
| 7 | \fBnetwork [OPTIONS] device <device> [status|discover] ...\fR | |
| 8 | ||
| 9 | .SH DESCRIPTION | |
| 10 | By the device subcommands, it is very easy to get status information | |
| 11 | about network devices and do some more things. | |
| 12 | ||
| 13 | .SH OPTIONS | |
| 14 | The \fBnetwork device\fR command offers various commands: | |
| 15 | ||
| 16 | \fB<device> status\fR | |
| 17 | .RS 4 | |
| 18 | This will show you very detailed information about the given device. | |
| 19 | .PP | |
| 20 | This is all about the ethernet parts of the device and does not contain | |
| 21 | any IP information as this is defined as a zone (\fBnetwork-zone\fR(8)). | |
| 22 | .RE | |
| 23 | .PP | |
| 24 | ||
| 25 | \fB<device> discover\fR | |
| 26 | .RS 4 | |
| 27 | Runs a discovery for many hooks on the given device. This will check | |
| 28 | if the hook can find for example a DHCP server or DSLAM and thus predict | |
| 29 | for what the device should be used. | |
| 30 | .RE | |
| 31 | .PP | |
| 32 | ||
| 33 | .SH SEE ALSO | |
| 34 | network(8) | |
| 35 | ||
| 36 | .SH AUTHOR | |
| 37 | Michael Tremer (michael.tremer@ipfire.org) |