On Monday 22 September 2003 6:54 pm, pheonix1t wrote: Thanks to phoenix1t, Josh , Tom and Bruce for their replies ... <snipped>
smoothwall would probably be better, needs less memory than suse
I take it that it needs two nics, right? (Modem to firewall, firewall to router)
yes, check the HCL from smoothwall for supported NICs.
I'll check out smoothwall and see what it can do. As Bruce mentioned (in a later post) having a linux firewall is probably overkill, so this will be more of a learning experience / toy than a necessity.
Is the setup modem > firewall > router > computer land ?
i thought you'd expect ....ISP modem>linux firewall>switch>computers If you get a good switch, you don't need the router (linux is taking care of router functions), unless I'm not understanding this correctly?
This is still in the dreaming period of planning. I have a small LAN connected through a hub, with 1 main computer, 2 old PCs, an old Mac and hopefully apple's new g5. I'd like for all of them to have cable access. I know the definitions of router and switch but haven't actually configured either. I'm also poor and I thought switches were more expensive than routers.In fact I'm only getting the internet access because it will come through my job at Comcast. If you could point out some good info for the right time to use a switch versus a router I'd appreciate it. Or how to have linux take care of the routing info. TIA -- Franklin Maurer Using SuSE 8.2 Pro