From: Andrew Beverley <andy@andybev.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Ricardo Klein <klein.rfk@gmail.com>,
Nick Khamis <symack@gmail.com>,
netfilter <netfilter@vger.kernel.org>
Subject: Re: Dabase BAcked IPTables
Date: Sat, 29 Jun 2013 21:10:35 +0100 [thread overview]
Message-ID: <1372536635.3924.89.camel@andrew-desktop> (raw)
In-Reply-To: <alpine.DEB.2.00.1306292014350.26742@blackhole.kfki.hu>
On Sat, 2013-06-29 at 20:19 +0200, Jozsef Kadlecsik wrote:
> > > * User logs into the website, and provides mac address
> > > * We insert the record in the database as an allow rule...
> > > * Restart iptables?
>
> That's pretty similar to a captive portal, which is quite simple to setup:
> you need a small webpage written say in PHP (IP and MAC can be gathered
> directly if the webserver is on the same LAN) and a bitmap:ip,mac type of
> set with timeout, and some static iptables rules. It's almost trivial if
> the things run on the gateway.
And an example is here:
http://www.andybev.com/index.php/Using_iptables_and_PHP_to_create_a_captive_portal
Except it does not use ipset, which would be a *much* better way of
implementing it ;-)
next prev parent reply other threads:[~2013-06-29 20:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 15:01 Dabase BAcked IPTables Nick Khamis
2013-06-28 15:12 ` Ricardo Klein
2013-06-29 18:19 ` Jozsef Kadlecsik
2013-06-29 20:10 ` Andrew Beverley [this message]
2013-06-29 20:39 ` Nick Khamis
2013-06-29 21:00 ` Neal Murphy
2013-06-29 23:12 ` Nick Khamis
2013-06-30 12:13 ` Dash Four
2013-06-30 13:27 ` Nick Khamis
2013-06-28 23:19 ` /dev/rob0
2013-06-29 0:00 ` Ricardo Klein
2013-06-29 0:05 ` Nick Khamis
2013-06-29 0:28 ` /dev/rob0
2013-06-29 1:21 ` Nick Khamis
2013-06-29 14:47 ` Eliezer Croitoru
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=1372536635.3924.89.camel@andrew-desktop \
--to=andy@andybev.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=klein.rfk@gmail.com \
--cc=netfilter@vger.kernel.org \
--cc=symack@gmail.com \
/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