Peer Guardian for linux

o peer guardian na é um programa ke bloqueia ips perigosos?

O shorewall tem essa função (sem ser bloquear os ips manualmente) ?
 
Em traços gerais, a Shorewall não é mais do que um GUI (em modo texto) para as iptables.

Acrescenta também umas umas protecções extra a diversos ataques de DoS, entre outros.

Mas não contém nenhuma lista com ip's considerados "bad".
 
entao nao é nenhuma alternativa ao peer guardian, suponho.

Eu tb uso essa firewall, basicamente facilita a configuraçao das iptables, e dá para bloquear ips, mas com a tua conversa pensei que houvesse uma forma de actualizar essa lista automaticamente :)
 
Para quem posso ter dificuldades em instalar:

http://3v1n0.tuxfamily.org/dists/feisty/3v1n0/

Mais propriamente em:

http://3v1n0.tuxfamily.org/pool/feisty/3v1n0/moblock-ipq_0.8-14+3v1ubuntu0_i386.deb

e

http://3v1n0.tuxfamily.org/pool/feisty/3v1n0/moblock-nfq_0.8-14+3v1ubuntu0_i386.deb

Para verificar se apos instalação os blocks existem:

@ bash > tail -f /var/log/moblock.log

Para editar as listas em termos de blocks

Re: Moblock (peerguardian linux alternative)
ok got it

first
Code:

sudo gedit /etc/moblock/MoBlock-nfq.sh

then find,
WHITE_TCP_OUT="http https"

and amsn uses port 1863 so I changed it to this

WHITE_TCP_OUT="http https 1863"

then I simply did

Code:

sudo /etc/init.d/moblock-nfq restart

and I am now connected, able to send and receive messages. btw if anyone sees a problem with this plx feel free to point it out.

ok upon further investigation I found if I allow IN on 1863 I can get the full functionality such as nudges. Also this method works only if the allow over http doenst work. kept giving me a wrong username password error.

Posted @ ubuntu forums here:

http://ubuntuforums.org/showpost.php?p=1146376&postcount=25

Abraços ;)
 
Infelizmente apaguei a minutos :|

Enfim..

Vou a procura ;)

Já agora, alguem me consegue explicar como endereçar uma range ou um "name" a white list, ou a exeption list? É que o Steam anda sp a ser bloqueado, e eu tinha o meu Pg2 @ Windows sp configurado, aqui tb quero, só não consigo perceber onde e como editar..

Obrigado
 
Alguma ajuda please?

Fico meio a nora, se alguem com mais conhecimentos me pudesse ajudar agradecia, visto que estou sempre a aprender ;)

Por ex: Blocked OUT: Microsoft Corp,hits: 1,DST: 207.46.232.182
Blocked OUT: Microsoft Corp,hits: 2,DST: 207.46.232.182
Blocked OUT: Microsoft Corp,hits: 3,DST: 207.46.232.182


O Startup é este, tentei adicionar as ranges do steam, mas devo de estar a fazer algo mal:

#!/bin/sh
#
# MoBlock.sh - MoBlock start script
# ---------------------------------

ACTIVATE_CHAINS=1
WHITE_TCP_IN="72.165.61.166 72.165.61.188"
WHITE_UDP_IN="72.165.61.166 72.165.61.188"
WHITE_TCP_OUT="72.165.61.166 72.165.61.188 http https "
WHITE_UDP_OUT="72.165.61.166 72.165.61.188"
WHITE_TCP_FORWARD="72.165.61.166 72.165.61.188"
WHITE_UDP_FORWARD="72.165.61.166 72.165.61.188"


PIDF=/var/run/moblock.pid

FNAME=`basename $0 .sh`
MODE=`echo $FNAME|awk -F- '{print $2}'`

if [ -f $PIDF ]; then
PID=`cat $PIDF`
if [ `ps -p $PID|wc -l` -gt 1 ]; then
echo "$0: $PIDF exists and processs seems to be running. Exiting."
exit 1;
fi;
fi;

if [ -f /usr/bin/moblock-ipq ]; then
modprobe ip_queue
TARGET="QUEUE"
elif [ -f /usr/bin/moblock-nfq ]; then
modprobe ipt_NFQUEUE
TARGET="NFQUEUE"
fi;

modprobe ipt_state

# Filter all traffic, edit for your needs

iptables -N MOBLOCK_IN
iptables -N MOBLOCK_OUT
iptables -N MOBLOCK_FW

if [ $ACTIVATE_CHAINS -eq 1 ]; then
iptables -I INPUT -p all -m state --state NEW -j MOBLOCK_IN
iptables -I OUTPUT -p all -m state --state NEW -j MOBLOCK_OUT
iptables -I FORWARD -p all -m state --state NEW -j MOBLOCK_FW
fi;


iptables -I MOBLOCK_IN -p all -j $TARGET
#iptables -I MOBLOCK_IN -m state --state ESTABLISHED,RELATED -j ACCEPT

iptables -I MOBLOCK_OUT -p all -j $TARGET
#iptables -I MOBLOCK_OUT -m state --state ESTABLISHED,RELATED -j ACCEPT

iptables -I MOBLOCK_FW -p all -j $TARGET
#iptables -I MOBLOCK_FW -m state --state ESTABLISHED,RELATED -j ACCEPT

for PORT in $WHITE_TCP_OUT; do
iptables -I MOBLOCK_OUT -p tcp --dport $PORT -j ACCEPT
done
for PORT in $WHITE_UDP_OUT; do
iptables -I MOBLOCK_OUT -p udp --dport $PORT -j ACCEPT
done

for PORT in $WHITE_TCP_IN; do
iptables -I MOBLOCK_IN -p tcp --dport $PORT -j ACCEPT
done
for PORT in $WHITE_UDP_IN; do
iptables -I MOBLOCK_IN -p udp --dport $PORT -j ACCEPT
done

for PORT in $WHITE_TCP_FORWARD; do
iptables -I MOBLOCK_FW -p tcp --dport $PORT -j ACCEPT
done
for PORT in $WHITE_UDP_FORWARD; do
iptables -I MOBLOCK_FW -p udp --dport $PORT -j ACCEPT
done


# Loopback traffic fix

iptables -I INPUT -p all -i lo -j ACCEPT
iptables -I OUTPUT -p all -o lo -j ACCEPT

# Here you can change block list and log files
/usr/bin/moblock $@

# On exit delete the rules we added

if [ $ACTIVATE_CHAINS -eq 1 ]; then
iptables -D INPUT -p all -m state --state NEW -j MOBLOCK_IN
iptables -D OUTPUT -p all -m state --state NEW -j MOBLOCK_OUT
iptables -D FORWARD -p all -m state --state NEW -j MOBLOCK_FW
fi;

iptables -D INPUT -p all -i lo -j ACCEPT
iptables -D OUTPUT -p all -o lo -j ACCEPT

iptables -F MOBLOCK_IN
iptables -X MOBLOCK_IN
iptables -F MOBLOCK_OUT
iptables -X MOBLOCK_OUT
iptables -F MOBLOCK_FW
iptables -X MOBLOCK_FW

if [ -f $PIDF ]; then
rm $PIDF;
fi
 
Back
Topo