[L2tpd-devel] The road to 0.7

[Scott B. <sb...@ig...>]

Good evening all,

Sorry this is coming out roughly a week after Jeff's last code commits. I've
been dealing with starting statistics for state basketball Sectional
Tournaments, getting ready for a DC trip, blah blah blah... excuses excuses.
BTW, anyone happen to want a new retail-pacakged ATI All-In-Wonder Radeon
for about $200? I bought one on eBay, only to find a connection with a
friend who can get it for $150. LOL

Anyway... The PPPd shutdown code is nasty, I know, but we'll live with it
for now. Overall, pretty much every showstopper has been found and fixed.
I'd love to know, now, what unhandled attribute 47 or whatever it is when a
tunnel is created to Iglou. LOL

At this point, I think there needs to be a temporary reemphasis on
documenting the program's use and FAQ, etc. I noticed David started on it
already, and I'll start whacking on some of it myself.

Afterwards, once the docs are at least a little bit better shored up, we can
release this as 0.7. Looking towards 0.8 and maybe even 1.0, we might be
heading to the point to where it'd be more beneficial to us to start ripping
codeblocks and rewriting. :/ That's going to be a pain.

Eventually, I think what we need is for 1.0 to be a completely daemonizing
server system in the background, and then instead of having echo streams
passed to the control pipe, either try and eliminate the pipe if we can or
write a separate command line client to handle pipe commands. Something a
little bit easier or straightforward than echo "blah blah blah". Also, by
1.0, there needs to be at least initial support for some type of encryption
(hint IPSec)... unless we want to try and confuse the general Windoze public
with even more Registry screwups... err... fixes. :)

Even further forward, the 1.x tree towards 2.0 is where we really confuse
ourselves and try to see about separating the code into a kernel module. But
we won't go there yet. That's just scary...

Anyway, as for Jeff's comments about how to more cleanly shut down the
higher-layer controls, such as PPPd... I think we might want to take a look
at the source of getty, or whatever program controls a modem during a normal
PPP dialup session. That's all L2TP really is is just a glorified dialup
modem session in a way. It's been my position for a while now just to look
at how things are handled already by modem sessions, and then go from there.

And I'm STILL trying to figure out why our project summary page shows the
CVS as being empty. Oh well. Comments anyone on placing this roadmap up on
the docs area, and placing some of these tasks up in the to-do list?

Comments at all, or is it just me and I'm too dead at this hour to think
after homework? :)

--Scott