Changes between Version 6 and Version 7 of BridgedNetwork


Ignore:
Timestamp:
May 13, 2011, 1:00:05 PM (8 years ago)
Author:
stappers
Comment:

line breaks added, to make further changes more clear

Legend:

Unmodified
Added
Removed
Modified
  • BridgedNetwork

    v6 v7  
    1 This page describes the Network configuration of DebWRT after setting Debian to use the /etc/network/interfaces.lan-wlan-bridge by creating a symlink:
     1This page describes the Network configuration of DebWRT
     2after setting Debian to use the /etc/network/interfaces.lan-wlan-bridge
     3by creating a symlink:
    24{{{
    35ln -snf /etc/network/interfaces.lan-wlan-bridge /etc/network/interfaces
    46}}}
    57
    6 Afer setting the symlink and rebooting the router ( or starting the correct /etc/init.d scripts in the correct order ;-) ) the router will be configured like OpenWRT’s default network config. A WAN interface, which uses DHCP to get it’s IP information. And the LAN and WLAN bridged together. 
     8Afer setting the symlink and rebooting the router
     9( or starting the correct /etc/init.d scripts in the correct order ;-) )
     10the router will be configured like OpenWRT’s default network config.
     11A WAN interface, which uses DHCP to get it’s IP information.
     12And the LAN and WLAN bridged together. 
    713To start the WLAN and bridging
    814add the following symlinks
     
    3137
    3238
    33 The WLAN by default will be setup with ESSID Angel using WPA1/WPA2. A minimal firewall is installed which also does masquarading for LAN/WLAN traffic.
     39The WLAN by default will be setup with ESSID Angel using WPA1/WPA2.
     40A minimal firewall is installed which also does masquarading for
     41LAN/WLAN traffic.
    3442
    3543Resulting into the following IP/routing/wireless setup:
     
    4351}}}
    4452
    45 Basicaly configuring the network should not be more then setting the symlink to the correct Debian network config file and reboot. That’s it!
     53Basicaly configuring the network should not be more then setting the symlink
     54to the correct Debian network config file and reboot. That’s it!
    4655
    4756For people who want to  know more about the networking setup, keep reading. The following figure shows the DebWRT network configuration. Read below for detailed explenation. I used the same figure style as is used by OpenWRT on their network interfaces wiki page.
     
    5059
    5160= Programmable switch (et0) =
    52 The ASUS WL-500’s are equiped with a programmable switch. On the back of the router, there are 5 – 100 Mbit/s Full Duplex – ethernet RJ45 sockets. These are all connected to the programmable switch et0. This switch can be configured using the robocfg command line tool. By default the RJ45 socket with the WAN(Port 0) description are tagges as vlan100 by the switch hardware. And LAN ports 1 t/m 4 are tagged as vlan101. Tagging of ethernet packets received by the switch happens by adding a VLAN-ID to each ethernet frame transmitted on whatever port. See IEEE 802.1Q for more information on VLAN’s.
     61The ASUS WL-500’s are equiped with a programmable switch. On the back of the router, there are 5 – 100 Mbit/s Full Duplex – ethernet RJ45 sockets.
     62These are all connected to the programmable switch et0. This switch can be configured using the robocfg command line tool. By default the RJ45 socket with the WAN(Port 0) description are tagges as vlan100 by the switch hardware. And LAN ports 1 t/m 4 are tagged as vlan101. Tagging of ethernet packets received by the switch happens by adding a VLAN-ID to each ethernet frame transmitted on whatever port. See IEEE 802.1Q for more information on VLAN’s.
    5363
    5464= Receiving packets =
    55 After the tagging all packets from whatever port received are copied to the kernel (via switch internal hardware port 5) and received on eth0. Remember, packets received by eth0, are containing ethernet frames with 802.1Q VLAN-ID set. Using the VLAN support in the kernel, the kernel now knows how to separate the packets on this VLAN-ID and virtuale routes the packets to vlan eth0_wan (VLAN-ID 100) and to vlan etho_lan(VLAN-ID 101).
     65After the tagging all packets from whatever port received are copied to the kernel (via switch internal hardware port 5) and received on eth0.
     66Remember, packets received by eth0, are containing ethernet frames with 802.1Q VLAN-ID set. Using the VLAN support in the kernel, the kernel now knows how to separate the packets on this VLAN-ID and virtuale routes the packets to vlan eth0_wan (VLAN-ID 100) and to vlan etho_lan(VLAN-ID 101).
    5667
    5768= Trasmiting packets =
    58 When the kernel needs to transmit packets to the WAN or LAN, it will add the 802.1Q VLAN-ID to the ethernet frame. When packets are transmitted over eth0_wan, VLAN-ID 100 is added, when transmitted to eth0_lan, VLAN-ID 101 is added. The programmable switch receives all the packets and based on the VLAN-ID it knows to which RJ-45 ethernet port to sent the packet. (Note: based on the MAC address table, the switch knows on which LAN port it needs to transmit the packet).
     69When the kernel needs to transmit packets to the WAN or LAN, it will add the 802.1Q VLAN-ID to the ethernet frame. When packets are transmitted over eth0_wan, VLAN-ID 100 is added, when transmitted to eth0_lan, VLAN-ID 101 is added.
     70The programmable switch receives all the packets and based on the VLAN-ID it knows to which RJ-45 ethernet port to sent the packet. (Note: based on the MAC address table, the switch knows on which LAN port it needs to transmit the packet).
    5971
    6072= Init scripts and configuration files involved =