<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
Indeed the ID of the network interface was added to the name of the
firewall rules, but quite recently. 1.1.4 did not have this
feature. I'd suggest the latest svn or latest release which is
20090925 whose sources and some packages you can find at
<a class="moz-txt-link-freetext" href="http://sourceforge.net/projects/wifidog/">http://sourceforge.net/projects/wifidog/</a><br>
<br>
Geneviève<br>
<br>
On 11-09-14 11:09 AM, acv wrote:
<blockquote cite="mid:20110914150945.GD91329@miniguru.ca"
type="cite">
<pre wrap="">On Wed, Sep 14, 2011 at 10:51:49AM -0400, Marc Delisle wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
Thanks Alex,
our situation is that we need to add an address block for our numerous
clients and due to another constraint, we cannot change the addressing
scheme which is currently using a /24.
If I understand you correctly, Wifidog (I'm using version 1.1.4) does
not expect to create the appropriate iptables rules for two instances?
</pre>
</blockquote>
<pre wrap="">
As of the current version in SVN (I don't remember if it's 1.1.4) the firewall
tables have an ID value in their names so multiple instances can run. I just
referred to rules like the captive portal mangle rules, I think as long as
it's a different network interface (i.e.: eth0 and eth1) then it shouldn't
have any conflicts.
Alexandre
</pre>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
WiFiDog mailing list
<a class="moz-txt-link-abbreviated" href="mailto:WiFiDog@listes.ilesansfil.org">WiFiDog@listes.ilesansfil.org</a>
<a class="moz-txt-link-freetext" href="http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog">http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog</a></pre>
</blockquote>
<br>
</body>
</html>