IKEA BEKANT Sit/Stand Desk (2021 Update)

I purchased an IKEA BEKANT Sit/Stand desk back in late 2014 as an update to my old GALANT desk and it has worked great over the last 6+ years (no PSU issues). I've updated my desk a bit since then and wanted to post a quick update for 2021.

Current Setup:

• IKEA BEKANT Sit/Stand (Black-Brown/White)
• Scandinavian Hub Cable Management NEW
• Mount-It! MI-776 Hex Monitor Mount
• (6) Dell P2418D
• Dell AE515 Professional Soundbar
• APC Back-UPS 550
• Apple Mac Mini 2012 
• Apple Mac Mini 2018 NEW
• Logitech MX Keys Keyboard NEW
• Logitech MX Master 3 Mouse NEW
• Logitech C925-e Webcam NEW

I finally had to give up on my Mac Pro 2013, it was surprisingly slow when running Windows 10 in Boot Camp (which is what I run 99% of the time for work) compared to a 2019 MacBook pro I had used briefly as a replacement. The main attraction of the Mac Pro, for me, was the ability to run 6 monitors natively in a small form-factor without a bunch of other hardware/dongles.

The MacBook Pro 2019 worked well, but had it's own issues with supporting so many monitors using DisplayLink hubs/dongles, along with the heat and fan noise that would eventually ramp up.

I eventually moved on to a 2018 Mac Mini, which works well with the two Dell D6000 DisplayLink hubs that control 6 out of the 7 monitors. It's fast, quiet and has all the ports that I need. 

I've always wanted to be able to hide my PC/Mac desktop and the Mac Mini is perfect for this. I was  able to finally mount it underneath the desk to hide it away. It was such a good solution, I also mounted my 2012 Mac Mini which I use as an ESXi server for lab and personal VMs.

WSL2 AnyConnect Network Issue Fix

Ran into this issue a while back and finally figured out a couple of fixes. WSL2 would lose network connectivity *sometimes* when connecting to our company's Cisco AnyConnect VPN client. After some digging, I discovered that, when connected to AnyConnect, a new WSL2 network gateway was added with a lower metric by AnyConnect, thus routing WSL2 network traffic over the VPN instead of locally. 

UPDATE: I noticed that this only occurred when I had enabled internet sharing between my primary network interface and the WSL2 network adapter. I enabled sharing previously because I believe it had resolved some other issue, but when I disabled internet sharing, AnyConnect no longer created the new gateway route and everything worked fine...go figure

Here's my WSL2 network (172.20.144.0/20) in the Windows route table when not connected to AnyConnect:

Here's my WSL2 network (172.20.144.0/20) in the Windows route table when connected to AnyConnect:

For some reason AnyConnect creates a new, additional gateway for the 172.20.144.0/20 network. Since this new route was created by AnyConnect, it also has a lower metric than the On-Link gateway metric of 257. Thus, it takes priority over the On-Link gateway and sends the traffic over the VPN instead of routing it locally.

Temporary Fix #1

Found this while Googling and seems to be the most popular fix. Basically, it's a PowerShell command that changes the metric of the routes added by the AnyConnect network interface.

Get-NetAdapter | Where-Object {$_.InterfaceDescription -Match "Cisco AnyConnect"} | Set-NetIPInterface -InterfaceMetric 4000

This command will set routes created by the AnyConnect network interface to 4000. There's nothing magical about 4000, the new metric just needs to be higher than the local On-Link metric to make it less preferred (route with the lowest metric is preferred).

After running the PowerShell command, I ran route print 172.20.144.* to confirm the metric update:

Now, we're back in business...until you reboot, reconnect or wake from sleep, then you need to run the command again :(

Temporary Fix #2

I you prefer using the GUI, then you can adjust the metric through the control panel instead. I haven't found a way to make this permanent though, if anyone knows how, please let me know.

Go to Control Panel > Network and Sharing Center > Change adapter settings > Cisco AnyConnect Secure Mobility Client Connection > Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties > Advanced and set the metric to a number higher than your current On-Link metric. In the example, I'm setting the metric to be 500:

And now my route table reflects the change: