[Re: [lug] DSL question]

[PC Drew]

Thus spake Justin on Sunday, April 23, 2000, 11:38:12 AM:


J> I'm kinda confused now. The scenario I am trying to complete is this. My linux
J> router box has two eth interfaces eth0 and eth1. Since the Cisco router comes
J> pre configured in bridging mode (ie: no routing functions) I have it connected
J> to eth0 in my linux box. Then eth1 (192.168.1.1) goes to my hub on the
J> internal network and this I use as my gateway for my other machines (ipchains
J> does the masq'ing/routing for the interfaces). I 'plan' on configuring eth0
J> with the DSL static ip and dns info. This way my linux box acts as my frontend
J> firewall, ftp server, webserver, blah blah. Anyhow, that is how I had it setup
J> on my cable modem. Are these other options that you have been talking about
J> "better" with the cisco router features? 

Everything that you've described above is great for a DSL MODEM or a
Cable MODEM.  What you've got now is a DSL ROUTER.  This means that
you can serve your entire network with out the need for a linux
machine.  Using PPP, your DSL router has the static IP address and DNS
info contained inside it.  You can setup filters to deny/allow
packets, port forwarding to allow packets to go to a certain machine,
etc.

This way, you setup your DSL router the same way your T1 router would
be setup at an office.  You plug the router into the same switch as
your other machines.  You setup the default gateway on all of the
other machines to be 10.0.0.1 (the default internal IP address of the
Cisco 675).  Now you've got your router setup as a router, not as a
modem.

If you're positive that your ISP is using bridging mode, then you've
probably got it setup in the most secure manner.  I do know that when
you received your router in the mail, there should've been
instructions with it on how set it up using PPP because US West
doesn't use bridging anymore.