Hello everyone.  I am trying to setup a Rocket M2 to act as an internet gateway.    I have run across the article that talks about the need for setting up a managed switch to split off the single ethernet port on the M2 using VLANS.  I have the common port set to tagged on my vlan for WAN.  It is eth0.3 on the M2 (1 is the default vlan on the Procurve I have so I found how to change it to 3).  The port on the switch to connect to the internet source is tagged on vlan 3, no tagging on any other vlan.  The LAN port eth0 is untagged on the default VLAN (1).  

In sanity testing I have verified that I can get an IP address from the rocket on my default vlan and not from my internet source.  This leads me to believe the vlan config is correct.

I am not having luck on the WAN port though.  It is on VLAN 3.  I have tried to let DHCP issue it an IP address.  I never see it send the request to the DHCP server.  I have verified this by tailing the syslog on my dhcp server and port monitor the port on the switch.  I have tried manually assigning the WAN port an IP address on the same subnet as the internet source.  I can not ping the gateway address.  Watching the monitor port does not show the pings going out the port.  This leads me to believe that the M2 is not using eth0.3.  When manually assigned, I do show the default GW to be my gateway to the internet source.

Other documentation I found on the forum says to disable WAN, put LAN on the same subnet as the internet source, set the default gateway, disable the DHCP server, check the gateway box (that is in the WAN section), and reboot. The documentation does not say anything about vlans.   I tried that earlier and had no luck.

First question,  am I going down the totally wrong path here or do I have something setup wrong on the M2?

The Denton County Amateur Radio Club is starting on MESH as a project and internet access is a starting point.  I will be adding a proxy server later to deal with content issues.

73 and thank you,

Guy

KC5GOI

This sounds like a switch configuration issue not routing the vlan you have configured or not in tagging it later.

Your internet needs to be connected to the same vlan as what's used for the mesh node (default of 1)

http://www.hp.com/rnd/support/config_examples/primary_vlan.pdf

you can change the primary vlan on the switch.

it boils down to (by default which you have changed)

tagged vlan 1 out of Ubiquit node = wan

You need to untag it and treat it as the parent vlan on the port you connect to your access network.

im not an expert at procure switches but I would assume the easiest setup should be leave parent vlan the same across the board and primary vlan,  set the switch to expect vlan 1 to be tagged on the port with the Ubiquiti node and add a 2nd vlan (such as 10) as in tagged on that same port to be used for local users.