Posts

Hyper-V NAT network setup using the default switch

This was the easiest guide to use the default virtual switch to enable NAT for the VMs to download patches from the internet without adding more IP addresses to your network. https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/setup-nat-network Basically steps are: 1. Start Powershell as administrator 2. PS C:\WINDOWS\system32> Get-NetAdapter 3. "Extract the ifIndex for the Hyper-V Virtual Ethernet Adapter. In my case it was 28" 4. PS C:\WINDOWS\system32> New-NetIPAddress -IPAddress 172.16.0.1 -PrefixLength 24 -InterfaceIndex 28 5. PS C:\WINDOWS\system32>New-NetNat -Name NAT -InternalIPInterfaceAddressPrefix 172.16.0.0/24 6. After that, go to the VM and assign a static IP address to the VM as 172.16.0.2 with subnet mask as 255.255.255.0 and gateway as 172.16.0.1. DNS settings can be 8.8.8.8

dead pi

Well, I guess it has to happen at some point. the home automation raspberry pi has died. Much to do with the stupid Strontium mini SD card. Have to say I should have known better. There was a problem with the card and when I took it back to RMA, the service center said it was bad blocks and they updated the firmware on the card to not "see" the bad blocks and all was good. Well, until the next bad block comes along. Well that's the last time I am going to get a strontium card. Starting from scratch well, not having the same luxury of time, basically, I had to determine what are the key gaps that Alexa and homekit (my 2 main control methods) The good news is that it gets easier and integrations are getting more native. Here are the plugins for my Homekit setup. 1. Fibaro Homekit: Homebridge Fibaro Hc3 2. Sonoff eWelink Homekit: Homebridge Ewelink 3. Broadlink Homekit: Homebridge Broadlink Rm4 5. TP Link Homekit: Homebridge Tplink Smarthome Alexa skills are fairly straight ...

Splitting the home network

Image
Who wouldn't want to separate the traffic at home for security reasons. The more common ones include wireless guest and wireless users. I've logically classified my devices and users as: Wireless guests and un-trusted wireless IOT devices, e.g. xiaomi and ewelink Wireless users and tablets Gaming machines and media boxes An application/server type network A lot of this has to do with configuring the router. I'm using the Asus RT-AC88U Separating  wireless traffic for guests For splitting the wireless traffic, it's easy enough to use the wireless router and create a guest network without access to the intranet. This will allow "guest" devices to connect to the internet at a lower bandwidth and unable to connect to the local network. QoS media, gaming and work machines For gaming, i would say the router did it all. Just need to enable QoS and other router features that automatically prioritises the devices that you want. Application/server ne...