Would it be like a kernel compile time thing? Or like a setsockopt type of mechanism
so each broadcast socket would have a different callsign? What's the application or
bug fix you have in mind for this? (That is configurable callsigns for ip broadcast
packets.)
More interesting to me, is what happens if we turn on the MULTICAST flag with the
ax25 driver. Me, I'm not even sure exactly how to test MULTICAST, but I was thinking
that maybe, it might be fun to have some kind of HAMBONE (like M-bone) with news
messages
or maybe audio or something.
-----Original Message-----
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Saturday, October 23, 1999 6:18 PM
Subject: Re: dhcpd + sv2agw
On 23 Oct, Jens David wrote:
> [EMAIL PROTECTED] wrote:
>> There are a couple of de-facto standards around: QST-0 for example, but
>> I've seen nothing that actually defines a standard AX.25 broadcast
>> address. Until that happens it's kinda difficult to know what to do
>> with datagrams sent to the IP broadcast address. Reasonable behaviour
>> would probably be to make the AX.25 broadcast address configurable and
>> then support IP broadcast over it in UI mode.
>
> In fact everything I´ve seen so far (and that was a lot, starting
> with xNOS DOS applications, FlexNet, AIRS (OS/2, Linux), the original
> WAMPES etc.) did it that way. I think we can safely call this a
> standard.
Sorry, it's unclear to me what you're suggesting is the standard here.
> The ability to configure the broadcast address.
or
> Using QST-0 as the broadcast address.
I personally would prefer a configurable broadcast address with QST-0
used as the default if unspecified.
