3 ms·
Maybe one way to describe MPLS is its kinda a VPN for VLANs. Or a way to put VLANs in something like a VLAN sorta. I can't speak for them but I worked at what
by VLM 10y ago
Maybe one way to describe MPLS is its kinda a VPN for VLANs. Or a way to put VLANs in something like a VLAN sorta.
I can't speak for them but I worked at what boils down to a semi competitor a decade ago doing network stuff. MPLS is old stuff now and you can google the specific cisco model numbers and MPLS if you'd like to read configuration guides.
Superficially only having 4096 VLAN labels on an ethernet connection appears to be a big problem if you have more than 4096 customers. However MPLS label space is 20 bits so you're good to a million customers.
Then you have some "fun" mapping games such that your router connects traffic on MPLS label 123456 (which is your customer number) to local ethernet interface port wtf on vlan 100 or whatever you have been given.
At least that would have been cutting edge a decade ago and probably still is today.
Its unlikely to be any more, or any less, secure than anything else in a virtualized cloudy environment.
- jlgaddis 10y ago> Or a way to put VLANs in something like a VLAN sorta. 802.1ad, a.k.a. "Q-in-Q" [0] > However MPLS label space is 20 bits so you're good to a million customers. VXLAN, cf. RFC 7348 [1], is the latest coolness, allowing for up to 16M "virtual" networks (using 24 bits) and bridging layer 2 over IP (4789/UDP). [0]: https://en.m.wikipedia.org/wiki/IEEE_802.1ad https://en.m.wikipedia.org/wiki/IEEE_802.1ad [1]: https://tools.ietf.org/html/rfc7348 https://tools.ietf.org/html/rfc7348