Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Sudden Wifi Issues #2647

Closed
sectshun8 opened this issue Jan 19, 2021 · 47 comments
Closed

Sudden Wifi Issues #2647

sectshun8 opened this issue Jan 19, 2021 · 47 comments
Labels
help wanted troubleshooting

Comments

@sectshun8
Copy link

sectshun8 commented Jan 19, 2021 •
edited
Loading

Preliminary Docs

I confirm that I have read the CONTRIBUTING guide before opening this issue.

I confirm that I have read the FAQ before opening this issue.

motionEyeOS Version

Have tried various versions...

Board Model

Raspberry PI 3B+

Network Connection

My motionEyeOS unit is connected to the network via: Wifi, though Wired for initial setup

So I've been using motionEyeOS since late 2018 and never had any issues until now. I work offshore and this allows me a nice way to keep tabs on my home when I'm away. About halfway through last month, I noticed my cams had gone offline. When I got home, I tried connecting locally via the wifi and I could not connect to my devices, even though my router showed they were indeed connected to the network. Could not ping them either.

I have two cameras, both on Pi 3B+ models, and running the newest update, 20200606. I reflashed both, hooked up via a wired connection for initial setup, no problem. Entered in my usual wifi details, no issues. As soon as I removed the wired connection, and move the device to it's end location and power backup... nothing. Again, my router can see its connected to my wifi network, but I can't actually connect to it via the web interface.

I've tried reverting back to a version from 2019, no luck. I've tried making the wpa_supplicant.conf as it should, no luck.

Oddly enough, if I leave both wifi and wired connections on DHCP, they each of course get their own individual IPs... but I can't access the web interface on either. As soon as I disabled the wifi connection, I can then access the interface on the wired. But then RPi goes into a panic reboot initiated by the wifi going down. Which then puts me back to square one.

I've reflashed and only used a Wifi connection, never a wired and again, the wireless is recognized by the router, the RPi gets a DHCP address, and then again, I cannot connect via the web interface.

In all of this, if I never use the wifi, the wired connection works flawlessly. Really wierd whatever is going on... be strange if both RPi's hardware physically went bad at the same time.

Any ideas?
@starbasessd
Copy link

starbasessd commented Jan 19, 2021 via email

@sectshun8
Copy link
Author

sectshun8 commented Jan 19, 2021 •
edited
Loading

I have tried both the new dev available and that 2019 release... both exhibiting the same symptoms.

And I have a third RPi running RaspberryPiOS that is having no issues with the Wifi at all, running my Plex media server wonderfully. Though it is a RPi 4, whereas the two having issues are 3B+'s.

@starbasessd
Copy link

starbasessd commented Jan 19, 2021 via email

@sectshun8
Copy link
Author

Can confirm with RaspberryPiOS on the two devices in question, using the same wpa_supplicant.conf file on boot works exactly as it should, no issues. Devices were given the same DHCP IP's as they were assigned using mEOS. Connects to the internet, but oddly... I can ping my other RPi devices, but not my Windows machines.

@starbasessd
Copy link

starbasessd commented Jan 19, 2021 via email

@sectshun8
Copy link
Author

Both... I generally always ping by IP, but yeah, hostname doesn't work either. But like I said, with all three RPi's on the network, including my Synology Disk Station... I can ping between of them by IP just fine. And come to find out, my one Windows laptop upstairs can ping the RPi's as well... just the not the one I'm currently working on. Were you thinking a DNS issue?

@starbasessd
Copy link

starbasessd commented Jan 19, 2021 via email

@sectshun8
Copy link
Author

Neither the Pi's or the Windows machine can trace to each other, both timeout, host unreacheable. Both can route to google.com with no issue.

Both the 2 questionable Pi's, as well as the Windows machine can ping my 3rd Pi (media server) with no issue. And the media server can ping the others as well.

@starbasessd
Copy link

starbasessd commented Jan 19, 2021 via email

@sectshun8
Copy link
Author

sectshun8 commented Jan 19, 2021 •
edited
Loading

All the network setups are the same, except for the actual IPs. All are on the same subnet, same gateway, etc. Obviosuly the router has a different default gateway on the public IP side... but all my devices internally have the router as their gateway. I had at first thought maybe because my laptop wasn't "Discoverable" on the network... but that was not the issue. I can ping my both ways between my media server Pi and my Windows laptop no problem.

Let's also keep in mind, that when hard wired, pinging is no issue. It's just when wifi is enabled. But I don't generally have the RPi's wired, theyve always operated just fine on the Wifi until now.

@starbasessd
Copy link

starbasessd commented Jan 19, 2021 via email

@starbasessd
Copy link

starbasessd commented Jan 19, 2021 via email

@sectshun8
Copy link
Author

So my RPi's are: 192.168.0.XX and 192.168.0.XY
Windows PC: 192.168.0.XZ
Subnet: 255.255.255.0
Gateway: 192.168.0.1
DNS: 194.168.8.100, 8.8.8.8

I have a pretty simple setup, I've checked these over time and time again... and nothing in them has changed from when they were working, to now. No router changes, no device changes, nothing. And again, if I don't use the wpa_supplicant file, and just start straight away with a wired connection, BAM, no issues, straight in. As soon as I turn the wifi on in the software with my credentials and reboot... can no longer access the interface wired or wireless.

@starbasessd
Copy link

starbasessd commented Jan 19, 2021 via email

@sectshun8
Copy link
Author

So from the RPi 4 running RaspberryPiOS, I can SSH into both the wired and wireless connections on the mEOS RPi. Likewise, I can ping back and forth between them. I can also ping the gateway, the DNS, and a few other devices on my network... just not the PC I use to view the cameras.

However, with both RPi 3B+'s with mEOS and RaspberryPiOS respectively, I cannot ping between the two on either wired or wireless IP, let alone SSH. But I can ping the gateway and other devices except the two RPi units to each other and them both to my Windows PC. There's deifnitely something specific to those two boxes that is causing this.

I had thought maybe my Powerline network was interfering, but have since ruled that out as well. Still soem wierd stuff going on... surprised it's happening on freshly flashed units.

I'll get to the bottom of it eventually.

@starbasessd
Copy link

starbasessd commented Jan 19, 2021 via email

@Sharpie
Copy link

Sharpie commented Jan 20, 2021

I'm seeing a similar issue trying MotionEyeOS on a Raspberry Pi Zero W 1.1 for the first time. The device boots and connects to the network, but the connection is very flaky. If I'm lucky, I can get a SSH session after a half-dozen tries but the connection will destabilize and close whenever I try to do anything more complicated than cd or ls, such as dmesg or less /var/log/messages.

Re-flashing the SD card to use 2021-01-11-raspios-buster-armhf-lite.img instead of motioneyeos-raspberrypi-20200606.img allows the hardware to maintain a stable network connection.

The wpa_supplicant.conf I added to /boot for MotionEyeOS is from this template in the wiki:

country=US
update_config=1
ctrl_interface=/var/run/wpa_supplicant

network={
  scan_ssid=1
  ssid="<redacted>"
  psk="<redacted>"
}

And the wpa_supplicant.conf added to /boot for Raspberry Pi OS is from this template in the Pi docs:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=US

network={
 ssid="<redacted>"
 psk="<redacted>"
}

@starbasessd
Copy link

starbasessd commented Jan 20, 2021 via email

@rdukes6514
Copy link

So my RPi's are: 192.168.0.XX and 192.168.0.XY
Windows PC: 192.168.0.XZ
Subnet: 255.255.255.0
Gateway: 192.168.0.1
DNS: 194.168.8.100, 8.8.8.8

I have a pretty simple setup, I've checked these over time and time again... and nothing in them has changed from when they were working, to now. No router changes, no device changes, nothing. And again, if I don't use the wpa_supplicant file, and just start straight away with a wired connection, BAM, no issues, straight in. As soon as I turn the wifi on in the software with my credentials and reboot... can no longer access the interface wired or wireless.

The DNS you have listed here is the WAN side of your router, right?
And your using your router for your internal DNS/DHCP?
Make sure your router's DHCP setup is using itself as the primary DNS server...
Double check all the numbers - I don't know how many times I've used an o instead of a 0!

@rdukes6514
Copy link

Oh, and reboot everything...

@sectshun8
Copy link
Author

sectshun8 commented Jan 20, 2021 •
edited
Loading

@starbasessd my wpa_supplicant file is exactly as yours, but with GB as my country instead of US (I've tried US as well with no luck).

As for using my router itself as it's own DNS, that's not an option I have. I'm using what has come from my ISP in router mode. I supposed I could use it in modem mode and use a separate router for the network... but really that's not going to happen.

Everything has been restarted from the router to each of the client machines. Let's not forget here, the RPI's are visible as connected to the router. I can ping the router from each. I can ping internet sites from each... it's just the talking back and forth to my Windows laptop on the network that's the issue as I can ping back and forth between my RPi running mEOS and another RPi running RaspberryPiOS and even view the web interface from the RaspberryPiOS device. And the RaspberryPiOS one can ping my Windows laptop... go figure when the wpa_supplicant files are identical. And everything is setup as DHCP, so all auto assigned for each of the clients, no typos ;) (I have tried static as well but didn't help).

And it WAS all working, like literally last week still working.

@starbasessd
Copy link

It's possible that your ISP thumb-fingered a setting. It happens. Have them check it out, describing the issues you're having. Have them check your DHCP service on the router, make sure it's set up correctly.

@Sharpie
Copy link

Sharpie commented Jan 26, 2021

I took another try at setting things up from scratch over the weekend and WiFi on the Pi Zero worked this time around. So, whatever was causing my initial troubles is not re-producing its self.

@sectshun8
Copy link
Author

It's possible that your ISP thumb-fingered a setting. It happens. Have them check it out, describing the issues you're having. Have them check your DHCP service on the router, make sure it's set up correctly.

So my ISP did something that only effects the two RPi's on my network... but not the other RPi, or the 3 PC's, or the phones, tablets, tv's... just the two RPi's?

@sectshun8
Copy link
Author

sectshun8 commented Jan 26, 2021 •
edited
Loading

So a new observation today. Just trying to get back too square one, a fresh mEOS install, no wpa_supplicant pre-loaded, running on a wired connection, DHCP. No issues. Can bring up web interface on my Windows PC, can ping back and forth, no issues. Now as soon as I enable the Wifi with correct details and also DHCP and reboot... I can no longer communicate with the RPi via the Windows PC... not even on the wired IP. So it's directly related to enabling/using the wifi on the RPi. That being said, on my RPi 4 running RaspberryPiOS, I can access the web interface via the wifi connection at this exact same time. Subsequently disabling the Wifi does not restore the Wired connection and just makes the unit panic restart.

A side note, generally after I have this all set up, I use my phone, point it to the IP and use that for mobile viewing throughout the house. My phone has the same symptoms as the Windows PC. When the RPi is wired, my phone can pick it up and view the web interface just fine... but again, as soon as Wifi is enabled, that goes away.

@starbasessd
Copy link

starbasessd commented Jan 26, 2021 via email

@sectshun8
Copy link
Author

On another note of observation, on the RPi's in question where once I enable the wifi the connections no longer work... I read another thread in regard to dongles and just happened to have one. I put it in the USB, configured ap1 with an IP and BAM... the wifi works over the USB dongle with no issues, even comes up on my Windows PC and Phone.

@sectshun8
Copy link
Author

And both of my RPI's are:
Raspberry Pi 3 Model B+

Near the GPIO are the letters JB.

And yes I'm using the correct release for my board.

@starbasessd
Copy link

starbasessd commented Jan 26, 2021 via email

@sectshun8
Copy link
Author

I've tried both... as both of the ones listed should work for my board.

Question about the dev releases... how can you actually get into the settings on those in the web interface?

@starbasessd
Copy link

starbasessd commented Jan 26, 2021 via email

@starbasessd
Copy link

starbasessd commented Jan 26, 2021 via email

@sectshun8
Copy link
Author

sectshun8 commented Jan 26, 2021 •
edited
Loading

Mine boot exactly as yours do...

So when I use the dev version, using the standard supplicant, as usual, no problems on boot... Wifi connects, IP is assigned, just like normal. Again, my Windows PC nor my Phone can connect to web interface. However my media server RPi 4 can. When I open up the web interface, I have to logout and log back in to access any of the settings (before hand all the settings were greyed out and it had a password set on the admin account that I didn't set so I couldn't access any settings). To note... at this point, just on wifi, I can ping internet sites, and I can ping other devices on my network, just not my Windows PC and Phone. So to me, that rules out there being an issue with the onboard wifi... it works.

Being able to access it on my phone is the main issue here. If I can do all the setups via my RPi 4 over the web interface and just use my phone to view as I was doing before that'd be great. I mean, heck, if I port forward in my router and turn the wifi off on my phone I can view the cams no problem... frustrating. Really not sure whats going on with it to where internally over my home wifi there seems a block...

@starbasessd
Copy link

starbasessd commented Jan 26, 2021 via email

@starbasessd
Copy link

Any update?

@sectshun8
Copy link
Author

Nope, no update. I've been working offshore, but been home the last week and made no headway. Both RPi 3 B+ devices still are not playing ball and I cannot access the from my windows laptop or my iPhone via the web interface.

@starbasessd
Copy link

starbasessd commented Mar 5, 2021 •
edited
Loading

<=- to internet --- modem/router --- switch --- WiFi router --- Pis

or another arrangement?

@BennyIsYourBestFriend
Copy link

Hi,
you might have found a solution to the WiFi problem by now - I had the exact same issue with my Raspberry Pi 4B and couldn't find help on this site, and I got pretty frustrated of such an annoying problem, so I just tested out some tweaks in the wpa_supplicant.conf -file as I was pretty sure my other setups were spot on. It took some time and beers but the following configuration worked for me:

ctrl_interface=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=Country

network={
ssid="*"
psk=""
key_mgmt=WPA-PSK
}

@Osmii
Copy link

Osmii commented Mar 7, 2021

Hello!
I also had problems with wifi droping(totaly first and new setup,Rpi2 with Tp-link dongle) with latest and other releases. Then I connected to a different AP on other location and now is working ok.

@sectshun8
Copy link
Author

<=- to internet --- modem/router --- switch --- WiFi router --- Pis

or another arrangement?

Much simpler...

<=- to internet --- modem/router --- Pis

@starbasessd
Copy link

starbasessd commented Mar 11, 2021 via email

@sectshun8
Copy link
Author

Hi,
you might have found a solution to the WiFi problem by now - I had the exact same issue with my Raspberry Pi 4B and couldn't find help on this site, and I got pretty frustrated of such an annoying problem, so I just tested out some tweaks in the wpa_supplicant.conf -file as I was pretty sure my other setups were spot on. It took some time and beers but the following configuration worked for me:

ctrl_interface=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=Country

network={
ssid="*" psk=""
key_mgmt=WPA-PSK
}

Appreciate the effort, but you'll see by reading the thread that I've tried that very supplicant.conf already... though not necessarily with the SSID and PSK on the same line... or is that a typo?

@sectshun8
Copy link
Author

sectshun8 commented Mar 11, 2021 •
edited
Loading

Your modem/router does WiFi too?
…

Yes. Coax line comes into the back, it then has 4 ports for wired connections and also broadcasts via Wifi.

@BennyIsYourBestFriend
Copy link

Hi,
you might have found a solution to the WiFi problem by now - I had the exact same issue with my Raspberry Pi 4B and couldn't find help on this site, and I got pretty frustrated of such an annoying problem, so I just tested out some tweaks in the wpa_supplicant.conf -file as I was pretty sure my other setups were spot on. It took some time and beers but the following configuration worked for me:
ctrl_interface=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=Country
network={
ssid="*" psk=""
key_mgmt=WPA-PSK
}

Appreciate the effort, but you'll see by reading the thread that I've tried that very supplicant.conf already... though not necessarily with the SSID and PSK on the same line... or is that a typo?

Yes, it's a typo... sorry for that....
I hope you'll manage to get it working soon again.

@starbasessd
Copy link

starbasessd commented Mar 11, 2021 via email

@sectshun8
Copy link
Author

I'll delve more into it in about a month when I'm back home and can mess around a bit. Currently headed back offshore so can't really do much.

@sectshun8
Copy link
Author

So... back at this. I had a completely separate IPC360 camera in my daughters room I could never get on the wifi before... and I gave that one another go recently, and it just joined no problem. So I thought, hmm... I'll give my two RPi's a go again with the newest iteration of mEOS and see what happens.

Believe it or not, both my RPi cameras are working again with no real explanation why. I can say instead of using the supplicant to join the Wifi straight away, I set them up on my wired network first, then enabled the Wifi setting in the mEOS via the web interface and entered in the appropriate credentials. That would really be the only thing I did different... but that being said, I tried this months ago with no luck, so who knows.

Anyhow, both RPi 3B+'s using image 202006, back up and running. I really wish we could have come up with a reason why to help anyone in the future, but that doesnt look like it's going to be the case. Unless anyone has anything add this thread can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted troubleshooting
Milestone
No milestone
Development

No branches or pull requests
6 participants
@Sharpie @Osmii @starbasessd @rdukes6514 @sectshun8 @BennyIsYourBestFriend