1
* Choose the Client Network Interface
3
You MUST make sure that the correct network interface is specified
4
in the DEVICE setting in the "/etc/initramfs-tools/initramfs.conf"
5
file. *If* this is changed, it will be necessary to update the
6
initrd image by running the command
8
update-initramfs -k all -u
10
The device can be overridden at boot time on the Linux kernel
11
command line using the sixth colon-separated field of the "ip="
12
option; for exact syntax, read the documentation in the file
13
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfsroot.txt",
14
available in the "linux-doc-*" package.
16
Note that since this network interface is used in the initial RAM
17
disk environment, the network interface *must* exist at that stage.
18
Thus, the interface can *not* be a pseudo-interface such as "br0" or
19
"tun0"; instead, a real interface (such as "eth0") must be used.
1
21
* Adding a Client Password to the Server
3
23
The server must be given a password to give back to the client on
24
44
it, and output it to standard output. There it can be verified to
25
45
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.
54
This can be overcome by writing a "network hook" program (see
55
mandos-client(8mandos)) and placing it in
56
"/etc/mandos/network-hooks.d", from where it will be copied into the
57
initial RAM disk. Some example network hook scripts can be found in
58
"/usr/share/doc/mandos-client/network-hooks.d".
60
47
* User-Supplied Plugins
62
49
Any plugins found in "/etc/mandos/plugins.d" will override and add
73
60
Mandos client will be the new default way for getting a password for
74
61
the root file system when booting.
65
If it ever should be necessary, the Mandos client can be temporarily
66
prevented from running at startup by passing the parameter
67
"mandos=off" to the kernel.
76
69
* Non-local Connection (Not Using ZeroConf)
78
71
If the "ip=" kernel command line option is used to specify a
79
72
complete IP address and device name, as noted above, it then becomes
80
73
possible to specify a specific IP address and port to connect to,
81
74
instead of using ZeroConf. The syntax for doing this is
82
"mandos=connect:<IP_ADDRESS>:<PORT_NUMBER>" on the kernel command
75
"mandos=connect:<IP_ADDRESS>:<PORT_NUMBER>".
77
Warning: this will cause the client to make exactly one attempt at
78
connecting, and then fail if it does not succeed.
85
80
For very advanced users, it it possible to specify simply
86
81
"mandos=connect" on the kernel command line to make the system only
89
84
work, "--options-for=mandos-client:--connect=<ADDRESS>:<PORT>" needs
90
85
to be manually added to the file "/etc/mandos/plugin-runner.conf".
92
-- Teddy Hogeborn <teddy@recompile.se>, Sun, 27 Nov 2011 03:30:40 +0100
87
-- Teddy Hogeborn <teddy@fukt.bsnet.se>, Tue, 8 Sep 2009 08:25:58 +0200