News for hackers. Stuff that matters.
Re:Forwarding issues related to MACs starting with 4 or 6 by toast0 on Friday December 02, 2016 @02:54PM (#13091731)
Ethernet frames start with the destination mac address, IP payloads start with the version. It appears that in some networking equipment, there are places where it may have a ethernet frame or an IP playload and uses the first four bits to determine: if it starts with 4, it treats it as IPv4, and 6, IPv6.

So if it gets an ethernet frame destined for your address starting with 4 or 6, it will think it's actually an IP payload, and discard it because it doesn't validate as a IP packet or otherwise misdirect it.

Edit to add: In MPLS networks, 'P routers' (core routers) by design don't know if the payload is Ethernet or IP; but may want to peak into the payload to do hashed traffic balancing or validating packets before forwarding. Hashing the packet as an IP packet when it's an ethernet packet is problematic because you want all packets on a given TCP connection to have the same hash value -- but since you misidentified the type of packet, the bytes used as input to the hash aren't static for a given connection so different packets in the connection may take different paths and may arrive out of order.

Re:Forwarding issues related to MACs starting with 4 or 6 by IshKebab on Friday December 02, 2016 @07:27PM (#13093467)
Wow that is idiotic. How can you be skilled enough to program routers and still do something as obviously wrong as this?
Re:Forwarding issues related to MACs starting with 4 or 6 by wmf on Friday December 02, 2016 @08:33PM (#13093709)
In this case there simply isn't enough information in the packet to do the right thing so it's a question of choosing which wrong thing to do.
Re:Forwarding issues related to MACs starting with 4 or 6 by uxp on Friday December 02, 2016 @09:44PM (#13093977)
Seems like an attempt at being "clever". L2 equipment shouldn't care what kind of packet it is, but we're trying to subvert the original spec and come up with new hacks by "peeking" into the payload and make assumptions about what it is in order to rule or queue it differently.

Obviously in hindsight this is a bad idea and "idiotic", but I can't see the immediate fault of whomever first decided to try this a decade ago when MAC addresses were sequential, IPv4 was fairly abundant, and we didn't really even have smartphones and the explosion of connected devices.

Re:Forwarding issues related to MACs starting with 4 or 6 by bogomipz on Friday December 02, 2016 @11:33PM (#13094319)
Ethernet has always "cared" what type of upper payload its carrying. It has to, there are any other things besides IP that run directly on top of Ethernet frames. For instance 0x0800 means that the ethernet frame is carrying an IPv4 datagram.

Here is a list of all the ethertypes it cares about: http://www.networksorcery.com/enp/Protocol/802/ethertypes.ht...

Fire up wireshark and you will see these.

Re:Forwarding issues related to MACs starting with 4 or 6 by colanderman on Saturday December 03, 2016 @12:45AM (#13094525)
What the GP means is that layer 2 switches should forward traffic agnostic of what the Ethertype field says. That field only exists so layer 3 knows what it's dealing with.
Re:Forwarding issues related to MACs starting with 4 or 6 by bogomipz on Saturday December 03, 2016 @08:55AM (#13095649)
I see. I misunderstood then.
Re:Forwarding issues related to MACs starting with 4 or 6 by qb45 on Saturday December 03, 2016 @02:05PM (#13096978)
This is MPLS, not Ethernet. No protocol field, only endpoints know what's inside.