tipxd-devel Mailing List for Tom's IPX Tunneling Daemon
Status: Beta
Brought to you by:
thomash
Menu
▾
▴
tipxd-devel
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
(10) |
Apr
(11) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: <sou...@ex...> - 2000-04-11 21:25:14
|
> I reviewed these changes this morning (boy, the differizer-thingy from > sourceforge just rocks, period). Took me all of ten minutes to see all > the changes and understand what they did. Outstanding work, dude. I'm > glad someone likes to deal with va_args functions, because I never liked > to. I've updated my source tree to include your changes. Cool :) > As far as coding guidelines go, I'm probably ten times more verbose than > I need to be, but that's a good thing, right? =) Definitely. |
|
From: Thomas H. <nor...@ya...> - 2000-04-11 17:26:06
|
I reviewed these changes this morning (boy, the differizer-thingy from sourceforge just rocks, period). Took me all of ten minutes to see all the changes and understand what they did. Outstanding work, dude. I'm glad someone likes to deal with va_args functions, because I never liked to. I've updated my source tree to include your changes. As far as coding guidelines go, I'm probably ten times more verbose than I need to be, but that's a good thing, right? =) --Tom --- sou...@ex... wrote: > Well, no, not really. > > Modified logging system and added further command line switches: > Verbose option > Stderr log output option (instead of syslog) > Some small smattering of help > Added log.c containing log wrapper > > -e (hmm, better single-char switch might be found?) will chuck logs out to > STDERR, I want to do it with a timestamp, will add at a later date. > > -v sets verbose switch (opt_flags in sysinfo structure, same with stderr > thing) > > -h will give a little bit of help :) > > log.c contains the log wrapper (tipxd_log to avoid namespace collisions > with the pleuthora of *log* functions under various unicies) > > Not a lot of coding involved. Attempted to follow style guidelines :) > > Compiles clean. __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com |
|
From: <sou...@ex...> - 2000-04-11 12:06:09
|
Well, no, not really. Modified logging system and added further command line switches: Verbose option Stderr log output option (instead of syslog) Some small smattering of help Added log.c containing log wrapper -e (hmm, better single-char switch might be found?) will chuck logs out to STDERR, I want to do it with a timestamp, will add at a later date. -v sets verbose switch (opt_flags in sysinfo structure, same with stderr thing) -h will give a little bit of help :) log.c contains the log wrapper (tipxd_log to avoid namespace collisions with the pleuthora of *log* functions under various unicies) Not a lot of coding involved. Attempted to follow style guidelines :) Compiles clean. |
|
From: <sou...@ex...> - 2000-04-11 10:38:38
|
> > Regarding syslog, I'd like to re-engineer the code to use either syslog or > > stderr (compile time option). The reason for this being that I have the > > current tipxd running on a floppy disk, which doesn't have space for > > syslogd or anything on it, and i'd prefer to just see it dump out to > > console. Ok with you? > I think that it should be run-time option rather then compile time. > I still have no time to put my hands on tipxd's getopt(). I just commited a modification to use getopt, I didn't even know I could commit :) Changes to Makefile, conf.l and main.c Feel free to hack to make prettier, I think its pretty clean. Compiles clean on my system. |
|
From: Roman S. <ro...@xp...> - 2000-04-11 09:26:50
|
On Tue, 11 Apr 2000 sou...@ex... wrote: > Regarding syslog, I'd like to re-engineer the code to use either syslog or > stderr (compile time option). The reason for this being that I have the > current tipxd running on a floppy disk, which doesn't have space for > syslogd or anything on it, and i'd prefer to just see it dump out to > console. Ok with you? I think that it should be run-time option rather then compile time. I still have no time to put my hands on tipxd's getopt(). --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] |
|
From: <sou...@ex...> - 2000-04-11 09:22:27
|
Regarding syslog, I'd like to re-engineer the code to use either syslog or stderr (compile time option). The reason for this being that I have the current tipxd running on a floppy disk, which doesn't have space for syslogd or anything on it, and i'd prefer to just see it dump out to console. Ok with you? Richard. |
|
From: Thomas H. <nor...@ya...> - 2000-04-11 07:52:43
|
I have added the code to src/main.c that will comprise the engine for dealing with the file descriptors and handling the main select( )-loop portion of the code. It should be solid, and display exactly my 'vision' of what the program is going to do exactly. take a look over it. Tomorrow night I am off because it is gaming night (everquest), but back to work on it on Wednesday! Keep us all up-to-date if you make progress! --Tom __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com |
|
From: Thomas H. <nor...@ya...> - 2000-04-10 22:15:09
|
Well, if anyone has the time, feel free to migrate the code over to use getopt instead of popt. Hey, one less dependancy makes me happy... =) Everything looks happy for the May 1 Release. Going to be working some more tonight. I'll let you know how it goes. BTW, I forgot to mention that last weekend I actually posted a page to our site! So, check out http://tipxd.sourceforge.net/ and let me know if there are any really bad errors. =) --Tom. --- sou...@ex... wrote: > > I was reading back through the mailing list, and saw Roman's post about > using > > getopt instead of popt. I was wondering what the list thought about this. > I'm > > all for portability, and used popt because I thought it was "Neat(tm)". > > However, if getopt is more portable, I'd like to consider using that > instead. > > I've found getopt more than adequate, and entirely by accident found the > software in question compiled under most unix platforms. I recommend it. > > Richard. > > > > _______________________________________________ > Tipxd-devel mailing list > Tip...@li... > http://lists.sourceforge.net/mailman/listinfo/tipxd-devel > __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com |
|
From: <sou...@ex...> - 2000-04-10 21:17:23
|
> I was reading back through the mailing list, and saw Roman's post about using > getopt instead of popt. I was wondering what the list thought about this. I'm > all for portability, and used popt because I thought it was "Neat(tm)". > However, if getopt is more portable, I'd like to consider using that instead. I've found getopt more than adequate, and entirely by accident found the software in question compiled under most unix platforms. I recommend it. Richard. |
|
From: Thomas H. <nor...@ya...> - 2000-04-10 07:31:53
|
I was reading back through the mailing list, and saw Roman's post about using getopt instead of popt. I was wondering what the list thought about this. I'm all for portability, and used popt because I thought it was "Neat(tm)". However, if getopt is more portable, I'd like to consider using that instead. --Tom __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com |
|
From: Thomas H. <nor...@ya...> - 2000-04-10 07:28:16
|
Well, some major strides this weekend. I coded the final pieces of the
configuration file parser, and it appears to scan everything correctly. I have
begun work on the code to start opening sockets, handling errors on them, etc.
I need to write the main engine of the code, namely the for( ; ; ) { select();
} loop in main. however, once this loop is written, it should be pretty solid.
From there, it is a matter of writing the functions to take data off the
sockets and put them on other sockets. I humbly suggest that you take a look
at the code whenever you get the chance.
Once I get IPX sockets open, and can start routing between IPX interfaces, I'll
label a developer release (probably to be named tipxd-1-1-0) and start
packaging the release together.
My intention is the have the first release of tipxd-2.0.0 (CVS:tipxd-2-0-0) on
May 1st. If I can make that goal, I will order myself a laptop. =) I'll keep
you guys posted. After the 2.0.0 release, I'd like to get started on the
tipxd-test module.
--Tom
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
|
|
From: Thomas H. <nor...@ya...> - 2000-03-28 06:36:32
|
I managed to accomplish something worthwhile tonight. Tipxd now reads in ROUTER And PEER records from the configuration file. I also generalized some the string and number extracting functions so they are more stable and less prone to crash with a SEGV, casue memory leaks, etc. Feel free to look over the changes whenever you get a chance! Affected files: src/conf.l etc/tipxd.conf src/router.c include/router.h --Tom __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com |
|
From: Thomas H. <nor...@ya...> - 2000-03-16 08:10:40
|
I did some work tonight on the configuration file parser. It's a lex file which you will find under src/conf.l, and I added makefile targets to automagically build the lex file as necessary. It seems to parse the GENERAL record from the file correctly. It needs error checking badly, as well as better handling of quoted strings and numbers. More work on this during the weekend. Let me know how you think the code is progressing. If you see something that needs to be fixed, by all means fix it. That's the great thing about version control... =) --tom. __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com |
|
From: Thomas H. <nor...@ya...> - 2000-03-15 02:48:12
|
Last night I added the last of the major DS's to include/main.h in the
repository. This data structure, selectinfo_t, will be used to list the
currently open file descriptors for processing with the select() syscall. It
is my intent to have a single linked-list of these, one for each file
descriptor, and each one having pointers to the appropriate operations for
reading, writing, and processing errors on it. Then the structure of main will
look similar to this:
--- [SNIP] --- [SNIP] ---
for( ; ; )
selectinfo_t *info;
FD_SET read_fds, err_fds;
for(info = selectinfo; info != NULL; info = info->next )
{
FD_ADD( &read_fds, info->fd );
FD_ADD( &err_fds, info->fd );
}
retval = select( &read_fds, NULL, &err_fds, &timeout );
for(info = selectinfo; info != NULL; info = info->next )
{
if(FD_ISSET( &read_fds, info->fd ) )
retval = info->read_op( info );
if(FD_ISSET( &err_fds, info->fd ) )
retval = info->err_op( info );
}
}
--- [SNIP] --- [SNIP] ---
This is a little more than psuedo-code, but I'm not really compiling the code
above. Hopefully from this, though, you get the general idea we're going for.
The trick is coding the read, write, and error operations for the socket types
that we are going to have:
UDP Data
TCP Data
TCP Control
UDP Control
TCP Admin
UDP Admin
More on this when I get back to coding. Probably going to be Wednesday night
for at least a little while.
--tom
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
|
|
From: Thomas H. <nor...@ya...> - 2000-03-14 06:08:30
|
I updated the configuration file format specification, and made several CVS commits tonight. Be sure to check the CVS logs, and you might want to check doc/config.tex for the documentation as well as include/main.h for some data structure additions. Hopefully, the distribution now includes *all* the major data structures it will need. Now we just need operations on them and a main loop and a configuration file parser and *voice trails off*... I am marking the configuration file format task as completed. 1 down, many to go! =) I'll be off tomorrow night because it's gaming night. (Everquest, if you were wondering). Be back hacking at it on Wednesday. --Tom __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com |
|
From: <sou...@ex...> - 2000-03-13 21:37:47
|
> I need a volunteer to create a website for tipxd. Right now, the main static > page is there. I'd like something with at least a simple description there, > and a link to the tipxd project page. Past that, the manual next followed by > the latest/greatest sources and packages. > > Any volunteers? =) Heh, not me :) Web pages scare me. But I would like to know whether you got a lot done on the code this weekend? I'm looking forward to having a play but didn't want to start until structure had stabilised. Richard |
|
From: Thomas H. <nor...@ya...> - 2000-03-13 21:29:33
|
I need a volunteer to create a website for tipxd. Right now, the main static page is there. I'd like something with at least a simple description there, and a link to the tipxd project page. Past that, the manual next followed by the latest/greatest sources and packages. Any volunteers? =) --Tom __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com |
|
From: Thomas H. <nor...@ya...> - 2000-03-13 21:27:37
|
Hi all. Thanks to Roman for the BSD portability issues. I have incorporated the changes in the patch he sent me in to the latest sources. Additionally, I have added a new directory "doc/" and a new file "doc/config.tex". I was trying to determine the documentation format that I wanted to use. I would have used plaintext, since it is by far the most portable. However, I can see the tipxd user manual eventually growing beyond the limits of simple text and I decided that at least *minimal* formatting should be included. I tried my best not to have a subsubsub...section for every little thing. However, if I've gone off the deep end, let me know. =) The document is written in LaTeX, which can easily be converted to postscript with the following commands: > latex config.tex # Produces "config.dvi" as well as some other files > dvips -o config.ps config.dvi # Produces "config.ps" for printing or viewing with ghostview When the document is fleshed out a little more, I'll create an HTML page for posting to the website so that people can browse the user manual online. Now, there will be a manpage eventually. There will also be README that contains some simplified information like known bugs. Someone also needs to create a CHANGELOG file for inclusion with the distro. I haven't created these files yet. If someone wants to volunteer for this, though, be my guest... =) Other than that, feel free to checkout the current documentation. I will hopefully be working some more tonight to get this document put together so we have something on the configuration file format, and the main program data structures. --Tom __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com |
|
From: Roman S. <ro...@xp...> - 2000-03-12 14:53:59
|
forwarded :)
--Roman Shterenzon, UNIX System Administrator and Consultant
[ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ]
---------- Forwarded message ----------
Date: Fri, 10 Mar 2000 16:14:43 -0800
From: Thomas Hendrick <th...@qu...>
To: Roman Shterenzon <ro...@xp...>
Subject: Re: patch to compile on freebsd 3.x
I thought about this. You might wanna post this to the mailing list,
though. For archive purposes. =)
To answer your question, I for some reason thought popt was the more
portable, though getopt is the older. popt has some nice features, like
automatic generation of usage and help options and some nice output. WE
can discuss this further on the mailing list. I'm just trying to reply to
these before I leave work. =)
-Tom.
On Fri, Mar 10, 2000 at 03:15:34PM +0200, Roman Shterenzon wrote:
>
> Hello,
> One thing that I already noticed;
> popt is not a stardard while getopt is..
> It may be not problem on FreeBSD where it's in ports collection, but it
> can be problem on solaris..
> Do you want me to rewrite it using getopt?
> Most gnu software comes with getopt.c, getopt1.c and getopt.h which makes
> it possible to use getopt_long.
> What do you think?
> getopt() is a part of most UNIX operating systems.
>
> --Roman Shterenzon, UNIX System Administrator and Consultant
> [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ]
>
--
-----------------------------------------------------------------
Thomas Hendrick Office: 1-(858)-845-3045
AI-105C Pager : 1-(619)-557-8917
th...@qu... Mobile: 1-(619)-980-8624
No official representation of Qualcomm is implicit in the above
-----------------------------------------------------------------
|
|
From: <sou...@ex...> - 2000-03-08 20:33:32
|
On Wed, 8 Mar 2000, Thomas Hendrick wrote: > Hi everyone! Mostly I'm writing this mail for the archives, but just so you > know, if you want to contact me, I'll be on DALnet Internet Relay Chat > (irc.dal.net will take you to a random DALnet server, any server will do) > hanging around on #tipxd. My handle is "norritt". I might be in during the > day, but more than likely I'll be on at night when I'm actually doing stuff. :) Oh well, while we're swapping nicks and channels, Undernet, #nz, PhiRatE. And I'm always on :) Phi. |
|
From: Thomas H. <nor...@ya...> - 2000-03-08 18:12:15
|
Hi everyone! Mostly I'm writing this mail for the archives, but just so you know, if you want to contact me, I'll be on DALnet Internet Relay Chat (irc.dal.net will take you to a random DALnet server, any server will do) hanging around on #tipxd. My handle is "norritt". I might be in during the day, but more than likely I'll be on at night when I'm actually doing stuff. Have fun, and hopefully we'll get this thing out the door sometime. =) --tom. __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com |
