Recommended Posts

Hi All, 

 

I would like to be able to connect a VM to a tagged VLAN without the host machine being connected to that VLAN. 

 

My machine only has one NIC and all the networks I connect to are tagged VLANs associated with that NIC. 

 

If I add the tagged VLAN to the NIC I can connect the VM to that network correct however my machine is then in that network as well. 

 

Does anyone know if this is possible? I really hope that makes sense! 

 

Thanks in advance. 

Well the connection to your machines nic would have to be trunked for starters. The switch port your currently connected to is most likely access and only allows the vlan your physical nic is in.

Hi BudMan, 

 

The port that my NIC is in, is tagged in both of the VLANS. I can bring up the VLAN on my machine and connect my VM to it no problem, however I don't want my machine to be in that lan for various reasons. 

So port is trunked already and allows both, ok.

So in workstation can you tag say a vswitch like you can in esxi?

post-14624-0-13920000-1385477606.png

What virtual nic do you have setup, vmxnet3 should allow for vlan ID right on the nic

post-14624-0-76985800-1385477661.png

From a quick google with workstation it seems you need to make map it in network correctly, and you might have to uncheck deterministic or other options on the vm nic to see it in the mapping, check out this article

http://brandonjcarroll.com/blog/using-vlans-with-vmware-workstation

Hi Budman, 

 

You can't change the VLAN tagged on the vswitch like ESXi, I was hoping the same thing. 

 

I've had a look at the article but that would still put my machine in that LAN. For I've removed everything from the networking selection (unticked Internet Protocol Version 6 etc.) which looks like I can't connect to that network, and nothing from that network can connect to my machine, but the VM is working fine. I think this will work ok for now. 

 

Thank you Budman. 

Your physical nic is going to require the ability to add multiple vlan tags - as per the article, then can create different virtual networks and match them up with the specific vlans you want to run your vms on.

You might be able to get away with juts putting the tag on the virtual nic on your vm and bridging it to your physical nic that is in a different vlan.

That article shows how to run different vms under different vlans, ie more than 1 can be done. Your just needing 1 I take it - but still applies. What is the actual physical nic you have in your machine.. Does it it support the advanced features like multiple vlan tags on it?

My NIC is an Intel 82579LM and yes it does support VLAN tagging. That's how I'm currently doing it. When you add a new Tagged VLAN it created a new adaptor which needs to be enabled for you to use it via VMware workstation. 

 

I didn't have a problem getting the VM into the VLAN, the problem is I don't want my physical machine in that VLAN at all but it seems to be working correctly now. 

I think that is all you can do evoman91 - just untick the un-needed protocols and services in the properties of the virtual adapter like you said. It seems a bit of a messy way to do it though, don't you think? 

  • 1 year later...

After creating your vlan interfaces, then creating your VMware workstation bridge to the new adapters, go into the local adapter and disable ipv4 and ipv6.  Your computer will not have access via ipv4 n'or 6 to communicate on that network, but your vmware workstation will still be able to bridge over that nic to the vlan and IT has IPv4 or 6 and will function just fine.  So again... vmware workstation nic, IPv4 is left on and alone, Local PC nic that it's bridging through has NO IPv4 or 6 enabled.  Therefore, no local computer access.

This topic is now closed to further replies.
  • Popular Now

  • Posts

    • For those still looking to get a 5090 at or around MSRP, there's one on scan.co.uk for £1,874.99 its pre-order though with expected shipping date of June 27. https://www.scan.co.uk/products/nda-zotac-nvidia-geforce-rtx-5090-solid-32gb-gddr7-graphics-card
    • Kudos are due because I always expect you to jump to Microsoft's defense in the many, many, many Win11 hate posts. Thanks for holding back for once.
    • Windows 11 finally gets a small, but long-requested Windows 10 taskbar feature by Taras Buria Windows 11 turns four later this year, but some of the features that Microsoft removed during the transition remain missing to this day. However, the company is slowly but steadily restoring some of the most requested bits and pieces. The latest omission that is finally being addressed is the missing clock in the calendar flyout. Windows enthusiasts spotted the first traces of a calendar clock coming to Windows 11 in April. Now, with the latest builds released in the Dev and Beta channels a few days ago, Microsoft is officially restoring the calendar flyout clock. You can now have a bigger clock with seconds displayed, just like in Windows 10 (Microsoft tried to remove that for some reason but quickly restored it). When enabled, the clock appears with the calendar collapsed or expanded. Microsoft is not only restoring the calendar clock but also improving it. Those who do not want it can go to Settings and toggle the clock off for a cleaner look. You can customize this feature in Settings > Time & Language > Date & Time. Note that the feature is rolling out gradually, so not all insiders have access to it right now. However, you can turn it on with the ViVeTool app: Download ViveTool from GitHub and unpack the files in a convenient and easy-to-find folder. Run Command Prompt as Administrator and navigate to the folder containing the ViveTool files with the CD command. For example, if you have placed ViveTool in C:\Vive, type CD C:\Vive. Type vivetool /enable /id:42651849,48433719 and press Enter. Restart your computer. Unfortunately, the taskbar calendar remains pretty spartan in terms of features. It still does not display your agenda and does not allow creating new events. All that Windows 11 users have is a dumb calendar and a couple of buttons for the Focus Assist feature. As such, the only way to improve it is to use third-party applications. Did you miss the calendar flyout clock in Windows 11?
    • To the extent that we are talking about beta software, this article falls more in the realm of nerds sharing thoughts and tricks. I love seeing articles like this, people should very openly share what they like and dislike about the new look. We all know Apple tends to be stubborn, but maybe they still make minor tweaks to improve the readability.
  • Recent Achievements

    • Apprentice
      Wireless wookie went up a rank
      Apprentice
    • Week One Done
      bukro earned a badge
      Week One Done
    • One Year In
      Wulle earned a badge
      One Year In
    • One Month Later
      Wulle earned a badge
      One Month Later
    • One Month Later
      Simmo3D earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      611
    2. 2
      ATLien_0
      284
    3. 3
      +FloatingFatMan
      179
    4. 4
      Michael Scrip
      151
    5. 5
      Steven P.
      112
  • Tell a friend

    Love Neowin? Tell a friend!