ModeSDeco2 and ModeSMixer2 - console programs for RTLSDR and transcoding

[adsb4fun]

Im well aware im trying to sending data to www.google.com 

Its just for visualising that im having trouble to do DNS-lookups with modesmixer.

I have no trouble finding the DNS-record for www.google.com when i do a ping or a straight nslookup, but modesmixer does not seem to be able to.

It does not really matter if its a DNS name or an straight up IP-address, i just get "cant resolve host" from modesmixer.

The localhost vs 127.0.0.1 is of the same problem, modesmixer tries to do a lookup of the host set as inconnect, no matter if its an ip-address or hostname.

Its the "service not found". Which service?

root@test:~# /usr/bin/modesmixer2 --inConnect 127.0.0.1:30005 --outConnect beast:www.google.com:10000
2020-06-07 09:39:14.681  INFO     ModeSMixer2 v.20190413
2020-06-07 09:39:14.684  ERROR    outConnect(beast:www.google.com:10000) can't resolve host www.google.com Service not found
2020-06-07 09:39:14.684  INFO     outConnect(beast:www.google.com:10000) reconnect in 10 seconds
2020-06-07 09:39:14.685  ERROR    inConnect(127.0.0.1:30005) can't resolve host 127.0.0.1 Service not found
2020-06-07 09:39:14.685  INFO     inConnect(127.0.0.1:30005) reconnect in 10 seconds
2020-06-07 09:39:18.338  INFO     Closed successfully

root@test:~# nslookup www.google.com
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   www.google.com
Address: 216.58.207.196
Name:   www.google.com
Address: 2a00:1450:400f:809::2004

root@test:~# ping localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.063 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.079 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.076 ms
64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.080 ms

adsb4fun - looks like in some you are using the wrong commandlines

First one you are telling it to send your data to google.. (did you copy an example perhaps)

and the latter it is unable to resolve using the word 'localhost'. This has been an issue on trimmed OS as sometimes missed from /etc/hosts

You would be best to use --inConnect 127.0.0.1:30005 and nothing else and see if at least it can get to the local 30005 port rather than resolve 'localhost'

Then work out what the internal test it uses has been left off that distro.
It may be dnsutils/nslookup

I expect being diet, it is possibly missing stuff, or being blocked by Pihole which appears to come preloaded.

[sergsero]

Hello,

Its the "service not found". Which service?

Looks like a DNS issue. Might be due to PiHole service being stopped.
Whats the DNS server setting in dietpi-config > Networking Options > Ethernet?

Due to dietpi-services stopping pihole service prior to download.
May be the solution:
Check and enable pihole service during update.

Next check domain name resolution for local applications - it is handled by the service systemd-resolved
root@test:~# systemctl start systemd-resolved
root@test:~# systemctl enable systemd-resolved

Next - /etc/hostname and /etc/hosts is already updated when changing the host name via dietpi-config.
Please assure that entries in /etc/hostname and /etc/hosts match (and as well not all kind of characters are allowed).

E.g. example for test machine:
root@test:~# cat /etc/hostname
test

root@test:~# cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 test


However for some reason to be fail-safe, /etc/hosts should look like this:
127.0.0.1 localhost
127.0.1.1 <hostname>
with matching /etc/hostname.

The 127.0.0.1 should be associated with localhost and optionally localhost.localdomain only.
The FQDN (fully qualified domain name)/host name otherwise should be associated with either a static external IP that points to this host directly or (AFAIK in all NAT situations) 127.0.1.1. Otherwise asking the system for the FQDN (e.g. hostname -f) would show the local domain instead of the wanted (external) FQDN.
If you indeed have a static external IP, then replace 127.0.1.1 with it.
127.0.0.1 localhost
127.0.1.1 <your_FQDN_hostname>

If this was not available on your LAN except via the static ip. To make it accessible internally have to add the line (example for network 192.168.x.x):
192.168.x.x <your_FQDN_hostname>

Best regards,
sergsero

[abcd567]

A Little Enhancement to Automated install Script for ModeSMixer2

At the very start of installtion, the script creates a folder /usr/share/mm2
Next things script does are:
- downloads the .tgz file from Google Drive
- extracts binary modesmixer2
- creates config and startup script files.

The script stores all above files in the folder /usr/share/mm2
The purpose was for user to find all files at one place.

However it has the disadvantage that if someone wanted to run commands "modesmixer2 -h" or "modesmixer2 --inConnect 127.0.0.1:30005" from home folder, he would get responce "file not found". The person had to add full path to binary "/usr/share/mm2/modesmixer2 -h" or "/usr/share/mm2/modesmixer2 --inConnect 127.0.0.1:30005".

To overcome this shortcoming, in installation script I have added command to create a symlink to modesmixer2 binary in folder /usr/bin. In installs done from now on, commands issued from home folder will not require full path to the modesmixer2 binary.

For existing installs, users can add this symlink by manually issuing this command:

Code Select Expand


sudo ln -s /usr/share/mm2/modesmixer2 /usr/bin/modesmixer2


[adsb4fun]

Hi!

Thanks for responding!

This is really a bare minimum installation. No added software at all from the dietpi repository. Only change is default Dropbear that has been replaced by OpenSSH.

So no Pihole.

These are all services running (except stopped adsb-related software)

root       102  0.0  0.6  37600  6660 ?        Ss   May27   0:20 /lib/systemd/systemd-journald
root       148  0.0  0.3  17624  3752 ?        Ss   May27   0:02 /lib/systemd/systemd-udevd
message+   231  0.0  0.2   6556  2936 ?        Ss   May27   0:02 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
root       241  0.0  0.5  12908  5520 ?        Ss   May27   0:04 /lib/systemd/systemd-logind
root       247  0.0  0.0  27656    80 ?        SLsl May27   0:42 /usr/sbin/rngd -r /dev/hwrng
root       467  0.0  0.4   7912  4904 ?        Ss   May27   0:00 /sbin/dhclient -4 -v -i -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -I -df /var/lib/dhcp/dhclient6.eth0.leases eth0
root       603  0.0  0.1   6616  1864 ttyS0    Ss+  May27   0:00 /sbin/agetty -o -p -- \u --keep-baud 115200,38400,9600 ttyS0 vt220
root       898  0.0  0.1   4308  1240 tty1     Ss+  May27   0:00 /sbin/agetty -o -p -- \u --noclear tty1 linux
root       901  0.0  0.5  10724  5684 ?        Ss   May27   0:00 /usr/sbin/sshd -D
root       937  0.0  0.2   7948  2328 ?        Ss   May27   0:02 /usr/sbin/cron -f
root     24522  0.0  0.4  12284  4988 ?        Rs   Jun07   0:01 /usr/bin/ssh -o StrictHostKeyChecking=yes -o ExitOnForwardFailure yes -NT -R 9999:localhost:22 secure@tunnel.xxx.xxx

Started per your recommendation, no change, same problem.
systemd+ 27006  0.0  0.6  19164  6536 ?        Ss   10:56   0:00 /lib/systemd/systemd-resolved

/etc/hostname
root@test:~# more /etc/hostname
test

/etc/hosts
root@test:~# more /etc/hosts
127.0.0.1 localhost
127.0.1.1 test

No static IP

If i run tcpdump, doing a regular ping to www.google.com, works. Starting modesmixer, no packets.

root@test:~# tcpdump -nn -i eth0 -u port 53
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
11:21:03.057883 IP 192.168.1.228.45735 > 8.8.8.8.53: 37918+ A? www.google.com. (32)
11:21:03.084276 IP 8.8.8.8.53 > 192.168.1.228.45735: 37918 1/0/0 A 172.217.22.164 (48)
11:21:03.113808 IP 192.168.1.228.60363 > 8.8.8.8.53: 16195+ PTR? 164.22.217.172.in-addr.arpa. (45)
11:21:03.144789 IP 8.8.8.8.53 > 192.168.1.228.60363: 16195 2/0/0 PTR arn09s11-in-f4.1e100.net., PTR arn09s11-in-f164.1e100.net. (114)

As described before (se previous posts for examples), no other binary has problems doing lookups. Dump1090/Readsb, mlat-client, ping, nslookup, apt, curl, ntp etc, all work.

(I have been running ModeSMixer2 together with dump1090 and mlat-client on Dietpi since 2015. A few iterations and releases of dietpi (and Debian) since then, on multiple devices.)

Grateful that you take your time looking into this!

Hello,

Its the "service not found". Which service?

Looks like a DNS issue. Might be due to PiHole service being stopped.
Whats the DNS server setting in dietpi-config > Networking Options > Ethernet?

Due to dietpi-services stopping pihole service prior to download.
May be the solution:
Check and enable pihole service during update.

Next check domain name resolution for local applications - it is handled by the service systemd-resolved
root@test:~# systemctl start systemd-resolved
root@test:~# systemctl enable systemd-resolved

Next - /etc/hostname and /etc/hosts is already updated when changing the host name via dietpi-config.
Please assure that entries in /etc/hostname and /etc/hosts match (and as well not all kind of characters are allowed).

E.g. example for test machine:
root@test:~# cat /etc/hostname
test

root@test:~# cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 test


However for some reason to be fail-safe, /etc/hosts should look like this:
127.0.0.1 localhost
127.0.1.1 <hostname>
with matching /etc/hostname.

The 127.0.0.1 should be associated with localhost and optionally localhost.localdomain only.
The FQDN (fully qualified domain name)/host name otherwise should be associated with either a static external IP that points to this host directly or (AFAIK in all NAT situations) 127.0.1.1. Otherwise asking the system for the FQDN (e.g. hostname -f) would show the local domain instead of the wanted (external) FQDN.
If you indeed have a static external IP, then replace 127.0.1.1 with it.
127.0.0.1 localhost
127.0.1.1 <your_FQDN_hostname>

If this was not available on your LAN except via the static ip. To make it accessible internally have to add the line (example for network 192.168.x.x):
192.168.x.x <your_FQDN_hostname>

Best regards,
sergsero

[abcd567]

Manual method of installing MULTIPLE instances of ModeSMixer2 on a RPi using systemd.

In this tutorial, I will create 3 instances (copies). This method can be expanded to any number of instances (copies) required.


(1) Create a folder "modesmixer" to store all files

Code Select Expand


sudo mkdir /usr/share/modesmixer 


(2) Download ModeSMixer2 file from Google Drive 

Code Select Expand


sudo wget -O /usr/share/modesmixer/modesmixer2_rpi2-3_deb9_20190223.tgz "https://drive.google.com/uc?export=download&id=18DjTxitzZj9RsVPxt7lmnptfL5eZqHxJ"   


(3) Unzip downloaded file 

Code Select Expand


sudo tar xvzf /usr/share/modesmixer/modesmixer2_rpi2-3_deb9_20190223.tgz -C /usr/share/modesmixer   


(4) Create a symbolic link to the modesmixer2 binary in the folder "/usr/bin/"

Code Select Expand


sudo ln -s /usr/share/modesmixer/modesmixer2 /usr/bin/modesmixer2 



(5) Startup script file
(5.1) Create a blank startup script file "startup-mm2.sh"

Code Select Expand


sudo nano /usr/share/modesmixer/startup-mm2.sh   


(5.2) Copy-paste the following code into the startup file "startup-mm2.sh", then save the file

Code Select Expand


#!/bin/sh
CONFIG=""
while read -r line; do CONFIG="${CONFIG} $line"; done < /usr/share/modesmixer/$1.conf
/usr/share/modesmixer/modesmixer2 ${CONFIG}



(5.3) Make "startup-mm2.sh" file executable

Code Select Expand


sudo chmod +x /usr/share/modesmixer/startup-mm2.sh 


(6) Systemd Service file

(6.1) Create the service file "mm2@.service"

Code Select Expand


sudo nano /lib/systemd/system/mm2@.service 


(6.2) Copy-paste the following code into the service file, then save the file "mm2@.service"

Code Select Expand


[Unit]
Description=modesmixer2 copy %i
Wants=network.target
After=network.target
[Service]
RuntimeDirectory=%i
RuntimeDirectoryMode=0755
ExecStart=/bin/bash /usr/share/modesmixer/startup-mm2.sh %i
SyslogIdentifier=%i
Type=simple
Restart=on-failure
RestartSec=30
RestartPreventExitStatus=64
Nice=-5
[Install]
WantedBy=default.target




(7) Individual configuration files for all the instances

(7.1) Create configuration file "01.conf" for 1st instance of modesmixer2

Code Select Expand


sudo nano /usr/share/modesmixer/01.conf 


Copy-paste the following code into the configuration file "01.conf ", then save the file

Code Select Expand


--inConnectId 127.0.0.1:30005:ADSB
--inConnectId 127.0.0.1:30105:MLAT
--web 8181



(7.2) Create configuration file "02.conf" for 2nd instance of modesmixer2

Code Select Expand


sudo nano /usr/share/modesmixer/02.conf 


Copy-paste the following code into the configuration file "02.conf ", then save the file

Code Select Expand


--inConnectId 127.0.0.1:30005:ADSB
--inConnectId 127.0.0.1:30105:MLAT
--web 8282



(7.3) Create configuration file "03.conf" for 3rd instance of modesmixer2

Code Select Expand


sudo nano /usr/share/modesmixer/03.conf   


Copy-paste the following code into the configuration file "03.conf ", then save the file

Code Select Expand


--inConnectId 127.0.0.1:30005:ADSB
--inConnectId 127.0.0.1:30105:MLAT
--web 8383



( 8 ) Enable systemd service, and start all instances

(8.1) Instance 1

Code Select Expand


sudo systemctl enable mm2@01 
sudo systemctl start mm2@01 
sudo systemctl status mm2@01 


(8.2) Insrance 2

Code Select Expand


sudo systemctl enable mm2@02 
sudo systemctl start mm2@02   
sudo systemctl status mm2@02 


(8.3) Instance 3

Code Select Expand


sudo systemctl enable mm2@03 
sudo systemctl start mm2@03   
sudo systemctl status mm2@03 


(9) Check web interfaces in your browser:
- Instance 01 at:  IP-of-Pi:8181
- Instance 02 at:  IP-of-Pi:8282
- Instance 03 at:  IP-of-Pi:8383

(10) To create additional Instances:

(a) Create additional config files 04.conf, 05.conf, etc as in step (7).

(b) Enable systemd service mm2@04, mm2@05, etc as in step( 8 ).

[adsb4fun]

*BUMP* Any ideas around this?

(The problem is easy to re-create by installing a plain dietpi-box and try to run the latest ModesMixer binary)

Hi!

Thanks for responding!

This is really a bare minimum installation. No added software at all from the dietpi repository. Only change is default Dropbear that has been replaced by OpenSSH.

So no Pihole.

These are all services running (except stopped adsb-related software)

root       102  0.0  0.6  37600  6660 ?        Ss   May27   0:20 /lib/systemd/systemd-journald
root       148  0.0  0.3  17624  3752 ?        Ss   May27   0:02 /lib/systemd/systemd-udevd
message+   231  0.0  0.2   6556  2936 ?        Ss   May27   0:02 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
root       241  0.0  0.5  12908  5520 ?        Ss   May27   0:04 /lib/systemd/systemd-logind
root       247  0.0  0.0  27656    80 ?        SLsl May27   0:42 /usr/sbin/rngd -r /dev/hwrng
root       467  0.0  0.4   7912  4904 ?        Ss   May27   0:00 /sbin/dhclient -4 -v -i -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -I -df /var/lib/dhcp/dhclient6.eth0.leases eth0
root       603  0.0  0.1   6616  1864 ttyS0    Ss+  May27   0:00 /sbin/agetty -o -p -- \u --keep-baud 115200,38400,9600 ttyS0 vt220
root       898  0.0  0.1   4308  1240 tty1     Ss+  May27   0:00 /sbin/agetty -o -p -- \u --noclear tty1 linux
root       901  0.0  0.5  10724  5684 ?        Ss   May27   0:00 /usr/sbin/sshd -D
root       937  0.0  0.2   7948  2328 ?        Ss   May27   0:02 /usr/sbin/cron -f
root     24522  0.0  0.4  12284  4988 ?        Rs   Jun07   0:01 /usr/bin/ssh -o StrictHostKeyChecking=yes -o ExitOnForwardFailure yes -NT -R 9999:localhost:22 secure@tunnel.xxx.xxx

Started per your recommendation, no change, same problem.
systemd+ 27006  0.0  0.6  19164  6536 ?        Ss   10:56   0:00 /lib/systemd/systemd-resolved

/etc/hostname
root@test:~# more /etc/hostname
test

/etc/hosts
root@test:~# more /etc/hosts
127.0.0.1 localhost
127.0.1.1 test

No static IP

If i run tcpdump, doing a regular ping to www.google.com, works. Starting modesmixer, no packets.

root@test:~# tcpdump -nn -i eth0 -u port 53
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
11:21:03.057883 IP 192.168.1.228.45735 > 8.8.8.8.53: 37918+ A? www.google.com. (32)
11:21:03.084276 IP 8.8.8.8.53 > 192.168.1.228.45735: 37918 1/0/0 A 172.217.22.164 (48)
11:21:03.113808 IP 192.168.1.228.60363 > 8.8.8.8.53: 16195+ PTR? 164.22.217.172.in-addr.arpa. (45)
11:21:03.144789 IP 8.8.8.8.53 > 192.168.1.228.60363: 16195 2/0/0 PTR arn09s11-in-f4.1e100.net., PTR arn09s11-in-f164.1e100.net. (114)

As described before (se previous posts for examples), no other binary has problems doing lookups. Dump1090/Readsb, mlat-client, ping, nslookup, apt, curl, ntp etc, all work.

(I have been running ModeSMixer2 together with dump1090 and mlat-client on Dietpi since 2015. A few iterations and releases of dietpi (and Debian) since then, on multiple devices.)

Grateful that you take your time looking into this!

Hello,

Its the "service not found". Which service?

Looks like a DNS issue. Might be due to PiHole service being stopped.
Whats the DNS server setting in dietpi-config > Networking Options > Ethernet?

Due to dietpi-services stopping pihole service prior to download.
May be the solution:
Check and enable pihole service during update.

Next check domain name resolution for local applications - it is handled by the service systemd-resolved
root@test:~# systemctl start systemd-resolved
root@test:~# systemctl enable systemd-resolved

Next - /etc/hostname and /etc/hosts is already updated when changing the host name via dietpi-config.
Please assure that entries in /etc/hostname and /etc/hosts match (and as well not all kind of characters are allowed).

E.g. example for test machine:
root@test:~# cat /etc/hostname
test

root@test:~# cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 test


However for some reason to be fail-safe, /etc/hosts should look like this:
127.0.0.1 localhost
127.0.1.1 <hostname>
with matching /etc/hostname.

The 127.0.0.1 should be associated with localhost and optionally localhost.localdomain only.
The FQDN (fully qualified domain name)/host name otherwise should be associated with either a static external IP that points to this host directly or (AFAIK in all NAT situations) 127.0.1.1. Otherwise asking the system for the FQDN (e.g. hostname -f) would show the local domain instead of the wanted (external) FQDN.
If you indeed have a static external IP, then replace 127.0.1.1 with it.
127.0.0.1 localhost
127.0.1.1 <your_FQDN_hostname>

If this was not available on your LAN except via the static ip. To make it accessible internally have to add the line (example for network 192.168.x.x):
192.168.x.x <your_FQDN_hostname>

Best regards,
sergsero

[mikkyo]

Any idea how to get a BaseStation.sqb and FlightRoutes.sqb to work with mm2?
I tried copying the ones from by VRS install, but it doesn't like them...
Seems like it doesn't like the schema.

Added to the mm2.conf

--db /home/pi/BaseStation.sqb
--frdb /home/pi/FlightRoutes.sqb

Code Select Expand

ERROR    sqlite3_prepare_v2() SELECT LocationID FROM Locations ORDER BY LocationID DESC LIMIT 1; no such table: Locations
terminate called after throwing an instance of 'BaseStationDbException'
what():  sqlite3_prepare_v2() SELECT LocationID FROM Locations ORDER BY LocationID DESC LIMIT 1; no such table: Locations
/usr/share/mm2/mm2.sh: line 4:  2718 Aborted                 /usr/share/mm2/modesmixer2 ${CONFIG}


and removing the --db line and just leaving the --frdb

Code Select Expand

ERROR    sqlite3_prepare_v2() SELECT route FROM FlightRoute WHERE flight = ? ORDER BY updatetime DESC LIMIT 1; no such
ERROR    sqlite3_step() no such table: FlightRoute 1

I thought if maybe if I gave it an empty file, it would set up the db, but no such luck.
Anyone done a empty schema dump ever?

[sergsero]

Hello,

Your error message, "no such table", probably is telling that the table doesn't exist in the database. This can happen if during any time you created the database but failed to create the tables. And if that ever happened sqlite3_open will, if it doesn't find the database, will create a blank database (with, obviously, no event table). And subsequent attempts to run MM2 will find this blank database and incorrectly conclude that it doesn't exist.

MM2 uses a standard database whose structure is identical by 'Kinetic Avionics'. However, the database file itself must already have been created by third-party tools. MM2 is able to work with the database in two modes: read and write, and read-only.

You can take a ready-made existing database file basestation.sqb by downloading it from some resources on the Internet. Or create it again using the VRS plugin.

Make sure that the DatabaseWriterPlugin plugin is installed in your VRS instance.
1. Run Virtual Radar Server and click <Tools>|<Plugins>. You will be shown a list of all installed plugins.
2. Find the <Database Writer> and click the <Options> button to bring up the configuration screen.
3. In <Database filename> enter the full path and filename of the NEW (doesn't exist yet) database file here.
4. Click the button <Create Database> will create an empty SQLite database file using the name and folder from <Database filename>.

Attention!
Only click this button if you have actually changed and entered a different full path and file name that does not yet have a database and that differs from the ones where you use your main (existing) database file.

VRS will create a new database file with the necessary structure, which you can use in MM2.

/sergsero

[hdphilip]

Hi,
on the ModeSmixer2 console, is it possible to change the map icons to resemble the type of aircraft? currently all of my icons look like 747's.

thanks,

[adsb4fun]

Problem solved. Installed package "netbase" which seems to be required for name lookups by ModesMixer.

*BUMP* Any ideas around this?

(The problem is easy to re-create by installing a plain dietpi-box and try to run the latest ModesMixer binary)

Hi!

Thanks for responding!

This is really a bare minimum installation. No added software at all from the dietpi repository. Only change is default Dropbear that has been replaced by OpenSSH.

So no Pihole.

These are all services running (except stopped adsb-related software)

root       102  0.0  0.6  37600  6660 ?        Ss   May27   0:20 /lib/systemd/systemd-journald
root       148  0.0  0.3  17624  3752 ?        Ss   May27   0:02 /lib/systemd/systemd-udevd
message+   231  0.0  0.2   6556  2936 ?        Ss   May27   0:02 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
root       241  0.0  0.5  12908  5520 ?        Ss   May27   0:04 /lib/systemd/systemd-logind
root       247  0.0  0.0  27656    80 ?        SLsl May27   0:42 /usr/sbin/rngd -r /dev/hwrng
root       467  0.0  0.4   7912  4904 ?        Ss   May27   0:00 /sbin/dhclient -4 -v -i -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -I -df /var/lib/dhcp/dhclient6.eth0.leases eth0
root       603  0.0  0.1   6616  1864 ttyS0    Ss+  May27   0:00 /sbin/agetty -o -p -- \u --keep-baud 115200,38400,9600 ttyS0 vt220
root       898  0.0  0.1   4308  1240 tty1     Ss+  May27   0:00 /sbin/agetty -o -p -- \u --noclear tty1 linux
root       901  0.0  0.5  10724  5684 ?        Ss   May27   0:00 /usr/sbin/sshd -D
root       937  0.0  0.2   7948  2328 ?        Ss   May27   0:02 /usr/sbin/cron -f
root     24522  0.0  0.4  12284  4988 ?        Rs   Jun07   0:01 /usr/bin/ssh -o StrictHostKeyChecking=yes -o ExitOnForwardFailure yes -NT -R 9999:localhost:22 secure@tunnel.xxx.xxx

Started per your recommendation, no change, same problem.
systemd+ 27006  0.0  0.6  19164  6536 ?        Ss   10:56   0:00 /lib/systemd/systemd-resolved

/etc/hostname
root@test:~# more /etc/hostname
test

/etc/hosts
root@test:~# more /etc/hosts
127.0.0.1 localhost
127.0.1.1 test

No static IP

If i run tcpdump, doing a regular ping to www.google.com, works. Starting modesmixer, no packets.

root@test:~# tcpdump -nn -i eth0 -u port 53
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
11:21:03.057883 IP 192.168.1.228.45735 > 8.8.8.8.53: 37918+ A? www.google.com. (32)
11:21:03.084276 IP 8.8.8.8.53 > 192.168.1.228.45735: 37918 1/0/0 A 172.217.22.164 (48)
11:21:03.113808 IP 192.168.1.228.60363 > 8.8.8.8.53: 16195+ PTR? 164.22.217.172.in-addr.arpa. (45)
11:21:03.144789 IP 8.8.8.8.53 > 192.168.1.228.60363: 16195 2/0/0 PTR arn09s11-in-f4.1e100.net., PTR arn09s11-in-f164.1e100.net. (114)

As described before (se previous posts for examples), no other binary has problems doing lookups. Dump1090/Readsb, mlat-client, ping, nslookup, apt, curl, ntp etc, all work.

(I have been running ModeSMixer2 together with dump1090 and mlat-client on Dietpi since 2015. A few iterations and releases of dietpi (and Debian) since then, on multiple devices.)

Grateful that you take your time looking into this!

Hello,

Its the "service not found". Which service?

Looks like a DNS issue. Might be due to PiHole service being stopped.
Whats the DNS server setting in dietpi-config > Networking Options > Ethernet?

Due to dietpi-services stopping pihole service prior to download.
May be the solution:
Check and enable pihole service during update.

Next check domain name resolution for local applications - it is handled by the service systemd-resolved
root@test:~# systemctl start systemd-resolved
root@test:~# systemctl enable systemd-resolved

Next - /etc/hostname and /etc/hosts is already updated when changing the host name via dietpi-config.
Please assure that entries in /etc/hostname and /etc/hosts match (and as well not all kind of characters are allowed).

E.g. example for test machine:
root@test:~# cat /etc/hostname
test

root@test:~# cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 test


However for some reason to be fail-safe, /etc/hosts should look like this:
127.0.0.1 localhost
127.0.1.1 <hostname>
with matching /etc/hostname.

The 127.0.0.1 should be associated with localhost and optionally localhost.localdomain only.
The FQDN (fully qualified domain name)/host name otherwise should be associated with either a static external IP that points to this host directly or (AFAIK in all NAT situations) 127.0.1.1. Otherwise asking the system for the FQDN (e.g. hostname -f) would show the local domain instead of the wanted (external) FQDN.
If you indeed have a static external IP, then replace 127.0.1.1 with it.
127.0.0.1 localhost
127.0.1.1 <your_FQDN_hostname>

If this was not available on your LAN except via the static ip. To make it accessible internally have to add the line (example for network 192.168.x.x):
192.168.x.x <your_FQDN_hostname>

Best regards,
sergsero

[Oblivian]

It appears it's not the first time DietPi lacking it has struck

https://forum.radarbox24.com/index.php?topic=101981.msg400661#msg400661

abcd567 to the rescue back then too.

[adsb4fun]

Yepp. Not sure what is lacking though. All other software (readsb, mlat-client, ping, ntp, apt, curl etc.) had no problem with name lookups, only Modesmixer.

For me, this is somewhat to expect when going "of path" running something called DIETpi and being stripped down to bare minimal. Not blaming any part here.

It appears it's not the first time DietPi lacking it has struck

https://forum.radarbox24.com/index.php?topic=101981.msg400661#msg400661

abcd567 to the rescue back then too.

[airvb]

Hello all
modesmixerversion : modesmixer2_Ubuntu_18.04_x86_64_20190223

Today i update my own ubuntu server to 20.04.1.

modesmixer2  doesn't want to restart

The snag is the same as few month away

Code Select Expand

/modesmixer2: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory


Code Select Expand

modesmixer2$  ldd modesmixer2
linux-vdso.so.1 (0x00007ffeee181000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fb92a2cc000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fb92a2c1000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fb92a2bb000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fb92a0da000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fb929f8b000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fb929f70000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb929d7c000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb92a8a9000)

   libssl.so.1.0.0 => not found
   libcrypto.so.1.0.0 => not found

Code Select Expand

sudo apt install libssl1.0.0 libssl-dev
[sudo] password for airvb:
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package libssl1.0.0 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libssl1.0.0' has no installation candidate



Any idea ?

Thanks

[sergsero]

Hello,

Please use this version of modesmixer2 if your operating system is Ubuntu 20.04 64 bit: https://drive.google.com/file/d/1BH7zPxzk7qTMhhGOD6KPHMnM7qRf4_Dc/view?usp=sharing

Best regards,
sergsero

[airvb]

Super Sergio, work like a charm

Thanks again for all .

PS : Is it expecting to use OpenStreetMap ?