Posts

How to remove old kernels from Ubuntu

This method should work for both Ubuntu server OS (instances) and desktops that we use. Use case: Automatic or manual updates to the OS may result in multiple kernels installed in your system. This is usually alright, but it can become a problem if your the OS has a small /boot partition, and it runs out of space because of a large number of old kernels installed there. You could follow these simple steps to delete the older kernels 1. Verify the kernel that is currently booted and is in use: uname -r 4.4.0-79-generic   Whatever you do, don't delete this kernel. 2. Finding out what kernels are currently installed in the system: dpkg —list | grep linux-image linux-image-4.4.0-72-generic 4.4.0-72.93 amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP linux-image-4.4.0-75-generic 4.4.0-75.96 amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP linux-image-4.4.0-77-generic 4.4.0-77.98 amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP

Useful tcpdump commands and examples

Packet sniffing/capturing is a troubleshooting tool that many system and network engineers use for troubleshooting. If you're like me who uses Linux a lot, tcpdump is a useful tool that you can use. In this tutorial, I'm listing a couple of frequently used tcpdump commands  that I use. I'll keep adding additional interesting commands that I stumble upon over time. Installing tcpdump CentOS/RHEL # yum install tcpdump Ubuntu/Debian # apt-get install tcpdump Examples tcpdump requires root privileges. Please use a privileged user, or use sudo  where applicable. Running tcpdump and listening on all network interfaces # tcpdump Listening on a specific network interface # tcpdump -i eth0 All my examples have  ' -i eth0' parameter because I'm used to it. You could choose not to use this parameter depending on your use case, for example if you have only one NIC in the server. Write packet capture to Wireshark compatible

How to enable DNSBL or RBL on Zimbra to fight against spam

Image
DNS-based Blackhole List (DNSBL) or Real-time Blackhole List (RBL) is an effort to fight spam emails. It is a blacklist of source IP addresses that have a reputation of sending spam emails. Most email systems can be configured to check these lists and block or flag emails that were sent from domains/IPs listed there. The ‘Blackhole List’ is sometimes called ‘blacklist’ by email admins. In this tutorial, we’ll see how we can configure RBL with Zimbra using both GUI and CLI. Method 1 - GUI: Login to the Zimbra admin console – https://mail.example.com:7071 , and then go to Configure . Configure Then, go to Global Settings . Global Settings Next, go to MTA . I’ve enabled some parameters to harden the server, and added the RBLs that Zimbra supports. You could add the RBLs of your choice here. MTA Changes   Save your settings. There no need to do any service restarts. Zimbra sho