public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Questions for adding code
Date: Wed, 17 Oct 2012 12:13:50 +0200	[thread overview]
Message-ID: <1350468830.9815.61.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <507CF735.3060404@oab.de>

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

On Tue, 2012-10-16 at 07:57 +0200, Alexander Marx wrote:
> As i only know ipcop, i hope you can help me here.
> I am thinking of developing some extracode for being able to
> configure 
> vpn-Firewall rules via WUI.
> 
> I don't know how to start.

Well, let's see then. You won't need a build environment in the first
place. Just set up a virtual machine and add your changes. If you got it
all working, we will bother to get things into the source tree.

> I just want to create a cgi, that is similar to the outgoing firewall
> with the exception that this
> configures the CUSTOMFORWARD Chain.

Go to /srv/web/ipfire/cgi-bin and copy a CGI script that is very similar
to what you want to do. For example the outgoing firewall script.

Then edit it until it does what you want it to do.

> The gui should create a txt file with the rules.... 

For example that. Create a basic configuration file and just build the
CGI that edits this configuration file.

When you are done, start with the script that actually adds firewall
rules.

> 
> I need to know:
> 
> 1) Where should i beginn to make ipfire read the rules on boot?!

The firewall is initialized in /etc/init.d/firewall.

> 2) How do i implement the code in the checked-out git repository
> local?

CGI scripts go to html/cgi-bin/. All necessary configuration files have
to be created in lfs/cfgroot.
But again, first get this stuff working. We will see how to merge those
files when it is time for that.

Michael


           reply	other threads:[~2012-10-17 10:13 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <507CF735.3060404@oab.de>]

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=1350468830.9815.61.camel@rice-oxley.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