Le jeudi 15 juin 2006 à 12:52 +0200, Tore Anderson a écrit : > close 373716 > quit > > * Jerome Warnier > > > 2) the initscript should ensure that the iptables rules are loaded, > > and load them if necessary. > > I feel I cannot do this. Munin has no authority over the iptables > ruleset, so I cannot just change them arbitrarily - that might cause > breakage. I know I'd be furious if a package did that to my ruleset. I can understand, I thought about this but I felt like the rules needed are not intrusive at all: iptables -A INPUT -d 192.168.0.1 iptables -A OUTPUT -s 192.168.0.1
Maybe the script should just verify if such accounting rules are present in chains INPUT and OUTPUT first. Then it could work. Or maybe a switch in /etc/default/munin-node? Another option: base ip_ on something else than iptables (maybe /proc or/sys?). > Besides, ip_ and if_ are orthogonal - ip_ graphs traffic to/from a > specific IP address, while if_ considers network interface traffic, > which might not be IP at all. I thought about this too, but then, I think you should: - provide a patch for Debian not to advertise a concerning warning message when using if_ (because here, my bug was actually the error message) and/or: - talk about this issue with upstream (forward upstream). > I'm therefore closing your bug report. I don't think it's fair, but I won't reopen it myself, and let you judge by yourself. I attach the initscript modified by a quick hack from me to make ip_ work for me, but would probably never be useful for anyone else. > Thanks Thanks anyway for your time. -- Jérôme Warnier <[EMAIL PROTECTED]> BeezNest
munin-node.init
Description: application/shellscript
