Interface config is very simple: interface GigabitEthernet0/0 ip address ...... ipv6 address ..... no ip proxy-arp no mop enabled duplex auto speed auto
The question is really why destination MAC 0000.0000.0000 passes behind PHY/mac_filter on this platform and whether such behavior should be generally considered wrong. It's not the case on other Cisco platforms. Thx 2017-05-08 10:57 GMT+02:00 Saku Ytti <s...@ytti.fi>: > Hey, > > I'm not sure why this is relevant? > > OP is asking if frame should have passed PHY/mac_filter, If L3 port > receives frame, it does not care about L2 headers, it'll just forward > it based on L3, and generates new L2 rewrite on egress. > > _______________________________________________ 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/
