Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--net argument and testing? #6

Closed
GustelDE opened this issue Jan 25, 2023 · 2 comments
Closed

--net argument and testing? #6

GustelDE opened this issue Jan 25, 2023 · 2 comments

Comments

@GustelDE
Copy link

Hi, in the documentation is stated:

This requires an already running dump1090-mutability or dump1090-fa instance with the --net argument.

I have this default stuff in there:
/usr/bin/dump1090-fa --quiet --device-type rtlsdr --device-index 10900001 --gain 60 --adaptive-range --fix --lat 47.xxxxx --lon 11.xxxxx --max-range 360 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005 --json-location-accuracy 1 --write-json /run/dump1090-fa

Is this correct? If not, where (and what) do I have change?
And is there a way to test the injection of OGN-data into dump1090 in some way?

Thanks

@b3nn0
Copy link
Owner

b3nn0 commented Jan 26, 2023

It connects to beast port 30004, so your command should work, yes.
Testing: well.. by transmitting something that the OGN receiver can receive. E.g. an esp32-ogn-tracker.

@b3nn0 b3nn0 closed this as completed Jan 26, 2023
@GustelDE
Copy link
Author

Thanks! I understand it so: --net-bi-port stands for Beast-In? If true, ogn-injected data are going then out via --net-bo-port 30005 (bo = Beast-Out?)? VRS listens on port 30005, I assume tar1090 must listen on some of the 3000x-ports too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants