fresh install - pialert.1.log - It is probably currently running scan

[JYewdall]

RPiOs Bookworm on a Pi3B running pi-hole v6.
A fresh install of PiAlert shows one device only - Internet and the log viewer permanently shows 'It is probably currently running scan'
pialert.conf has been edited for pi-hole v6
Forcing an update install leaves me with my expected network devices but the log viewer still permanently show 'It is probably currently running scan'

[JYewdall]

Uninstalled and reinsta!led - no change

[leiweibau]

Hello,

in your mail you write that you now have 2 networks and for this reason you want to operate a 2nd Pi.Alert instance. I actually built the Pi.Alert satellite for such cases. This only runs the scans, but the entire management remains with the actual Pi.Alert installation.

Could you perhaps tell me again exactly what the current structure of your network is, how you envision the end result and what you have already implemented to achieve your desired goal. An insight into the pialert.conf file/files would also help. If you don't want to make this public, we can also do this via email.

Please excuse me for not paying attention to the request here.

[JYewdall]

My original network is I suspect insecure as I found a rogue device. That network currently consists of a dd-wrt router behind a cable modem and with a wifi access point. The mesh wifi was intended to replace the original network but currently is sat on my original network natting local devices. ! moved most of my devices from the original network onto the new network including the working pihole/pialert pi leaving behind the pi3b running pihole. Devices on my new network are double natted. The espressif adapters in my new solar battery system cannot connect to the new mesh wifi so must remain on the old network hence the need for a working pialert on the old network. I initially installed Pi.Alert satellite but it did not work probably because it could not contact the pialert on the new network so was uninstalled. If I had known the solar battery system had to connect to a server in HongKong once a minute I would not have bought it. I lose my warranty if it goes offline for extended periods. If I had known this tp-link mesh wifi was so basic I would not have bought it.

[JYewdall]

Apologies for delay

General Settings

----------------------

PIALERT_PATH = '/home/pi/pialert'
DB_PATH = PIALERT_PATH + '/db/pialert.db'
LOG_PATH = PIALERT_PATH + '/log'
PRINT_LOG = False
VENDORS_DB = '/usr/share/arp-scan/ieee-oui.txt'
PIALERT_APIKEY = ''
PIALERT_WEB_PROTECTION = False
PIALERT_WEB_PASSWORD = '****************************************' [redacted]
NETWORK_DNS_SERVER = 'localhost'
AUTO_UPDATE_CHECK = True
AUTO_DB_BACKUP = False
AUTO_DB_BACKUP_KEEP = 5
REPORT_NEW_CONTINUOUS = False
NEW_DEVICE_PRESET_EVENTS = True
NEW_DEVICE_PRESET_DOWN = False
SYSTEM_TIMEZONE = 'Europe/London'
OFFLINE_MODE = False

Pi-hole Configuration

----------------------

PIHOLE_ACTIVE = True
PIHOLE_VERSION = 6
PIHOLE_DB = '/etc/pihole/pihole-FTL.db'
PIHOLE6_URL = 'http://localhost:8080/'
PIHOLE6_PASSWORD = '**********' [redacted]
PIHOLE6_API_MAXCLIENTS = 100
DHCP_ACTIVE = False
DHCP_LEASES = '/etc/pihole/dhcp.leases'
DHCP_INCL_SELF_TO_LEASES = False

[leiweibau]

Okay,

Apologies for delay

No need for excuses. I also had my difficulties over the turn of the year, which were more important than this project. I'm only slowly getting back to doing something here.

I'll summarize the structure for myself once again. You have an OpenWRT router that provides a WLAN. This WLAN (I'll call it W1) still contains older devices, as they only work with 2.4 GHz and can't cope with the new WLAN. The new mesh WLAN (I'll call it W2) is also connected to the OpenWRT router and also performs NAT again so that this mesh WLAN is isolated.

You write that it is a dd-wrt router and I assume at this point that it is OpenWRT. Am I right here?

I now see 2 possibilities here. One that is already working (A) and one that will come with the next update (B).

A:
You could install a satellite in W1. In addition, you install a web server and configure the API. The satellite can load its scan results onto this web server. In Pi.Alert in W2, configure the URL of the web server as SATELLITE_PROXY_URL so that Pi.Alert can retrieve the results.

B:
With the next update, Pi.Alert and Pi.Alert-Satellite will be able to import the active clients from OpenWRT. So if Pi.Alert can reach the web interface of the OpenWRT router and 'luci-mod-rpc' is installed on it, you do not need a satellite.

[JYewdall]

Dd-wrt is very much like openwrt. Option a and b sound above my pay grade. I am happy to have 2 pialert installs. I am sure the history of this failing pialert begins with a test install to help find out why my working pihole pialert was failing some months back. Remember the login to the API problem. When you fixed the V6 API login problem I uninstalled this working test pialert. When my network was split into 2 and I moved the working pialert onto my new network I installed pialert satellite which wouldn't work as it cannot access my working pialert. I then uninstalled the satellite and reinstalled pialert to find I now have this never ending scan.

[JYewdall]

Now working it would appear. I had to install using
sudo bash -c "$(wget -qLO - https://github.com/leiweibau/Pi.Alert/raw/main/install/pialert_install.sh)"
So it works when installed as root?

[leiweibau]

So it works when installed as root?

I have environments where Pi.Alert is installed via root, others are installed as a normal user. But here too there are additional differences between the distributions. Unfortunately, I can't and don't want to test everything, as this is a free time project.