Reason I chosen iptables because I have a repo keeping my generic for all my machines.

Here is how to make iptables work on Debian. First, get apt repo update and install iptables-persistent. Persistent making the rules permanently there

apt update && apt install iptables-persistent 

Once it’s install, it will automatically start without a default rules, unlike rocky/alma, it comes with the default rules and enable port 22 (ssh)

Here is the rules you can refer to as a start in /etc/iptables/rules.v4

*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT

## Free flow for VPN IP
-A INPUT -p tcp -m state --state NEW -s x.x.x.x/32 -m tcp -j ACCEPT

## Only allow 80 and 443
-A INPUT -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 443 -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT

-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT

That will be the same iptables’ rules for ipv4. Restart the services

# systemctl restart iptables 

That’s the basic setup of iptables on Debian with persistent rules.

Whenever I restart my Proxmox host, it cannot boot up the VM and throwing the error “proxmox cluster no quorum”

It was due to the quorum for a cluster required minimum of 2 hosts. You can set the quorum expect to 1 manually whenever the host boot up.

pvmctl expect 1

However it cannot be hard coded, whenever you patch the proxmox machine, you are required to set the value again on order to have the VMs running.

I’ve decided to find a permanent fix, to remove the host from the cluster.

Here are the steps to do it.

systemctl stop pve-cluster corosync
pmxcfs -l
rm /etc/corosync/*
rm /etc/pve/corosync.conf
killall pmxcfs
systemctl start pve-cluster

Thankfully, the info was shared in one of the Promox forum threads.

Now, I can patch the proxmox machine and reboot it, sipping coffee and wait for the VMs slowly boot up

Previously the auto update (Check for update on Thunderbird) didn’t work well for me. I’ve had issues like calendar invite missing, attachment cannot view in the email, sender name didn’t display correctly in an email view.

After a “clean” migration, I noticed it also doesn’t have performance issue. i.e previously loading email was pretty slow, and it took almost a second to load an email.

But, I’ve have the issue of the Unified didn’t display all inbox folders for my 12 email accounts, only 10 inboxes are showing on Unified Inbox folder.

This support forum in Mozilla resolve my issue.

All you need to do is close your Thunderbird (in my case it’s Thunderbird running on MacOS), and go to your profile folder, usually it’s in your Library/Thunerbird/Profile folder.

In your profile folder, delete the file virtualFolders.dat.

Navigate to Mail folder, and delete the folder smart mailboxes.

Launch Thunderbird again, and now you should be seeing all the inboxes in Unified Folder view option.

Things have changed quite a lot, I think there are fewer people writing or blogging. Now they do it on Youtube (Youtuber) for tutorials.

Let’s see what I will start to write next

p/s: I don’t think people visit this site either, if you do, please drop a message and say hi.

Here is what you need to prepare before proceed with the backup.

1. Create a directory for backup. i.e folder name of ServerBackup. Go to “Control Panel” -> “Shared Folder”.

2. Enable SSH on Synology. Go to “Control Panel” -> “Terminal & SNMP” -> “Enable SSH Service”. If you option to change the SSH port or not

3. Try to ssh into Synology with username “root”. The root password is the same with “admin”.

If are you done, let’s do it.

Generate SSH Key

You wouldn’t want to key in password whenever want to access to the server to grab the file. Generate a “custom” ssh key which will be used for synology. Remember, please do not set the password. Give you ssh file a “special name”, DO NOT use the default. I.e we used synobackup, there are 2 files will be generate

1. synobackup – This is the private key files
2. synobackup.pub – This is the public key which will be placed on the remote server.

Next, we will copy this 2 files into Synology folder ServerBackup. We create a folder name “scripts”, and the file will be placed in synology

1. /Volume/ServerBackup/scripts/synobackup
2. /Volume/ServerBackup/scripts/synobackup.pub

We will copy the key on synobackup.pub into remote server’s ssh directory “.ssh/authorized_keys” for the user’s home directory where you will login with the username later. i.e “/home/takizo/.ssh/authorized_keys”

Ok.. we are done with ssh thingy. Let’s write some script.

Simple Scripting

Next, we will do some scripting as below.

#!/bin/ash

#This is the private key
PRIVKEY="/volume/ServerBackup/scripts/snology"

#This is the folder you would like to backup from
HOSTFOLDER=/backup/*

#This is the folder you would like to backup to Synology
DESTFOLDER="/volume/ServerBackup/database/server-godzilla/"

#We will be using rsync in synology, this will do the rync! 
/usr/syno/bin/rsync -avz -e "ssh -p7777 -i $PRIVKEY" takizo@godzilla.takizo.com:$HOSTFOLDER $DESTFOLDER

Save the script above into your Synology backup folder which created earlier “/volume/ServerBackup/scripts/database.backup.sh”

Please take note that the remote folder is define by yourself. We are done with the script, it’s time to Execute it!

Configure the Backup Script

Due to it’s the first time access to the remote server, you need to manually run the script in shell to accept the SSH session. We are almost there.

SSH to Synology server

ssh -p2222 root@your_synology_ip
mydisk> cd /volume/ServerBackup/scripts
mydisk> ./database.backup.sh
The authenticity of host '[godzilla.takizo.com]:2222 ([123.456.123.111]:2222)' can't be established.
ECDSA key fingerprint is f7:9b:d6:92:7b:33.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[godzilla.takizo.com]:2222,[123.456.123.111]:2222' (ECDSA) to the list of known hosts.
receiving incremental file list
20150721122502.dbbackup.tar.gz

sent 42 bytes  received 18901016 bytes  1021678.81 bytes/sec
total size is 18997573  speedup is 1.01

The important part for this action is this line

Warning: Permanently added '[godzilla.takizo.com]:2222,[123.456.123.111]:2222' (ECDSA) to the list of known hosts.

This will add the host into /root/.ssh/known_hosts, when the script is run next time, it will not prompt the message again.

Setup the Task on Synology

Since the script is working perfectly fine. The last step is add it into Synology’s Task Schedule.

1. Go to “Control Panel” -> “Task Schedule”
2. Create “User defined-script”
3. Give a meaningful name for your “Task”
4. User choose “root” or any user you prefer
5. User-defined script: The script you created earlier inside Synology folder, “/volume/ServerBackup/scripts/database.backup.sh”
6. Put up a schedule for this, how often it should run and at what time.

After the schedule has been created, try run it again and check is the files transfer into your Synology folder (if you don’t have new copy of file in the server, delete the files earlier being rsync into synology).

Yep, basically you have another copy of backup on synology! Enjoy backup more stuff from remote server

LeetCode have list of programming interview question for programmer to run through, well it’s not necessary for programmer, it’s good for employer to give programming question to programmer if they want to test out the programmer’s thinking skills.

It’s a good way to prepare yourself for a Whiteboard Interview, you can try to go through the coding test and give your some confident myth.

Good luck.

You will see a bunch of mdworker(s) doing their work in Activity Monitor

If you want to find out what are mdworker(s) working on, can try this command in the terminal

$ sudo fs_usage -w -f filesys mdworker

If you found out there are folders you don’t want Spotlight to index, can add it into Privacy tab on Spotlight’s preference.

Enjoy!

After news leaked of Apple’s upcoming iPhone event on September 10th, it was assumed the new iOS 7 would be announced at the same time — but now there’s proof. Today, a developer named Owen Williams received an email indicating that iOS 7 would be released to the general public on the 10th, giving non-developers their first peek at the controversial operating system. The email comes from Nuance, which works closely enough with Apple to know the date in advance.

[News via TheVerge]

Looks like white and brown won’t be the only colors on offer for Samsung’s Galaxy Tab 3 7.0 for long. Evidently set to join those variants, @evleaks recently pushed out a purported press render of the slate clad in a deep blue. No word on when and where this version might be available

[via Engadget]

A quality control employee at Pegatron, Apple’s manufacturing partner, has published a photo on her Weibo profile (a Chinese microblogging site), which appears to be a large number of iPhone 5C units in testing mode.

Engadget reports that the employee appears to have joined the quality control department in mid-July.

[via iPhoneHacks]