On Fri, May 30, 2008 at 5:22 PM, Tom Eastep <[EMAIL PROTECTED]> wrote:
> Tom Eastep wrote:
>
> A couple if points:
>>
>> a) Why the Linksys router? Why don't you just add a third NIC to the
>> Shorewall box and use Shorewall's multi-ISP capability?
>> http://www.shorewall.net/MultiISP.html
>>
>
Mainly because I could use the router's wireless functions. I already have a
wireless network however it's only a wireless nic connected to an external
antenna on the same shorewall router, bridged to eth0, running hostapd,
which is not very used. This is changing though, as a few users are
switching to notebooks, and using the linksys router I would have a boost on
signal, range and throughput for these new clients.
Of course I could still add the 3rd nic to the shorewall box and use the
router as a plain access point, however it would be "cleaner" for me to get
things working as I planned.
> b) Even with your proposed topology, you could use Shorewall's MultiISP
>> capability but you would need to understand a lot more about how it works
>> (no one is likely to write a HOWTO for anything like what you propose).
>>
>
>> And if you feel like you must use the Linksys, I would _still_ add a third
> NIC to the Shorewall box and connect that box to the Linksys with a
> crossover cable. And use Shorewall's MultiISP feature.
>
Well, it _is_ possible then. I haven't digged thru the documentation enough,
so I'm going to try my topology first, and if I don't succeed, I'll go your
way.
Just another thing, do you think shorewall 4 have any advantages over 3.x on
this particular matter?
Thanks for your reply.
Gustavo
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
