[L2tpd-devel] l2tpd in CVS needed?

[Jeff M. <je...@ig...>]

Any need for the l2tpd (the compiled binary) file in CVS?  Seems
reasonable to remove that file, though not a big deal one way or the
other.

I've been looking more at the call/session/tunnel shutdown code.  All I
can say is "ugh."  I think, eventually, it'll need to be ripped out and
completely replaced with something cleaner that takes into account the
upper layers.  Shutting down an individual call/session is not hard
(that's working now, with the couple of ugly hacks that I did), but
shutting down the calls/sessions by doing a disconnect on the whole
tunnel doesn't work cleanly.  Any thoughts on a procedure to handle this
cleanly?  I'm lazy, so I don't want to re-write any more than I have to,
so leveraging functions and structures that are already in the code is
good.  :)

Another thing I'd like to see done eventually...and this is not a big
deal...would be to see the terminology, comments, variable names, etc.
updated to match the RFC defining L2TP.  An example of that being the
call/session stuff.  The RFC calls them "sessions", l2tpd calls them
"calls."  Like I said...not a big deal, but might help in discussions
about what needs to be done to have a consistent terminology.
-- 
Jeff McAdams                            Email: je...@ig...
Head Network Administrator              Voice: (502) 966-3848
IgLou Internet Services                        (800) 436-4456