From: Eric Martin <freak4uxxx@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is this firewall safe?
Date: Mon, 27 Apr 2009 15:35:22 -0400 [thread overview]
Message-ID: <49F608FA.7030007@gmail.com> (raw)
In-Reply-To: <93d30e950904241053x55b9f169x887296edc4a74830@mail.gmail.com>
Marco wrote:
> On Fri, Apr 24, 2009 at 4:59 PM, Eric Martin <freak4uxxx@gmail.com> wrote:
>
>> Marco wrote:
>>
>>> Hi all,
>>>
>>> I set up my first firewall on my notebook (not running any services
>>> reachable from outside) using iptables. Since I am new to the topic,
>>> could you please verify if the output of 'iptables -L -v' is
>>> considered to be a safe firewall? Thanks!
>>>
>>> Chain INPUT (policy DROP 0 packets, 0 bytes)
>>> pkts bytes target prot opt in out source
>>> destination
>>> 0 0 ACCEPT all -- lo any anywhere
>>> anywhere
>>> 0 0 ACCEPT all -- eth0 any anywhere
>>> anywhere state RELATED,ESTABLISHED
>>> 0 0 REJECT tcp -- eth0 any anywhere
>>> anywhere reject-with tcp-reset
>>> 0 0 REJECT udp -- eth0 any anywhere
>>> anywhere reject-with icmp-port-unreachable
>>> 0 0 DROP udp -- eth0 any anywhere
>>> anywhere udp spt:bootps
>>> 0 0 LOG all -- eth0 any anywhere
>>> anywhere LOG level warning prefix `INPUT '
>>> 1 79 ACCEPT all -- wlan0 any anywhere
>>> anywhere state RELATED,ESTABLISHED
>>> 0 0 REJECT tcp -- wlan0 any anywhere
>>> anywhere reject-with tcp-reset
>>> 0 0 REJECT udp -- wlan0 any anywhere
>>> anywhere reject-with icmp-port-unreachable
>>> 0 0 DROP udp -- wlan0 any anywhere
>>> anywhere udp spt:bootps
>>> 0 0 LOG all -- wlan0 any anywhere
>>> anywhere LOG level warning prefix `INPUT '
>>>
>>> Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
>>> pkts bytes target prot opt in out source
>>> destination
>>> 0 0 LOG all -- any any anywhere
>>> anywhere LOG level warning prefix `FORWARD '
>>> 0 0 LOG all -- any any anywhere
>>> anywhere LOG level warning prefix `FORWARD '
>>>
>>> Chain OUTPUT (policy ACCEPT 5 packets, 1691 bytes)
>>> pkts bytes target prot opt in out source
>>> destination
>>> 0 0 ACCEPT all -- any lo anywhere
>>> anywhere
>>> 0 0 LOG all -- any eth0 anywhere
>>> anywhere LOG level warning prefix `OUTPUT '
>>> 1 52 LOG all -- any wlan0 anywhere
>>> anywhere LOG level warning prefix `OUTPUT '
>>>
>>>
>
<snip>
> Sorry for the bad format. gmail decided to insert some sub ideal pagebreaks...
>
> Talking about the 1 log line at the bottom you mean I should configure
> it to not specify an interface (eth0, wlan0)?
>
> Thanks!
>
>
Yeah, not specifying an interface for the log rule to apply to will make
it catch all interfaces (including lo but all traffic has already been
approved ahead of time so it won't catch).
next prev parent reply other threads:[~2009-04-27 19:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 15:28 [gentoo-user] Is this firewall safe? Marco
2009-04-24 16:59 ` Eric Martin
2009-04-24 17:53 ` Marco
2009-04-27 19:35 ` Eric Martin [this message]
2009-04-24 17:00 ` Chris Frederick
2009-04-24 17:05 ` Hazen Valliant-Saunders
2009-04-24 18:20 ` Marco
2009-04-24 17:23 ` Daniel Troeder
2009-04-24 18:40 ` Marco
2009-04-24 19:38 ` Daniel Troeder
2009-04-24 21:28 ` Chris Frederick
2009-04-27 18:56 ` Daniel Troeder
2009-04-27 20:03 ` Alan McKinnon
2009-04-24 18:18 ` Marco
2009-04-24 18:26 ` Marco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49F608FA.7030007@gmail.com \
--to=freak4uxxx@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox