Subnetting sucks. Let's not be coy about it. It's a pain in the ass, takes forever and I hate doing it. But life is suffering, and subnetting is something you at least need to understand in concept since, well, modern networking - and, in turn, modern communication - is built on it. It's also a requirement in case you're chasing certification in IT or networking.
So my here goal is to give you a runthrough that will help you create a coherent internal concept for subnetting. This will help you read and understand network topology, and allow you to progress to understanding of deeper networking concepts.
One of the most fundamental parts of any operating systems is managing memory; the subsystem conveniently known as the Memory Management Unit or MMU. This subsystem is a very complex one but, fortunately for us, it's very well documented. Today's article breaks it all down.
Just like you might have several ID cards for yourself, depending on where you are and what you have to verify, so does your computer on a network. The most common ID used for computers is the IP address, and IP addresses really build up the framework for both local network and internet communication. Usually, a computer will have at least two IP addresses; one for the internal network and one for external (internet). Nowadays, you might actually have a second external IP address since everyone is slowly switching over to a new addressing system. The previous IP version 4 (IPv4) is still the more common one, since it's been around so long. But now that it's literally running out of possible addresses to assign, there's a movement towards IPv6 which solves the issue by having more bits available for addressing.
In this article we will be covering the basics of how to remotely manage a Linux based virtual private server. Remote control of a VPS through Linux is done through its console. If you're using Windows, however, you'll need to get a utility that allows you to connect to your Linux server over SSH, such as Putty. For Mac users, "SSH-client" is a built-in app that functions similarly.
Using utilities like scp, rsync, sftp we can control the server as well as send and recieve files over an encrypted connection. As long as your server is properly configured to use SSH, it will be very secure from any possible intrusion. To that end, there's a couple of guidelines you should follow to ensure a secure configuration of your SSH-server; a) keep access credentials as private as possible, limiting them to only the individuals actively using the server and b) use access keys instead of password, since passwords are easier to create and easier to brute force.
We're here! The third and final article in our series discussing server monitoring tools. If you're just joining us, you can check out Part I and Part II. Today we're focusing on cloud monitoring solutions, so let's get into it.
Today, GNU/Linux based operating systems are considered to be among the most secure available. They're used by a majority of the largest super computers we have available, far outpacing the amount of computers running UNIX or Windows. And one of the reasons Linux holds its reputation for security is the way it handles user access. Its user and group control functions was developed around the time of the first UNIX systems, and these controls allow file owners to control access to reading, execution, and writing of files, directories, processes and other system tools.
This is the second part of our ongoing review of Linux monitoring tools you're likely to encounter in the market. Follow this link for the first article we posted on the subject.
In this review, we'll be going over monitoring software that tends to focus on network monitoring primarily.
Maintaining server uptime is an absolute necessity in pretty much every environment in our modern life, and server monitoring solutions serve that specific purpose. Server monitoring systems keep tabs on where you're server's at, where it's running into bottlenecks or other issues, helps maintain backups and reserve copies. A good server monitoring platform is really like a tool chest; a collection of things that seem small on their own, but they work together to both secure your server and allow you to react in critical situations.
Within most operating systems, including all Linux distros, there exists a range of ports that are considered privileged ports. All privileged ports range from 1 to 1023 and can accessed by root user and, in most cases, can't be accessed for any other users. So what we're going to do is rebind some ports to allow users access without compromising your root account.
Ansible kind of exploded into popularity almost immediately after its release in 2012, and has become a staple for network administrators. In today's article, we're just going to immediately dive in and give you a good idea of what Ansible does and how you can get the most out of it.
Ansible is an open source automation platform. What that means is that it lets you manage software installations, updates, configurations and tasks within your network environment. It's especially handy in situations where you need to carry out sequential operations. It's also comparably easy to use, when put against other similar solutions.