Linux-Hams archive - January 1997: Re: Request for Comments
Re: Request for Comments
Matthias Welwarsky (zrmibhhm.borzmese@dhltd.com)
Fri, 03 Jan 1997 12:01:14 +0100
Jonathan Naylor wrote:
>
> On Thu, 2 Jan 1997, Matthias Welwarsky wrote:
> > I definitely like this idea. But the main question that arises with this
> > is, how to interface the userspace-digipeater with the kernel-ax25. What
> > API should be used? Hm, I'd like to have something like this:
> >
> > Get a socket(), bind() it to an address that will be the address to
> > digipeat via, then signal to the kernel that we would like to digipeat
> > ourselves, maybe by setsockopt(). Then listen() on that socket.
>
> Whoa a second. Its a lot easier than that, remember we are talking about
> *real* digipeating outside of the kernel, therefore we cannot assume
> anything about the incoming packets, we may want to retransmit them out
> of another AX.25 port etc.
Ah, well, now I got the picture. I'm sorry, guess I am too familiar with
what you call pseudo-digipeating that I just didn't see the point. I was
thinking about giving up kernel-digipeating *at all*, not only simple
l2-digipeating.
> The interface to build a real digipeater in user space is very much
> simpler than doing a listen() or whatever. The user space digipeater
> would listen for packets in the same way that the listen program does,
> and transmits them out using a sendto().
Yes your're right, and stripping that digipeating stuff off the kernel
will at least clean up the code a bit ;-)
--
Matthias