If you use iptables... set up explicit allow rules... for instance:
iptables -I INPUT 1 -s 202.a(network address) -i eth0 -j ACCEPT
iptables -I OUTPUT 1 -o 202.a(network address) -o eth0 -j ACCEPT
iptables -I OUTPUT 2 -o eth0 -j ACCEPT
This will setup the rules in the proper order, and you can r
Sorry, I meant to send:
(I wasn't sure what your network address(es) were, so replace 202.0.0.0/8 with
your information)
iptables -I INPUT 1 -s 202.0.0.0/8 -i eth0 -j ACCEPT
iptables -I INPUT 2 -i eth0 -j ACCEPT
iptables -I OUTPUT 1 -o 202.0.0.0/8 -o eth0 -j ACCEPT
iptables -I OUTPUT 2 -o eth0 -
I have a wierd error from when I tried to upgrade a system from stable/woody (a
few sarge packages like snort) to SID.
I understand SID is a bit unstable (thus Still in Development)...
Any ideas what could be causing /usr/bin/du to be undeletable? I can't write a C
program to delete it, I can't de
s exact same problem. I found it had been rootkitted. YMMV.
>
> It could be something else but I'd check anyway.
>
> Regards,
>
> Brad Lay
> ([EMAIL PROTECTED])
>
>
> On Wed, 2 Apr 2003, Roger Ward wrote:
>
> > I have a wierd error from when I tried
I have a wierd error from when I tried to upgrade a system from stable/woody (a
few sarge packages like snort) to SID.
I understand SID is a bit unstable (thus Still in Development)...
Any ideas what could be causing /usr/bin/du to be undeletable? I can't write a C
program to delete it, I can't de
s exact same problem. I found it had been rootkitted. YMMV.
>
> It could be something else but I'd check anyway.
>
> Regards,
>
> Brad Lay
> ([EMAIL PROTECTED])
>
>
> On Wed, 2 Apr 2003, Roger Ward wrote:
>
> > I have a wierd error from when I tried
6 matches
Mail list logo