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.
21
1
* Adding a Client Password to the Server
23
3
The server must be given a password to give back to the client on
44
24
it, and output it to standard output. There it can be verified to
45
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 this should result in an incorrect
37
interface, edit the DEVICE setting in the
38
"/etc/initramfs-tools/initramfs.conf" file. (The default setting is
39
empty, meaning it will autodetect the interface.) *If* the DEVICE
40
setting is changed, it will be necessary to update the initrd image
41
by running the command
43
update-initramfs -k all -u
45
The device can be overridden at boot time on the Linux kernel
46
command line using the sixth colon-separated field of the "ip="
47
option; for exact syntax, read the documentation in the file
48
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfsroot.txt",
49
available in the "linux-doc-*" package.
51
Note that since this network interface is used in the initial RAM
52
disk environment, the network interface *must* exist at that stage.
53
Thus, the interface can *not* be a pseudo-interface such as "br0" or
54
"tun0"; instead, only real interface (such as "eth0") can be used.
55
This can be overcome by writing a "network hook" program to create
56
the interface (see mandos-client(8mandos)) and placing it in
57
"/etc/mandos/network-hooks.d", from where it will be copied into the
58
initial RAM disk. Example network hook scripts can be found in
59
"/usr/share/doc/mandos-client/network-hooks.d".
47
61
* User-Supplied Plugins
49
63
Any plugins found in "/etc/mandos/plugins.d" will override and add
60
74
Mandos client will be the new default way for getting a password for
61
75
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.
69
77
* Non-local Connection (Not Using ZeroConf)
71
79
If the "ip=" kernel command line option is used to specify a
72
80
complete IP address and device name, as noted above, it then becomes
73
81
possible to specify a specific IP address and port to connect to,
74
82
instead of using ZeroConf. The syntax for doing this is
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.
83
"mandos=connect:<IP_ADDRESS>:<PORT_NUMBER>" on the kernel command
80
86
For very advanced users, it it possible to specify simply
81
87
"mandos=connect" on the kernel command line to make the system only
84
90
work, "--options-for=mandos-client:--connect=<ADDRESS>:<PORT>" needs
85
91
to be manually added to the file "/etc/mandos/plugin-runner.conf".
87
-- Teddy Hogeborn <teddy@fukt.bsnet.se>, Tue, 8 Sep 2009 08:25:58 +0200
93
-- Teddy Hogeborn <teddy@recompile.se>, Mon, 28 Nov 2011 23:07:22 +0100