From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Firewall Question
Date: Sat, 13 Oct 2012 19:18:29 +0200 [thread overview]
Message-ID: <1350148709.1206.3.camel@hughes.tremer.info> (raw)
In-Reply-To: <5079610A.3020507@oab.de>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
Hey Alex,
On Sat, 2012-10-13 at 14:39 +0200, Alexander Marx wrote:
> Dear developers.
>
> Are there any plans to implement the possibillity to create firewall
> rules for openvpn subnets?
> Actually all vpn connections are able to do anything in the remotenetwork
> The only solution is to put own iptables rule in the
> /etc/sysconfig/firewall.local
No, there are currently no plans to do that.
/etc/sysconfig/firewall.local is a mighty way to do these rules,
although it is not very nice to type them. Agreed.
> I already tried to play with the OVPNFORWARD Chain but had no luck.
You should use CUSTOMFORWARD/CUSTOMINPUT for those rules.
> It would be great if one can say:
> Hey, VPN1 is only allowed to connect to my internal servers 192.168.0.2
> and 192.168.0.3 via RDP (3389)
> ans that via gui
You can use the outgoing firewall to limit some sorts of traffic, but
you cannot block incoming packets with it.
> I already developed addons for ipcop, but ipfire seems complete different...
No, the web UI is pretty much the same (crap). The firewall scripts do
not differ too much, either.
> Greetings
> Al
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
next prev parent reply other threads:[~2012-10-13 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 12:39 Alexander Marx
2012-10-13 17:18 ` Michael Tremer [this message]
[not found] <5079AABC.4020104@oab.de>
2012-10-17 10:08 ` 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=1350148709.1206.3.camel@hughes.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@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