Para saber si tu firewall esta filtrando (funcionando), checa si tiene
reglas activas. Si al ejecutar, como root:
# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
No recibes otro output que el de arriba, tu firewall no esta filtrando
nada. En
manolo wrote:
Me sale esto:
iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
El Domingo, 14 de Noviembre de 2004 22:17, escribió:
El linux lleva un corta fuegos integrado, el iptables, pero no tiene
ninguna instruccion para aceptar ni denegar asi que en principio no
tendrias que tener ningun problema por ahi. Observa bien que puertos
debes abrir puesto que muchos
Hola, saludos. Os parecera tonta pregunta, pero no se si tengo activo algun
firewall en mi debian sarge... yo no he instalado ninguno conscientemente, a
lo mejor durante la instalacion (NetInstall) se instalo alguno, pero lo
ignoro. ¿Como saberlo, por donde busco?
El problema es que estoy tras
--- manolo [EMAIL PROTECTED] escribió:
Hola, saludos. Os parecera tonta pregunta, pero no
se si tengo activo algun
firewall en mi debian sarge... yo no he instalado
ninguno conscientemente, a
lo mejor durante la instalacion (NetInstall) se
instalo alguno, pero lo
ignoro. ¿Como saberlo,
--- manolo [EMAIL PROTECTED] escribió:
El Domingo, 14 de Noviembre de 2004 17:19, escribió:
A que te refieres con que no se abre?
Pues lo escribo aqui:
http://www.adslayuda.com/TestPort.php
y siempre aparece cerrado
Que puerto??
Cualquiera, el 23456, por ejemplo
Que programa usa ese
manolo wrote:
Hola, saludos. Os parecera tonta pregunta, pero no se si tengo activo algun
firewall en mi debian sarge... yo no he instalado ninguno conscientemente, a
lo mejor durante la instalacion (NetInstall) se instalo alguno, pero lo
ignoro. ¿Como saberlo, por donde busco?
El problema
Incoming from Adi Linden:
On my system I put a firewall script in /etc/init.d and have it loaded on startup.
But this is on a LAN. You may want to do things differently for dial-up.
It's on a LAN. Sounds like everyone just rolls their own then, no standard
place to stick iptables rules.
Douglas == Douglas G Phillips [EMAIL PROTECTED] writes:
Adi Linden [EMAIL PROTECTED] writes:
In Debian/Sarge, where is the appropriate place for some iptables
rules to deny access to some local ports?
On my system I put a firewall script in /etc/init.d and have it
loaded on
On Fri, Oct 15, 2004 at 10:43:52AM -0400, Marc D Ronell wrote:
Douglas == Douglas G Phillips [EMAIL PROTECTED] writes:
On my system I put a firewall script in /etc/init.d
I concur and did the same.
That seems to be the default, but I wonder for how long. I don't
think I changed my
In Debian/Sarge, where is the appropriate place for some iptables rules to
deny access to some local ports?
Adi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Incoming from Adi Linden:
In Debian/Sarge, where is the appropriate place for some iptables rules to
deny access to some local ports?
Dunno about sarge, but there's a /etc/network/if-up.d/ here. If
you're using a modem, there's /etc/ppp/ip-up.d/
--
Any technology distinguishable from magic
Adi Linden [EMAIL PROTECTED] writes:
In Debian/Sarge, where is the appropriate place for some iptables rules to
deny access to some local ports?
On my system I put a firewall script in /etc/init.d and have it loaded on startup.
But this is on a LAN. You may want to do things differently
On my system I put a firewall script in /etc/init.d and have it loaded on startup.
But this is on a LAN. You may want to do things differently for dial-up.
It's on a LAN. Sounds like everyone just rolls their own then, no standard
place to stick iptables rules.
Adi
--
To UNSUBSCRIBE,
On 11 Jun 2004, Mike Chandler wrote:
On Friday 11 June 2004 07:30 pm, John Fleming wrote:
Is there anything analagous to pmfirewall in Sarge (2.6 kernel)? I
downloaded pmfirewall because I was familiar with it, but it's not
compatible with the 2.6 kernel. I need something newbie-easy that
Is there anything analagous to pmfirewall in Sarge (2.6 kernel)? I
downloaded pmfirewall because I was familiar with it, but it's not
compatible with the 2.6 kernel. I need something newbie-easy that I can
configure remotely. Thanks - John
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
On Friday 11 June 2004 07:30 pm, John Fleming wrote:
Is there anything analagous to pmfirewall in Sarge (2.6 kernel)? I
downloaded pmfirewall because I was familiar with it, but it's not
compatible with the 2.6 kernel. I need something newbie-easy that I can
configure remotely. Thanks -
On Friday 11 June 2004 07:30 pm, John Fleming wrote:
Is there anything analagous to pmfirewall in Sarge (2.6 kernel)? I
downloaded pmfirewall because I was familiar with it, but it's not
compatible with the 2.6 kernel. I need something newbie-easy that I can
configure remotely. Thanks
On Friday 11 June 2004 08:34 pm, John Fleming wrote:
On Friday 11 June 2004 07:30 pm, John Fleming wrote:
Is there anything analagous to pmfirewall in Sarge (2.6 kernel)? I
downloaded pmfirewall because I was familiar with it, but it's not
compatible with the 2.6 kernel. I need
John Fleming wrote:
Anyway, I think I will keep working on getting Firestarter going. What if
I'm using KDE and open a terminal -window- and then start firestarter - Will
that make the GUI appear??
As long as you call it up as root, yes.
Regards,
David.
--
To UNSUBSCRIBE, email to [EMAIL
an entry for Firestarter anywhere in the KDE menus (after appropriately
installing Firestarter). When I did the same things in Knoppix/Sid, I did
find the Firestarter entry in the KDE menus.
Um. Here was the answer to my similar query a bit back. Some new thing
(menu-xdg) you have to
21 matches
Mail list logo
