Crosstalk between different netids
- Dominant language
- C
- Stars
- 343
- Forks
- 245
- PR merge metrics
- No merged PRs in 30d
Description
Using the current master, I noticed that I get some of the (mavlink) packets sent from a device with different netid.
Having 3 radios A (`netid = 25`, plugged to pixhawk), B (`netid = 25`) and C (`netid = 15`) (see complete config below), communication between A and B seems to work fine. Plugging radio C, I receive quiet a few of the mavlink packets sent by A.
Using the old [release-1-9](/ArduPilot/SiK/tree/release-1-9), I didn't notice such a behavior.
#### Radio A ####
```
ATI
RFD SiK 2.0 on HM-TRP
ATI5
S0:FORMAT=26
S1:SERIAL_SPEED=57
S2:AIR_SPEED=64
S3:NETID=25
S4:TXPOWER=20
S5:ECC=1
S6:MAVLINK=1
S7:OPPRESEND=0
S8:MIN_FREQ=433050
S9:MAX_FREQ=434790
S10:NUM_CHANNELS=10
S11:DUTY_CYCLE=100
S12:LBT_RSSI=0
S13:MANCHESTER=0
S14:RTSCTS=0
S15:MAX_WINDOW=131
```
#### Radio B ####
```
ATI
RFD SiK 2.0 on HM-TRP
ATI5
S0:FORMAT=26
S1:SERIAL_SPEED=57
S2:AIR_SPEED=64
S3:NETID=25
S4:TXPOWER=20
S5:ECC=1
S6:MAVLINK=1
S7:OPPRESEND=1
S8:MIN_FREQ=433050
S9:MAX_FREQ=434790
S10:NUM_CHANNELS=10
S11:DUTY_CYCLE=100
S12:LBT_RSSI=0
S13:MANCHESTER=0
S14:RTSCTS=0
S15:MAX_WINDOW=131
```
#### Radio C ####
```
ATI
RFD SiK 2.0 on HM-TRP
ATI5
S0:FORMAT=26
S1:SERIAL_SPEED=57
S2:AIR_SPEED=64
S3:NETID=15
S4:TXPOWER=20
S5:ECC=1
S6:MAVLINK=1
S7:OPPRESEND=0
S8:MIN_FREQ=433050
S9:MAX_FREQ=434790
S10:NUM_CHANNELS=10
S11:DUTY_CYCLE=100
S12:LBT_RSSI=0
S13:MANCHESTER=0
S14:RTSCTS=0
S15:MAX_WINDOW=131
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the three-radio setup from the issue using netids 25, 25, and 15, then compare current master with release-1-9. Trace how netid filtering handles MAVLink packets and determine why radio C receives packets from radio A. Done means radios with different netids no longer receive each other's packets while same-netid communication continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100