On Thu, 22 Jun 2006 15:12:31 +1200 Andy George <[EMAIL PROTECTED]> wrote:
> Correct. I dont have to maintain a heartbeat at all. UTP cable to > modem (which is only a means of transport), the GATEWAY does the NAT and > Routing and so forth... Haven't had to do anything with heartbeats since I last used thick ethernet, and that was in the 80's! > > I use IPCop as the Gateway, and it just works.. No intervention from me > required. Your wireless/wired setup sounds just the ticket. I'm > interested in how the wireless part of this goes, cause thinking of > doing a wireless home setup myself in the near future... Linux based of > course... IPCop is fine, despite Volker's prejudices. The wireless bit is only an extra DMZ with prority between the existing DMZ and your internal network interfaces, so don't expect anything dondrous. I don't think that there's the possibility to run a wireless interface as an AP off it, although a) I haven't read up on it, and b) I haven't tried. Maybe I will whilst the managed cisco router is installed in place of my IPCop box ( tc are trying to find out what's wrong with our ADSL line! ). I've tried a lot of the dedicated linux wireless distro's, and have settled on voyage as the best ap software. I'm currently working on extending it to also run asterisk, which is fun! > > > > > In AU TCC requires software to put a heart beat on the line. I think > > you've indirectly said that there's no such thing required here. The > > modem just gives you a live ip which you then host. No pppoe software > > required either. > > > > I'll put a second nic in the debian box then use it to nat for a > > wireless and wired network via a switch. Hopefully you won't be putting any content on your firewall this time (^: > > > > Thanks to all for the response. > > > > Cheers Don > > > > > > > Steve
