Re: Cable Modem and Routing

["Dan Downs" <retnuh@xxxxxxxxxx>]

> Why do you need the bridging stuff to act as a router?  Or does this (now)
> include other functionality as well?

Tell you the truth, I'm not sure, I just remember compiling in the modules
listed in a HOWTO, or a web site I found on it. This was at least a year
ago, so I don't fully remember. The setup had two NICs that were fast
fowarding between them. One to the cable modem, and one to the internal
network. I don't know if that requires bridging or not.

I haven't compiled a kernel to do this in so long I can't remember the exact
kernel modules that are required, I just remember that we had a bunch of the
routing and masqing stuff compiled in.

Either way check out the help on the network kernel modules if you're not
sure if something might be required.

> >3: Make sure you have a firewall. Email me if you want one, I've got a
> >copy  of the one they used. I use it at work to masq a modem connection.
>
> Isn't the box connected to the cable modem acting as a firewall?  I use
> "floppyfw" for my DSL connection box, and it's great stuff.  No HD to fail
or
> get hacked.

Maybe I wasn't clear enough, the linux box is the firewall/router/dhcp
server. We were using the box for a bit more than a router, telnet and ftp
mainly. The CPU usage was so low that for awhile they were running seti@home
on it.

I like the floppyfw idea, I'll have to keep that in mind.

Dan Downs