Quote:
I can't see ICS being better than using an actual hardware router.
|
I`ve used ics in Linux now for the whole 15 months practically and it`s been great for our needs.
Having 2 bb connections kinda put off the need for any router at first i suppose,especially with only the 2 machines.As more have been added though ics and the little switching hub i have been just as good....if not better than a router would be......in some ways that is.
Both desktops here(mine & girls) can act as router/firewall/gateway depending on which connection is being shared around the rest of the house and as everything usually runs through my machine beforehand everything is so easy to control & monitor.
Everything is filtered as appropriate for relevant machines and i`m happy to say we`ve never had a problem.All machines are quite capable of recieving the full 20Mb...when we`re getting the full 20Mb of course
I have access to all internal machines(kids) as it were with ssh & vnc etc but none of them have access to me....purely because nothing like that runs on this machine of course.
Always have all ports closed & icmp filtering always on in firestarter so anything that is`nt some requsted web page is dropped at that the door so to speak.
Plenty blocked connections but not much else.
Quote:
I keep get firestarter startup failed... on boot yet it appears to be active when you run the GUI
Today 20:55
|
The only time i`ve had firestarter "fail" is when my network settings have been wrong,such as having my eth0 & eth1 mixed up etc.
A mistake many seem to make is assuming firestarter should be left to run or made to run at startup etc(or assuming firestarter IS the firewall etc).This is NOT the case of course...
Firestarter is merely a gui frontend for iptables and whenever your "configuring" is done you should close firestarter again.