Ooops. Sorry. That is confusing.
-Original Message-
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Sunday, October 24, 1999 6:37 PM
Subject: Re: dhcpd + sv2agw
>On 24 Oct, Cathryn Mataga wrote:
>
>> MULTICAST,
On 24 Oct, Cathryn Mataga wrote:
> MULTICAST, that is "/sbin/ifconfig device multicast",
> should, as I understand it, with a network of worldwide servers, be smart enough
> only to forward to servers who have users who need the packets. It's like I open
> one socket, write a packet, and either
-Original Message-
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Sunday, October 24, 1999 4:46 PM
Subject: Re: dhcpd + sv2agw
>On 24 Oct, Cathryn Mataga wrote:
>
>> I suspect, that if MULTICAST does what I think it is
On 24 Oct, Cathryn Mataga wrote:
> I suspect, that if MULTICAST does what I think it is supposed to do, that it might
> be uniquely suited for ham radio links with low bandwidth. That is, say,
> for doing something like a convers or irc type chat system, where the chat messages
> were smart enou
-Original Message-
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Sunday, October 24, 1999 3:46 PM
Subject: Re: dhcpd + sv2agw
>On 24 Oct, Cathryn Mataga wrote:
>> Would it be like a kernel compile time thing? Or like
On 24 Oct, Cathryn Mataga wrote:
> 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
om: [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 ex
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
yway, this might be more operator
confusion or something. In any case, I got it working.
-Original Message-
From: Cathryn Mataga <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Saturday, October 23, 1999 5:23 PM
Subject: Re: dhcpd + sv2agw
>Okay, I th
thryn was 0 */
These flags would be changed in all the hamradio drivers.
I just make this change, and the kernel seems to work. Though I need to pull
my teltales, and run it a bit more to make sure it's okay. And, I still need
to try getting dhcpd running, though I'll mess with that later.
---
sending out udp test packets?
Hmm?
-Original Message-
From: Cathryn Mataga <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Saturday, October 23, 1999 12:08 AM
Subject: Re: dhcpd + sv2agw
>Thanks for the pointer. Well, this patch does allow me to get t
[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. Reasonabl
Thanks for the pointer. Well, this patch does allow me to get the
BROADCAST flag and address set. Except this still doesn't allow
me to receive the broadcasts -- like you said. Or, at least I dhcpd
doesn't work.I probably need to cook up a simpler test program
than dhcpd.
Btw, in mkiss
On 22 Oct, Ken Koster wrote:
> Broadcast operation seems to be broken, at least on those ax25 ports
> supported via KISS. I ran into this problem some time back when trying
> to get gated to work over the air. It is likely that the same problem is
> keeping dhcp from working.
Actually Ken, I'
On Fri, 22 Oct 1999, Cathryn Mataga wrote:
> -Original Message-
> From: Bob Meyer <[EMAIL PROTECTED]>
...
> >Cathryn Mataga wrote:
> >
> >> I'm trying to get dhcpd on Linux talking to SV2agw on Win98. The idea here
...
>
> I'm also still trying to figure out the BROADCAST flag, and
Oh S..t Guess MS is multicasting code 'non-functional fixes' to all
machines.
On Fri, 22 Oct 1999, Chris Hewitt wrote:
> Cathryn Mataga wrote:
> >
> > What's at 224.0.0.2, anyway? Who is Microsoft trying to talk
> > to?
>
> nslookup reveals the hostname ALL-ROUTERS.MCAST.NET whatever
Cathryn Mataga wrote:
>
> What's at 224.0.0.2, anyway? Who is Microsoft trying to talk
> to?
nslookup reveals the hostname ALL-ROUTERS.MCAST.NET whatever that is.
Regards
Chris
g0pae
-Original Message-
From: Bob Meyer <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Friday, October 22, 1999 6:52 AM
Subject: Re: dhcpd + sv2agw
>Cathryn Mataga wrote:
>
>> I'm trying to get dhcpd on Linux talking to SV2agw on Win98. T
Cathryn Mataga wrote:
> I'm trying to get dhcpd on Linux talking to SV2agw on Win98. The idea here
> is to put the 9600 baud port on a C-net and 192.168.1.0, and use
> ip masquerade to convert ip adresses to my amprnet adress. When
> I use static ip adresses on the Windows machines, it works gr
I'm trying to get dhcpd on Linux talking to SV2agw on Win98. The idea here
is to put the 9600 baud port on a C-net and 192.168.1.0, and use
ip masquerade to convert ip adresses to my amprnet adress. When
I use static ip adresses on the Windows machines, it works great,
and I have no trouble with
20 matches
Mail list logo
