What i meant is, grab one of these, 
http://downloads.smoothwall.org/source/2.0/smoothwall-2.0.src.tar.gz 
for example, it will build a smoothwall for you entirely from source. Now what 
you really want is download an extra module compile it and (plant) it among 
the modules for your smoothwall kernel. Now you have a failover capability, 
configure it according to the instructions on your newly built firewall, and 
make sure you have plenty of connections and nicks to fail-over-to. Very 
similar scenario goes for ipCop. So you actually create a new install image 
and use that for your customers.
Cheers
Szemir

On January 27, 2007 00:17, Jon wrote:
> I sincerely wish I was smart enough to know what you were talking about :)
>
> J
>
> bogi wrote:
> > You could allways add a bonding device and set it up with multiple nicks,
> > than you would have multiple isp failover. I have tried the bonding
> > device setup, and it works very well. You could build it into either
> > ipcop or smoothwall, since both make source code distributions of
> > themselves available, just rebuild them with the bonding module available
> > as a module for the kernel. The rest of the configuration , while not
> > simple, is straight foreword.
> >
> > http://linux-net.osdl.org/index.php/Bonding
> > http://www.kernel.org/pub/linux/kernel/people/marcelo/linux-2.4/Documenta
> >tion/networking/bonding.txt http://linux-ip.net/html/ether-bonding.html
> >
> > Cheers
> > Szemir
> >
> > On January 26, 2007 16:14, Jon wrote:
> >> Kevin Anderson wrote:
> >>> like the dual ISP ability.
> >>
> >> Hot failover? We have a couple of sites looking for this capability.
> >>
> >> J
> >
> > _______________________________________________
> > clug-talk mailing list
> > [email protected]
> > http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> > Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> > **Please remove these lines when replying

_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to