Some nice For Dummies Books.

Will add more as I stumble upon them.

Network Virtualization for Dummies

Micro‐segmentation For Dummies

NVMe over Fibre Channel For Dummies Brocade Special Edition

Firewalls for Dummies

Next Generation Firewall for Dummies

Cybersecurity for Dummies

Network Security in Virtualized Data Centers for Dummies

Virtualization for Dummies


Requires registration

Modern PC Management for Dummies Guide

SMB Hybrid IT for Dummies

Next-Gen Virtualization for Dummies
Hyper-Converged Infrastructure For Dummies
Network Virtualizations For Dummies


Client VPN and VPN server in ASUS router at the same time. Route all traffic thru VPN service.

What we want:



I don’t think this will work with ASUS orginal firmware, I have not tested.
I use Merlin (

Check what TUN you have in the router via ssh
Command: route

Then you see what TUN you have on the vpn, in my case tun15
You can also use tun1+ but then all TUN will be affected

iptables -I POSTROUTING -t nat -s $(nvram get vpn_server1_sn)/24 -o tun15 -j MASQUERADE

Test if this works

Then add it to a script that will apply this automatic after renoot.

1. Enable script in the gui
2. Create script

vi /jffs/scripts/firewall-start

iptables -I POSTROUTING -t nat -s $(nvram get vpn_server1_sn)/24 -o tun15 -j MASQUERADE

chmod +x /jffs/scripts/firewall-start


Don’t forget to tick to start vpn client on boot in the gui


Redirect Internet traffic Any or selective routing

Create wildcard from lets encrypt from another machine. And convert to p12

You need to verify by dns, that’s what I read anyway.

I was doing this from ubuntu 18.04

Install certbot:

sudo add-apt-repository ppa:certbot/certbot

sudo apt install python-certbot-apache


  1. Certbot certonly –manual –preferred-challenges=dns –email –server –agree-tos -d *
  2. Add DNS txt vaule, you get this from above command
  3. Convert cert to p12: openssl pkcs12 -export -inkey privkey.pem -in fullchain.pem -out portal.p12




Update Manager is missing in the Flash or HTML5 gui. No errors, service is started. Unable to access Virtual Center from Linux Client.

One smash, two flies

After upgrading from 6.5 vcsa to 6.7 without any problem, update manager is missing in the clients, both flash and html5.

No errors on services, and everything looked fine.

But when I from Linux client browse to virtualcenter adress I get:


And I am not able to proceed to the site.


After the upgrade, for some reason the machine certificate got fucked up!
Common Name was set to CA. Don’t know why.

But i HTML5 gui, go to Administration, Certificate Management

Look at __MACHINE_CERT. The Common name was set to CA, and that was not the server name. So we choose action and press renew. Restarted the appliance and after that Update Manager and the cert error was gone.

If you are using third party application like veeam, don’t forget to verify the connection to the Virtual Center.




Unable to migrate Virtual Center to 6.5 from 5.5. Certificate errors.

Easy one

Uninstall VCenter Server from Windows

Copy/Backup and  Remove

C:\ProgramData\VMware\VMware VirtualCenter\SSL

Reinstall same Virtual Center that was installed before.


Or you can follow this great blogg from Zlatko Mitev

Some notifcation from me:

OpenSSL 0.9.8 is requried

Deploying and using the SSL Certificate Automation Tool 5.5

#When you are running openssl 0.9.8 you can go past 2037 or something so you need to change -days to something smaller
openssl x509 -req -days 1300 -sha256 -in c:\tmp\rui.csr -signkey c:\tmp\rui.key -out c:\tmp\rui.crt -extensions v3_req -extfile c:\tmp\openssl_config.cfg

#For me Openssl 0.9.8 did not work so I used the openssl version from C:\Program Files\VMware\Infrastructure\Inventory Service\bin
openssl.exe pkcs12 -export -in c:\tmp\rui.crt -inkey c:\tmp\rui.key -name rui -passout pass:testpassword -out c:\tmp\rui.pfx


Windows 2008 R2 cleanmgr.exe how to fix without reboot.

If not have desktop expirence installed and want to clean up C: on Windows 2008R2. Then copy below files the you are able to run clenmgr whitout reboot.
Yo need to overwrite, because the old files will be there.


to C:\windows\system32\


to C:\windows\system32\en-us\

The you can run cleanmgr.exe