VBox + ASA 5505

[Waynerd]

Hi,

I want to create a little testing environment, so I got a spare ASA 5505 and allready have my MacBook Pro with Mountain Lion on it. The ASA is correctly configured(I used it at a customer until the new one arrived)

I have VirtualBox installed with various servers and 2 clients, and want to work with separate Vlans to get this testing environment as real as possible(i still have much to learn - right now i focus on OpenLDAP and ASA ACL's)

on the Mac:
The Vlan Tags are working - i get the correct DHCP IP Address on the Mac(on the Vlans where its configured)
ip_forwaring is activated

VirtualBox:
I could select the bridged Vlans for each network interface.
When i start a Virtual Windows Client he gets the correct IP Address and can reach the mac but not the ASA (ipconfig /renew wont work). Also when i start a Virtual Client which is in the ADMIN Vlan and have all rights i can ping the Mac but not the ASA.

Wireshark:
"1642","1424.381718000","CadmusCo_b1:96:ee","Broadcast","ARP","42","Who has 172.28.19.1? Tell 172.28.19.129"
... tomorrow i can send the image, today it won't work

Any advice how i can get Vlans on VirtualBox working so i can make use of ASA access-list would be nice.
I think there is a problem on the MAC so he wont forward the traffic.

Best Regards,
Peter

[BillG]

If you are using bridged networking, your problem has nothing to do with the host OS. With bridged networking the guest behaves just like any other machine on the network. Traffic which is addressed to a guest goes to the guest and traffic addressed to the host goes to the host. Traffic addressed to a guest is never seen by the host OS, so it is not the Mac causing the problem.

Whether the guest can handle VLANs is a different matter. I have never really tried it so I really have no idea. Hyper-V can but I really don't know about VirtualBox or Virtual PC. I always use standard IP addressing, one subnet per network.

[Waynerd]

I think it has something to do with Vlan tagging/stripping.
I already tried to use other network adapter like PCnet FAST III or Paravirtualized Network. Also installing vlan on the client to assign there a Tag. Still the same problem.