All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ugo Poddine <ugo.poddine@gmail.com>
To: linux-hams@vger.kernel.org
Subject: Re: Packet duplication in kernels 2.6 onwards
Date: Mon, 18 May 2015 06:15:53 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150518T080209-188@post.gmane.org> (raw)
In-Reply-To: 5558FA02.5070308@rns-stearn.demon.co.uk

Hello everyone, hi Richard,

a couple of remarks, regarding this issue.

a) "duplication" on the air

Indeed I discovered the problem exactly "on the air", at least using 
software "TNCs".
I have some logs taken from Direwolf or MIXw2 showing duplication being 
sent on the radio channel (I can share, if somebody needs), and also 
some reports from Canada (thanks to VE1JOT) reporing practical 
impossibility to transmit TCP over AX25 on HF channels due to the 
duplication.

b) 6PACK problem

I was curious to understand if the problem affects also 6PACK, but I was 
unable to test it : on Debian Wheezy, switching kissattack in 6pack mode 
always crashes the kernel, on Jessie it doesn’t, but no data exchange is 
possible and - worst - sniffing the interface always show "kiss" frames 
instead of 6PACK frames (at least in the ARP dialogue). This happens 
also on Fedora21. I opened a ticket on the Jessie side on Saturday. 

Thank-you
Regards
73, Ugo






  reply	other threads:[~2015-05-18  6:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04 18:30 Packet duplication in kernels 2.6 onwards Richard Stearn
2015-05-05  4:05 ` David Ranch
2015-05-06 15:01   ` Patrick Ouellette
     [not found] ` <55483EB3.6070600@trinnet.net>
2015-05-17 20:28   ` Richard Stearn
2015-05-18  6:15     ` Ugo Poddine [this message]
2015-05-20 12:33     ` Richard Stearn
2015-05-26  7:54       ` Ralf Baechle DL5RB
2015-05-26 15:09         ` Richard Stearn
2015-05-26  7:29 ` Ralf Baechle DL5RB

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=loom.20150518T080209-188@post.gmane.org \
    --to=ugo.poddine@gmail.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 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.