@SSgtFodder 

Not sure whether the mentioned devices can work with the VLAN. Please contact the related support team regarding their VLAN capability.

Follow the VLAN guide and config:

How to Set Up VLAN Interface on the Omada Router

At least this works with a full Omada setup.

IPsec site-to-site requires the public IP addresses on both sites. Any VPN service requires a public IP. If you don't know if you have a public IP or not, contact your ISP regarding that.

  @Clive_A Both the router, ER605 and the TP Link TL-WA3001 are VLAN capable. The rest of the basic switches are just that, simple non VLAN enabled. 

I didn't mention before but I'm not using an Omada controller hardware or software; just the basic web interfaces.

On the ER605 -> Network -> VLAN -> VLAN List ->--- vLan1 and vLan2,,,, are ID and VLAN 1 and 2 respectively

vLan1 has ports 2-5 (untag) and vLan2 has ports 2-5 (Tag)

On Network -> VLAN -> Ports -> Ports 2-5 all have PVID set to 1

This way all untaged devices coming into the router are automatically assigned to vLan1

The only devices on vLan2 will be connecting to the network over the Wireless on the SSID-vLan2 of the WA3001

In the diagram on your link, most say PVID-None,,, How? The ER605 only allows the ports to be labeled by selecting an ID and "none" is not in the dropdown list.

However, from the config page for Omada I'm (deducing) that where the web page askes fore the "MODE" as "normal" or "bridged" that is the same as the Omada where it says "VLAN TYPE" as "single" or "multiple" and provide a situation for 2 vLans to share a subnet or IP range.

Yes, the ER605 and the WA3001 will both be edge devices with internet IPs

  @SSgtFodder 

SSgtFodder wrote

  @Clive_A Both the router, ER605 and the TP Link TL-WA3001 are VLAN capable. The rest of the basic switches are just that, simple non VLAN enabled. 

 

I didn't mention before but I'm not using an Omada controller hardware or software; just the basic web interfaces.

 

On the ER605 -> Network -> VLAN -> VLAN List ->--- vLan1 and vLan2,,,, are ID and VLAN 1 and 2 respectively

vLan1 has ports 2-5 (untag) and vLan2 has ports 2-5 (Tag)

On Network -> VLAN -> Ports -> Ports 2-5 all have PVID set to 1

This way all untaged devices coming into the router are automatically assigned to vLan1

 

The only devices on vLan2 will be connecting to the network over the Wireless on the SSID-vLan2 of the WA3001

 

In the diagram on your link, most say PVID-None,,, How? The ER605 only allows the ports to be labeled by selecting an ID and "none" is not in the dropdown list.

However, from the config page for Omada I'm (deducing) that where the web page askes fore the "MODE" as "normal" or "bridged" that is the same as the Omada where it says "VLAN TYPE" as "single" or "multiple" and provide a situation for 2 vLans to share a subnet or IP range.

 

 

Yes, the ER605 and the WA3001 will both be edge devices with internet IPs

I have explained what none is in the guide, instead of asking how, but really calm yourself down and read it carefully. This is not gonna be easy for any new users.

If you have questions about the VLAN, please research the forum where I have guides and discussions about VLAN. Or try Wikipedia.

As you are not using the Omada series for the rest of the other parts, I don't have any idea about whether they work with the VLAN or not, or help on how to configure VLAN on them.

  @Clive_A Ok Clive, listen up. Because seriously, you need a little bit of check here. I appreciate that I've come here looking for help and there are a lot of things I'm personally putting in check because I’m trying to avoid purchasing additional equipment and solve the problem with the exceptionally limited TP-Link products.

For an analogy: I'm used to dealing with bank vaults and in this case I'm dealing with a shed. So I've got a simple TP Link lock for a shed. Because of the extremely poor and limited documentation, I've got questions how to use this very simplified device, and the guy (you) who responded to my questions is acting condescending and disrespectful.

Two of your comments are inappropriate. So I'm giving you a little feedback so you might work on your personal skills. The comments, " really calm yourself down and read it carefully" and "This is not gonna be easy for any new users".

Telling me to calm down as if I'm acting like a hysterical lunatic is quite a defensive act, given it is YOUR mistake in a document which caused the confusion to which I was asking for clarification. I will admit I missed your little corrective note at the bottom. However, even though you provided that, there is nothing associating it with the actual issue, such as a footnote marking or asterisk * mark which would denote there is an additional comment. And YES, it is a mistake in your image. In the image you should have put a 1. You could have then added a * and at the bottom noted the additional information that 1 is also the default. Instead you’ve put the invalid value of “none”. You then corrected it at the bottom to say it should be a 1 but added the additional information that 1 is the default to cover up the mistake. Now you’re telling me to calm down, which is ironic since I’m very calmly asking questions and you’re panicked because I tripped on your mistake.

The Second comment is assumptively disrespectful. It’s true, it will be difficult for any new user to use new equipment, especially since I’m used to working with fully functional routers. However, it's not because I don't know about vlans, it's because of extremely limited functionality of the product and poor if documentation. I cut my teeth building vlans using Bay Network ATM routers to build out the U.S Air Force network for the entire South Korean peninsula back in 1995. We’re talking the full build out and interconnection of networks covering entire Military bases, the size cities. Those are not MANs, not Lans. Plus all the little satellite locations.

Now, from this you can deduce, no, you can’t hep me. You have neither the temperament nor the skill. You’ve also admitted you don’t have the familiarity with all of the TP Link products I’m discussing here. As someone who has over 7000 posts over 2 years, I’m going to presume you  work for TP Link albeit limited to business solutions and not residential/consumer. Otherwise, the next likely option would be that you are someone who merely loves to act like “Nick Burns, the Computer Guy”. So, on the chance you do work for TP Link, you might want to talk to them about using the same language on different interfaces. As pointed out in the previous post, I had to figure out that the native interface of the ER605 uses the terms "MODE" with options  of "normal" or "bridged", the Omada uses the terms  "VLAN TYPE" with "single" or "multiple" for the exact same functions.

My final suggestion for you as a "business solutions answer guy" and based on your limited skills of only being familiar with Omada based control of the business level devices: You should either familiarize yourself with the native interfaces of the business products, OR You should discuss with the forum administrators the ability to split the “Business Community” into more groups. Splitting the groups would allow you to specialize only in Omada controlled questions and not run into the areas you are not familiar. There are MANY small businesses that will rely on using only the native interface of the products and have no interest in the Omada management system. Additionally, you may even want to split that into another group that is the gray area between consumer and business, typically referred to as the “Prosumer”. Such as IT guys doing complex IT home solutions. Since, I’m helping a family member with a complex home solution, he has consumer products but is trying to enhance his network with the additional functions only found in the business level product if the ER605. Thus the reason I have questions on both.

  @SSgtFodder 

SSgtFodder wrote

  @Clive_A Ok Clive, listen up. Because seriously, you need a little bit of check here. I appreciate that I've come here looking for help and there are a lot of things I'm personally putting in check because I’m trying to avoid purchasing additional equipment and solve the problem with the exceptionally limited TP-Link products.

 

For an analogy: I'm used to dealing with bank vaults and in this case I'm dealing with a shed. So I've got a simple TP Link lock for a shed. Because of the extremely poor and limited documentation, I've got questions how to use this very simplified device, and the guy (you) who responded to my questions is acting condescending and disrespectful.

 

Two of your comments are inappropriate. So I'm giving you a little feedback so you might work on your personal skills. The comments, " really calm yourself down and read it carefully" and "This is not gonna be easy for any new users".

 

Telling me to calm down as if I'm acting like a hysterical lunatic is quite a defensive act, given it is YOUR mistake in a document which caused the confusion to which I was asking for clarification. I will admit I missed your little corrective note at the bottom. However, even though you provided that, there is nothing associating it with the actual issue, such as a footnote marking or asterisk * mark which would denote there is an additional comment. And YES, it is a mistake in your image. In the image you should have put a 1. You could have then added a * and at the bottom noted the additional information that 1 is also the default. Instead you’ve put the invalid value of “none”. You then corrected it at the bottom to say it should be a 1 but added the additional information that 1 is the default to cover up the mistake. Now you’re telling me to calm down, which is ironic since I’m very calmly asking questions and you’re panicked because I tripped on your mistake.

 

The Second comment is assumptively disrespectful. It’s true, it will be difficult for any new user to use new equipment, especially since I’m used to working with fully functional routers. However, it's not because I don't know about vlans, it's because of extremely limited functionality of the product and poor if documentation. I cut my teeth building vlans using Bay Network ATM routers to build out the U.S Air Force network for the entire South Korean peninsula back in 1995. We’re talking the full build out and interconnection of networks covering entire Military bases, the size cities. Those are not MANs, not Lans. Plus all the little satellite locations.

 

Now, from this you can deduce, no, you can’t hep me. You have neither the temperament nor the skill. You’ve also admitted you don’t have the familiarity with all of the TP Link products I’m discussing here. As someone who has over 7000 posts over 2 years, I’m going to presume you  work for TP Link albeit limited to business solutions and not residential/consumer. Otherwise, the next likely option would be that you are someone who merely loves to act like “Nick Burns, the Computer Guy”. So, on the chance you do work for TP Link, you might want to talk to them about using the same language on different interfaces. As pointed out in the previous post, I had to figure out that the native interface of the ER605 uses the terms "MODE" with options  of "normal" or "bridged", the Omada uses the terms  "VLAN TYPE" with "single" or "multiple" for the exact same functions.

 

My final suggestion for you as a "business solutions answer guy" and based on your limited skills of only being familiar with Omada based control of the business level devices: You should either familiarize yourself with the native interfaces of the business products, OR You should discuss with the forum administrators the ability to split the “Business Community” into more groups. Splitting the groups would allow you to specialize only in Omada controlled questions and not run into the areas you are not familiar. There are MANY small businesses that will rely on using only the native interface of the products and have no interest in the Omada management system. Additionally, you may even want to split that into another group that is the gray area between consumer and business, typically referred to as the “Prosumer”. Such as IT guys doing complex IT home solutions. Since, I’m helping a family member with a complex home solution, he has consumer products but is trying to enhance his network with the additional functions only found in the business level product if the ER605. Thus the reason I have questions on both.

I am only taking care of the business products. Which is ER605 in this context. Other models are either home products or not current business-grade products. I am not required to familiarize myself with them as they are not under my reign.

The current setup and guides on the forum are based on the Omada product line.

For the other models, I don't have a device active on my hands. And they belong to different departments.

If you seek a full setup of Omada, these guides on the forum would offer you a basic concept on how to configure the most popular features.

The forum is only providing supplementary documentation to the FAQ, which is available on the official website.

VLAN is a complex concept and that's why I created guides on understanding the VLAN. You don't have a specific question on the VLAN, so I cannot lecture you on the VLAN without your reading on basic stuff. The questions you've asked are answered in the hyperlink I provided. Some of your terms are not used by us so with some readings you might learn about our system and wording on VLAN.

Side note in the guides have written about the details and what "none" means in PVID.

I specifically left it as none for starters, which they think is strange when you have the following devices on a different VLAN but the device itself is on PVID 1.

There is a difference between tagged and untagged. See that all the untagged are properly assigned with the PVID. Also, PVID and VLAN ID are different.

You don't appreciate the diagram. That's fine. But don't mistake what I am doing. These VLAN guides I made are working together to help people understand a complete VLAN for a regular network.

You are too sensitive about that "VLAN is not easy...". I am just saying that it's complicated and might need some time to digest the guides.