Let me first not get your hopes up, I have never configured a vSphere Distributed Switch I use the free portion of ESXI. I have waited to see if anyone more qualified would answer your posts.
I am going to make an assumption that you do not have a need to physically separate your lan’s you only need to do this virtually. I believe the first step would be to establish communication via one vlan to the ClearOS vm and the rest should hopefully fall into place. I do not know how to configure your physical switch and regrettably in the world where everyone making a Layer 2 and above switch seems to run their own show in the hardware world. Now you may ask where vDS fits in all this, well it does not for now best to get a handle on you equipment. I am going to describe the steps that are required to have proper communication and you will be required to find the right configuration parameters for your equipment. Let say we attempted to connect a PC to your ClearOS vm Lan adapter:
PC < -- > stream frames not tagged < -- > Physical Switch (i.e. Access Port 1) configure the port to initiate tagging on the stream frames to (i.e. vlan 100), note configuration must be set to remove tags on the way back to the pc < -- > Configure the Physical Switch to create a Trunk, may or may not be required to configure a group? Must accept frames that are tagged for vlan 100 from Port 1, exit via (i.e. Access via Port 2), note trunk configuration should not remove tags on exiting the switch < -- > ESXI Physical Adapter (i.e. vmnic0) frames are still tagged < -- > ESXI Standard vSwitch0 frames are tagged, configure new VMKernel Group Name vlan100 to use VLAN ID: 100, tags will automatically be removed to frames exiting to the vm adapter card and tagged on the way back < -- > ClearOS vm adapter card configured to use VMKernel Group vlan100, stream frames are not tagged.
I made another assumption that we are going to use a Trunk between the Physical Switch and the ESXI Server. You could use a port without trunking but keep the logic consistent to a Trunk you must configure the port to not remove the tags when you exit the Switch with the frames on port 2. I noticed that you have a Layer 3 physical switch do not use the routing capabilities of your switch in other words stick to the Layer 2 capabilities for your configuration. I do not recall changing the network policy on my ESXI Switch, I recently built an ESXI 6 server connected the Trunk and everything worked out of the box. In regards to which lan adapter to use from your CLearOS vm, if you are not sure let me know we will have to track down the mac address from your vm adapters in the CLearOS server.
If you ping the ClearOS box after all this we are half there.
The GPG keys listed for the repository are already installed but they are not correct for this package. ClearOS Community release 6.5.0 (Final)
Maybe someone can give me a hint on how to proceed?
"Users of Community edition will have a 30-day window to upgrade to Home or Business version"
I want to first say that do not wish to sound like I am attempting to nickel and dime the ClearOS product line but I want to make sure that I have my facts right.
Definitely a 30-day window to upgrade to a paid version is a shift of direction for ClearOS and may I say ClarkConnect. I have looked at the release notes and cannot reconcile the above statement I could only find: https://tracker.clearos.com/view.php?id=2111 but the summary talks about a 30-day countdown support.
The 30-day countdown support, is that the same as the 30-day window to upgrade?
I have not changes that particular setting but my wife uses SOGO configured for a different language and that setting seems to hold. Have you looked at your SOGO log? My instructions is fairly old, have you made any changes to the installation procedure?
Yes I do have multiple VM’s running in ESXi including Gateways setup using PPPoE.
In the ESXI world and I am assuming all Virtualisation software have the same approach: the hardware becomes the responsibility of the virtualisation software including the network cards except if you configure your device in passthrough mode.
Now I going to muddy the water a little bit, you can run your setup using one single network card to do all the networking same as what ClearOS allows, network topologies can be complex and many approaches exist to provide your request. I am going to provide what I believe to be the simplest approach and assuming that you have multiple network cards and all are ESXI compliant.
The 101 approach would be to create one ESXI Virtual Switches for each network card that you have and attach it: two networks would equate to building two vSwitch: let say vSwitch0 and vSwitch1. Then all that is left to do is associate the VM network card to the appropriate vSwitch.