Ping not working in WSL2 Kali Linux

 I found the answer here:

           sudo setcap cap_net_raw+ep /usr/bin/ping

Issues with WSL2 Networking

 WSL2 networking continues to be problematic, be it DNS not working or network connectivity being lost with the wider network. I also had an issue where WSL2 seemed to prefer a disconnected WiFi connection over a connected Ethernet one.

Things I have done:

1. Disable the unused WiFi Adaptor, this has prevented WSL2 from trying to use it.

2. Turned off Windows Fast Start - This is accessed from the power butttons options underneath power plan. Apparantly it helps fix issues if you shutdown\startup the machine with WSL2 rather than restart.

3. Configured static DNS for WSL2 machines. I created a /etc/wsl.conf file containing the following (replace the name servers with what you want): 
            [network]
            generateResolvConf = false
            nameserver 192.168.1.3
            nameserver 192.168.1.4

4. Networking still craps out but I find this network stack reset recommendation from stackOverflow helps:
            wsl --shutdown
            netsh winsock reset
            netsh int ip reset all
            netsh winhttp reset proxy
            ipconfig /flushdns
            Windows Search > Network Reset
            Restart Windows

NALA v0.7 Relased

 I've been using NALA for a little while on my Ubuntu distros as it compacts the update process and makes it much more obvious what's going on than if you use APT alone.

Up until now, the "nala fetch" command wasn't working on ARM\Pi as it set some repo's that either had no, or broken arm packages. 

With v0.7, "nala fetch" now sets up the repos correctly so ARM\Pi users can make use of features like parallel downloads etc.

Find NALA on GitLab here.

Unable to upgrade Google Apps Legacy to Google Workspace Starter with UK billing

 I had discovered by accident that the old free Google Apps Legacy edition which I've been using since 2013 was being discontinued this year and that I had to upgrade to at least Google Workspace Starter before the end of July this year or potentially lose access to the service.

I have four family members using this, so losing access to email and purchased apps\media would be a big deal, so I had to go through the upgrade process.

The problem was, every time I ran through the upgrade wizard, I was being asked for a US, rather than a UK billing address. I did not have that.

I posted a question on the Google community forums, and having run around in circles for a few days I had my post closed as the duplicate for another question, again with no real answers. 

I came back today to thankfully find an answer. It turns out that at the top of the page where you select you Workspace edition there is a country\currency selection drop down. It looks like this is easily missed as the page in the browser can be displayed slightly scrolled down with this option scrolled off the top:

Here's the post with the answer here.

Now, a small rant. 

I'm very grateful to Google for providing this service for the 9 years or so, and I certainly have no issues paying a fair price for the service. Not at all. It just doesn't seem very competitive to other options out there, so I get the distinct impression Google want the legacy apps account holders to disappear.

List price for Google Workspace Starter is currently about £4.60 per user, per month. So for my family of four, this is £4.60*4*12=£220.80 per year. Compare this against £79.99 for up to 6 users on Microsoft 365 and that is nearly three times the cost. You also only get 30GB on Workspace starter vs M365 family. I also get the latest MS Office desktop apps on M365 family as well...

The only thing that has stopped me moving for now is:

• Upgrade is free until end of July 2022
• Upgrade is half price until July 2023
• You can't move apps\media purchases to a new account

I might be able to justify this July 22-23 at £110.40 for they year, but I will most probably have to move and sacrifice apps\media in 2023.

I'm going to head over to the Google suggestions community page ans suggest that Google create a Workspace Family edition, but I won't hold my breath. The last time I tried, I couldn't register because of some mainteance

Chia Daemon Not Starting

I have been busy recovering from a 5 * 16TB Segate Exos drive crash, and had just updated Chia to v1.2.11. 

After a reboot and an attempt to restart Chia, I was only getting two lines in the log file:

    1: Starting Chia Daemon

    2: Not Implemented

The Wallet remained stuck on a "Connecting" message.

Turns out the Chia Daemon port 55400 had been blocked by the WINNAT service.

It was confirmed by running the following command from an elevated CMD prompt: 

    netsh interface ipv4 show excludedportrange protocol=tcp

The following commands also ran from the same elevated CMD prompt fixed it:

    net stop winnat

    [Now stat Chia]

    net start winnat 

 Thanks to MrGreenApe and his post here:

    https://github.com/Chia-Network/chia-blockchain/issues/2269#issuecomment-838645580

World Community Grid

How to change Microsoft 365 Channel from command line

Good article here on how to change Microsoft 365 without worrying about registry keys.

1. Run a CMD prompt
2. type cd C:\Program Files\Common Files\Microsoft Shared\ClickToRun
3. To change to e.g. Current channel do the following
4. Type OfficeC2RClient.exe /changesetting Channel=Current
5. Type OfficeC2RClient.exe /update user

This allowed me to easy change form SemiAnnual to Current channel.

More details here: https://www.fmsinc.com/microsoft-office/change-office-365-channel.html#CommandPrompt

Prepare and create a RAID5 Array of 5 * 4TB Segate Barracuda Disks

 We need to prepare the disks as GPT labeled as they are > 2TB.

For each disk:

• parted -a optimal /dev/sdx
• mklabel gpt
• mkpart primary 0% 100%
• set 1 raid on
• align-check optimal 1
• print
• quit

Create the array:

• mdadm --create /dev/md0 --level=raid5 --raid-devices=5 /dev/sdx1 /dev/sdx1 /dev/sdx1 /dev/sdx1 /dev/sdx1 

In all of the above replace /dev/sdx1 with appropriates devices, e.g /dev/sda1 /dev/sda2 etc.