|
||||||||
On Thu, 9 Sep 2004, Chris Buechler wrote: > (another bitten by the having to hit reply to all to send to list, > this message below was intended for the list) > > ---------- Forwarded message ---------- > From: GA Burghout <g dot burghout at hccnet dot nl> > Date: Thu, 9 Sep 2004 22:24:32 +0200 > Subject: RE: [m0n0wall] dialup > To: Chris Buechler <cbuechler at gmail dot com> > > Hi, > > I hate to burst your bubble, but Chris is right... You need to do a lot to > get dialup support in m0n0wall. Short and/or imcomplete checklist: > > - add dialup support to the kernel (add tun0 device; recompile the lot) I think that only pertains to doing it with the userland PPP implementation. MPD (already included in m0n0wall) can do it via netgraph, and it appears that NETGRAPH_TTY is already included in the kernel config. > - add the tun0 device to the "device detector" when you first boot m0n0wall > (now m0n0wall only detects devices with an active link) I doubt that that would be the right level even if one *were* using the userland PPP, since "detecting" tun0 with no PPP link established wouldn't do much good. But in this case it would be an MPD configuration issue. > - add (extra) webpages to the interface so you can configure dialup settings > (like phone number and account information) > - extensive testing to make sure everything works like it should (sigh...) And for Soekris users: An *accessible* serial port that's not the console. :-) These issues are also relevant for dial *out*, for backup purposes. Fred Wright |