Re: [L2tpd-devel] 0.64 released, et al
Status: Inactive
Brought to you by:
dami0nd
|
From: Ian <Rel...@Hu...> - 2002-01-16 00:11:41
|
G'day Jeff, I've been on the list for about 12months, but have never attempted to run your software (the thing I wanted to use it for has gone away again :-) I just wanted to let you know that yesterday in my travels I found that EtheReal (http://www.ethereal.com/) has L2TP recognition/understanding .. I don't know how sophisticated their code is (or if you wrote it for them ;) but I thought I'd point it out .. maybe some friends over there .. Thanks for reiving this project ... I only recently started my own project on sourceforge ... and as a "hobby" it really is hard to keep up the development ... ----- Original Message ----- >From: "Jeff Mcadams" <je...@ig...> >To: "Scott Balmos" <sco...@ut...> >Subject: Re: [L2tpd-devel] 0.64 released, et al >Date: Tue, 15 Jan 2002 18:35:27 -0500 > > Also sprach Scott Balmos > >http://prdownloads.sourceforge.net/l2tpd/l2tpd-0.64.tar.gz (apparently > >the file release area says the release exists, but no files are > >added... It's there, believe me) > > Yup, confirmed...the files are there. May have just taken the > sourceforge pages some time to update behind the scenes or something > *shrug* > > >I would *really* love to take this thing farther, and I know it'll > >continue to do so... But should I be the project maintainer if I can't > >even really follow the code? > > There's more to being a project maintainer than just coding on the > software...though that's really not an answer to your question. > > >Does anyone else out there want to become a project manager? At the > >moment, Jeff is our Alan Cox, as I like to call him. He deals with the > >bugfixes and all that fun. But really I think there needs to be a > >complete rewrite, audit, whatever you want to call it, that puts us > >into the kernelspace. This CVS tree has been set up for a long while, > >as l2tpd-devel, and was to be the 0.7 tree (devel releases would be > >like 0.701, and 0.71 through 0.75 would be matching the functionality > >of the existing 0.6 tree). That, unfortunately, is completely out of my > >realm (reentrant kernel code scares me. :D), and as Jeff said, he only > >has about the first 20 lines of the kernel module template. > > >We need a project manager that can spearhead the bleeding edge 0.7 > >rewrite... Anyone??? :) > > If noone else steps up to the plate...I could probably take on a more > active role. It'd be nice to have someone that has a little more time > to put into it than I have as well...though I realize that there just > plain may not be someone that has the time and inclination to do that > out there. > > > Funny anecdote...tangentially related to the topic at best... > > Was working with RedBack today (our SMS 500 decided to reboot with > *alarming* regularity) and at one point, dude at RedBack asked me if we > had anyone connecting with l2tpd as the LAC to our SMS as the LNS. I > kinda chuckled and said, "yeah...a few." He said that some of the > versions of AOS on the RedBack's had trouble with some things that l2tpd > did. I chuckled again and said, "Can you get me details? You see..." > and then I promptly when on to explain the situation as it exists wrt to > l2tpd. Dude laughed and said he'd put me in touch with one of their > developers about it ASAP. Turns out that it was purely a bug in AOS, > and was not anything l2tpd was doing wrong (which kinda surprised me!), > but that the developer would certainly keep my name and email on hand > for any other issues that come up. :) > -- > Jeff McAdams Email: je...@ig... > Head Network Administrator Voice: (502) 966-3848 > IgLou Internet Services (800) 436-4456 > > _______________________________________________ > L2tpd-devel mailing list > L2t...@li... > https://lists.sourceforge.net/lists/listinfo/l2tpd-devel > |