> > 1) get pon to come run from the time the box boots, and redial/reconnect > if it looses carrier or get's a busy signal, etc... If this box is on, > I want the modem connected. Not sure what to do here, anyone got a > script or two I could use, and tell me where they go?
The supplied ppp package can do this, read the docs and you will discover. However should you is another question. Tying up a one of your ISPs lines just because you can is noy a nice thing to do. Use it when you need it. > > 2) change the default gateway in this box to be ppp0 instead of eth0 (I > routed it through my current LAN and other gateway to grab a couple > packages) Not sure where this is exactly, what should I be looking > at/for? > >From below it sounds like you have a 2.2 kernel going -- it will do the routes for you. Do not set them, do not worry. > 3) Stick the following in some rc.d somewhere to run at boot time: > echo "ip_masq 192.128.1.4" > echo "1" > /proc/sys/net/ipv4/ip_forward > /sbin/depmod -a > /sbin/modprobe ip_masq_ftp.o > /sbin/modprobe ip_masq_raudio.o > /sbin/modprobe ip_masq_irc.o > /sbin/ipfwadm -F -p deny > /sbin/ipfwadm -F -a m -S 192.168.1.0/24 -D 0.0.0.0/0 > /sbin/ifconfig eth0 192.168.1.4 > /sbin/route add -net 192.168.1.0 > /sbin/ipfwadm -A in -i -S 0.0.0.0/0 > /sbin/ipfwadm -A out -i -D 0.0.0.0/0 > But where should that go? the rc.d stuff looks a little different in > Debian that what I am use to. > When you install and config ipmasq one of the things it ask is should ipmasq be run when the ppp connection goes up -- tell it yes and config the /etc/ipmasq stuff and you are all set, no muss no fuss. As to the modules, place a scrip in /etc/init.d and then read the man page for update-rc.d. Should cover ya. 2.2 does all the routes you need. Do not bother setting them.
