connecting host and vm true different vlan connections

[whitewater]

I would like to know if its possible to connect both the host and the vm machine with different vlan connections. i've been trying for days now and have read all support topics but nothing seems to help. Both vlan connections are working fine, my guess is that its a virtualbox setting some where. But first a litle explanation of the setup and why.

since a couple of weeks i have 2 separate internet connections, both have there own router with dhcp enabled, and all the devices are connected true a 24 poort switch. both internet connections are separated by vlans installed on the switch. So far so good, both routers are connected to the switch and i manualy added poorts to use within the vlan. now for the problem.

Because one of the connections is mainly used the play online with a xbox , playstation or a wii-u, its a lot of work to change settings within this connection. you first have to disconnect the console , then plugin a laptop and change and test the settings. This is the reason why i would like to have a virtual machine connected with the gamer vlan.

because there is a bug in the firmware of the switch i already installaed a windowx xp virtal machine, and tried to use this one., i installed the intel nic, and changed the vlan settings in the properties of the nic. after choosing vlan 2 ( gamer ) the machine is trying to get a ip adres, but fails and always gets a 169.254.... adres. when i remove the vlan settings and reset the connection it all works fine.



i hope that my explanation is clear enough , and that someone can help me

router home vlan router rt-n66u
192.168.2.1
255.255.255.0

router gamer vlan rv082
168.168.1.1
255.255.255.0
switchs rw2024
192.1682.2

i hope that my explanation is clear enough , and that someone can help me

[noteirak]

I assume you use bridging?
I would do a packet sniffing and see if everything gets tagged properly.

[whitewater]

yes its a bridged connection. I tried to run different packet sniffing programs but none of them gave any results. I guess this is because the nic does not the right ip adres but a 169.254.....

any more ideas?

[noteirak]

There is always a result to packet sniffing :
- Error because no packet is sent
- Error because the wrong packets are sent
- Success because the proper packets are sent

In any case, each means something specific. I would expect to see a DHCP request with the good VLAN tag on the packet at least. You should do the packet sniffing in the guest and the host.

[whitewater]

finaly solved the problem about a hour ago. It was a router/switch vlan problem. After reading some more information about trunk, and access vlan settings and setting it up again, the trick was to make the port trunk in stead of access, i also hard wired the network port of the host into the vlan, but im not sure if this is the solution. . Now my virtual xp machine has two network connections, and they both get different adresses from the vlans

thanks for your help !