linux-hams.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cathryn Mataga <cathrynm@junglevision.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: Writing raw ax25 packets -- "no buffer space available"
Date: Sat, 30 Dec 2006 20:27:22 -0800	[thread overview]
Message-ID: <45973C2A.3010805@junglevision.com> (raw)
In-Reply-To: <45966961.2030909@junglevision.com>

Cathryn Mataga wrote:

Okay, sorry, never mind.  I restarted the Linux machine and it works 
now.  I think
my Kam ports got confused due to some other unrelated issue. 

Right now it looks like sending RAW ax25 is working on all my RF ports.

> I'm working on a little program that needs to out put raw ax25. And it's
> working somewhat, though not completely. Basically the code uses
> socket(PF_PACKET, SOCK_RAW, IPPROTO_AX25);. It builds
> a kiss header of one byte, and then fills in a packet. I bind( and then
> send(. That's basically the whole thing.
>
> (For the curious I thought it'd be fun to print out messages on
> my TS2000 using the CLuster feature, but this needs 'connected
> packets' on DX Cluster format, and I seem to need to go raw for this.
> I do have this working and I have it setup now so I type a comand line
> and a message pops up on the LCD on the TS2000.)
>
> Here's the deal. I have a sound modem setup and also a PK232 in
> KISS which I can test hooked to the system. These both work fine.
>
> But, I also have a 'KPC-9612' with 3 ports plugged in , and when I send
> raw packets to this, I get a "No buffer space available" error. This is
> on the first and only send(
>
> I'm using /sbin/mkiss to plug create the three ports from one serial
> port, and I was thinking it's somehow related to this. Though I'm
> not really sure. I guess SOCK_RAW would just send data to
> mkiss just like the other ports. It seems like it wouldn't be a problem.
>
> In the kernel, I only see one ENOBUFS in ax25 and that's in AF_AX25
> after a kmalloc, but this doesn't make any sense. It must be coming from
> somewhere else I think. The issue is not a 'flakey' at all here, and it
> just doesn't work on mkiss. It shows an error consistently. The send(
> call gets ENOBUFS returned to it, but 'listen' never sees anything 
> going out
> at all.
>
> Anyway, I'm posing this in case someone else has information on
> how to write raw AX25. I didn't really find what looked like a recent
> simple example of this in any of the AX5 libraries or tools.
>
> Thank you.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      parent reply	other threads:[~2006-12-31  4:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18 10:21 New Linux hamradio related website Ralf Baechle DL5RB
2006-04-18 10:27 ` Vic
2006-04-18 10:39   ` Ralf Baechle DL5RB
2006-04-18 10:58     ` Vic
2006-04-24 15:03       ` Ralf Baechle DL5RB
2006-12-30 13:28 ` Writing raw ax25 packets -- "no buffer space available" Cathryn Mataga
2006-12-30 17:34   ` test richard
2006-12-31  4:27   ` Cathryn Mataga [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=45973C2A.3010805@junglevision.com \
    --to=cathrynm@junglevision.com \
    --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;
as well as URLs for NNTP newsgroup(s).