Change Details

Certain internet service providers transmit vlan 0 priority tagged EAPOL frames from the ONT towards the residential gateway. VID 0 should be ignored, and the frame processed according to the priority set in the 802.1P bits and the encapsulated EtherType (i.e. EAPOL). The pcap filter utilized by l2_packet is inadquate for this use case. Here we modify the pcap filter to accept both unencapsulated and encapsulated (with VLAN 0) EAPOL EtherTypes. This preserves the original filter behavior while also matching on encapsulated EAPOL. Sponsored by: Rubicon Communications, LLC ("Netgate")

Certain internet service providers transmit VLAN 0 priority tagged EAPOL frames from the ONT towards the residential gateway. VID 0 should be ignored, and the frame processed according to the priority set in the 802.1P bits and the encapsulated EtherType (i.e. EAPOL). The pcap filter utilized by l2_packet_* is inadquate for this use case. Here we modify the pcap filter on FreeBSD to accept both unencapsulated and encapsulated (with VLAN 0) EAPOL EtherTypes. This preserves the original filter behavior while also matching on encapsulated EAPOL. Additional work is required to support this handling on other platforms. We also modify the rx_receive handler to offset the packet buffer and length when handling dot1q encapsualted frames so the existing packet parsing code works as-is.

Certain internet service providers transmit vlanVLAN 0 priority tagged EAPOL frames from the ONT towards the residential gateway. VID 0 should be ignored, and the frame processed according to the priority set in the 802.1P bits and the encapsulated EtherType (i.e. EAPOL). The pcap filter utilized by l2_packet_* is inadquate for this use case. Here we modify the pcap filter on FreeBSD to accept both unencapsulated andd and encapsulated (with VLAN 0) EAPOL EtherTypes. This preserves the original filter behavior while also matching on encapsulated EAPOL. Sponsored by: Rubicon Communications, LLC ("Netgate")Additional work is required to support this handling on other platforms. We also modify the rx_receive handler to offset the packet buffer and length when handling dot1q encapsualted frames so the existing packet parsing code works as-is.