A class A IP address space is 16,000,000 not 65,000. A class B IP address space is around 64,000 maybe 65,000. I don't remember the exact number as it has been a lot of years.
$ ipcalc 10.0.0.0/16
Address: 10.0.0.0 00001010.00000000. 00000000.00000000
Netmask: 255.255.0.0 = 16 11111111.11111111. 00000000.00000000
Wildcard: 0.0.255.255 00000000.00000000. 11111111.11111111
=>
Network: 10.0.0.0/16 00001010.00000000. 00000000.00000000
HostMin: 10.0.0.1 00001010.00000000. 00000000.00000001
HostMax: 10.0.255.254 00001010.00000000. 11111111.11111110
Broadcast: 10.0.255.255 00001010.00000000. 11111111.11111111
Hosts/Net: 65534 Class A, Private Internet
$ ipcalc 10.0.0.0/8
Address: 10.0.0.0 00001010. 00000000.00000000.00000000
Netmask: 255.0.0.0 = 8 11111111. 00000000.00000000.00000000
Wildcard: 0.255.255.255 00000000. 11111111.11111111.11111111
=>
Network: 10.0.0.0/8 00001010. 00000000.00000000.00000000
HostMin: 10.0.0.1 00001010. 00000000.00000000.00000001
HostMax: 10.255.255.254 00001010. 11111111.11111111.11111110
Broadcast: 10.255.255.255 00001010. 11111111.11111111.11111111
Hosts/Net: 16777214 Class A, Private Internet
Do you have a point? Public / Private either way you can spilt the CIDR into other segments as you desire as long as there's no overlap.Yes every network is a part of a class A. Private IP addresses are defined. Some are full class A and some are not.
Yes. /8 is class A. /16 is class B. The mask defines the address space. He has an "A" for class but he is using /16.
ipcalc 10.0.0.0/24
Address: 10.0.0.0 00001010.00000000.00000000. 00000000
Netmask: 255.255.255.0 = 24 11111111.11111111.11111111. 00000000
Wildcard: 0.0.0.255 00000000.00000000.00000000. 11111111
=>
Network: 10.0.0.0/24 00001010.00000000.00000000. 00000000
HostMin: 10.0.0.1 00001010.00000000.00000000. 00000001
HostMax: 10.0.0.254 00001010.00000000.00000000. 11111110
Broadcast: 10.0.0.255 00001010.00000000.00000000. 11111111
Hosts/Net: 254 Class A, Private Internet
With the likes of Google / Level3 / Facebook / ATT / VZW etc. having the bigger scopes that could get them into large swaths of IP's to use there's options to use A class routing w/o worry of exhaustion. With some tricks like MPLS you can setup things that are more like a VLAN but, routable / tagged / private from internet snooping. For instance one network that's popular uses a 5.x.x.x MPLS scheme for nationwide routing. When you go to lookup the IP though you get some little ISP in Turkey. DOD uses some MPLS trickery as well to route things in a similar fashion. Throwing things into a tagged MPLS environment allows you to use IP's more liberally because they typically only need a couple of IP's on either end that are public to exit the network to the outside world. ATT business routing does things with 10.x.x.x or 12.x.x.x
When I was Network Engineer for an Enterprise environment, we had nothing but MPLS at all of our sites and Datacenters...definitely worth the money and a lot less packet overhead compared to VPN Tunnels.MPLS doesn't use addresses, it uses labels - MPLS is essentially Layer 2 with some Layer 3 added...
Best way to consider MPLS is VPN on steroids - that's all most people need to know - it's a virtual wire
Telco carriers - their internal networking is largely abstracted from the public, but internally, they use a lot of RFC1918 ranges internally - and depending on last mile, for example, in wireless operators, one is usually nat'ed in a 10dot range, because (a) it doesn't matter, and (b) easier to manage with the P-GW/SGSN-GGSN networks across MME's
Carriers do use MPLS internally across markets and sometimes from the core out to the edge, or from core to core, esp with the majors where thru mergers/acquisitions, can and often due have multiple cores.
Should also mention that MPLS is used with partners (for example ATT roaming into Rogers - that's over MPLS links)
(note - edited for clarity)
definitely worth the money and a lot less packet overhead compared to VPN Tunnels.
The downside of MPLS is that one pays for the bandwidth whether it is used or not - it's a high quality link with defined class/quality of service, but if sized incorrectly, it can be very expensive indeed...
That's where SD-WAN can come into play - there's tradeoffs of course, but properly architected, one can use both - MPLS as primary, and SD-WAN for yield on demand.
When I retired we were heading to MPLS. We had the Cisco hardware in place. It was a matter of a transition plan from A to B on how we were going to get there. I left it for the new guy taking my place. I am thinking the video conferencing would also have been converted over from ATM using our Cisco LS1 switch to ethernet.The downside of MPLS is that one pays for the bandwidth whether it is used or not - it's a high quality link with defined class/quality of service, but if sized incorrectly, it can be very expensive indeed...
That's where SD-WAN can come into play - there's tradeoffs of course, but properly architected, one can use both - MPLS as primary, and SD-WAN for yield on demand.
ATM is ok if you can live in those small cell sizes. It is kind of old technology. ATM has been around a long time. It was what you used a long time ago for video conferencing.With the telco's pushing to kill off TDM lines, MPLS has shown to be the replacement for ATM in many cases... in those use cases, MPLS has all the properties of both internet and ATM.
Oddly enough, one can run MPLS over ATM...
The answer is..So, past the MPLS/ATM/CDMA/HALO/FM/AM/BBC/IPLS, what's the answer to the original question?
Thread starter | Title | Forum | Replies | Date |
---|---|---|---|---|
I am trying to understand vlans | Other LAN and WAN | 4 |
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!