This post will show you how to install the telnet client in Microsoft’s Windows Server 2019. I’ll show examples with command prompt, PowerShell, and of course using the graphical user interface.
Tag Archives: networking
The Socket Statistics (ss) command is similar to netstat, in that it is used to display useful network socket information.
For some time now the netstat manual page has noted “This program is obsolete. Replacement for netstat is ss.”, so this is going to be a useful command to know how to use moving forward.
Fortunately a lot of the options are similar to the ones used by netstat, however there are a few differences as we will see.
In Linux it is possible to aggregate multiple network links together into a single logical link which can either increase network throughput or redundancy. For example we can assign an IP address to a group of two network interfaces to double our throughput, or reserve one interface for backup purposes so if the first one fails we can fail over.
Here we’re going to cover how to create and configure a network team with two different network interfaces.
In the past many system administrators have simply resorted to disabling IPv6 rather than properly configuring it, continuing to rely on the older IPv4 which has worked just fine for a very long time. As the IPv4 address space has since become exhausted, administrators are starting to slowly take up IPv6 out of necessity.
Here we’re going to cover how to configure IPv6 addressing in Linux and provide some basic tips and advice for troubleshooting IPv6 network issues.
By default SELinux policy defines the ports that a particular service is allowed bind to and make use of with port labeling. This increases system security by preventing random services or malicious code from being able to bind to a well known defined port that may otherwise be used by a legitimate service.
In order to change a service to use a non standard port we must change SELinux policy and specify the SELinux port types that are allowed to use specific ports.
By default all network traffic will normally be configured to route via the default gateway, that is the router attached to the network interface. It may not always be the case that you want all traffic to take the same path, in these instances we can set additional static routes that will forward specific traffic out of a different interface rather than the default gateway. This may be required if you need to be able to reach a particular network that your default gateway router does not know about.
Here we’re going to cover how to configure a static route in Linux.