EricSe7en Posted August 15, 2019 Share Posted August 15, 2019 Hi, I'm getting multiple error messages, which I've searched the forum for, but not been able to fix. They are - Uncaught TypeError: Cannot read property 'length' of undefined Uncaught SyntaxError: Invalid or unexpected token Uncaught TypeError: wanProtocolRadio.indexOf is not a function So far I've tried - Rebooting Factory Resetting Rolling back to earlier firmware and updating again At the moment, I can't do anything. I can't add my PS4 as a device for Geo filtering or for QOS. I can't change any settings or any of the system information settings (such as the password after the factory reset). I've tried through wifi and directly connected to my PC - nothing seems to help. Can I get an admin to take a look please? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted August 15, 2019 Administrators Share Posted August 15, 2019 It's surprising a factory reset hasn't fixed this. When did this start happening? Was it after a setting change or upgrade? What pages does it occur on? Link to comment Share on other sites More sharing options...
EricSe7en Posted August 15, 2019 Author Share Posted August 15, 2019 Geo-Filter - Uncaught TypeError: Cannot read property 'length' of undefined Device Manager - Uncaught SyntaxError: Invalid or unexpected token Network Settings - Uncaught TypeError: wanProtocolRadio.indexOf is not a function I reinstalled the old R1 version (this allowed me to at least change the WiFi password so i didn't have to change every device in my house) and updated again to the current Dumo Os. After upgrading to the Dumo OS I can't access anything on the Network Settings page. I cannot add anything to the Geo Filter. When I click on 'Add Device' The device list appears, but when I click on PS4, I can't then click the next button, it doesn't make itself available, I can only cancel. This is the same if I try adding the device for Traffic Prioritization on the QoS page. This is the same for all devices, I cannot click 'next' for anything. I've not changed any of the settings - I haven't really bothered with it at all for a few months, so I have no idea why it's doing this all of a sudden. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted August 15, 2019 Administrators Share Posted August 15, 2019 Not sure I understand exactly the reason behind downgrading as if you change the WiFi password on the router then you would need to update the devices with the new password. Could you downgrade back to the R1 firmware please, do a factory reset from misc settings and then when you upgrade make sure that preserve settings are disabled. Once upgraded to DumaOS do another factory reset to ensure no legacy issues from previous firmware. Link to comment Share on other sites More sharing options...
EricSe7en Posted August 15, 2019 Author Share Posted August 15, 2019 I didn't intend to change the password - it reset during the factory reset. I'll do what you suggested. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted August 15, 2019 Administrators Share Posted August 15, 2019 Great let us know if that works! Link to comment Share on other sites More sharing options...
EricSe7en Posted August 16, 2019 Author Share Posted August 16, 2019 Ok.... This partially worked. I installed the R1 firmware, factory reset, unticked 'preserve settings; and then updated to the first DumaOS version - 2.1.2.10 When doing this, it did something to the wifi settings - the netduma wouldn't show when searching for wifi networks, and even when I connected it by cable to my laptop I was unable to access the usual Dashboard screen. I was getting this error message - This site can’t be reached 192.168.88.1 took too long to respond. I tired this with different browsers too, and had the same message. Resetting seemed to re activate the wifi and I was able to access the normal Duma Dashboard - at this point everything was working fine, i could access the Geo Filter, QOS and make changes to the network settings if I needed to. I tried upgrading to the latest firmware - 2.1.3.29 - and encountered the same wifi issue again, but another reset sorted this. Sadly, when I managed to access the Dashbaord, I encountered the same errors outlined previously and was unable to make any changes to the settings. I have noticed when this happens the Geo Filter doesn't seem to load at all? Not sure if this is relevant? Link to comment Share on other sites More sharing options...
Administrators Netduma Alex Posted August 16, 2019 Administrators Share Posted August 16, 2019 Long shot, but have you tried different browsers while accessing DumaOS? I wonder if the problem is on the client side rather than the router. Link to comment Share on other sites More sharing options...
EricSe7en Posted August 16, 2019 Author Share Posted August 16, 2019 I have, errors are still there sadly. Link to comment Share on other sites More sharing options...
Administrators Netduma Alex Posted August 16, 2019 Administrators Share Posted August 16, 2019 Something strange happening here for sure. On DumaOS, can you see the current CPU and RAM usage in System Information? Link to comment Share on other sites More sharing options...
EricSe7en Posted August 16, 2019 Author Share Posted August 16, 2019 Yes, I can see them and they appear to be fine - lots of free space. Here's the log, if it helps Fri Aug 16 13:43:19 2019 kern.info kernel: [ 388.224000] recv: nf_ct_get failed Fri Aug 16 13:43:19 2019 kern.info kernel: [ 388.224000] send: nf_ct_get failed Fri Aug 16 13:43:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:43:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:43:38 2019 kern.info kernel: [ 407.204000] recv: nf_ct_get failed Fri Aug 16 13:43:38 2019 kern.info kernel: [ 407.204000] send: nf_ct_get failed Fri Aug 16 13:43:46 2019 kern.info kernel: [ 414.880000] recv: nf_ct_get failed Fri Aug 16 13:43:46 2019 kern.info kernel: [ 414.880000] send: nf_ct_get failed Fri Aug 16 13:43:48 2019 kern.info kernel: [ 416.612000] recv: nf_ct_get failed Fri Aug 16 13:43:48 2019 kern.info kernel: [ 416.612000] send: nf_ct_get failed Fri Aug 16 13:43:50 2019 kern.info kernel: [ 418.412000] recv: nf_ct_get failed Fri Aug 16 13:43:50 2019 kern.info kernel: [ 418.412000] send: nf_ct_get failed Fri Aug 16 13:43:50 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:43:50 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:43:50 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:43:58 2019 local5.info geoip-daemon[9152]: {"t":426644,"ip":-1754646989,"category":"wd","distance":490, "lat": 48, "lng": 2, "rtt": 0, "islan2wan": true } Fri Aug 16 13:43:58 2019 local5.info geoip-daemon[9152]: verdict 1 524288 Fri Aug 16 13:43:58 2019 local5.info geoip-daemon[9152]: {"t":426647,"ip":-1754646989,"category":"wd","distance":490, "lat": 48, "lng": 2, "rtt": 0, "islan2wan": true } Fri Aug 16 13:43:58 2019 local5.info geoip-daemon[9152]: verdict 1 524288 Fri Aug 16 13:44:14 2019 kern.info kernel: [ 443.240000] recv: nf_ct_get failed Fri Aug 16 13:44:14 2019 kern.info kernel: [ 443.240000] send: nf_ct_get failed Fri Aug 16 13:44:15 2019 kern.info kernel: [ 443.460000] recv: nf_ct_get failed Fri Aug 16 13:44:15 2019 kern.info kernel: [ 443.460000] send: nf_ct_get failed Fri Aug 16 13:44:29 2019 kern.info kernel: [ 457.728000] recv: nf_ct_get failed Fri Aug 16 13:44:29 2019 kern.info kernel: [ 457.728000] send: nf_ct_get failed Fri Aug 16 13:45:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:45:38 2019 daemon.warn odhcpd[740]: A default route is present but there is no public prefix on br-lan thus we don't announce a default route! Fri Aug 16 13:45:38 2019 daemon.warn odhcpd[740]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri Aug 16 13:47:09 2019 daemon.info hostapd: wlan0: STA dc:53:60:34:ac:e7 WPA: group key handshake completed (RSN) Fri Aug 16 13:47:09 2019 daemon.info hostapd: wlan0: STA 7a:9f:29:be:d0:92 WPA: group key handshake completed (RSN) Fri Aug 16 13:47:09 2019 daemon.info hostapd: wlan0: STA 38:8b:59:6b:69:05 WPA: group key handshake completed (RSN) Fri Aug 16 13:47:09 2019 daemon.info hostapd: wlan0: STA 0e:fc:e0:14:72:f2 WPA: group key handshake completed (RSN) Fri Aug 16 13:47:09 2019 daemon.info hostapd: wlan0: STA 0c:f9:c0:29:72:f6 WPA: group key handshake completed (RSN) Fri Aug 16 13:47:09 2019 daemon.info hostapd: wlan0: STA 88:51:fb:f9:eb:dc WPA: group key handshake completed (RSN) Fri Aug 16 13:47:09 2019 daemon.info hostapd: wlan0: STA 50:f5:da:ba:ea:61 WPA: group key handshake completed (RSN) Fri Aug 16 13:47:10 2019 daemon.info hostapd: wlan0: STA cc:c7:60:56:03:88 WPA: group key handshake completed (RSN) Fri Aug 16 13:47:10 2019 daemon.info hostapd: wlan0: STA d0:d2:b0:03:67:82 WPA: group key handshake completed (RSN) Fri Aug 16 13:47:11 2019 daemon.info hostapd: wlan0: STA dc:d3:a2:a6:38:8e WPA: group key handshake completed (RSN) Fri Aug 16 13:47:18 2019 daemon.info hostapd: wlan0: STA 08:f4:ab:a4:53:77 IEEE 802.11: deauthenticated due to local deauth request Fri Aug 16 13:47:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:48:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:49:14 2019 local5.info geoip-daemon[9152]: {"t":742395,"ip":1839808722,"category":"wd","distance":303, "lat": 51, "lng": 0, "rtt": 0, "islan2wan": true } Fri Aug 16 13:49:14 2019 local5.info geoip-daemon[9152]: verdict 1 524288 Fri Aug 16 13:49:14 2019 local5.info geoip-daemon[9152]: {"t":742438,"ip":1839808722,"category":"wd","distance":303, "lat": 51, "lng": 0, "rtt": 0, "islan2wan": true } Fri Aug 16 13:49:14 2019 local5.info geoip-daemon[9152]: verdict 1 524288 Fri Aug 16 13:49:15 2019 kern.info kernel: [ 744.080000] recv: nf_ct_get failed Fri Aug 16 13:49:15 2019 kern.info kernel: [ 744.080000] send: nf_ct_get failed Fri Aug 16 13:49:18 2019 kern.info kernel: [ 746.320000] recv: nf_ct_get failed Fri Aug 16 13:49:18 2019 kern.info kernel: [ 746.320000] send: nf_ct_get failed Fri Aug 16 13:49:50 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:49:50 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:50:02 2019 local5.info geoip-daemon[9152]: {"t":790612,"ip":624808727,"category":"wd","distance":785, "lat": 51, "lng": 7, "rtt": 0, "islan2wan": true } Fri Aug 16 13:50:02 2019 local5.info geoip-daemon[9152]: verdict 1 524288 Fri Aug 16 13:50:02 2019 local5.info geoip-daemon[9152]: {"t":790615,"ip":624808727,"category":"wd","distance":785, "lat": 51, "lng": 7, "rtt": 0, "islan2wan": true } Fri Aug 16 13:50:02 2019 local5.info geoip-daemon[9152]: verdict 1 524288 Fri Aug 16 13:51:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:51:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:51:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:51:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:51:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:53:48 2019 kern.info kernel: [ 1016.404000] recv: nf_ct_get failed Fri Aug 16 13:53:48 2019 kern.info kernel: [ 1016.772000] recv: nf_ct_get failed Fri Aug 16 13:54:05 2019 local5.info geoip-daemon[9152]: {"t":1033645,"ip":-867508086,"category":"bd","distance":7541, "lat": 32, "lng": -97, "rtt": 0, "islan2wan": true } Fri Aug 16 13:54:05 2019 local5.info geoip-daemon[9152]: verdict 1 1048576 Fri Aug 16 13:54:05 2019 local5.info geoip-daemon[9152]: {"t":1033648,"ip":-867508086,"category":"bd","distance":7541, "lat": 32, "lng": -97, "rtt": 0, "islan2wan": true } Fri Aug 16 13:54:05 2019 local5.info geoip-daemon[9152]: verdict 1 1048576 Fri Aug 16 13:54:07 2019 kern.info kernel: [ 1035.688000] recv: nf_ct_get failed Fri Aug 16 13:54:07 2019 kern.info kernel: [ 1035.688000] send: nf_ct_get failed Fri Aug 16 13:54:15 2019 local5.info geoip-daemon[9152]: {"t":1043708,"ip":597400202,"category":"bd","distance":7956, "lat": 43, "lng": -120, "rtt": 0, "islan2wan": true } Fri Aug 16 13:54:15 2019 local5.info geoip-daemon[9152]: verdict 1 1048576 Fri Aug 16 13:54:17 2019 local5.info geoip-daemon[9152]: {"t":1046067,"ip":1839808744,"category":"wd","distance":303, "lat": 51, "lng": 0, "rtt": 0, "islan2wan": true } Fri Aug 16 13:54:17 2019 local5.info geoip-daemon[9152]: verdict 1 524288 Fri Aug 16 13:54:17 2019 local5.info geoip-daemon[9152]: {"t":1046070,"ip":1839808744,"category":"wd","distance":303, "lat": 51, "lng": 0, "rtt": 0, "islan2wan": true } Fri Aug 16 13:54:17 2019 local5.info geoip-daemon[9152]: verdict 1 524288 Fri Aug 16 13:54:19 2019 daemon.warn odhcpd[740]: A default route is present but there is no public prefix on br-lan thus we don't announce a default route! Fri Aug 16 13:54:19 2019 daemon.warn odhcpd[740]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri Aug 16 13:54:21 2019 kern.info kernel: [ 1049.592000] recv: nf_ct_get failed Fri Aug 16 13:54:21 2019 kern.info kernel: [ 1049.592000] send: nf_ct_get failed Fri Aug 16 13:54:38 2019 local5.info geoip-daemon[9152]: {"t":1066571,"ip":1836803602,"category":"wd","distance":601, "lat": 52, "lng": 4, "rtt": 0, "islan2wan": true } Fri Aug 16 13:54:38 2019 local5.info geoip-daemon[9152]: verdict 1 524288 Fri Aug 16 13:54:38 2019 local5.info geoip-daemon[9152]: {"t":1066574,"ip":1836803602,"category":"wd","distance":601, "lat": 52, "lng": 4, "rtt": 0, "islan2wan": true } Fri Aug 16 13:54:38 2019 local5.info geoip-daemon[9152]: verdict 1 524288 Fri Aug 16 13:54:50 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:54:50 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:55:05 2019 kern.info kernel: [ 1093.360000] recv: nf_ct_get failed Fri Aug 16 13:55:10 2019 kern.info kernel: [ 1098.740000] recv: nf_ct_get failed Fri Aug 16 13:55:17 2019 kern.info kernel: [ 1106.228000] recv: nf_ct_get failed Fri Aug 16 13:55:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:57:09 2019 daemon.info hostapd: wlan0: STA dc:53:60:34:ac:e7 WPA: group key handshake completed (RSN) Fri Aug 16 13:57:09 2019 daemon.info hostapd: wlan0: STA 7a:9f:29:be:d0:92 WPA: group key handshake completed (RSN) Fri Aug 16 13:57:09 2019 daemon.info hostapd: wlan0: STA 0e:fc:e0:14:72:f2 WPA: group key handshake completed (RSN) Fri Aug 16 13:57:09 2019 daemon.info hostapd: wlan0: STA 0c:f9:c0:29:72:f6 WPA: group key handshake completed (RSN) Fri Aug 16 13:57:09 2019 daemon.info hostapd: wlan0: STA 38:8b:59:6b:69:05 WPA: group key handshake completed (RSN) Fri Aug 16 13:57:09 2019 daemon.info hostapd: wlan0: STA 88:51:fb:f9:eb:dc WPA: group key handshake completed (RSN) Fri Aug 16 13:57:10 2019 daemon.info hostapd: wlan0: STA dc:d3:a2:a6:38:8e WPA: group key handshake completed (RSN) Fri Aug 16 13:57:10 2019 daemon.info hostapd: wlan0: STA d0:d2:b0:03:67:82 WPA: group key handshake completed (RSN) Fri Aug 16 13:57:10 2019 daemon.info hostapd: wlan0: STA 50:f5:da:ba:ea:61 WPA: group key handshake completed (RSN) Fri Aug 16 13:57:11 2019 daemon.info hostapd: wlan0: STA cc:c7:60:56:03:88 WPA: group key handshake completed (RSN) Fri Aug 16 13:58:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 13:59:52 2019 daemon.warn odhcpd[740]: A default route is present but there is no public prefix on br-lan thus we don't announce a default route! Fri Aug 16 13:59:52 2019 daemon.warn odhcpd[740]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri Aug 16 14:02:59 2019 local5.info geoip-daemon[9152]: {"t":1567410,"ip":1836796452,"category":"wd","distance":303, "lat": 51, "lng": 0, "rtt": 0, "islan2wan": true } Fri Aug 16 14:02:59 2019 local5.info geoip-daemon[9152]: verdict 1 524288 Fri Aug 16 14:02:59 2019 local5.info geoip-daemon[9152]: {"t":1567413,"ip":1836796452,"category":"wd","distance":303, "lat": 51, "lng": 0, "rtt": 0, "islan2wan": true } Fri Aug 16 14:02:59 2019 local5.info geoip-daemon[9152]: verdict 1 524288 Fri Aug 16 14:02:59 2019 kern.info kernel: [ 1568.020000] recv: nf_ct_get failed Fri Aug 16 14:02:59 2019 kern.info kernel: [ 1568.020000] send: nf_ct_get failed Fri Aug 16 14:03:02 2019 kern.info kernel: [ 1571.008000] recv: nf_ct_get failed Fri Aug 16 14:03:02 2019 kern.info kernel: [ 1571.008000] send: nf_ct_get failed Fri Aug 16 14:03:33 2019 daemon.warn odhcpd[740]: A default route is present but there is no public prefix on br-lan thus we don't announce a default route! Fri Aug 16 14:03:33 2019 daemon.warn odhcpd[740]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri Aug 16 14:03:50 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 14:03:50 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 14:03:56 2019 daemon.info hostapd: wlan0: STA 90:cd:b6:7d:d6:4b IEEE 802.11: authenticated Fri Aug 16 14:03:56 2019 daemon.info hostapd: wlan0: STA 90:cd:b6:7d:d6:4b IEEE 802.11: associated (aid 😎 Fri Aug 16 14:03:57 2019 daemon.info hostapd: wlan0: STA 90:cd:b6:7d:d6:4b WPA: pairwise key handshake completed (RSN) Fri Aug 16 14:04:00 2019 daemon.info dnsmasq-dhcp[1151]: DHCPDISCOVER(br-lan) 90:cd:b6:7d:d6:4b Fri Aug 16 14:04:00 2019 daemon.info dnsmasq-dhcp[1151]: DHCPOFFER(br-lan) 192.168.88.229 90:cd:b6:7d:d6:4b Fri Aug 16 14:04:00 2019 daemon.info dnsmasq-dhcp[1151]: DHCPREQUEST(br-lan) 192.168.88.229 90:cd:b6:7d:d6:4b Fri Aug 16 14:04:00 2019 daemon.info dnsmasq-dhcp[1151]: DHCPACK(br-lan) 192.168.88.229 90:cd:b6:7d:d6:4b android-1250e50230069aac Fri Aug 16 14:04:00 2019 user.info com.netdumasoftware.neighwatch: DHCP new event. Fri Aug 16 14:04:00 2019 user.info com.netdumasoftware.neighwatch: DHCP new lease allocated. Fri Aug 16 14:04:01 2019 user.info com.netdumasoftware.qos: applying qos for zone wan Fri Aug 16 14:04:01 2019 user.info com.netdumasoftware.qos: applying qos for zone lan Fri Aug 16 14:04:01 2019 kern.warn kernel: [ 1629.852000] HTB: quantum of class 10001 is big. Consider r2q change. Fri Aug 16 14:06:10 2019 local5.info geoip-daemon[9152]: {"t":1759140,"ip":-1176383151,"category":"wd","distance":924, "lat": 51, "lng": 9, "rtt": 0, "islan2wan": true } Fri Aug 16 14:06:10 2019 local5.info geoip-daemon[9152]: verdict 1 524288 Fri Aug 16 14:06:10 2019 local5.info geoip-daemon[9152]: {"t":1759182,"ip":-1176383151,"category":"wd","distance":924, "lat": 51, "lng": 9, "rtt": 0, "islan2wan": true } Fri Aug 16 14:06:10 2019 local5.info geoip-daemon[9152]: verdict 1 524288 Fri Aug 16 14:06:17 2019 kern.info kernel: [ 1765.388000] recv: nf_ct_get failed Fri Aug 16 14:06:17 2019 kern.info kernel: [ 1765.388000] send: nf_ct_get failed Fri Aug 16 14:06:19 2019 kern.info kernel: [ 1768.176000] recv: nf_ct_get failed Fri Aug 16 14:06:20 2019 kern.info kernel: [ 1768.780000] recv: nf_ct_get failed Fri Aug 16 14:06:20 2019 kern.info kernel: [ 1768.780000] send: nf_ct_get failed Fri Aug 16 14:06:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 14:06:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 14:06:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 14:06:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 14:06:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 14:06:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 14:06:23 2019 kern.info kernel: [ 1771.480000] recv: nf_ct_get failed Fri Aug 16 14:06:50 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 14:06:50 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 14:06:50 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 14:07:09 2019 daemon.info hostapd: wlan0: STA dc:53:60:34:ac:e7 WPA: group key handshake completed (RSN) Fri Aug 16 14:07:09 2019 daemon.info hostapd: wlan0: STA 7a:9f:29:be:d0:92 WPA: group key handshake completed (RSN) Fri Aug 16 14:07:09 2019 daemon.info hostapd: wlan0: STA 0e:fc:e0:14:72:f2 WPA: group key handshake completed (RSN) Fri Aug 16 14:07:09 2019 daemon.info hostapd: wlan0: STA 38:8b:59:6b:69:05 WPA: group key handshake completed (RSN) Fri Aug 16 14:07:09 2019 daemon.info hostapd: wlan0: STA 0c:f9:c0:29:72:f6 WPA: group key handshake completed (RSN) Fri Aug 16 14:07:09 2019 daemon.info hostapd: wlan0: STA 90:cd:b6:7d:d6:4b WPA: group key handshake completed (RSN) Fri Aug 16 14:07:09 2019 daemon.info hostapd: wlan0: STA 88:51:fb:f9:eb:dc WPA: group key handshake completed (RSN) Fri Aug 16 14:07:09 2019 daemon.info hostapd: wlan0: STA d0:d2:b0:03:67:82 WPA: group key handshake completed (RSN) Fri Aug 16 14:07:10 2019 daemon.info hostapd: wlan0: STA 50:f5:da:ba:ea:61 WPA: group key handshake completed (RSN) Fri Aug 16 14:07:10 2019 daemon.info hostapd: wlan0: STA cc:c7:60:56:03:88 WPA: group key handshake completed (RSN) Fri Aug 16 14:07:14 2019 daemon.info hostapd: wlan0: STA dc:d3:a2:a6:38:8e IEEE 802.11: authenticated Fri Aug 16 14:07:14 2019 daemon.info hostapd: wlan0: STA dc:d3:a2:a6:38:8e IEEE 802.11: associated (aid 11) Fri Aug 16 14:07:14 2019 daemon.info hostapd: wlan0: STA dc:d3:a2:a6:38:8e WPA: pairwise key handshake completed (RSN) Fri Aug 16 14:07:14 2019 daemon.info dnsmasq-dhcp[1151]: DHCPREQUEST(br-lan) 192.168.88.150 dc:d3:a2:a6:38:8e Fri Aug 16 14:07:14 2019 daemon.info dnsmasq-dhcp[1151]: DHCPACK(br-lan) 192.168.88.150 dc:d3:a2:a6:38:8e MalisiPodtouch Fri Aug 16 14:07:14 2019 user.info com.netdumasoftware.neighwatch: DHCP old event. Fri Aug 16 14:07:14 2019 user.info com.netdumasoftware.neighwatch: DHCP lease change. Fri Aug 16 14:07:15 2019 daemon.warn odhcpd[740]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri Aug 16 14:07:37 2019 kern.info kernel: [ 1845.796000] recv: nf_ct_get failed Fri Aug 16 14:08:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 14:11:40 2019 kern.info kernel: [ 2089.248000] recv: nf_ct_get failed Fri Aug 16 14:14:50 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 14:15:02 2019 daemon.info hostapd: wlan0: STA 08:f4:ab:a4:53:77 IEEE 802.11: authenticated Fri Aug 16 14:15:02 2019 daemon.info hostapd: wlan0: STA 08:f4:ab:a4:53:77 IEEE 802.11: associated (aid 12) Fri Aug 16 14:15:02 2019 daemon.info hostapd: wlan0: STA 08:f4:ab:a4:53:77 WPA: pairwise key handshake completed (RSN) Fri Aug 16 14:15:04 2019 daemon.info dnsmasq-dhcp[1151]: DHCPREQUEST(br-lan) 192.168.88.113 08:f4:ab:a4:53:77 Fri Aug 16 14:15:04 2019 daemon.info dnsmasq-dhcp[1151]: DHCPACK(br-lan) 192.168.88.113 08:f4:ab:a4:53:77 CerisAppleWatch Fri Aug 16 14:15:04 2019 user.info com.netdumasoftware.neighwatch: DHCP old event. Fri Aug 16 14:15:04 2019 user.info com.netdumasoftware.neighwatch: DHCP lease change. Fri Aug 16 14:15:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 14:15:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri Aug 16 14:15:40 2019 daemon.warn odhcpd[740]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri Aug 16 14:15:44 2019 local5.info geoip-daemon[9152]: {"t":2332942,"ip":1836796452,"category":"wd","distance":303, "lat": 51, "lng": 0, "rtt": 0, "islan2wan": true } Fri Aug 16 14:15:44 2019 local5.info geoip-daemon[9152]: verdict 1 524288 Fri Aug 16 14:15:44 2019 local5.info geoip-daemon[9152]: {"t":2332948,"ip":1836796452,"category":"wd","distance":303, "lat": 51, "lng": 0, "rtt": 0, "islan2wan": true } Fri Aug 16 14:15:44 2019 local5.info geoip-daemon[9152]: verdict 1 524288 Fri Aug 16 14:15:48 2019 kern.info kernel: [ 2336.760000] recv: nf_ct_get failed Fri Aug 16 14:15:48 2019 kern.info kernel: [ 2336.764000] send: nf_ct_get failed Fri Aug 16 14:15:53 2019 kern.info kernel: [ 2341.368000] recv: nf_ct_get failed Fri Aug 16 14:15:53 2019 kern.info kernel: [ 2341.368000] send: nf_ct_get failed Link to comment Share on other sites More sharing options...
Administrators Netduma Alex Posted August 16, 2019 Administrators Share Posted August 16, 2019 I'll forward this to the devs to see if they can figure out where the problem is occuring. Link to comment Share on other sites More sharing options...
EricSe7en Posted August 19, 2019 Author Share Posted August 19, 2019 On 8/16/2019 at 3:31 PM, Netduma Alex said: I'll forward this to the devs to see if they can figure out where the problem is occuring. Hi, did anyone get round to looking at this? EDIT - I've just tried opening in Edge and Internet explorer and it appears to be working fine in both, it just takes an age to open. Isn't chrome the preferred browser? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted August 20, 2019 Administrators Share Posted August 20, 2019 They'll likely get to it this week. It looks fine to me but I'm not a developer. Yes it is, are you trying to access using HTTPS by any chance? If so try with HTTP on Chrome does it work properly then? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.