Bug 197169 - duplicate packets on ax25 interfaces
Summary: duplicate packets on ax25 interfaces
Status: NEW
Alias: None
Product: Networking
Classification: Unclassified
Component: Other (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: Stephen Hemminger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-09 12:39 UTC by Gabor
Modified: 2022-02-16 15:14 UTC (History)
2 users (show)

See Also:
Kernel Version: 4.9.30
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Gabor 2017-10-09 12:39:47 UTC
all outgoing packets are duplicated on ax25 interface

steps to reproduce:

kissattach /dev/ttyS0 radio
ifconfig ax0 10.0.0.2
arp -H ax25 -s 10.0.0.111 TEST-0
tshark -i ax0
ping -c1 10.0.0.111            

root@debian:~# tshark -i ax0
Running as user "root" and group "root". This could be dangerous.
tshark: Lua: Error during loading:
 [string "/usr/share/wireshark/init.lua"]:44: dofile has been disabled due to running Wireshark as superuser. See https://wiki.wireshark.org/CaptureSetup/CapturePrivileges for help in running Wireshark as an unprivileged user.
Capturing on 'ax0'

    1 0.000000000     10.0.0.2 → 10.0.0.111   ICMP 101 Echo (ping) request  id=0x11a4, seq=1/256, ttl=64
    2 0.000005518     10.0.0.2 → 10.0.0.111   ICMP 101 Echo (ping) request  id=0x11a4, seq=1/256, ttl=64
Comment 1 Shad 2022-02-16 15:14:58 UTC
Found same duplicates in Wireshark log. I've test on "direwolf" software modem.

BUT, at least "direwolf" modem seems NOT sent this packages to channel. So duplicates do not appear in audio channel. Not sure, but seems it is some representations bug.

Also, "ifconfig ax0" show same picture - while Wireshark show two duplicate packets, "TX packets" counter increases only to one packet.

Any news about bug welcome!

Env:

Ubuntu 20.04 + Direwolf 1.7 (dev) + AX.25

My setup (for direct audio connect):

$ direwolf -p -B 19200 -n 1 -I 1
$ sudo /usr/sbin/kissattach $TNC_PTS vradio $IP

# Setup low delays + half duplex
$ sudo /usr/sbin/kissparms -p vradio -t 20 -s 10 -r 32 -l 50 -f n

Note You need to log in before you can comment on or make changes to this bug.