Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
docs:guide-user:virtualization:virtualbox-advanced [2020/05/04 11:32] – someothertimedocs:guide-user:virtualization:virtualbox-advanced [2020/08/15 16:11] (current) – [Resources] add flink re: 80211 bridging issues someothertime
Line 5: Line 5:
 This guide extends the basic VirtualBox HowTo with broader setup recommendations, samples and common "gotcha-s". This guide extends the basic VirtualBox HowTo with broader setup recommendations, samples and common "gotcha-s".
  
 +NOTE: Use a wired virtualbox host (unless you are really confident with virtualbox i.e. 80211 bridging issues ).
 ===== Prerequisite Concepts ===== ===== Prerequisite Concepts =====
 ==== x86_64 Basics ==== ==== x86_64 Basics ====
Line 147: Line 148:
 VBoxManage modifyvm "$VMNAME" --nicbandwidthgroup1 Limitlan #assign to nic1 VBoxManage modifyvm "$VMNAME" --nicbandwidthgroup1 Limitlan #assign to nic1
 VBoxManage modifyvm "$VMNAME" --nicbandwidthgroup2 Limitwan #assign to nic2 VBoxManage modifyvm "$VMNAME" --nicbandwidthgroup2 Limitwan #assign to nic2
 +</code>
 +
 +
 +=== Tagging for VM's  ===
 +
 +Note: example ip link is non-permanent... see your distro for appropriate place to configure your host nic for a vlan.
 +
 +You can use a single cable as a "trunk". This essentially turns your wired link into a managed switch as you will tag VLAN per vm upstream on the wired link.
 +
 +This can be used for clients... with openwrt on a "real router" running several vlans over a single LAN port. Or you could use this method for an OpenWrtVM... tag several of it's interfaces outside of the guest software... "mimicking" a managed switch.
 +
 +
 +This example shows clientVM's to an upstream OpenWrt router.
 +<code bash>
 +
 +######################################################### Step1 ONHOST
 +NIC="enp0s25"
 +ip link add link $NIC name $NIC.50 type vlan id 50
 +ip link set dev $NIC.50 up
 +
 +######################################################### Step2
 +In VirtualBox change bridge for a VM to interface NIC.50
 +
 +######################################################### Step3 In Openwrt
 +#-Go to switch... add vlan 50 tagged on same port as pc/server + cpu1
 +#-Go to interfaces... add interface... NAME + INTERFACE:ethNcpu.50 + IP:192.168.50.1 etc. etc.
 +
 +
 +################################## debugging on host
 +#ip -d link show $NIC.50
 +#ip link delete $NIC.50
 +#tcpdump -nnei $NIC -vvv
 +
 </code> </code>
  
Line 288: Line 322:
 [5] Image filesystems and alteration in detail [5] Image filesystems and alteration in detail
 [[https://quantumwarp.com/kb/articles/25-dsl-broadband/899-run-lede-as-a-virtualbox-virtual-machine]] [[https://quantumwarp.com/kb/articles/25-dsl-broadband/899-run-lede-as-a-virtualbox-virtual-machine]]
 +
 +[7] forum re: macos 80211 bridging issues
 +[[https://forum.openwrt.org/t/virtualbox-openwrt-works-fine-but-clients-connecting-to-vm-router-have-no-internet/71398]]
 +
  
  • Last modified: 2020/05/04 11:32
  • by someothertime