SCM Repository

project home | /[freewrt]/branches/freewrt_1_0/docs/handbook/user/handbook.tex

Diff of /branches/freewrt_1_0/docs/handbook/user/handbook.tex

Parent Directory | Revision Log | View Patch Patch

-revision 2546 by n0-1,
Thu May 17 21:12:17 2007 UTC
+revision 2547 by wbx,
Sat May 19 10:36:16 2007 UTC
 Line 610 
 guides for using FreeWRT in general, of
  \section{Network Configuration}
+ <<<<<<< .mine
+ The device names for real network interfaces in Linux are named \code{ethx} (\code{x} is
+ \code{0--9}). If the device has a switch, the different ports are separated via VLAN
+ technology. The vlan interfaces are named \code{ethx.y}.  The network configuration in
+ FreeWRT is managed via \app{Busybox}'s \app{ifupdown} implementation. \app{Busybox}'s builtin \app{ip}
+ command configures the network interfaces. There is no \app{ifconfig} or \app{route}, you can activate
+ it in the ADK menue, if you like.
+ =======
  The device names for real network interfaces in Linux are named \code{ethx}
  (\code{x} is \code{0--9}). If the device has a switch, the different ports are
  separated via VLAN technology. The vlan interfaces are named \code{ethx.y}.
  The network configuration in FreeWRT is managed via \app{Busybox}'s
  \app{ifupdown} implementation. \app{Busybox}'s builtin \app{ip} command
  configures the network interfaces. There is no \app{ifconfig} or \app{route}.
+ >>>>>>> .r2546
  To show all configured network interfaces use:
  \begin{Verbatim}[label=show IP address]
  $ ip addr show
-Line 635 
 iface <iface-name> inet <method>
+Line 645 
 iface <iface-name> inet <method>
    <option-z> <value>
  \end{Verbatim}
+ <<<<<<< .mine
+ <b>ATTENTION: Be sure you have no whitespaces at the and of any value!</b>
+ \code{auto <iface-name>} is optional and, if set, tells the \app{ifup} script to
+ start this interface automatically on bootup.
+ =======
  \code{auto <iface-name>} is optional and, if set, tells the \app{ifup} script
  to start this interface automatically on bootup.
+ >>>>>>> .r2546
  Each interface needs a unique name which, depending on the method, represents
  either a physical interface or a logical interface name like \code{eth0.1} for
-Line 757 
 iface eth0.1 inet dhcp
+Line 774 
 iface eth0.1 inet dhcp
  \end{Verbatim}
  Typically this configures the WAN-Port to start a DHCP request on bootup.
- \subsection{Bridging}
- This is mostly needed to combine LAN and WLAN to a homogeneous network.  Be
- sure you have installed the package \app{bridge-utils}.
- \begin{Verbatim}[label=\file{/etc/network/interfaces}]
- auto eth0.0
- iface eth0.0 inet manual
-     switch-ports 1 2 3 4 5*
- auto eth1
- iface eth1 inet manual
-     wireless-bridge-if br0
-     [... other wifi-settings, see below ...]
- auto br0
- iface br0 inet static
-     bridge-ifaces eth0.0 eth1
-     address 192.168.1.1
-     netmask 255.255.255.0
-     broadcast +
- \end{Verbatim}
- This creates a new bridging interface \code{br0} which combines the VLAN
- interface \code{eth0.0} (representing the LAN-ports 1--4) and the WLAN
- interface \code{eth1} (on some devices like \term{Asus WL500gP} this might be
- \code{eth2}).  The bridge interface needs always be the last one, otherwise it
- can not find the interfaces in \code{bridge-ifaces}.
  \subsection{WLAN}
  A router containing a WLAN interface has an additional ethernet device
  representing it. On Broad\-com-based hardware it is typically \code{eth1}
-Line 981 
 Mandatory options and default parameters
+Line 969 
 Mandatory options and default parameters
  \hline
  \end{longtable}
- \subsubsection{Examples}
+ \subsubsection{Examples for wireless configuration}
- \paragraph{WLAN with WEP128}
+ \paragraph{WLAN with WPA1/WPA2 AES+TKIP}
+ This combination works with any kind of WPA client implementation.
  \begin{Verbatim}[label=\file{/etc/network/interfaces}]
+ auto eth1
  iface eth1 inet static
          address 192.168.10.1
          netmask 255.255.255.0
-Line 992 
 iface eth1 inet static
+Line 985 
 iface eth1 inet static
          wireless-country DE
          wireless-mode ap
          wireless-ssid FreeWRT
-         wireless-security wep
+         wireless-security wpa-psk
-         wireless-key1 11223344556677889900112233
+         wireless-authorization psk psk2
+         wireless-encryption aes+tkip
+         wireless-wpa-key 12345678
          wireless-channel 11
  \end{Verbatim}
- \paragraph{WLAN without encryption}
+ If you want to do MAC filtering, add the following to the sample above:
  \begin{Verbatim}[label=\file{/etc/network/interfaces}]
- iface eth1 inet static
+         wireless-macmode 2
-         address 192.168.10.1
+         wireless-mac 00:01:02:03:04:05 06:07:08:09:0a:0b
-         netmask 255.255.255.0
-         broadcast +
-         wireless-type broadcom
-         wireless-country DE
-         wireless-mode ap
-         wireless-ssid FreeWRT
-         wireless-security none
-         wireless-channel 11
  \end{Verbatim}
+ this enables the filter and defines the list to contain addresses that should be allowed.
+ \paragraph{WLAN without encryption}
+ If you already use VPN to secure your connection, you can just use an unencrypted setup
+ and setup the firewall on your embedded device.
- \paragraph{WLAN with WPA2 (AES)}
  \begin{Verbatim}[label=\file{/etc/network/interfaces}]
+ auto eth1
  iface eth1 inet static
          address 192.168.10.1
          netmask 255.255.255.0
-Line 1021 
 iface eth1 inet static
+Line 1014 
 iface eth1 inet static
          wireless-country DE
          wireless-mode ap
          wireless-ssid FreeWRT
-         wireless-security wpa-psk
+         wireless-security none
-         wireless-authorization psk2
-         wireless-encryption aes
-         wireless-wpa-key 12345678
          wireless-channel 11
  \end{Verbatim}
- If you want to do MAC filtering, add the following to the sample above:
+ \paragraph{WLAN client with WPA2 (AES)}
- \begin{Verbatim}[label=\file{/etc/network/interfaces}]
-         wireless-macmode 2
-         wireless-mac 00:01:02:03:04:05 06:07:08:09:0a:0b
- \end{Verbatim}
- this enables the filter and defines the list to contain addresses that should
- be allowed.
- To enhance wireless performance, you can enable some flags like Broadcom's
+ This can only be used in routing mode, you can not bridge it with LAN or WAN interfaces.
- SpeedBooster. Normally, these flags are not dangerous:
- \begin{Verbatim}[label=\file{/etc/network/interfaces}]
-         wireless-gmode performance
-         wireless-frameburst 1
-         wireless-afterburner 1
- \end{Verbatim}
- \paragraph{WLAN client with WPA2 (AES) (\strong{untested})}
  \begin{Verbatim}[label=\file{/etc/network/interfaces}]
+ auto eth1
  iface eth1 inet static
          address 192.168.10.1
          netmask 255.255.255.0
-Line 1060 
 iface eth1 inet static
+Line 1038 
 iface eth1 inet static
          wireless-wpa-key 12345678
  \end{Verbatim}
- \paragraph{WLAN client with WEP128}
- \begin{Verbatim}[label=\file{/etc/network/interfaces}]
- iface eth1 inet dhcp
-         wireless-type broadcom
-         wireless-country DE
-         wireless-mode sta
-         wireless-ssid FreeWRT
-         wireless-security wep
-         wireless-key1 11223344556677889900112233
- \end{Verbatim}
  WLAN with WDS nodes, the WDS nodes need to have the same
- SSID, channel and encryption parameters.
+ SSID, channel and encryption parameters. The WDS connection is separetely
+ secured via WPA1 and AES. WPA2 for WDS connection security is \_not\_ working.
  WDS node 1 (MAC of Wireless \code{06:05:04:03:02:01})
  \begin{Verbatim}[label=\file{/etc/network/interfaces}]
+ auto br0
  iface br0 inet static
          bridge-ifaces eth1
          address 192.168.10.1
-Line 1085 
 iface br0 inet static
+Line 1054 
 iface br0 inet static
          wireless-country DE
          wireless-mode wds
          wireless-ssid FreeWRT-WDS
-         wireless-security none
+         wireless-security wpa-psk
-         wireless-lazywds 0
+         wireless-authorization psk psk2
+         wireless-encryption aes+tkip
+         wireless-wpa-key apkey
+         wireless-lazywds 1
+         wireless-wds-security wpa-psk
+         wireless-wds-encryption aes
+         wireless-wds-wpa-key wdskey
          wireless-wds 01:02:03:04:05:06
          wireless-wds-bridge br0
  \end{Verbatim}
  WDS node 2 (MAC of Wireless \code{01:02:03:04:05:06})
  \begin{Verbatim}[label=\file{/etc/network/interfaces}]
+ auto br0
  iface br0 inet static
          bridge-ifaces eth1
          address 192.168.10.2
-Line 1101 
 iface br0 inet static
+Line 1077 
 iface br0 inet static
          wireless-country DE
          wireless-mode wds
          wireless-ssid FreeWRT-WDS
-         wireless-security none
+         wireless-security wpa-psk
-         wireless-lazywds 0
+         wireless-authorization psk psk2
+         wireless-encryption aes+tkip
+         wireless-wpa-key apkey
+         wireless-lazywds 1
+         wireless-wds-security wpa-psk
+         wireless-wds-encryption aes
+         wireless-wds-wpa-key wdskey
          wireless-wds 06:05:04:03:02:01
          wireless-wds-bridge br0
  \end{Verbatim}
- \paragraph{Peer-to-Peer mode (no encryption, IP must be static)}
+ \paragraph{Peer-to-Peer/AdHoc mode (no encryption, IP must be static)}
  \begin{Verbatim}[label=\file{/etc/network/interfaces}]
+ auto eth1
  iface eth1 inet static
          address 192.168.10.1
          netmask 255.255.255.0
-Line 1121 
 iface eth1 inet static
+Line 1104 
 iface eth1 inet static
          wireless-channel 11
  \end{Verbatim}
+ \subsection{Bridging}
+ This is mostly needed to combine LAN and WLAN to a homogeneous network.
+ Be sure you have installed the package \app{bridge-utils}.
+ See the example for a bridging setup, WLAN is secured via WPA/WPA2.
+ \begin{Verbatim}[label=\file{/etc/network/interfaces}]
+ auto eth0.0
+ iface eth0.0 inet manual
+         switch-ports 1 2 3 4 5*
+ auto eth1
+ iface eth1 inet manual
+         wireless-type broadcom
+         wireless-country DE
+         wireless-mode ap
+         wireless-ssid FreeWRT
+         wireless-channel 11
+         wireless-security wpa-psk
+         wireless-authorization psk psk2
+         wireless-encryption aes+tkip
+         wireless-wpa-key MyWlanSecret
+         wireless-bridge-if br0
+ auto br0
+ iface br0 inet static
+         bridge-ifaces eth0.0 eth1
+         address 192.168.1.1
+         netmask 255.255.255.0
+         broadcast +
+ \end{Verbatim}
+ This creates a new bridging interface \code{br0} which combines the VLAN
+ interface \code{eth0.0} (representing the LAN-ports 1--4) and the WLAN interface
+ \code{eth1} (on some devices like \term{Asus WL500gP} this might be \code{eth2}).
+ The bridge interface needs always be the last one, otherwise it can not find
+ the interfaces in \code{bridge-ifaces}.
  \subsection{PPP}
  PPP comes in various flavours for different situations, the most commonly

 Legend:



Removed from v.2546
 


changed lines


 
Added in v.2547
 Legend:



Removed from v.2546
 


changed lines


 
Added in v.2547
-Removed from v.2546
+Added in v.2547

root@freewrt.org:443	ViewVC Help
Powered by ViewVC 1.1.20

// Log In
// CVSweb
Project: FreeWRT
// Summary // Activity // Search // Tracker // Lists // News // SCM // Wiki