The "down" worked; the "up" didn't produce any error output but it
didn't work --- I had to reboot the Pi and the at output email came
through afterwards.
Any suggestions?
Every few days it disconnects from the wifi but keeps running
On 20/08/2021 11:24, Adam Funk wrote:
The "down" worked; the "up" didn't produce any error output but it
didn't work --- I had to reboot the Pi and the at output email came
through afterwards.
Any suggestions?
I wrote about 6months back about minimising SDcard wear when leaving a
Pi Zero W running 24/7. The Pi provides SSH access to my network from
the internet.
I mount all the logs etc. on /tmp to reduce SDcard wear and then to stop
/tmp filling up I take the simple but drastic fix of rebooting every
24hrs. There are better ways but for what this is used for, a gateway,
it works fine.
In those 6 months with a reboot every day the Wifi stays working and
I've never had a problem with Wifi connections failing or failing to
come up. This may be a less than perfect solution but should keep you
from having to intervene manually as long as you can accept the time it
takes to reboot in your logging. You could adjust the reboot time to be
now plus 24h 1m so the reboot time is different each day.
Not a fix but something to reduce your hassle.
Adam Funk <a24061@ducksburg.com> wrote:
Every few days it disconnects from the wifi but keeps running
Same here, I've always had this problem with my Zero based webcams. Tried
the same things you did. I have given up, reliable webcams are not possible with Raspberry Pi on wifi, as far as I am concerned. I asked a few times on the official forums but it always gets dismissed as "it works for me, i've never seen that" etc.
I suppose I ought to wire up a "safe shutdown" button:
<https://core-electronics.com.au/tutorials/how-to-make-a-safe-shutdown-button-for-raspberry-pi.html>
Or (lazy option) I could just crontab a reboot every night or two.
In article <m3j4vhx966.ln2@news.ducksburg.com>, a24061@ducksburg.com
says...
I suppose I ought to wire up a "safe shutdown" button:
<https://core-electronics.com.au/tutorials/how-to-make-a-safe-shutdown-button-for-raspberry-pi.html>
Or (lazy option) I could just crontab a reboot every night or two.
What I do is configure all my RPis to run a program which listens for
the insertion of a USB stick with disk or partition label SHUTDOWNPI.
No extra hardware needed!
Adam Funk <a24061@ducksburg.com> wrote:
Every few days it disconnects from the wifi but keeps running
Same here, I've always had this problem with my Zero based webcams. Tried
the same things you did. I have given up, reliable webcams are not possible with Raspberry Pi on wifi, as far as I am concerned. I asked a few times on the official forums but it always gets dismissed as "it works for me, i've never seen that" etc.
On 20/08/2021 12:33, A. Dumas wrote:
Adam Funk <a24061@ducksburg.com> wrote:My Pi Zero W says on logging onto it via wifi that its been up 26 days
Every few days it disconnects from the wifi but keeps running
Same here, I've always had this problem with my Zero based webcams. Tried
the same things you did. I have given up, reliable webcams are not possible >> with Raspberry Pi on wifi, as far as I am concerned. I asked a few times on >> the official forums but it always gets dismissed as "it works for me, i've >> never seen that" etc.
and so has the wifi
It may be actually a router or wifi point issue.
For sure the Pi is capable or maintaining a connection but I am not sure
it is capable or resetting one on loss of signal.
Im running mine about *3 feet* through a wall to a Netgear router re-configured as an ethernet to wifi bridge. before that I did have
problems with the pi going off line and it might have needed a reboot
This is the iwconfig for what is now reliable
$ iwconfig wlan0
wlan0 IEEE 802.11 ESSID:"xxxxxxx"
Mode:Managed Frequency:2.457 GHz Access Point:
30:46:9A:A2:89:F6
Bit Rate=65 Mb/s Tx-Power=31 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
Link Quality=44/70 Signal level=-66 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:5 Invalid misc:0 Missed beacon:0
* read a DHT-22 sensor (attached to the GPIO pins)
Every few days it disconnects from the wifi but keeps running (it
accumulates Tilt and DHT-22 data, and the emails stay in the
nullmailer queue). Because this Pi is headless, I have to cut the
power off and on (at the switched socket) to reconnect it.
On 2021-08-20, A Dumas wrote:
Adam Funk <a24061@ducksburg.com> wrote: > Every few days it disconnects
from the wifi but keeps running
Same here, I've always had this problem with my Zero based webcams.
Tried the same things you did. I have given up, reliable webcams are not possible with Raspberry Pi on wifi, as far as I am concerned. I asked a
few times on the official forums but it always gets dismissed as "it
works for me, i've never seen that" etc.
I suppose I ought to wire up a "safe shutdown" button:
<https://core-electronics.com.au/tutorials/how-to-make-a-safe-shutdown-but ton-for-raspberry-pi.html>
Or (lazy option) I could just crontab a reboot every night or two.
If the Pi doesn't have a fixed IP address assigned to it, then I'd
try that in case it's a problem with DHCP.
Failing that, perhaps you could try unloading then reloading the
WiFi driver module occasionally, between toggling the interface
down/up.
On 2021-08-20, Computer Nerd Kev wrote:
If the Pi doesn't have a fixed IP address assigned to it, then I'd
try that in case it's a problem with DHCP.
Worth trying --- until recently I thought the DHCP by MAC on the
router was good enough! I'll have to remember how to remove that on
the router though.
Failing that, perhaps you could try unloading then reloading the
WiFi driver module occasionally, between toggling the interface
down/up.
So something like this in the wifibump script?
/sbin/ip link set wlan0 down
modprobe -r brcmfmac
sleep 5
modprobe brcmfmac
/sbin/ip link set wlan0 up
I don't think you should need to actually, just don't run the DHCP
client on the Pi and set the IP address manually instead.
On Wed, 25 Aug 2021 22:24:05 +0000, Computer Nerd Kev wrote:
That works for me - I've done this on both RPi and my Fedora systems on
I don't think you should need to actually, just don't run the DHCP
client on the Pi and set the IP address manually instead.
my house LAN, which all have fixed IP addresses and hostnames.
/etc/hostname contains one line holding the fully qualified hostname as
it will be used locally, e.g.: rpi.local.lan
/etc/hosts contains at least:
IP-address fully-qualified-hostname list of aliases, e.g
192.168.5.2 rpi.local.lan rpi
In addition you can add other lines containing the IP, fqn aliases etc.
of printers, ADSL gateway, etc which have fixed IPs on your LAN. If all
hosts on your LAN have fixed IPs and hostnames then you don't need to run
a name service (e.g. named/unbound or DHCP server), and you can still run dhcp if sone devices on your LAN can't be configured to use a fixed IP address and host name.
Dana Wed, 25 Aug 2021 23:06:38 -0000 (UTC), Martin Gregorie <martin@mydomain.invalid> napis'o:
On Wed, 25 Aug 2021 22:24:05 +0000, Computer Nerd Kev wrote:
I don't think you should need to actually, just don't run the DHCPThat works for me - I've done this on both RPi and my Fedora systems on
client on the Pi and set the IP address manually instead.
my house LAN, which all have fixed IP addresses and hostnames.
/etc/hostname contains one line holding the fully qualified hostname as
it will be used locally, e.g.: rpi.local.lan
/etc/hosts contains at least:
IP-address fully-qualified-hostname list of aliases, e.g
192.168.5.2 rpi.local.lan rpi
In addition you can add other lines containing the IP, fqn aliases etc.
of printers, ADSL gateway, etc which have fixed IPs on your LAN. If all
hosts on your LAN have fixed IPs and hostnames then you don't need to run
a name service (e.g. named/unbound or DHCP server), and you can still run
dhcp if sone devices on your LAN can't be configured to use a fixed IP
address and host name.
Or he could configure DHCP server to give "static" fixed IPs to fixed MAC.
Adam Funk <a24061@ducksburg.com> wrote:
On 2021-08-20, Computer Nerd Kev wrote:
If the Pi doesn't have a fixed IP address assigned to it, then I'd
try that in case it's a problem with DHCP.
Worth trying --- until recently I thought the DHCP by MAC on the
router was good enough! I'll have to remember how to remove that on
the router though.
I don't think you should need to actually, just don't run the DHCP
client on the Pi and set the IP address manually instead.
Failing that, perhaps you could try unloading then reloading the
WiFi driver module occasionally, between toggling the interface
down/up.
So something like this in the wifibump script?
/sbin/ip link set wlan0 down
modprobe -r brcmfmac
sleep 5
modprobe brcmfmac
/sbin/ip link set wlan0 up
Yes, though if this is the same problem that you're having then
apparantly reloading the driver module doesn't work every time: http://web.archive.org/web/20201123161546/https://andreas.scherbaum.la/blog/archives/1001-Reboot-the-Raspberry-Pi-on-network-failures-brcmfmac-brcmf_cfg80211_scan-scan-error-110.html
Dana Wed, 25 Aug 2021 23:06:38 -0000 (UTC), Martin Gregorie <martin@mydomain.invalid> napis'o:
On Wed, 25 Aug 2021 22:24:05 +0000, Computer Nerd Kev wrote:
That works for me - I've done this on both RPi and my Fedora systems on
I don't think you should need to actually, just don't run the DHCP
client on the Pi and set the IP address manually instead.
my house LAN, which all have fixed IP addresses and hostnames.
/etc/hostname contains one line holding the fully qualified hostname as
it will be used locally, e.g.: rpi.local.lan
/etc/hosts contains at least:
IP-address fully-qualified-hostname list of aliases, e.g
192.168.5.2 rpi.local.lan rpi
In addition you can add other lines containing the IP, fqn aliases etc.
of printers, ADSL gateway, etc which have fixed IPs on your LAN. If all
hosts on your LAN have fixed IPs and hostnames then you don't need to run
a name service (e.g. named/unbound or DHCP server), and you can still run
dhcp if sone devices on your LAN can't be configured to use a fixed IP
address and host name.
Or he could configure DHCP server to give "static" fixed IPs to fixed MAC.
On 2021-08-25, Nikolaj Lazic wrote:
Dana Wed, 25 Aug 2021 23:06:38 -0000 (UTC), Martin Gregorie <martin@mydomain.invalid> napis'o:
On Wed, 25 Aug 2021 22:24:05 +0000, Computer Nerd Kev wrote:
That works for me - I've done this on both RPi and my Fedora systems on
I don't think you should need to actually, just don't run the DHCP
client on the Pi and set the IP address manually instead.
my house LAN, which all have fixed IP addresses and hostnames.
/etc/hostname contains one line holding the fully qualified hostname as
it will be used locally, e.g.: rpi.local.lan
/etc/hosts contains at least:
IP-address fully-qualified-hostname list of aliases, e.g
192.168.5.2 rpi.local.lan rpi
In addition you can add other lines containing the IP, fqn aliases etc.
of printers, ADSL gateway, etc which have fixed IPs on your LAN. If all
hosts on your LAN have fixed IPs and hostnames then you don't need to run >>> a name service (e.g. named/unbound or DHCP server), and you can still run >>> dhcp if sone devices on your LAN can't be configured to use a fixed IP
address and host name.
Or he could configure DHCP server to give "static" fixed IPs to fixed MAC.
That's what I was doing (DHCP "reservation" on the router). I'm now
trying a static IP address in the /etc/dhcpcd.conf file on the Pi
Zero.
| Sysop: | deepend |
|---|---|
| Location: | Calgary, Alberta |
| Users: | 264 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 31:00:48 |
| Calls: | 2,002 |
| Files: | 4,428 |
| D/L today: |
18 files (8,990K bytes) |
| Messages: | 410,046 |