Abhinav Jain If necessity is the mother of inventions, passion is the father

There are times when one wants to quickly check the speed and ping for there server to ensure the connection is good enough. I found this simple command that comes handy when one runs it on the command-line of a linux server (lost the original source):

curl -s https://raw.githubusercontent.com/sivel/speedtest-cli/master/speedtest.py | python –

(retype the hypen sign at the end in case you copy-paste from the website)

It is a neat alternative compared to installing ‘speedtest’ on debian/ubuntu servers

sudo apt install speedtest-cli

speedtest

Hi there,

Thanks for attending my talk at UAA 2019. I’ll be posting additional resources after August 15th, 2019. Please stay tuned or drop me a note.

Thanks,

Abhinav

My debian 9 (stretch) server became slow and I was not sure what was causing it. Another thing I noticed was that it was taking longer than usual to boot. While booting, I also noticed a message showing up momentarily on the screen such as

“gave up waiting for suspend/resume device”

I also noticed that SWAP was not being utilized. Apparently, this happens when the UUID of the swap doesn’t match and swap is encrypted. I managed to fix it by the running code snippets given in this link–

1. Get the UUID of the swap by running the command: lsblk -f
2. Note down the UUID and edit: /etc/initramfs-tools/conf.d/resume
3. Replace the UUID with the correct one and run the command: update-initramfs -u
4. Reboot and enjoy

This is assuming that you are a root user. You may have to use sudo prefix if you are not a root user. In case you are looking for a command to avoid typing things then you may refer to this link.

I noticed that the internet in one of the VM was super slow. I could not find the root cause, however, it seems to work better if I check “Disable hardware checksum offload” under System>Advance>Networking tab

Thanks to this reddit for saving the day: https://www.reddit.com/r/PFSENSE/comments/8dskri/slow_wan_speeds/

I struggled for about a month to fix the problem of no outward DNS resolve for my VMs. IP addresses such as 8.8.8.8 of Google DNS service would ping, however, www.google.com would not ping.

Things were fine for one of the VM though. I finally noticed that the VM where things were working fine had model Intel E1000 for network devices. I edited that for the other non-working VMs as well and restarted the VM. That fixed the issue.

Therefore, while choosing network card for a VM in Proxmox with firewall (pfsense), I noticed that inward internet does not work when virtlo model is selected for the network device. Changing it to Intel E1000 fixed the problem.

Enjoy Virtualization