mlat error

[abcd567]

(1) Open file rbfeeder.ini for editing
sudo nano /etc/rbfeeder.ini

(2) In file opened, in [mlat] section ADD line shown in RED
NOTE: The entire text in RED make one single line command, though forum might have wrapped it in 2 or 3 lines.



[client]
key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
sn=EXTRPI014534

lat=43.62
lon=-79.48
alt=128

network_mode=true
log_file=/var/log/rbfeeder.log
disable_log=0

sat_used=0

sat_visible=0

[network]
mode=beast
external_port=30205
external_host=127.0.0.1

[mlat]
autostart_mlat=true
#mlat_cmd=/usr/bin/python3.7 /usr/bin/mlat-client
mlat_cmd=/usr/bin/python3.7 /usr/bin/mlat-client --input-type dump1090 --input-connect 127.0.0.1:32457 --server mlat1.rb24.com:40900 --lat 43.62 --lon -79.48 --alt 128 --user EXTRPI014534 --results beast,connect,127.0.0.1:32004


(3) Save file (Press Ctrl & o Keys togather) and Close file (Press Ctrl & x Keys togather)

(4) Reboot Pi

(5) Check status. Is mlat line is there in CGroup: ?
sudo systemctl status rbfeeder

[Taxom]

here it is

[abcd567]

Delete the RED command you have added under [mlat]]  as per my previous post,  then reboot Pi,  then check status. L

[Taxom]

this

[abcd567]

Seems mlat-client installed from RB24 site (using command sudo apt install mlat-client) has some defect. Better purge it, then build & install from source code

(1) First purge existing package

Code: [Select]

sudo apt purge mlat-client


(2) Install dependencies and tools required to build package from source-code

Code: [Select]

sudo apt update -y
sudo apt install -y git curl build-essential debhelper python-dev python3-dev

(3) Downloaded source code and build mlat-client's installation package.

Code: [Select]

cd
git clone https://github.com/mutability/mlat-client.git

cd mlat-client
sudo apt install -y dh-python
sudo dpkg-buildpackage -b -uc


(4) Install newly built package by following command

Code: [Select]

cd
sudo dpkg -i mlat-client_*.deb 


[Taxom]

Will this not break me Mlat with other services?

[abcd567]

Will this not break me Mlat with other services?

No, it wont break your other feeders. The reason is that there are THREE (3) INDEPENDENT mlat-clients installed on your Pi. These 3 work independent of each other. If any one of these is removed or replaced, it will affect mlat of only that feeder for which it was installed. Other feeder's mlat will continue to work normally.

(1) Location of fa-mlat-client binary installed for Flightaware (installed automatically during installation of piaware)

Code: [Select]

/usr/lib/piaware/helpers/fa-mlat-client 

(2) Location of mlat-client binary installed for Adsbexchange (installed automatically during installation of Adsbexchange feeder)

Code: [Select]

/usr/local/share/adsbexchange/venv/bin/mlat-client 

(3) Location of mlat-client binary installed for Radarbox24 (installed manually by the user: sudo apt install mlat-client OR sudo dpkg -i mlat-client_*.deb)

Code: [Select]

/usr/bin/mlat-client


.

[Taxom]

something went wrong

[abcd567]

something went wrong

Oops, there were some minor errors in the commands which resulted in failure to build mlat-client from source code. I have made following corrections in my post for building mlat-client from source code. Now it will work ok.

(1) Changed:
cd /~

To:
cd


(2) Changed:
cd /mlat-client

To:
cd mlat-client

Please try to build and install mlat-client again using the corrected commands below:

Code: [Select]

cd 
cd mlat-client
sudo dpkg-buildpackage -b -uc


cd
sudo dpkg -i mlat-client_*.deb 


.

[Taxom]

Thank you very much! It worked!

[abcd567]

Glad to know your problem is solved   :)


.

[abcd567]

When in future any update/upgrade command is run, it will replace healthy mlat-client (which you have built yourself) by the defective mlat-client from RB24 repository.

To prevent this, put your mlat-client on hold by following command

Code: [Select]

sudo apt-mark hold  mlat-client 

The responce to above command will be:

mlat-client set on hold..



.

[Taxom]

Thank you.
Now I would like to figure out why, after some of the previous updates, OrangePi now changes the MAC address after each reboot.

[abcd567]

Now I would like to figure out why, after some of the previous updates, OrangePi now changes the MAC address after each reboot.

Very old post (June 2016), but may give you some insight.
On page below, scroll down to : (3) MAC address spoof


WORK AROUND FOR 5 ISSUES
Orange Pi PC / ARMBIAN 5.10 Debian 8 (jessie)



.


.

[Taxom]

This is the correct format /etc/network/interfaces for wifi

Code: [Select]

source /etc/network/interfaces.d/*
# Network is managed by Network manager
auto lo
iface lo inet loopback

iface wlan0
  hwaddress ether xx:xx:xx:FC:76:3F