From: Henk de Groot <henk.de.groot@hetnet.nl>
To: kuznet@ms2.inr.ac.ru
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
linux-hams@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: AX25/socket kernel PATCHes
Date: Sun, 30 Dec 2001 23:13:14 +0100 [thread overview]
Message-ID: <5.1.0.14.2.20011230223848.00a2d570@pop.hetnet.nl> (raw)
In-Reply-To: <200112301924.WAA24526@ms2.inr.ac.ru>
In-Reply-To: <5.1.0.14.2.20011230174733.00a2fc50@pop.hetnet.nl>
Hello Alexey,
At 22:24 30-12-01 +0300, kuznet@ms2.inr.ac.ru wrote:
> skb->data -= dev->hard_header_len;
> skb->tail -= dev->hard_header_len;
>+ if (len < dev->hard_header_len)
>+ skb->nh.raw = skb->data;
> }
I'll try that. I'm currently rebuilding the kernel, APM is working lousy on my Compaq 12LX302 laptop so I'm recompiling without APIC to see if that makes a change. Anyway, that takes a while, I'll report back on this.
>which is sad. Not that it is wrong (it is wrong by design and not repairable
[snip]
>So, leave this as it is and try to switch to packet socket from SOCK_PACKET.
I would be happy to do this if I knew how. I posted the code I use now and I have to say that I'm not familiar with this socket business at all. When I build it I copy-catted it from other programs (mainly net2kiss), did a tidy up on stuff that seemed to be redundant and tried to make is sensible to me.
I also tried to get some information from the Internet about raw access (for the APRS digipeater I need full control over the received and transmitted AX.25 packets) after I got the first buggy message reports from the 2.1.x kernel because I was first convinced I just did something wrong out of ignorance. The only way I found is using SOCK_PACKET. The only deviation with which I was not too happy was having to use protocol family "ETH_P_AX25" instead of "PF_AX25" but with the latter - which seems to be the correct one if I understood all of this correctly - the transmitted data is echoed back to the receive socket which is not desired at all.
But I'm always in for improvements so if there is another way I'll be happy to swap my code for something better. I guess I have to live with SOCK_PACKET for use on older (2.0.36) kernels?
So I require help for this. I guess when a good alternative is known this will also make it to the AX.25 utilities. I've never seen any other way to do it yet, please educate me.
Kind regards,
Henk.
P.S. Maybe the discussion should now be taken of the lists as this is drifting off-topic now, at least for the linux-kernel list which is already loaded enough as it is...
next prev parent reply other threads:[~2001-12-30 22:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-28 16:41 link error in SCC driver Wichert Akkerman
2001-12-28 16:56 ` Dave Jones
2001-12-28 16:59 ` Wichert Akkerman
2001-12-28 17:08 ` Daniel T. Chen
2001-12-28 20:57 ` AX25/socket kernel PATCHes Henk de Groot
2001-12-28 23:09 ` Alan Cox
2001-12-28 23:15 ` Jeroen Vreeken
2001-12-29 17:29 ` Henk de Groot
2001-12-29 17:27 ` Henk de Groot
2001-12-29 18:02 ` Alan Cox
2001-12-29 20:37 ` kuznet
2001-12-29 23:56 ` Henk de Groot
2001-12-30 2:27 ` Alan Cox
2001-12-30 17:23 ` Henk de Groot
2001-12-30 22:13 ` Henk de Groot [this message]
2001-12-30 22:24 ` Sandor Dibuz
2002-01-01 22:32 ` Henk de Groot
2001-12-29 3:39 ` link error in SCC driver Keith Owens
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=5.1.0.14.2.20011230223848.00a2d570@pop.hetnet.nl \
--to=henk.de.groot@hetnet.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.