4 ms·
From what I gather the problem is basically: Certain routers are processing both IP packets and ethernet frames through the same logic. They want to know which
by Macha 10y ago
From what I gather the problem is basically:
Certain routers are processing both IP packets and ethernet frames through the same logic. They want to know which it is. Ethernet frames start with the destination mac address, which used to be sequential and reaching higher numbers seemed far away so most started with 0 or 1. IP packets start with the IP version, so they're 4 or 6.
As a result, some vendors basically implement the following:
def is_ethernet_frame(data):
return not (data.startswith(4) or data.startswith(6))
And similar to the problems with
os.name.startswith('Windows 9')
type issues, now we reach the higher numbers, these systems have issues.
- web007 10y agoAre these not at different OSI layers and should be handled correctly by encapsulation?
- danudey 10y agoThey are, but these routers are doing inspection, even when they should be purely Layer 2, and then doing it stupidly, and then breaking.
- wmf 10y agoTo save space in the MPLS header, it doesn't specify what comes next. So inside an MPLS packet may be Ethernet, IP, or something else and in many cases the switch/router has no way of knowing what is inside the packet, but it still wants to find the 5-tuple to generate ECMP entropy.
- linkregister 10y agoI was not aware that MPLS provides for encapsulation of Layer 2 frames.
- deleted 10y ago[deleted]