Posted: Thu Aug 15, 2019 18:34 Post subject: Push notifications not getting through
Hi guys!
I'm having problems with push notifications getting through. Specifically I mean Signal, WhatsApp, GMail, etc. on Android (tried multiple devices + versions). I've been having the issue for a while now and so I decided to do a factory reset, just to check, whether that solves my problem.
And it did solve the problem. Everything got through pretty fast (within a couple of seconds).
However, I then started to reconfigure everything, not using a backup on purpose. And sure enough, the push notifications stopped working again.
When going through all the configuration, I just couldn't find anything, which I think would have an impact on this. Anybody got a suggestion, what could be wrong?
Posted: Sun Aug 18, 2019 11:54 Post subject: Re: Push notifications not getting through
seombre wrote:
...
I'm having problems with push notifications getting through. Specifically I mean Signal, WhatsApp, GMail, etc. on Android (tried multiple devices + versions). I've been having the issue for a while now and so I decided to do a factory reset, just to check, whether that solves my problem.
...
Turns out, not even a factory reset actually works. After factory reset, I only configured these values:
- Setup
-- Basic Setup
--- WAN Setup
---- Router Name
---- Hostname
---- Domain name
--- Network Setup
---- Local IP Address
---- Subnet Mask
---- Start IP Address
---- Maximum DHC Users
---- Static DNS 1, 2 & 3 (8.8.8.8, 8.8.4.4, 9.9.9.9)
- Wireless
-- Basic Settings
--- SSID for ath0 (5GHz) and ath1 (2,4GHz) - same SSID for both
-- Wireless Security
--- WPA Shared Key - the same for both ath0 and ath1
... and that's it. Even with this very basic setup (imho), I can still reproduce the issue.
Yes, it's WPA2 Personal and the only enabled WPA algorithm is "CCMP-128 (AES)".
I don't know the exact build number, however, I have setup a second R7800 with a Kong build and there's absolutly no problem, when my device is in that router's WLAN. Also no problems at work or other WLANs, so this actually looks like a bug to me.
Edit: The build of the other router is probably 9 to 12 months old.
Joined: 18 Mar 2014 Posts: 12884 Location: Netherlands
Posted: Sun Aug 18, 2019 13:14 Post subject:
seombre wrote:
Yes, it's WPA2 Personal and the only enabled WPA algorithm is "CCMP-128 (AES)".
I don't know the exact build number, however, I have setup a second R7800 with a Kong build and there's absolutly no problem, when my device is in that router's WLAN. Also no problems at work or other WLANs, so this actually looks like a bug to me.
Edit: The build of the other router is probably 9 to 12 months old.
To be honest, going back to such an old build is absolutely not a solution. This is a regression introduced along the way.
I can't imagine it's a bug or you'd be seeing other reports of the behavior. I have multiple Android and Apple devices using push notifications on 40270 without any issues. _________________ Routing:.......Asus RT-AX88U (Asuswrt-Merlin 384.14) Switching:....Netgear GS608_V3 & GS605_V4, TrendNet TEG-S82G & TEG-S50G
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Mon Aug 19, 2019 15:11 Post subject: Re: Push notifications not getting through
seombre wrote:
Hi guys!
I'm having problems with push notifications getting through. Specifically I mean Signal, WhatsApp, GMail, etc. on Android (tried multiple devices + versions). I've been having the issue for a while now and so I decided to do a factory reset, just to check, whether that solves my problem.
And it did solve the problem. Everything got through pretty fast (within a couple of seconds).
However, I then started to reconfigure everything, not using a backup on purpose. And sure enough, the push notifications stopped working again.
When going through all the configuration, I just couldn't find anything, which I think would have an impact on this. Anybody got a suggestion, what could be wrong?
Currently running build 40270.
Go step by step, save, apply, check. Repeat until you find the configuration detail that breaks it, and then undo it. Pretty simple concept. And by step by step, I mean INDIVIDUAL, line-by-line, dot-by-dot. Obviously, you are using something or adding something to a config that is breaking something....
Did another factory reset now and will be doing every change one by one now. Quite time consuming, since it takes a while, until my devices go to standby
Sigh... As it turned out, the problem seems to be the modem/router, which I got a couple of years ago from my ISP. The same problem can be reproduced, when my devices are in this routers WLAN, so it's definitly not an issue with my R7800 or any specific build.
Posted: Tue Aug 27, 2019 0:52 Post subject: r7800 builds
Hows the r7800 with bs builds? What's the current most stable one,etc? Just bought one to replace my r7000. Was looking to use kong's but seen the message about him departing from dd-wrt (Tons of respect for him - Thanks for everything done for the community!).
seems k4.14 eol was extended, will we move to that? its not like its any worse, all k4.x are equally broken on ipq806x BS builds..
(and lol at that k5.4 eol date)
I'm all for trying k4.14 on the IPQ806x routers but don't know 'bout further with'em
just today got my old Linux computer, I normally use, up to k5.x ...and yea he's running very well
Code:
mrjcd@Deb:~$ uname -a
Linux Deb 5.2.0-2-amd64 #1 SMP Debian 5.2.9-2 (2019-08-21) x86_64 GNU/Linux
mrjcd@Deb:~$
Although it says "device recovered", it never did. The LED stayed off and no device could connect to it.
I changed a setting (ACK timing) on Ath0 and hit "Apply Settings" and it revived the interface.