1 The network configuration is stored in \texttt{/etc/config/network}
2 and is divided into interface configurations.
3 Each interface configuration either refers directly to an ethernet/wifi
4 interface (\texttt{eth0}, \texttt{wl0}, ..) or to a bridge containing multiple interfaces.
11 option ipaddr "192.168.1.1"
12 option netmask "255.255.255.0"
13 option gateway "192.168.1.254"
14 option dns "192.168.1.254"
17 \texttt{ifname} specifies the Linux interface name.
18 If you want to use bridging on one or more interfaces, set \texttt{ifname} to a list
19 of interfaces and add:
24 It is possible to use VLAN tagging on an interface simply by adding the VLAN IDs
25 to it, e.g. \texttt{eth0.1}. These can be nested as well. See the switch section for
32 This sets up a simple static configuration for \texttt{eth0}. \texttt{proto} specifies the
33 protocol used for the interface. The default image usually provides \texttt{'none'}
34 \texttt{'static'}, \texttt{'dhcp'} and \texttt{'pppoe'}. Others can be added by installing additional
37 When using the \texttt{'static'} method like in the example, the options \texttt{ipaddr} and
38 \texttt{netmask} are mandatory, while \texttt{gateway} and \texttt{dns} are optional.
39 You can specify more than one DNS server, separated with spaces:
42 config interface "lan"
46 option dns "192.168.1.254 192.168.1.253" (optional)
49 DHCP currently only accepts \texttt{ipaddr} (IP address to request from the server)
50 and \texttt{hostname} (client hostname identify as) - both are optional.
53 config interface "lan"
56 option ipaddr "192.168.1.1" (optional)
57 option hostname "openwrt" (optional)
60 PPP based protocols (\texttt{pppoe}, \texttt{pptp}, ...) accept these options:
63 The PPP username (usually with PAP authentication)
67 Ping the PPP server (using LCP). The value of this option
68 specifies the maximum number of failed pings before reconnecting.
69 The ping interval defaults to 5, but can be changed by appending
70 ",<interval>" to the keepalive value
72 Use Dial on Demand (value specifies the maximum idle time.
73 \item{server: (pptp)} \\
74 The remote pptp server IP
77 For all protocol types, you can also specify the MTU by using the \texttt{mtu} option.
78 A sample PPPoE config would look like this:
81 config interface "lan"
84 option username "username"
85 option password "openwrt"
86 option mtu "1492" (optional)
89 \subsubsection{Setting up static routes}
91 You can set up static routes for a specific interface that will be brought up
92 after the interface is configured.
94 Simply add a config section like this:
98 option interface "lan"
99 option target "1.1.1.0"
100 option netmask "255.255.255.0"
101 option gateway "192.168.1.1"
104 The name for the route section is optional, the \texttt{interface}, \texttt{target} and
105 \texttt{gateway} options are mandatory.
106 Leaving out the \texttt{netmask} option will turn the route into a host route.
108 \subsubsection{Setting up the switch (currently broadcom only)}
110 The switch configuration is set by adding a \texttt{'switch'} config section.
115 option vlan0 "1 2 3 4 5*"
119 On Broadcom hardware the section name needs to be eth0, as the switch driver
120 does not detect the switch on any other physical device.
121 Every vlan option needs to have the name vlan<n> where <n> is the VLAN number
122 as used in the switch driver.
123 As value it takes a list of ports with these optional suffixes:
127 Set the default VLAN (PVID) of the Port to the current VLAN
129 Force the port to be untagged
131 Force the port to be tagged
134 The CPU port defaults to tagged, all other ports to untagged.
135 On Broadcom hardware the CPU port is always 5. The other ports may vary with
138 For instance, if you wish to have 3 vlans, like one 3-port switch, 1 port in a
139 DMZ, and another one as your WAN interface, use the following configuration :
143 option vlan0 "1 2 3 5*"
148 Three interfaces will be automatically created using this switch layout :
149 \texttt{eth0.0} (vlan0), \texttt{eth0.1} (vlan1) and \texttt{eth0.2} (vlan2).
150 You can then assign those interfaces to a custom network configuration name
151 like \texttt{lan}, \texttt{wan} or \texttt{dmz} for instance.
153 \subsubsection{Setting up IPv6 connectivity}
155 OpenWrt supports IPv6 connectivity using PPP, Tunnel brokers or static
158 If you use PPP, IPv6 will be setup using IP6CP and there is nothing to
161 To setup an IPv6 tunnel to a tunnel broker, you can install the
162 \texttt{6scripts} package and edit the \texttt{/etc/config/6tunnel}
163 file and change the settings accordingly :
167 option tnlifname 'sixbone'
168 option remoteip4 '1.0.0.1'
169 option localip4 '1.0.0.2'
170 option localip6 '2001::DEAD::BEEF::1'
174 \item{\texttt{'tnlifname'}:}
175 Set the interface name of the IPv6 in IPv4 tunnel
176 \item{\texttt{'remoteip4'}:}
177 IP address of the remote end to establish the 6in4 tunnel.
178 This address is given by the tunnel broker
179 \item{\texttt{'localip4'}:}
180 IP address of your router to establish the 6in4 tunnel.
181 It will usually match your WAN IP address.
182 \item{\texttt{'localip6'}:}
183 IPv6 address to setup on your tunnel side
184 This address is given by the tunnel broker
187 Using the same package you can also setup an IPv6 bridged connection:
194 By default the script bridges the WAN interface with the LAN interface
195 and uses ebtables to filter anything that is not IPv6 on the bridge.
196 This configuration is particularly useful if your router is not
197 IPv6 ND proxy capable (see: http://www.rfc-archive.org/getrfc.php?rfc=4389).
199 IPv6 static addressing is also supported using a similar setup as
200 IPv4 but with the \texttt{ip6} prefixing (when applicable).
203 config interface "lan"
205 option proto "static"
206 option ip6addr "fe80::200:ff:fe00:0/64"
207 option ip6gw "2001::DEAF:BEE:1"