Project

General

Profile

Bug #4798

fake_trx send TRXC responses from wrong source address

Added by laforge 10 days ago. Updated 10 days ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
TRX Toolkit
Target version:
-
Start date:
10/11/2020
Due date:
% Done:

0%

Resolution:
Spec Reference:

Description

I'm starting fake_trx.py like this:

./fake_trx.py -R 127.0.0.21 -r 127.0.0.21 --trx TRX1@127.0.0.21:5700/1   --trx TRX2@127.0.0.21:5700/2 --trx TRX3@127.0.0.21:5700/3

And then osmo-bts-trx is sending TRXC commands from 127.0.0.20 to 127.0.0.21, and fake_trx.py responds. However, the response originates from 127.0.0.1 instead of the 127.0.0.21 that was configured.

Subsequently, osmo-bts-trx rejects those UDP responses as (presumably) the socket is fully connected and hence only accepts packets with correct source ip+port.

pcap file attached.

fake_trx_wrong_source.png View fake_trx_wrong_source.png 18.7 KB laforge, 10/11/2020 03:58 PM
fake_trx_wrong_source.pcap fake_trx_wrong_source.pcap 4.11 KB laforge, 10/11/2020 03:58 PM
4309

History

#1 Updated by lynxis 10 days ago

  • Status changed from New to Feedback
  • Assignee changed from fixeria to laforge

I'm using for my ttcn3 test cases:

../../osmocom-bb//src/target/trx_toolkit/fake_trx.py -b 127.0.0.21 -R 127.0.0.20 -r 127.0.0.22  --trx TRX1@127.0.0.20:5700/1  --trx TRX2@127.0.0.20:5700/2  --trx TRX3@127.0.0.20:5700/3

-b for the bind address

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)