{"id":1762,"date":"2025-12-25T11:51:18","date_gmt":"2025-12-25T17:51:18","guid":{"rendered":"https:\/\/zewwy.ca\/?p=1762"},"modified":"2025-12-26T00:29:08","modified_gmt":"2025-12-26T06:29:08","slug":"wireless-hyper-v-host","status":"publish","type":"post","link":"https:\/\/zewwy.ca\/index.php\/2025\/12\/25\/wireless-hyper-v-host\/","title":{"rendered":"Wireless Hyper-V Host"},"content":{"rendered":"

<\/span>Back Story<\/span><\/h1>\n

Now a while back I wrote a blog post about creating a wireless ESXi hypervisor<\/a>. A lot of lessons learnt, so why would I attempt this again? *ASMR* Cause you have an idea…. Sigh these usually end up bad… but here we go!!<\/p>\n

Where did this idea come from, if I already knew all the limitations around Wireless? Cause I asked the same questions as last time, knowing I get the same answers:<\/p>\n

Off-topic: Is there a wifi trunk port? : r\/firewalla<\/a><\/p>\n

“Not possible unfortunately. You can\u2019t do VLAN tagging on WiFi except by separating the SSIDs.”<\/span><\/div>\n
<\/div>\n
However this time, the OP came back acknowledging the limitation, then planted that seed, like I’m being manipulated like in the move inception.<\/div>\n
<\/div>\n
“Thanks for the post. The radio bridge mode is interesting. There is another article here (https:\/\/forum.openwrt.org\/t\/trunking-over-wireless\/27517<\/a>) about achieving it using tunnels.”<\/div>\n
<\/div>\n
Then I debated with AI, which first was using technical differences, to denote I can’t do the same thing, (WDS vs STA) for connecting. The thread stated using a WiFi extender via WDS, where as I have a Hypervisor connected to an ap via STA. Done deal, we still can’t do this.. *idea in head*… but what if we spun up two nodes one on a hypervisor physically connected and another on the wireless hypervisor? We did the same trick with our Wireless ESXi host, but instead of layer3 routing traffic, we tunnel the layer2… making our whole broadcast domain work, and VLANs (at the cost of MTU cause of encapsulation)… I showed AI a basic ASCII network design of this and stated it in theory should work… so here I go… ready to immensely suffer though something that I could simply plug a hardwired cable into and be done with it…<\/div>\n

<\/span>Step 1) Hyper-V Base<\/span><\/h2>\n

Since I have no clue what I’m doing, I’m gonna start with a base.. a Hyper-V Server (on Server 2025), running on a laptop. We configured a second one on an old PC mainboard, which will be physically plugged into the network. (Making it the easiest setup ever). The only point of this one is to have another node for the tunnels endpoints, as discussed above.<\/p>\n

<\/span>Step 2) OpenWRT<\/span><\/h2>\n

Why OpenWRT instead of OPNsense… I used it before, I’m familiar with it… well mostly for one main reason (ok 2)…<\/p>\n

1. OpenWRT expects:<\/p>\n