1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
|
Network operation mode
11.. PPuurrppoossee
The network operation mode is selected either at boot time using
askrunlevel (called automatically) or any time, using the "netconf
--runlevel" command.
Basically, _L_i_n_u_x can operate in three different modes, network-wise.
+o Standalone (local) mode.
This mode is selected when no network adapter is installed. It
might be selected to save on RAM used.
This mode configures the loopback interface, allowing you to do
minimal "local" networking (which is a good way to practice without
bugging system administrators).
+o Client mode.
In this mode, only the minimal daemons necessary to access the
network are started. While minimal, the inetd daemon is activated,
allowing your computer to provide some services, such as telnet.
+o Server mode.
All daemons configured will be started.
22.. SSwwiittcchhiinngg nneettwwoorrkk lleevveellss oonn tthhee ffllyy
Your are allowed to switch the network operation mode on the fly using
the following commands:
+o netconf --runlevel local
+o netconf --runlevel client
+o netconf --runlevel server
In each case, it will make sure the proper daemons are running.
The command
netconf --update
may be also useful to make sure a system is current (in sync with its
configuration). The command
netconf --status
gives a report on what has to be done, while --update does it.
The file /var/run/netconf.level stores the current operation mode and
it is used by the --update and --status options for netconf. This
file is updated by "netconf --runlevel" and by /sbin/askrunlevel at
boot time.
|
