[nftables 0.9.2 | flow table] dynamic (soft) NETDEV

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



With some (soft) NETDEV being available only after NFT been invoked at
boot time, e.g. bridge or pppoe, NFT would fail to load at boot time if
such NETDEV being stipulated, e.g.

flowtable f { hook ingress priority 0; devices = { pppoe-wan, lan0,
lan1, lan2, lan3, lan4, br-lan }; }

Is there a syntax that would allow to add/alter such dynamic dev to an
initial stanza, e.g.

flowtable f { hook ingress priority 0; devices = { lan0, lan1, lan2,
lan3, lan4 }; }

and then adding pppoe-* and/or br-* to it? Or is there any other good
practice, e.g. are dynamic sets are working with flowtable device =?




[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux