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 linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 31 May 2010 21:51:17 +0200 (CEST) From: Jan Engelhardt <jengelh@...ozas.de> To: Luciano Coelho <luciano.coelho@...ia.com> cc: ext Patrick McHardy <kaber@...sh.net>, "netfilter-devel@...r.kernel.org" <netfilter-devel@...r.kernel.org>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, Timo Teras <timo.teras@....fi> Subject: Re: [RFC] netfilter: WIP: Xtables idletimer target implementation On Monday 2010-05-31 21:12, Luciano Coelho wrote: > >I considered this option, but then I didn't find a proper place where to >include the attribute in sysfs, since I cannot add it as part of the >interface (eg. /sys/class/net/wlan0/idletimer) as I was doing before. You couldn't have done that before either, because the interface name in ipt_ip may refer to an interface that does not exist at all times. >The other option would be to make the idletimer as part of the >xt_IDLETIMER module object in sysfs >(ie. /sys/module/xt_IDLETIMER/<user_supplied_name>), but it looks out of >place. I like it. It follows /proc/net/xt_{hashlimit,recent}/<user_supplied_name>. >And I think adding it as /sys/class/net/idletimer is most likely >out of the question. It follows /sys/class/leds/... I'm impartial though. -- 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