1
* Choose the Client Network Interface
3
Please make sure that the correct network interface is specified in
4
the DEVICE setting in the "/etc/initramfs-tools/initramfs.conf"
5
file. If the setting is empty, the interface will be autodetected
6
at boot time, which may not be correct. *If* the DEVICE setting is
7
changed, it will be necessary to update the initrd image by running
10
update-initramfs -k all -u
12
The device can be overridden at boot time on the Linux kernel
13
command line using the sixth colon-separated field of the "ip="
14
option; for exact syntax, read the documentation in the file
15
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfsroot.txt",
16
available in the "linux-doc-*" package.
18
Note that since this network interface is used in the initial RAM
19
disk environment, the network interface *must* exist at that stage.
20
Thus, the interface can *not* be a pseudo-interface such as "br0" or
21
"tun0"; instead, a real interface (such as "eth0") must be used.
23
1
* Adding a Client Password to the Server
25
3
The server must be given a password to give back to the client on
46
24
it, and output it to standard output. There it can be verified to
47
25
be the correct password, before rebooting.
29
If it ever should be necessary, the Mandos client can be temporarily
30
prevented from running at startup by passing the parameter
31
"mandos=off" to the kernel.
33
* Specifying a Client Network Interface
35
At boot time the network interface to use will by default be
36
automatically detected. If should result in an incorrect interface,
37
edit the DEVICE setting in the "/etc/initramfs-tools/initramfs.conf"
38
file. (The default setting is empty, meaning to autodetect the
39
interface.) *If* the DEVICE setting is changed, it will be
40
necessary to update the initrd image by running the command
42
update-initramfs -k all -u
44
The device can be overridden at boot time on the Linux kernel
45
command line using the sixth colon-separated field of the "ip="
46
option; for exact syntax, read the documentation in the file
47
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfsroot.txt",
48
available in the "linux-doc-*" package.
50
Note that since this network interface is used in the initial RAM
51
disk environment, the network interface *must* exist at that stage.
52
Thus, the interface can *not* be a pseudo-interface such as "br0" or
53
"tun0"; instead, only real interface (such as "eth0") can be used.
49
55
* User-Supplied Plugins
51
57
Any plugins found in "/etc/mandos/plugins.d" will override and add
62
68
Mandos client will be the new default way for getting a password for
63
69
the root file system when booting.
67
If it ever should be necessary, the Mandos client can be temporarily
68
prevented from running at startup by passing the parameter
69
"mandos=off" to the kernel.
71
71
* Non-local Connection (Not Using ZeroConf)
73
73
If the "ip=" kernel command line option is used to specify a
74
74
complete IP address and device name, as noted above, it then becomes
75
75
possible to specify a specific IP address and port to connect to,
76
76
instead of using ZeroConf. The syntax for doing this is
77
"mandos=connect:<IP_ADDRESS>:<PORT_NUMBER>".
77
"mandos=connect:<IP_ADDRESS>:<PORT_NUMBER>" on the kernel command
79
80
For very advanced users, it it possible to specify simply
80
81
"mandos=connect" on the kernel command line to make the system only
83
84
work, "--options-for=mandos-client:--connect=<ADDRESS>:<PORT>" needs
84
85
to be manually added to the file "/etc/mandos/plugin-runner.conf".
86
-- Teddy Hogeborn <teddy@fukt.bsnet.se>, Mon, 27 Sep 2010 19:53:21 +0200
87
-- Teddy Hogeborn <teddy@recompile.se>, Wed, 5 Oct 2011 17:50:22 +0200
added
removed
debian/mandos-client.README.Debian
