{"id":883,"date":"2013-04-16T16:03:59","date_gmt":"2013-04-16T20:03:59","guid":{"rendered":"https:\/\/infotechguy.net\/?p=883"},"modified":"2025-02-22T13:14:21","modified_gmt":"2025-02-22T18:14:21","slug":"multiple-access-points-over-802-1q-using-openwrtpart1","status":"publish","type":"post","link":"https:\/\/infotechguy.net\/?p=883","title":{"rendered":"OpenWRT — Multiple Access Points With 802.1Q (part1)"},"content":{"rendered":"

I set out on this home project with the intent of providing wireless internet to friends and family when visiting. I wanted to provide internet without allowing any malicious clients from consuming all my bandwidth and\/or crippling my internal home network. There are many Wireless Access Points(WAP) that are capable of broadcasting multiple SSIDs. Cisco makes a few from their Aironet series, however they seem to be pretty expensive. I settled with a Netgear WNDR3700 after reading a few posts on hardforum.com<\/a> that had success running OpenWRT.<\/p>\n

OpenWRT<\/a> is an third-party firmware designed for consumer based Access Points, such as Netgear, Linksys, Dlink, etc. OpenWRT adds many additional features, including the two features I needed. Support for 802.1Q trunking and gives the ability to run multiple SSID wireless signals.<\/p>\n

Topology<\/h3>\n

\"\"<\/a>\"\"<\/a>
\n<\/p>\n

Installing OpenWRT<\/h3>\n
    \n
  1. \n

    Download OpenWRT for Netgear WNDR3700<\/h4>\n

    Visit the OpenWRT download site, here<\/a>. Download the firmware image named openwrt-ar71xx-wndr3700-squashfs-factory.img<\/li>\n

  2. \n

    Upload firmware<\/h4>\n

    Connect to the Netgear WNDR3700 using an Ethernet cable, the instructions for uploading the firmware warn against doing it over wireless.<\/li>\n

  3. \n

    Verify firmware change<\/h4>\n

    The only point of this step is to verify that the new firmware was a success. We changed the OS running from the factory Netgear firmware to OpenWRT. Visit http:\/\/192.168.1.1<\/a>, you should say the following:
    \n    \"\"<\/a><\/p>\n

    \"\"<\/a><\/p>\n

    NOTICE:<\/strong> Verify the Firmware Version.<\/em><\/li>\n<\/ol>\n

    Configure OpenWRT<\/h3>\n
      \n
    1. \n

      Configuring our 1st SSIDs<\/h4>\n

      The two(2) SSIDs<\/strong> that we will be configuring will be named secureWiFi<\/strong> and insecureWiFi<\/strong>. To do this go to the Web Configuration page of the Netgear Router, http:\/\/192.168.1.1<\/a> (or whatever you have yours is IP’d for). Click on the main Network tab, and the WiFi subtab. This will list the following WiFi SSIDs defined. On a fresh firmware install it will be named OpenWRT and there should be only a single instance of it. Click Edit next to the OpenWRT SSID, change the name of the SSID to secureWiFi<\/strong>, then click Save & Apply.<\/strong>
      \n      \"\"<\/a><\/li>\n

    2. \n

      Configuring our 2nd SSID<\/h4>\n

      We will now add an additional SSID and name it insecureWiFi. On the Netgear Router’s page, go back to the Network tab and WiFi tab. Change the SSID name from OpenWRT to insecureWiFi<\/strong>.
      \n      \"\"<\/a><\/li>\n

    3. \n

      Configuring Interfaces in OpenWRT<\/h4>\n

      For the next part, we need to configure two separate interfaces on the OpenWRT router. These two separate interfaces will physically separate the two(2) different WiFi Access Points. We will need two separate IP network segemnets as well. For this article the two(2) IP networks will be 192.168.0.0\/24<\/strong> and 192.168.1.0\/24<\/strong>. To do this, go to the Network tab, then the Interfaces subtab. Here there should already be one or two default interfaces. Click the button for Add New Interface(s). On the next page, Fill out the Name of the New Interface, “secure”<\/strong>. Check the box for “Create a bridge over multiple interfaces”<\/strong>. Under the section “Cover the following interfaces”<\/strong> Check of the Wireless Network “OpenWRT”<\/strong> or whatever you called yours that you would like to be associated with this “secure” interface” we are creating. The last part is to check the box for “Custom Interface”<\/strong> and add the label “eth1.100”<\/strong>. Now the eth1<\/strong> is the physical interface of the WAN port, see diagram<\/a>. The “.100”<\/strong> means add a virtual interface or VLAN interface with VLAN ID (VID) 100.<\/strong><\/p>\n

      \"\"<\/a><\/li>\n

    4. \n

      802.1Q Trunking<\/h4>\n

      Now have to set the trunk port on the Netgear Access-point. Browse to the Network tab<\/strong> and then to the Switch subtab<\/strong>. Here You’ll see some information regrading the ports on the Netgear router and the VLAN IDs. With a new install there should be only VLAN ID 1 and it will be untagged on every port. This is the native VLAN, which pretty much means it is the only VLAN that will always be untagged for every interface, see here<\/a>.<\/p>\n

      Ok so Click Add button to add a new row. In the new row that appears type in 100<\/strong> in for the VLAN ID. Make sure every port number, except port 5 is off. Port 5 is tagged.<\/strong> Port 5 = WAN port <\/strong>on the back of the Netgear device. Perform this step again for our Guest\/Insecure VLAN 110.<\/strong> Last step is to ensure the checkbox is checked for Enable VLAN Functionality.<\/strong><\/p>\n

      \"\"<\/a><\/p>\n

      NOTICE:<\/strong> We have just created one end of a trunk link. The Netgear device will now tag Frames with VLAN ID 100 and 110 out Port5\/WAN port.<\/em><\/li>\n

    5. \n

      Optional: Set Device IP for Insecure Network<\/h4>\n

      As of now we have successfully configured our Layer 2 network. However, if we were to connect to our Guest\/Insecure network we would not be able to reach our Netgear device from an IP perspective. Meaning guests could not access the Netgear configuration page. This is only to make troubleshooting in the next section easier, you can remove it later if you are worried about security.<\/p>\n

      So browse to the Network Tab<\/strong>, then to the Interfaces<\/strong> subtab. Here you should see another subtab from earlier steps that shows our insecure interface. Click on that and there will be a Common Configuration <\/strong>section, with Status, Protocol, etc. Change the protocol to static address<\/strong>. There is an option for “Unmanaged” that would effectively mean that you cannot access the management part of the Netgear device through this interface. Fill in the IP information for our 192.168.1.0\/24 network<\/strong>.<\/p>\n

      \"\"<\/a><\/li>\n

    6. \n

      Save & Apply<\/h4>\n

      Go ahead and hit the Save & Apply button.<\/li>\n<\/ol>\n

      Switch Configuration<\/h3>\n
        \n
      1. \n

        Physical Configuration<\/h4>\n

        On your VLAN capable switch, choose an interface that will be used as a trunk interface. For this tutorial I am using a PowerConnect 5324 with 24 Gigabit ports. I will be using port 20 for the trunk between our Netgear device and the PoweConnect switch. I also have another Trunk port, port 24 which is a trunk between my Linux Firewall and the PowerConnect switch.<\/p>\n

        Go ahead and plug in the WAN on the Netgear AP to the trunk port on the switch that you chose.<\/li>\n

      2. \n

        Configuring the Switch<\/h4>\n

        Terminal into your switch. Now depending on what manufacture you have the commands may be a little different. But, really all we need to accomplish is add our two VLANs (100 & 110) to the VLAN database, and change the mode of the switch interface you picked to a trunk interface.<\/li>\n

      3. \n

        Adding to the VLAN Database<\/h4>\n

        On the PowerConnect:<\/p>\n

        SW1 configure\r\nSW1(config)vlan database\r\nSW1(config-vlan)vlan 100\r\nvlan 110\r\nSW1(config-vlan) exit\r\nSW1(config)\r\n<\/pre>\n
        Assign VLAN Names:<\/p>\n
        SW1 configure\r\nSW1(config) interface vlan 100<\r\nW1(config-if) name SecureVLAN\r\nSW1(config-if) exit\r\nSW1(config) interface vlan 110\r\nSW1(config-if) name InsecureVLAN\r\nSW1(config-if) exit\r\nSW1(config) exit<\/pre>\n<\/li>\n
      4. \n
        Assigning Trunk Ports<\/h4>\n
        Using interface g20<\/strong> as Trunk port<\/em><\/p>\n
        On the PowerConnect:<\/p>\n
        SW1 configure\r\nSW1(config) interface ethernet g20\r\nSW1(config-if) switchport mode trunk\r\n switchport trunk allowed 100\r\n switchport trunk allowed 110\r\n<\/pre>\n<\/li>\n
      5. \n
        Configuring Access VLAN Ports<\/h4>\n
        Access Ports are interfaces that 99% of the time are connected directly to an end user device, such as a computer or server. Sometimes referred to untagged ports, etc. These next steps will be heavliy relative to your physical set up. For me, I know on my PowerConnect 24-port switch that ports 1-19 are secure and trusted. These ports go directly to network drops in my house so I know they are secure. The remaining ports 20-24 are untrusted and insecure, at least I left them open to be used that way. Remember Your Scenario May Be Different.<\/p>\n
        Assigning Access Ports on the PowerConnect:<\/p>\n
        SW1 configure\r\nSW1(config) interface range ethernet g1-19\r\n<\/pre>\n
        NOTICE:<\/strong> This allows me to configure multiple interfaces within a range.<\/em><\/p>\n
        SW1(config-if) switchport access vlan 100<\/pre>\n
        NOTICE:<\/strong> We don’t do the same thing for our guest network or insecure network. There is no point as none of my network drops in my house I want on the insecure network.<\/em><\/li>\n<\/ol>\n
        That’s it for the first part!<\/h2>\n
        We have a trunk link going from our PowerConnect Switch to our Netgear Access Point. Wahoo!<\/p>\n
        See part 1<\/a>, part 2<\/a><\/h4>\n