public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: Thomas Berthel <t.berthel@gmx.net>
To: documentation@lists.ipfire.org
Subject: Re: VLAN Konfig
Date: Sun, 09 Jun 2013 13:58:42 +0200	[thread overview]
Message-ID: <51B46DF2.9050905@gmx.net> (raw)
In-Reply-To: <A74BA195-E17C-4CD6-A81A-DC0E246BF1E2@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2131 bytes --]


> I meant in this section --> http://wiki.ipfire.org/de/optimization/vlan/start#iptables_uebersicht are only spts: to be seen, but no dpts: in the rules you define "--dports 993,995,110,587,465" but they are listed as "spts:" (source ports) for example i have in the iptables -L listing for Mail something like this
> RETURN     tcp  --  192.168.7.0/24      anywhere             multiport dports imaps,urd,submission,pop3s,smtp TIME from 00:00:00 to 00:00:00 UTC
> so the dports are specified. I can´t find something like that in your iptables -L listing.

Ah. I'm using dport for single port (dpts:52 for DNS) an multiport
dports for more destination ports, is this not okay?

> So you have allowed only unprivileged ports as a source port, but isn´t it that the case per default anyway ? Or do you regard a security method with this ? 
> So i´am also not sure with this, but if you define only --dports isn´t it the same behavior anyway with the source port then you defined it ?

is this a default? Sorry, i don't now. Is that so wrong?

> What rules do you use in Mode 1 ?

A lot of rules ;) I can't post it here... one snipp: DNS, Mail,
Game-Ports, Whois, FTP, NTP and ssh for green, red and all interfaces.

But these rules are all double in my tables after the restart. Another
problem is when I usually re-upload my FW mode 0 although the WUI shows
me mode 1.

I have all my ports manually specified are no longer seen in the tables,
only when I reboot the FW.

> Ahh O.K. but is it possible to arrange rules for the VLAN interfaces over the WUI (e.g. DMZ pinnholes, etc...) ?
> So maybe it is less complicated (especially for the explanations in the wiki) if all the rules which can be arranged over the WUI will be set in that way ? MIght be nice if you can go for a try . So also if the outgoing FW will be configured, i think the CUSTOMFORWARD rules are defined then in the FORWARD and OUTPUT chains.

I just tested it on wui and FW mode 1 do not apply the rules. It seems
as if for wireless (blue) and the rule come from a different direction
no matter what is stored in the WUI.


       reply	other threads:[~2013-06-09 11:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A74BA195-E17C-4CD6-A81A-DC0E246BF1E2@ipfire.org>
2013-06-09 11:58 ` Thomas Berthel [this message]
2013-06-09 13:31   ` Erik K.
2013-06-09 16:40     ` Thomas Berthel
     [not found] <51D03494.7090008@gmx.net>
2013-07-01  9:53 ` Michael Tremer
2013-07-01 22:14   ` Thomas Berthel
2013-07-21 20:35     ` Thomas Berthel
2013-07-22  8:37       ` Michael Tremer
2013-08-08 18:12         ` Thomas Berthel
2013-08-08 18:24           ` Thomas Berthel
2013-06-08 11:42 Thomas Berthel
2013-06-09  4:54 ` Erik K.
2013-06-09  7:37   ` Thomas Berthel
2013-06-10 10:22 ` Michael Tremer

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=51B46DF2.9050905@gmx.net \
    --to=t.berthel@gmx.net \
    --cc=documentation@lists.ipfire.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