Changeset a2b1f0b in freewrt
- Timestamp:
- May 14, 2007, 10:36:43 AM (19 years ago)
- Children:
- 7f5285e
- Parents:
- 85e93a2
- File:
-
- 1 edited
-
docs/fwifupdown/fwifupdown.txt (modified) (7 diffs)
Legend:
- Unmodified
- Added
- Removed
-
docs/fwifupdown/fwifupdown.txt
r85e93a2 ra2b1f0b 8 8 9 9 The major goal of fwifupdown is the handling of network device dependencies. 10 It provides status information s to syslog and STDOUT as well in addition.10 It provides status information to syslog and STDOUT as well. 11 11 12 12 … … 14 14 15 15 Fwifupdown tries to figure out the type of given interface either from given 16 config (ifup) and (ifdown) from informations given by the system (/proc, 17 various system tools). 18 19 2.1 Legecy interface support 20 21 This is the default if no other device type can be figured out, the ifupdown 22 behavior is equal to busybox fupdown. 23 24 2.2 Alias support 16 config or from information given by the system (/proc, various system tools). 17 18 2.1 Legacy interface support 19 20 This is the default, if no other device type can be figured out, the ifupdown 21 behavior is equal to busybox ifupdown. 22 23 2.2 IP alias support 25 24 26 25 Alias interfaces are figured out by its name foo:* … … 28 27 sense. 29 28 30 2.3 V lansupport31 32 V laninterfaces from name eth*.* are supported, all other not.29 2.3 VLAN support 30 31 VLAN interfaces from name eth*.* are supported, all other not. 33 32 All configuration methods provided by busybox are supported. 34 33 … … 90 89 3.1 DHCP support 91 90 92 DHCP support by fwifupdown is added (version >= 0.2-1). 93 94 The default dchp client is busybox udhcpc if nothing else is configured or 91 The default dhcp client is busybox udhcpc, if nothing else is configured or 95 92 the configured client is not present. 96 93 … … 124 121 and syntax are equal to the old busybox network configuration. 125 122 126 There's one difference: There 's no need to tag all needed devices as123 There's one difference: There is no need to tag all needed devices as 127 124 "auto", only the main devices must be tagged, not the devices they depend 128 from.129 130 4.1 Example configuration with wi teless bridging and openvpn tunnel125 on. 126 127 4.1 Example configuration with wireless bridging and openvpn tunnel 131 128 132 129 # file /etc/network/interfaces … … 157 154 158 155 iface tap0 inet static 159 tuntap openvpn156 tuntap openvpn 160 157 address 0.0.0.0 161 158 netmask 255.255.255.255 … … 239 236 iface_type() 240 237 Add code here to figure out the interface type. 238 This function is mandatory. 241 239 242 240 if_preup()
Note:
See TracChangeset
for help on using the changeset viewer.
