This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Access point crashing
#1
Hi,  since last night the access point has been causing problems a few minutes after rebooting. Pi3 (not +) set to RPi3: AP + client.   After a reboot it will work OK for a few minutes then show no internet connection on a connected device then disappear on laptop/tablet. Edit - OK, still showing up on a win10 laptop but getting "cannot connect to this network" error. Also a connected esp8266 will be unconnected. Using internal wifi & usb/wifi dongle. 

Not sure where to look.....   TIA

This when AP not working >

Code:
$ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
       ether b8:27:eb:0e:29:55  txqueuelen 1000  (Ethernet)
       RX packets 0  bytes 0 (0.0 B)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 0  bytes 0 (0.0 B)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
       inet 127.0.0.1  netmask 255.0.0.0
       inet6 ::1  prefixlen 128  scopeid 0x10<host>
       loop  txqueuelen 1000  (Local Loopback)
       RX packets 6527  bytes 628711 (613.9 KiB)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 6527  bytes 628711 (613.9 KiB)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
       inet 192.168.43.97  netmask 255.255.255.0  broadcast 192.168.43.255
       inet6 fe80::20f:60ff:fe05:8d9f  prefixlen 64  scopeid 0x20<link>
       ether 00:0f:60:05:8d:9f  txqueuelen 1000  (Ethernet)
       RX packets 12999  bytes 1709137 (1.6 MiB)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 16042  bytes 9325613 (8.8 MiB)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
       inet 10.10.10.1  netmask 255.255.255.0  broadcast 10.10.10.255
       inet6 fe80::ba27:ebff:fe5b:7c00  prefixlen 64  scopeid 0x20<link>
       ether b8:27:eb:5b:7c:00  txqueuelen 1000  (Ethernet)
       RX packets 8932  bytes 923405 (901.7 KiB)
       RX errors 0  dropped 4  overruns 0  frame 0
       TX packets 13710  bytes 7888369 (7.5 MiB)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0



Code:
pi@openplotter:~ $ head -n2  /home/pi/.openplotter/openplotter.conf && echo "---Raspbian version---" &&  cat /etc/os-release
[GENERAL]
version = 1.1.0
---Raspbian version---
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Reply
#2
mine too, i thought it might be a power issue.
i changed the power cord,power supply yesterday i hope that's all it was..testing now.
Reply
#3
(2018-07-21, 12:18 PM)jim321 Wrote: mine too, i thought it might be a power issue.
i changed the power cord,power supply yesterday i hope that's all it was..testing now.

Hmm, seems to be between 10 & 20 minutes. Pi getting powered from a hifiberry amp board, should have enough power - haven't seen any warnings. 

Not sure where to find any log of problems, a glance at dmesg doesn't show anything..


Wonder if it could be anything to do with a esp8266 connected? Been fine for ages though, usually eveything is on 24/7. Just rebooted with the esp turned off.
Reply
#4
its still not working right. on a reboot it takes a long long time before the esp8266 reconnects to mqtt server, pages load real slow from laptop connected to ap sometimes with a error page then loads the page,after waiting.
shows the limited conductivity triangle sometimes windows to op ap.
router it connects to is two meter away.and works as expected when connected to laptop.
i'll try another wifi dongle next..
SOMETIMES not always, sticks but eventually continues on reboot shutting down at bluetooth and get an error that goes by to fast to see on restart..
i'll look for the logs.
Reply
#5
(2018-07-21, 05:25 PM)jim321 Wrote: its still not working right. on a reboot it takes a long long time before the esp8266 reconnects to mqtt server, pages load real slow from laptop connected to ap sometimes with a error page then loads the page,after waiting.
shows the limited conductivity triangle sometimes windows to op ap.
router it connects to is two meter away.and works as expected when connected to laptop.
i'll try another wifi dongle next..
SOMETIMES not always,  sticks but eventually continues on reboot shutting down at bluetooth and get an error that goes by to fast to see on restart..
i'll look for the logs.

Hmm, mine seems stable again with no esp connected. About 4 hours and access point still up and running. Showing 2Mbs on speed test which is probably max for the mobile phone wifi. 
ESP was running easyesp - I'll try firing that up again. Do wifi issues get logged anywhere on raspbian? No idea what's going on.... familiar learning curve territory Smile
Reply
#6
found this
/var/log/daemon.log.1

i have some events
openplotter wpa_supplicant [1334]:wlan0:CTRL-EVENT-SCAN-FAILED ret=-110
Reply
#7
Lightbulb 
i think most problems i was having was using onboard wifi, changed to an adapter seems to be working much better..
i thought i was using a small adapter but when i went to connect my alfa "power hog" i found out i was using the onboard.
i'll mark that as a ID10T error..lol
Reply
#8
No idea what happened there, esp connected again all day and rock solid.
Reply
#9
And crashed again!!
Given up with espeasy, slowly going over to a bespoke sketch on the esp8266 (assuming that is actually the culprit) , based on https://github.com/ItKindaWorks/ESPHelper

Updating sketches over the air is just so handy! Cool
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)