Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I thought I was suppose to use a zero for the last three ranges, but it appears that doing so does not all any IP such as 10.123.123.123 or 10.1.1.1 to get through. How should I be doing this? Thanks
Code:
14 ACCEPT tcp -- 10.0.0.0/24 0.0.0.0/0 tcp dpt:445 state NEW
Last edited by NotionCommotion; 04-09-2017 at 12:57 AM.
Your netmask should be just the first 8 bits, not the first 24:
Ah, I think I finally starting to get this IP thing. Let me explain my current understanding, and please correct me where I am wrong.
All IPv4 require 32 bits, and a given network can have?
(1) class A network with 2^24 IPs (16,777,216) where the remaining 8 bits are used to specify it is a class A network?
(16) class B networks with 2^20 IPs (1,048,576) where 8 of the remaining 12 bits are used to specify it is a class B network and the remaining 4 bits are used to specify which of the 16 (172.16 to 172.31) it is?
(256) class C networks with 2^16 IPs (65,536) where 8 of the remaining 16 bits are used to specify it is a class C network and the remaining 8 bits are used to specify which of the 256 (198.168 to ???) it is?
So, then these remaining 8, 12, or 16 bits are used to mask the IP so they don't conflict with others?
To be fair, Class A, Class B and Class C subnetworking isn't really used anymore, rather everything went to CIDR notation where Class A is equiv of a /8, Class B a /16 and Class C a /24 where the notation indicates the number of bits within the network address. CIDR is generally all round better, tho I am guessing Colleges and Universities probably still the old class style of subnetworking... cas those places usually get stuck in the past.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.