Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
We publish journal on-line that are mainly accessed from institutions. We get the IP address of institutions that should have access to these journals from publishers but there doesn't seam to be any consistency among them. Is there a standard for declaring an IP address ranges?
I looked a little for a standard but can't seam to find one. Should the range be expressed within the octet? ( 192.168.1-10.* ), as two full IPs (192.168.1.* - 192.168.10.*) or either. Do the ranges need to include subnetting information (192.168.1.* - 192.168.10.*/255.255.255.0 or 192.168.1.* - 192.168.10.*/24)? Or, can this be figured out by the IPs that are given?
Also, are there any PERL modules that follow and parse a spec?
In theory, there's a rule. But in real word - no rules. It depends on the institution or their ISP (how many IPs they get). In most situations you can just get a list. It happens quite often that the IPs are not in order (for example: 192.168.1.4, 192.168.4.125). Of course, all the IPs we use in the posts here are not real (they're local).
There is no standard as such, but the information you have been supplied with is in a fairly conventional format, and seems quite clear.
You don't need subnet mask information to setup filters for these ranges. Subnet masks only have relevance to hosts on the source subnet and routing protocols within the internet.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.