From: Hamish Moffatt <hamish@cloud.net.au>
To: linux-hams@vger.kernel.org
Subject: Re: listen -utility vs. aprsd and its treatment of AX.25 sockets..
Date: Wed, 7 Nov 2007 08:04:56 +1100 [thread overview]
Message-ID: <20071106210456.GC30845@cloud.net.au> (raw)
In-Reply-To: <20071106205247.GO6372@mea-ext.zmailer.org>
On Tue, Nov 06, 2007 at 10:52:47PM +0200, Matti Aarnio wrote:
> rx_socket = socket(PF_PACKET, SOCK_PACKET, htons(proto));
>
> tx_socket = socket(PF_AX25, SOCK_DGRAM, 0)
>
> Where the 'proto' is either ETH_P_AX25 or ETH_P_ALL.
>
>
> In the 'listen' utility the proto is ETH_P_AX25 unless '-a' option
> is given, then it is ETH_P_ALL. In 'aprsd' it is always ETH_P_ALL.
When I added AX.25 sockets functionality to aprsd, I "leveraged" the
code from listen, so you should expect them to be the same.
I can't think now why aprsd would need to monitor outgoing frames
though. Perhaps so that it hears packets sent by other AX.25
applications running on the same host eg aprsdigi. However it does add
the requirement to run as root which aprsd might not have otherwise.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
prev parent reply other threads:[~2007-11-06 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 20:52 listen -utility vs. aprsd and its treatment of AX.25 sockets Matti Aarnio
2007-11-06 21:04 ` Hamish Moffatt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071106210456.GC30845@cloud.net.au \
--to=hamish@cloud.net.au \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox