Le jeudi 15 juin 2006 à 15:11 +0200, Tore Anderson a écrit :
[..]
> * Jérôme Warnier
>
> > 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
>
> So if you're DROP-ing t
reopen 373716
clone 373716 -1
retitle 373716 if_ shouldn't claim ip_ is a direct alternative
severity 373716 minor
tags 373716 upstream
retitle -1 ip_ needs to be run as root to work properly
quit
* Jérôme Warnier
> I can understand, I thought about this but I felt like the rules
> needed are not
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, s
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
Package: munin-node
Version: 1.2.3-1
Severity: normal
It seems that the if_ plugin is deprecated, because it doesn't fit well
with 100Mbits and 1Gbs interfaces, where the counter can grow too
fast, and overflow.
So, as suggested in the interface when using if_, please use ip_
instead.
To allow th
5 matches
Mail list logo