Greetings,
> Each switch you define in vm.conf is isolated by itself (and shows up as
> a veb device on the host). So if you want to keep your VMs isolated,
> you don't need to worry about VLANs at the VM level.
Thanks, that's exactly what I had suspected. In my case, the default
gateway for the
Greetings,
> You don't have the vlan tag/trunk/id inside of the VM.
> On the host you have to "terminate" the vlan and map them to a veb or
> veb/vport.
> As was mentioned in another post, vport isn't mandatory, you can also do
> with just veb.
OK, so if I understand correctly, vlans are used the
On Wed, Jun 12, 2024 at 09:22:10PM -0700, jrmu wrote:
> > TL,DR: add the VLAN interface to the veb device configured in /etc/vm.conf
> >
> > It depends a bit on the role you want your vmm host to play in that
> > network. Everything written below refers to the host, unless otherwise
> > specif
You don't have the vlan tag/trunk/id inside of the VM.
On the host you have to "terminate" the vlan and map them to a veb or
veb/vport.
As was mentioned in another post, vport isn't mandatory, you can also do
with just veb.
# /etc.vm.conf
switch "uplink_vlan800" {
interface veb800
}
s
I tried the previously suggested setups with veb(4) but couldn't get it
to work, so I decided to start with simpler configurations to at least
figure out how to use vlan(4).
These experiments, though, have also failed. I'm attempting to use vlan
with vmm but making a mistake somewhere. Networking
I attempted to follow the advice posted, but perhaps misunderstood somewhere.
I attempted to assign the IP address to vlan0 inside the virtual machine
(104.167.241.51). Needless to say this did not work, but I am not quite sure
what the correct configuration is. Any help would be greatly welcome:
> TL,DR: add the VLAN interface to the veb device configured in /etc/vm.conf
>
> It depends a bit on the role you want your vmm host to play in that
> network. Everything written below refers to the host, unless otherwise
> specified.
Thanks. I think I follow the basic idea of the setup.
Howev
One more question I forgot to ask: How do you get the virtual machines
to use your vport800/vport880 interfaces? From what I see in vm.conf(5),
the virtual machines are required to use tap(4) interfaces.
--
jrmu
IRCNow (https://ircnow.org)
signature.asc
Description: PGP signature
Thanks for your help. I think I follow your logic.
If I understand correctly, each virtual machine needs its own vlan and
its own virtual switch? So the host running vmm needs to create N number
of vlans for its interface (in your example mcx0) for each of the N
vitrual machines, and we need to cr
On Tue, Jun 11, 2024 at 09:25:31AM +0100, Zé Loff wrote:
> On Mon, Jun 10, 2024 at 12:11:45PM -0700, jrmu wrote:
> > How can I configure vmm to use vlans for virtual machines? I saw
> > openbsd.amsterdam * use this, but I am not sure how to replicate it.
> >
> > As I understand it, vmm creates a
On Mon, Jun 10, 2024 at 12:11:45PM -0700, jrmu wrote:
> How can I configure vmm to use vlans for virtual machines? I saw
> openbsd.amsterdam * use this, but I am not sure how to replicate it.
>
> As I understand it, vmm creates a tap(4) interface for each virtual machine,
> and all tap interfaces
Hi,
You would have to do something like the following.
In /etc/vm.conf you configure multiple switches:
switch "uplink_vlan800" {
interface veb800
}
switch "uplink_vlan880" {
interface veb880
For /etc/hostname.if you have to go through the config per VLAN.
The actual interface
How can I configure vmm to use vlans for virtual machines? I saw
openbsd.amsterdam * use this, but I am not sure how to replicate it.
As I understand it, vmm creates a tap(4) interface for each virtual machine,
and all tap interfaces are then placed inside the switch defined in vm.conf,
which in
13 matches
Mail list logo
