Any carrier can forward this dmac 01:80:c2:00:00:03. I am not sure how they can handle etype 0x888e (EAPOL): forward or drop
I will PoC that On Sat, May 9, 2015 at 2:04 AM, Aaron DuShey <adus...@gmail.com> wrote: > Correction on the dmac. The correct multicast dmac is 01:80:c2:00:00:03. > > On Fri, May 8, 2015 at 10:33 AM, Aaron DuShey <adus...@gmail.com> wrote: > >> Depends on the carrier. Find out how they handle a multicast dmac --, >> etype 0x888e (EAPOL). If they cannot forward, some flavors of IOS XE >> support a custom EAPOL destination address(see link). I believe there is a >> feature request in to add a similar feature to IOS-ask your Cisco AM for >> more detail. >> >> >> http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/macsec/configuration/xe-3s/macsec-xe-3s-book.html#task_7BBF3B2C5C66466693AFDF9B72BDD381 >> >> Regards, >> Aaron >> >> On Thu, May 7, 2015 at 3:55 PM, Manu Chao <linux.ya...@gmail.com> wrote: >> >>> Is following 802.1AE MACsec over Non-MACsec Ethernet Transit supported? >>> >>> 3750X_SM_MACsec_SW1 <-> MAN Ethernet Provider <-> 3750X_SM_MACsec_SW2 >>> >> > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
