Changes between Version 7 and Version 8 of BridgedNetwork


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

line breaks added, to make further changes more clear

Legend:

Unmodified
Added
Removed
Modified
  • BridgedNetwork

    v7 v8  
    5454to the correct Debian network config file and reboot. That’s it!
    5555
    56 For 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.
     56For people who want to  know more about the networking setup, keep reading.
     57The following figure shows the DebWRT network configuration.
     58Read below for detailed explenation. I used the same figure style as
     59is used by OpenWRT on their network interfaces wiki page.
    5760
    5861[[Image(debwrt-network-config1.png)]]
    5962
    6063= Programmable switch (et0) =
    61 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.
    62 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.
     64The ASUS WL-500’s are equiped with a programmable switch. On the back of
     65the router, there are 5 – 100 Mbit/s Full Duplex – ethernet RJ45 sockets.
     66These are all connected to the programmable switch et0. This switch can be
     67configured using the robocfg command line tool.
     68By default the RJ45 socket with the WAN(Port 0) description are tagges as
     69vlan100 by the switch hardware. And LAN ports 1 t/m 4 are tagged as vlan101.
     70Tagging of ethernet packets received by the switch happens by adding a
     71VLAN-ID to each ethernet frame transmitted on whatever port.
     72See IEEE 802.1Q for more information on VLAN’s.
    6373
    6474= Receiving packets =
    65 After the tagging all packets from whatever port received are copied to the kernel (via switch internal hardware port 5) and received on eth0.
    66 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).
     75After the tagging all packets from whatever port received are copied to
     76the kernel (via switch internal hardware port 5) and received on eth0.
     77Remember, packets received by eth0, are containing ethernet frames with
     78802.1Q VLAN-ID set.
     79Using the VLAN support in the kernel, the kernel now knows how
     80to separate the packets on this VLAN-ID and virtuale routes
     81the packets to vlan eth0_wan (VLAN-ID 100)
     82and to vlan etho_lan(VLAN-ID 101).
    6783
    6884= Trasmiting packets =
    69 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.
    70 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).
     85When the kernel needs to transmit packets to the WAN or LAN,
     86it will add the 802.1Q VLAN-ID to the ethernet frame.
     87When packets are transmitted over eth0_wan, VLAN-ID 100 is added,
     88when transmitted to eth0_lan, VLAN-ID 101 is added.
     89The programmable switch receives all the packets and based on the VLAN-ID
     90it knows to which RJ-45 ethernet port to sent the packet.
     91(Note: based on the MAC address table, the switch knows on which
     92LAN port it needs to transmit the packet).
    7193
    7294= Init scripts and configuration files involved =