From: Tomi Manninen (snvppp.iscjrzk@mailit.tunk.net)
Date: Sun Jul 06 2003 - 21:01:33 EEST
On Sun, 2003-07-06 at 18:05, Steven Whitehouse wrote:
> - No application that I've seen actually uses them (of course someone on
> this list might prove me wrong on this point!)
About three years ago I rewrote netromd to use a PF_AX25, SOCK_RAW,
NETROM_PID socket for receiving NODES broadcasts. The main reason
for the rewrite was to support digipeated broadcasts. Raw socket was
an easy way of getting the digi path.
Unfortunately at that time something was broken in the kernel
(ax25_getname IIRC) so it only worked with a patched kernel.
Also there wasn't much interest in it so it was all forgotten.
I don't know of any other programs using raw AX.25 sockets.
> - They are broken and haven't worked for some time and I've not seen any
> bug reports posted recently (again leading me to think nothing uses them).
How exactly is it broken?
> - The PF_PACKET family would seem to be just as good an option for
> application writers.
Most applications use PF_PACKET but there is the problem that it needs
elevated privileges. Granted, using a raw socket and binding it to
anything else than your own callsign also needs privileges so this
may not be an issue.
Anyway using PF_PACKET for just about everything like it is currently
is in my opinion ugly so I would prefer maintaining raw socket support
if possible.
> - Its unclear exactly what the rules were for which packets should
> be delivered to raw sockets.
-- Tomi Manninen Internet: lgui@canopycanada.net OH2BNS AX.25: kvs.cnvpgad@intertek.net KP20ME04 Amprnet: cwsbok@tar-engineering.com- To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to sviw@megacom.net More majordomo info at http://vger.kernel.org/majordomo-info.html
This archive was generated by hypermail 2b30 : Sun Jul 06 2003 - 21:01:57 EEST