Network troubleshooting cookbook in linux?
- Thread starter oslon
- Start date
Linux Server Hacks might work - https://www.oreilly.com/library/view/linux-server-hacks/0596004613/
These pages should be of help:
Step by Step Guide to troubleshoot network issue in Linux
Troubleshooting a problem related to Linux networking can be a challenging experience, but it doesn’t have to be. By understanding the basic principles of Linux networking and having an organized approach, you can quickly identify and resolve any issue that arises. In this article, we will dive...www.howtouselinux.com
A beginner's guide to network troubleshooting in Linux
Every system administrator needs to have at least a basic understanding of network troubleshooting. And the first rule of network troubleshooting to remember is, "Packets don't lie."www.redhat.com
Also some of these book, I recommend the Linux Bible and How Linux Works.Home | Linux Journey
linuxjourney.com
Good luck.
17 Best Linux Networking And Troubleshooting Commands
From this article, you will learn the List of the 17 best Linux Networking and Troubleshooting Commands to troubleshoot Linux servers.
devopscube.com
Their 'man' pages have lots of details about their various command options, but the quickest way to learn is to set up a simple server yourself, & try out some of the commands.
Preferably, get a second computer for this, because you will probably stitch it up, & need to re install a few times, before you get to understand networking.
Whilst I didn't need a server, I set one up, just to see what it was like; learning doesn't need to cost a lot.
But, if you ask questions on forums such as here, there are people who will be willing to help you to understand.
Preferably, get a second computer for this, because you will probably stitch it up, & need to re install a few times, before you get to understand networking.
Whilst I didn't need a server, I set one up, just to see what it was like; learning doesn't need to cost a lot.
But, if you ask questions on forums such as here, there are people who will be willing to help you to understand.
Part of it is knowing the commands of how to change something.
The bigger part is knowing what to change, and what to change it to.
Do you know what a subnet is? What a subnet mask is?
What a default gateway is? What an IP address is, and why you have the one you have?
Do you know the difference between a DHCP assigned address and a static IP address?
Do you know what a supernet is?
Do you know which subnets are not route-able out to the internet?
Do you know how a DNS client works, and what it's purpose is?
Do you know what a TCP/IP port is?
Do you know the difference between TCP and UDP?
Knowing how to change these things is great, knowing why you are changing them,
and what to change them to is a lot more important.
TCP/IP, routing and firewalls are common across all network devices, the same principles
apply whether it is a Windows system, MacOS system, or Linux, the commands are different,
but the principles are the same.
The bigger part is knowing what to change, and what to change it to.
Do you know what a subnet is? What a subnet mask is?
What a default gateway is? What an IP address is, and why you have the one you have?
Do you know the difference between a DHCP assigned address and a static IP address?
Do you know what a supernet is?
Do you know which subnets are not route-able out to the internet?
Do you know how a DNS client works, and what it's purpose is?
Do you know what a TCP/IP port is?
Do you know the difference between TCP and UDP?
Knowing how to change these things is great, knowing why you are changing them,
and what to change them to is a lot more important.
TCP/IP, routing and firewalls are common across all network devices, the same principles
apply whether it is a Windows system, MacOS system, or Linux, the commands are different,
but the principles are the same.
