Comment 3 for bug 459554

Sure,

The output is in pt-BR, but I will try to translate to you after the
transcription:

leitao@amz:~$ sudo ufw disable
[sudo] password for leitao:
Filtro parado e desabilitado na inicialização do sistema
leitao@amz:~$ sudo ufw status
Estado: inativo
leitao@amz:~$ sudo ufw enable
Firewall está ativo e ativado no início do sistema
leitao@amz:~$ sudo ufw status
Estado: ativo

Para Ação De
---- ------ --
Apache Full ALLOW Anywhere
Bazaar ALLOW Anywhere
Samba ALLOW Anywhere
OpenSSH ALLOW Anywhere
CUPS ALLOW Anywhere
3306 ALLOW Anywhere
7234 ALLOW Anywhere
Redmine ALLOW Anywhere

The disable option has stopped the filters, as expected, and confirmed by
the following status option.

The enable option has restarted the funcions, as expected, and confirmed by
the following status option.

I can also confirm it since I have set my apache rule to allow access to a
different port than the traditional 80, but my apache settings still listen
to port 80 too. With the ufw disabled, I could navigate from other PC to
this IP:80 on a browser (amongst other obvious tests I did), and with ufw
enabled, I no longer could.

I the meantime, gufw never noticed any change, assuming it was always
disabled.

2009/10/24 Marcos <email address hidden>

> Hi!
> Can you do this test in the Terminal, please? Thanks!
> sudo ufw disable
> sudo ufw status
> sudo ufw enable
> sudo ufw status
>
> And tell me the exit of this commands :)
> Regards.
>
> --
> gufw wont detect the enabled state of ufw in karmic
> https://bugs.launchpad.net/bugs/459554
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Fábio Leitão
..-. .- -... .. --- .-.. . .. - .- --- ...-.-
&#70;&#97;&#98;&#105;&#111;&#32;&#76;&#101;&#105;&#74;&#97;&#111;
h0x46 h0x61 h0x62 h0x69 h0x6F h0x20 h0x4C h0x65 h0x69 h0x74 h0x61 h0x6F