Hello,
As explained in another thread, see Hotspot failing on RPI4 - #14 by dvo, I would like to integrate volumio in a local network, without any internet connection. Moslty to take advantage of the Wifi access point and DHCP features of an old NETGEAR FWG114P router, which will be my central access point.
Volumio (vers 3.173) runs on a RPI4, music is on a USB3 HDD, and the RPI is wired to the router. I have assigned a static adress to Volumio in the router. Only one plugin is installed: Touch Plugin (I use a 7" display). And that’s it for the volumio side.
Other clients (Laptop under Linux or Windows, smartphone…) will connect through the router using wifi. The goal is to control music through these clients, in addition to the Touch Display attached to the RPI.
As explained in the other thread, I could not have this work with Volumio 2, but switching to V3 solved this. So, basically, it works. Connections are fast and stable. Fine.
Except that I see the light on the router, corresponding to the cable connection to volumio, constantly blinking, indicating traffic, even when doing nothing. I suspect that Volumio, seeing a gateway, is repeatidly trying to reach internet…
Maybe to see whether an update is available or not. Or for other “internal” reason, I don’t know.
Is there a way (configuration?) to disable these requests? Again, they are not a major issue, but I would find it safer to prevent this.
Any solution to this? Even through a manual patch, it will fit me. The goal is to have use only of this local configuration, I don’t need (and won’t use) internet once everything is installed on the RPI, it will remain as is. It’s a kind of standalone use.
Any help appreciated.
EDIT: jounalctl shows only ntp traffic, twice per minut. I’m not sure it is the cause of this blinking light.
I have manually stopped the ntp service. No more “ntp error” in journalclt (no error at all, in fact), but still blinking.
volumio@volumio-px:~$ journalctl -f
– Logs begin at Thu 2021-12-09 20:40:05 UTC. –
Dec 09 22:14:20 volumio-px ntpd[588]: error resolving pool 0.debian.pool.ntp.org: System error (-11)
Dec 09 22:14:48 volumio-px ntpd[588]: error resolving pool 3.debian.pool.ntp.org: System error (-11)
Dec 09 22:15:16 volumio-px ntpd[588]: error resolving pool 2.debian.pool.ntp.org: System error (-11)
Dec 09 22:15:45 volumio-px ntpd[588]: error resolving pool 1.debian.pool.ntp.org: System error (-11)
Dec 09 22:16:13 volumio-px ntpd[588]: error resolving pool 0.debian.pool.ntp.org: System error (-11)
Dec 09 22:16:41 volumio-px ntpd[588]: error resolving pool 3.debian.pool.ntp.org: System error (-11)
…
Dec 09 22:16:54 volumio-px sudo[2888]: volumio : TTY=pts/2 ; PWD=/home/volumio ; USER=root ; COMMAND=/bin/systemctl stop ntp
Dec 09 22:16:54 volumio-px sudo[2888]: pam_unix(sudo:session): session opened for user root by volumio(uid=0)
Dec 09 22:16:54 volumio-px ntpd[588]: ntpd exiting on signal 15 (Terminated)
Dec 09 22:16:54 volumio-px systemd[1]: Stopping Network Time Service…
Dec 09 22:16:54 volumio-px systemd[1]: ntp.service: Succeeded.
Dec 09 22:16:54 volumio-px systemd[1]: Stopped Network Time Service.
Dec 09 22:16:54 volumio-px sudo[2888]: pam_unix(sudo:session): session closed for user root
Dec 09 22:16:59 volumio-px sudo[2893]: volumio : TTY=pts/2 ; PWD=/home/volumio ; USER=root ; COMMAND=/bin/systemctl status ntp
Dec 09 22:16:59 volumio-px sudo[2893]: pam_unix(sudo:session): session opened for user root by volumio(uid=0)
Dec 09 22:16:59 volumio-px sudo[2893]: pam_unix(sudo:session): session closed for user root
…
Denis