lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 30 Dec 2014 23:50:21 +0530 From: Siva Mannem <siva.mannem.lnx@...il.com> To: netdev@...r.kernel.org Subject: Clarification regarding IFLA_BRPORT_LEARNING_SYNC and aging of fdb entries learnt via br_fdb_external_learn_add() Hi, I am trying to understand the ongoing switch device offload effort and am following the discussions. I have a question regarding IFLA_BRPORT_LEARNING_SYNC flag and how aging happens when this flag is enabled on a port that is attached to a bridge that has vlan filtering enabled. If I understand correctly, when IFLA_BRPORT_LEARNING_SYNC is set on a bridge port, fdb entries that are learnt externally(may be learnt by hardware and driver is notified) are synced to bridges fdb using br_fdb_external_learn_add(). The fdb entries(fdb->added_by_external_learn set to true) that are learnt via this method are also deleted by the aging logic after the aging time even though L2 data forwadring happens in hardware. Is there a way where aging can be disabled for these entries? and let the entries be removed only via br_fdb_external_learn_delete()? or am I missing something? Regards, Siva. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists