Sponsored Content
Full Discussion: Subnetting
Special Forums IP Networking Subnetting Post 302993570 by drysdalk on Saturday 11th of March 2017 07:41:05 AM
Old 03-11-2017
Hi,

Firstly, from just looking at a single IP, you can't tell how large the network it's a part of is. You need to know the netmask. So for example, if I had an IP of 192.168.1.10, that doesn't tell you anything at all about how large or small the network I'm a part of is.

But if I tell you the netmask - e.g. 192.168.1.10/24 or 192.168.1.10/255.255.255.0 - then you know it's part of a network of 256 addresses, running from 192.168.1.0 to 192.168.1.255.

If on the other hand I'd told you the netmask was 192.168.1.10/25 or 192.168.1.10/255.255.255.128 - then you'd know it was part of a network of 128 addresses going from 192.168.1.0 to 192.168.1.127.

And again, in every network, the very first address and the very last address are not usable for hosts, as they are reserved for other purposes.

You can also get plenty of other netmasks than the old simple Class A, B, C notation tells you. For instance I could just have easily told you my netmask was 192.168.1.10/28, in which case you'd then be able to calculate that the network I was a part of runs from 192.168.1.0 to 192.168.1.15, and conists of 16 IP addresses.

So just from looking at an IP you can't tell anything about the size of the network. And these days, there are far more netmasks and subnet sizes that are far more common than the old Class A/B/C notation.
This User Gave Thanks to drysdalk For This Post:
 

3 More Discussions You Might Find Interesting

1. IP Networking

Subnetting

We have subnetted our Internal Network. We used an I.P. range of 172.16.16.0-254, 172.16.17.0-254, 172.16.18.0-254, 172.16.19.0-254 and mask 255.255.252.0. We created a subnet range of 172.16.10.0-254 and maske 255.255.255.0. Our routers are configure to route to approprate network. We are able... (2 Replies)
Discussion started by: cassy
2 Replies

2. IP Networking

Subnetting in 11 steps

As seen on Digg.com, here is my ip addressing article in full... Original Subnetting in 11 Steps article Subnetting in 11 Steps There are a few things that you will need to know first. I personally use 11 rules that I learned from Mike Vana. Below you will find the 11 rules as well as... (1 Reply)
Discussion started by: jking2100
1 Replies

3. IP Networking

Subnetting

Guys, Anyone could help me understand subnetting. I know a bit in networking but there are things that I don't get them easily. Thank You in advance. (1 Reply)
Discussion started by: etcpasswd
1 Replies
GRE(4)							   BSD Kernel Interfaces Manual 						    GRE(4)

NAME
gre -- encapsulating network device SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file: device gre Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_gre_load="YES" DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop. gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands. This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco routers. gre also supports Cisco WCCP protocol, both version 1 and version 2. The gre interfaces support a number of additional parameters to the ifconfig(8): grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option. enable_csum Enables checksum calculation for outgoing packets. enable_seq Enables use of sequence number field in the GRE header for outgoing packets. EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.* / / +------ the Internet ------+ Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal address 192.168.2.1, the following commands will configure the tunnel: On router A: ifconfig greN create ifconfig greN inet 192.168.1.1 192.168.2.1 ifconfig greN inet tunnel A B route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1 On router B: ifconfig greN create ifconfig greN inet 192.168.2.1 192.168.1.1 ifconfig greN inet tunnel B A route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1 NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8). For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop. The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero. SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8) A description of GRE encapsulation can be found in RFC 2784 and RFC 2890. AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org> Heiko W.Rupp <hwr@pilhuhn.de> BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as if they would belong to this interface. The sequence number field also used only for outgoing packets. BSD
November 7, 2014 BSD
All times are GMT -4. The time now is 06:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy