Jump to content

willphule

Members
  • Content Count

    99
  • Joined

  • Last visited

Everything posted by willphule

  1. I would be fine with that as I am in the states - if it was banned it would look for another server to connect to wouldn't it (a closer one hopefully)?
  2. Is there any reason I shouldn't be able to ban an overseas server? This is the id (I am in the USA) ed36a772d38c4348
  3. I reset to factory today and was going through the setup again and I forgot to make my PC appear as a PS4 in the device manager. Was surprised to see D2 PC listed in the game popup since it has to be setup as a console for geo to work doesn't it?
  4. Now when I enter a comp match I see dozens of peers around the world - not just the players in the match. Anybody else seeing this?
  5. On both ethernet and wifi. This will be a weekend project as the cable goes directly from the R1 out to the box on the side of the house - I'll let you know how it goes!
  6. and another one from this morning following a disconnect - this one looks to have more info: Fri May 24 12:58:00 2019 daemon.warn odhcpd[739]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri May 24 12:57:56 2019 daemon.notice netifd: Interface 'wan6' is disabled Fri May 24 12:57:56 2019 daemon.notice netifd: Interface 'wan6' is now down Fri May 24 12:57:56 2019 daemon.warn miniupnpd[1465]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping Fri May 24 12:57:56 2019 daemon.err miniupnpd[1465]: Failed to get IP for interface eth0.2 Fri May 24 12:57:56 2019 daemon.err miniupnpd[1465]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address Fri May 24 12:57:56 2019 daemon.notice netifd: Interface 'wan' has lost the connection Fri May 24 12:57:56 2019 daemon.notice netifd: wan (868): Lease lost, entering init state Fri May 24 12:57:56 2019 daemon.notice netifd: wan (868): Sending renew... Fri May 24 12:57:55 2019 daemon.notice netifd: wan (868): Sending renew... Fri May 24 12:57:52 2019 daemon.notice netifd: wan (868): Sending renew... Fri May 24 12:57:45 2019 daemon.notice netifd: wan (868): Sending renew... Fri May 24 12:57:45 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 12:57:45 2019 local5.info geoip-daemon[7329]: {"t":753263426,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Fri May 24 12:57:36 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri May 24 12:57:36 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri May 24 12:57:33 2019 kern.info kernel: [753251.348000] send: nf_ct_get failed Fri May 24 12:57:33 2019 kern.info kernel: [753251.348000] recv: nf_ct_get failed Fri May 24 12:57:32 2019 user.info com.netdumasoftware.neighwatch: DHCP lease change. Fri May 24 12:57:32 2019 user.info com.netdumasoftware.neighwatch: DHCP old event. Fri May 24 12:57:32 2019 daemon.info dnsmasq-dhcp[1578]: DHCPACK(br-lan) 192.168.88.172 Fri May 24 12:57:32 2019 daemon.info dnsmasq-dhcp[1578]: DHCPREQUEST(br-lan) 192.168.88.172 Fri May 24 12:57:31 2019 user.info com.netdumasoftware.neighwatch: DHCP lease change. Fri May 24 12:57:31 2019 user.info com.netdumasoftware.neighwatch: DHCP old event. Fri May 24 12:57:31 2019 daemon.info dnsmasq-dhcp[1578]: DHCPACK(br-lan) 192.168.88.172 Fri May 24 12:57:31 2019 daemon.info dnsmasq-dhcp[1578]: DHCPREQUEST(br-lan) 192.168.88.172 Fri May 24 12:57:31 2019 daemon.info hostapd: wlan0: STA b0:f1:ec:11:ab:ba WPA: group key handshake completed (WPA) Fri May 24 12:57:31 2019 daemon.info hostapd: wlan0: STA b0:f1:ec:11:ab:ba WPA: pairwise key handshake completed (WPA) Fri May 24 12:57:31 2019 daemon.info hostapd: wlan0: STA b0:f1:ec:11:ab:ba IEEE 802.11: associated (aid 3) Fri May 24 12:57:31 2019 daemon.info hostapd: wlan0: STA b0:f1:ec:11:ab:ba IEEE 802.11: authenticated Fri May 24 12:57:31 2019 daemon.notice netifd: wan (868): Sending renew... Fri May 24 12:56:47 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 12:56:47 2019 local5.info geoip-daemon[7329]: {"t":753205431,"ip":1359657410,"category":"wd","distance":4962, "lat": 48, "lng": 15, "rtt": 0, "islan2wan": true } Fri May 24 12:56:47 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 12:56:47 2019 local5.info geoip-daemon[7329]: {"t":753205427,"ip":1359657410,"category":"wd","distance":4962, "lat": 48, "lng": 15, "rtt": 0, "islan2wan": true } Fri May 24 12:56:47 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 12:56:47 2019 local5.info geoip-daemon[7329]: {"t":753205423,"ip":1359657410,"category":"wd","distance":4962, "lat": 48, "lng": 15, "rtt": 0, "islan2wan": true } Fri May 24 12:56:47 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 12:56:47 2019 local5.info geoip-daemon[7329]: {"t":753205419,"ip":1359657410,"category":"wd","distance":4962, "lat": 48, "lng": 15, "rtt": 0, "islan2wan": true } Fri May 24 12:56:43 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 12:56:43 2019 local5.info geoip-daemon[7329]: {"t":753202091,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Fri May 24 12:56:39 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 12:56:39 2019 local5.info geoip-daemon[7329]: {"t":753197747,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Fri May 24 12:56:23 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 12:56:23 2019 local5.info geoip-daemon[7329]: {"t":753181703,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Fri May 24 12:56:07 2019 daemon.notice netifd: wan (868): Sending renew...
  7. It is the same no matter the browser or device. I am hoping I may have caught one of the disconnects in the log this morning - does anything in it indicate an event that would could have resulted in a disconnect? (I stripped out a bunch of the nf_ct_get failed and kern.info dpiclass-daemon: Kill flow due to timeout messages to clean it up a bit, and I masked my IP.) ------------------------------------------------------------------------------------- Fri May 24 10:57:58 2019 kern.info kernel: [746076.220000] recv: nf_ct_get failed Fri May 24 10:57:56 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:56 2019 local5.info geoip-daemon[7329]: {"t":746074524,"ip":-1189950333,"category":"wd","distance":6906, "lat": 31, "lng": 34, "rtt": 0, "islan2wan": true } Fri May 24 10:57:56 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:56 2019 local5.info geoip-daemon[7329]: {"t":746074521,"ip":-1189950333,"category":"wd","distance":6906, "lat": 31, "lng": 34, "rtt": 0, "islan2wan": true } Fri May 24 10:57:56 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:56 2019 local5.info geoip-daemon[7329]: {"t":746074519,"ip":1467329919,"category":"wd","distance":7172, "lat": 55, "lng": 49, "rtt": 0, "islan2wan": true } Fri May 24 10:57:56 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:56 2019 local5.info geoip-daemon[7329]: {"t":746074516,"ip":1467329919,"category":"wd","distance":7172, "lat": 55, "lng": 49, "rtt": 0, "islan2wan": true } Fri May 24 10:57:56 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:56 2019 local5.info geoip-daemon[7329]: {"t":746074513,"ip":-1189950333,"category":"wd","distance":6906, "lat": 31, "lng": 34, "rtt": 0, "islan2wan": true } Fri May 24 10:57:56 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:56 2019 local5.info geoip-daemon[7329]: {"t":746074511,"ip":1467329919,"category":"wd","distance":7172, "lat": 55, "lng": 49, "rtt": 0, "islan2wan": true } Fri May 24 10:57:55 2019 kern.info kernel: [746073.916000] recv: nf_ct_get failed Fri May 24 10:57:50 2019 kern.info kernel: [746068.960000] recv: nf_ct_get failed Fri May 24 10:57:50 2019 daemon.warn odhcpd[739]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri May 24 10:57:50 2019 kern.info kernel: [746068.640000] send: nf_ct_get failed Fri May 24 10:57:48 2019 kern.info kernel: [746066.912000] recv: nf_ct_get failed Fri May 24 10:57:48 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:48 2019 local5.info geoip-daemon[7329]: {"t":746066906,"ip":-951924464,"category":"wd","distance":5306, "lat": 37, "lng": -98, "rtt": 0, "islan2wan": true } Fri May 24 10:57:48 2019 kern.info kernel: [746066.568000] recv: nf_ct_get failed Fri May 24 10:57:48 2019 kern.info kernel: [746066.380000] recv: nf_ct_get failed Fri May 24 10:57:45 2019 daemon.warn dnsmasq[1578]: possible DNS-rebind attack detected: 192-168-88-140.abcdefghijklmnopqrstuvwxyz012345.plex.direct Fri May 24 10:57:44 2019 kern.info kernel: [746062.980000] recv: nf_ct_get failed Fri May 24 10:57:44 2019 kern.info kernel: [746062.880000] send: nf_ct_get failedFri May 24 10:57:43 2019 kern.info kernel: [746061.364000] recv: nf_ct_get failed Fri May 24 10:57:43 2019 daemon.warn dnsmasq[1578]: possible DNS-rebind attack detected: 192-168-88-233.abcdefghijklmnopqrstuvwxyz012345.plex.direct Fri May 24 10:57:42 2019 kern.info kernel: [746061.100000] send: nf_ct_get failed Fri May 24 10:57:40 2019 daemon.warn dnsmasq[1578]: possible DNS-rebind attack detected: 192-168-88-220.abcdefghijklmnopqrstuvwxyz012345.plex.direct Fri May 24 10:57:39 2019 kern.info kernel: [746057.828000] send: nf_ct_get failed Fri May 24 10:57:39 2019 kern.info kernel: [746057.828000] recv: nf_ct_get failed Fri May 24 10:57:37 2019 user.notice firewall: Reloading firewall due to ifup of wan (eth0.2) Fri May 24 10:57:37 2019 kern.info kernel: [746055.504000] recv: nf_ct_get failed Fri May 24 10:57:37 2019 daemon.notice odhcp6c[22350]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0) Fri May 24 10:57:37 2019 kern.info kernel: [746055.468000] recv: nf_ct_get failed Fri May 24 10:57:37 2019 daemon.notice odhcp6c[22350]: (re)starting transaction on eth0.2 Fri May 24 10:57:37 2019 kern.info kernel: [746055.376000] recv: nf_ct_get failed Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: {"t":746055329,"ip":-1013273136,"category":"wd","distance":4003, "lat": 48, "lng": 2, "rtt": 0, "islan2wan": true } Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: {"t":746055326,"ip":-1013273136,"category":"wd","distance":4003, "lat": 48, "lng": 2, "rtt": 0, "islan2wan": true } Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: {"t":746055323,"ip":-1548955123,"category":"wd","distance":4251, "lat": 52, "lng": 4, "rtt": 0, "islan2wan": true } Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: {"t":746055319,"ip":-1548955123,"category":"wd","distance":4251, "lat": 52, "lng": 4, "rtt": 0, "islan2wan": true } Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: {"t":746055316,"ip":-1548955123,"category":"wd","distance":4251, "lat": 52, "lng": 4, "rtt": 0, "islan2wan": true } Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: {"t":746055313,"ip":-1548955123,"category":"wd","distance":4251, "lat": 52, "lng": 4, "rtt": 0, "islan2wan": true } Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: {"t":746055309,"ip":-1548955123,"category":"wd","distance":4251, "lat": 52, "lng": 4, "rtt": 0, "islan2wan": true } Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: {"t":746055306,"ip":-1548955123,"category":"wd","distance":4251, "lat": 52, "lng": 4, "rtt": 0, "islan2wan": true } Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: {"t":746055302,"ip":-1548955123,"category":"wd","distance":4251, "lat": 52, "lng": 4, "rtt": 0, "islan2wan": true } Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: {"t":746055299,"ip":-1548955123,"category":"wd","distance":4251, "lat": 52, "lng": 4, "rtt": 0, "islan2wan": true } Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: {"t":746055295,"ip":-1548955123,"category":"wd","distance":4251, "lat": 52, "lng": 4, "rtt": 0, "islan2wan": true } Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: {"t":746055292,"ip":-1548955123,"category":"wd","distance":4251, "lat": 52, "lng": 4, "rtt": 0, "islan2wan": true } Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: {"t":746055272,"ip":-1548955123,"category":"wd","distance":4251, "lat": 52, "lng": 4, "rtt": 0, "islan2wan": true } Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Fri May 24 10:57:37 2019 local5.info geoip-daemon[7329]: {"t":746055265,"ip":-1548955123,"category":"wd","distance":4251, "lat": 52, "lng": 4, "rtt": 0, "islan2wan": true } Fri May 24 10:57:36 2019 daemon.notice netifd: Interface 'wan' is now up Fri May 24 10:57:36 2019 daemon.notice netifd: Interface 'wan6' is setting up now Fri May 24 10:57:36 2019 daemon.notice netifd: Interface 'wan6' is enabled Fri May 24 10:57:36 2019 user.info com.netdumasoftware.qos: hotplug interface wan Fri May 24 10:57:36 2019 kern.info kernel: [746055.004000] recv: nf_ct_get failed Fri May 24 10:57:36 2019 kern.info kernel: [746054.976000] recv: nf_ct_get failed Fri May 24 10:57:36 2019 daemon.notice netifd: wan (868): Lease of [MY IP] obtained, lease time 3600 Fri May 24 10:57:36 2019 kern.info kernel: [746054.860000] recv: nf_ct_get failed Fri May 24 10:57:36 2019 kern.info kernel: [746054.788000] send: nf_ct_get failed Fri May 24 10:57:36 2019 kern.info dpiclass-daemon: Kill flow due to timeout Fri May 24 10:57:36 2019 kern.info kernel: [746054.252000] recv: nf_ct_get failed Fri May 24 10:57:36 2019 kern.info kernel: [746054.192000] recv: nf_ct_get failed Fri May 24 10:57:35 2019 daemon.notice netifd: wan (868): Sending select for [My IP ADDRESS]...
  8. Chrome, latest build. I can scroll when I first open it, but there is only the last 2-8 minutes showing (same if I download the log). I've pasted the log below That is all that was there when I first opened it just now. If I leave the system information page open it logs more events but eventually the log module stops responding (I am guessing) as I can no longer scroll through it. ------------- Wed May 22 21:53:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:53:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:53:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:53:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:53:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:53:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:53:43 2019 daemon.info hostapd: wlan0: STA b0:f1:ec:12:19:22 WPA: group key handshake completed (WPA) Wed May 22 21:53:43 2019 daemon.info hostapd: wlan0: STA 74:75:48:0e:4e:7b WPA: group key handshake completed (WPA) Wed May 22 21:53:43 2019 daemon.info hostapd: wlan0: STA b0:f1:ec:11:ab:ba WPA: group key handshake completed (WPA) Wed May 22 21:53:41 2019 daemon.info hostapd: wlan0: STA cc:9e:a2:35:26:d7 WPA: group key handshake completed (WPA) Wed May 22 21:53:41 2019 daemon.info hostapd: wlan0: STA 88:b4:a6:13:49:8e WPA: group key handshake completed (WPA) Wed May 22 21:53:41 2019 daemon.info hostapd: wlan0: STA 40:a5:ef:3c:76:46 WPA: group key handshake completed (WPA) Wed May 22 21:53:30 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:53:30 2019 local5.info geoip-daemon[7329]: {"t":612609136,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Wed May 22 21:53:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:53:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:53:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:53:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:52:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:52:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:52:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:52:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:52:50 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:52:50 2019 local5.info geoip-daemon[7329]: {"t":612568414,"ip":-1058955774,"category":"wd","distance":5306, "lat": 37, "lng": -98, "rtt": 0, "islan2wan": true } Wed May 22 21:52:50 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:52:50 2019 local5.info geoip-daemon[7329]: {"t":612568408,"ip":-1058955774,"category":"wd","distance":5306, "lat": 37, "lng": -98, "rtt": 0, "islan2wan": true } Wed May 22 21:52:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:52:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:52:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:52:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:52:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:52:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:52:17 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:52:17 2019 local5.info geoip-daemon[7329]: {"t":612535423,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Wed May 22 21:52:03 2019 kern.info kernel: [612521.872000] send: nf_ct_get failed Wed May 22 21:52:03 2019 kern.info kernel: [612521.872000] recv: nf_ct_get failed Wed May 22 21:51:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:51:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:51:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:51:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:51:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:51:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:51:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:51:37 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:51:37 2019 local5.info geoip-daemon[7329]: {"t":612495277,"ip":-1058955774,"category":"wd","distance":5306, "lat": 37, "lng": -98, "rtt": 0, "islan2wan": true } Wed May 22 21:51:30 2019 user.debug com.netdumasoftware.devicemanager: Marking device that is marked 192.168.88.215 23 17. Wed May 22 21:51:30 2019 kern.info kernel: [612488.472000] send: nf_ct_get failed Wed May 22 21:51:30 2019 kern.info kernel: [612488.472000] recv: nf_ct_get failed Wed May 22 21:51:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:51:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:51:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:51:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:51:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:51:19 2019 daemon.notice netifd: wan (868): Sending renew... Wed May 22 21:51:13 2019 kern.info kernel: [612471.792000] send: nf_ct_get failed Wed May 22 21:51:13 2019 kern.info kernel: [612471.792000] recv: nf_ct_get failed Wed May 22 21:51:11 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:51:11 2019 local5.info geoip-daemon[7329]: {"t":612469584,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Wed May 22 21:51:08 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:51:08 2019 local5.info geoip-daemon[7329]: {"t":612466152,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Wed May 22 21:51:05 2019 kern.info kernel: [612463.444000] send: nf_ct_get failed Wed May 22 21:51:05 2019 kern.info kernel: [612463.444000] recv: nf_ct_get failed Wed May 22 21:51:01 2019 kern.info kernel: [612459.272000] send: nf_ct_get failed Wed May 22 21:51:01 2019 kern.info kernel: [612459.272000] recv: nf_ct_get failed Wed May 22 21:50:59 2019 kern.info kernel: [612457.192000] send: nf_ct_get failed Wed May 22 21:50:59 2019 kern.info kernel: [612457.192000] recv: nf_ct_get failed Wed May 22 21:50:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:50:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:50:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:50:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:50:58 2019 kern.info kernel: [612456.160000] send: nf_ct_get failed Wed May 22 21:50:58 2019 kern.info kernel: [612456.160000] recv: nf_ct_get failed Wed May 22 21:50:57 2019 kern.info kernel: [612455.636000] send: nf_ct_get failed Wed May 22 21:50:57 2019 kern.info kernel: [612455.636000] recv: nf_ct_get failed Wed May 22 21:50:57 2019 kern.info kernel: [612455.352000] send: nf_ct_get failed Wed May 22 21:50:57 2019 kern.info kernel: [612455.352000] recv: nf_ct_get failed Wed May 22 21:50:56 2019 kern.info kernel: [612455.092000] send: nf_ct_get failed Wed May 22 21:50:56 2019 kern.info kernel: [612455.092000] recv: nf_ct_get failed Wed May 22 21:50:53 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:50:53 2019 local5.info geoip-daemon[7329]: {"t":612451631,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Wed May 22 21:50:53 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:50:53 2019 local5.info geoip-daemon[7329]: {"t":612451627,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Wed May 22 21:50:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:50:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:50:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:50:23 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:50:23 2019 local5.info geoip-daemon[7329]: {"t":612421573,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Wed May 22 21:50:23 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:50:23 2019 local5.info geoip-daemon[7329]: {"t":612421565,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Wed May 22 21:49:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:49:15 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:49:15 2019 local5.info geoip-daemon[7329]: {"t":612353601,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Wed May 22 21:49:04 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:49:04 2019 local5.info geoip-daemon[7329]: {"t":612342913,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Wed May 22 21:49:04 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:49:04 2019 local5.info geoip-daemon[7329]: {"t":612342910,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Wed May 22 21:48:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:48:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:48:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:48:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:48:49 2019 daemon.info dnsmasq-dhcp[1578]: DHCPACK(br-lan) 192.168.88.237 Wed May 22 21:48:49 2019 daemon.info dnsmasq-dhcp[1578]: DHCPINFORM(br-lan) 192.168.88.237 Wed May 22 21:48:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:48:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:48:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:48:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:48:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:48:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:48:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:48:23 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:48:23 2019 local5.info geoip-daemon[7329]: {"t":612301974,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Wed May 22 21:48:20 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:48:20 2019 local5.info geoip-daemon[7329]: {"t":612298241,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Wed May 22 21:48:03 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:48:03 2019 local5.info geoip-daemon[7329]: {"t":612281603,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Wed May 22 21:47:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:47:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:47:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:47:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:47:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:47:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:47:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:47:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:47:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:47:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:47:34 2019 daemon.info dnsmasq-dhcp[1578]: DHCPACK(br-lan) 192.168.88.237 Wed May 22 21:47:34 2019 daemon.info dnsmasq-dhcp[1578]: DHCPINFORM(br-lan) 192.168.88.237 Wed May 22 21:47:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:47:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:47:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:47:26 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:47:26 2019 local5.info geoip-daemon[7329]: {"t":612244254,"ip":-951924464,"category":"wd","distance":5306, "lat": 37, "lng": -98, "rtt": 0, "islan2wan": true } Wed May 22 21:47:14 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:47:14 2019 local5.info geoip-daemon[7329]: {"t":612232582,"ip":1828455801,"category":"wd","distance":5492, "lat": 30, "lng": -98, "rtt": 0, "islan2wan": true } Wed May 22 21:47:00 2019 kern.info kernel: [612218.512000] send: nf_ct_get failed Wed May 22 21:47:00 2019 kern.info kernel: [612218.512000] recv: nf_ct_get failed Wed May 22 21:46:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:42 2019 daemon.warn odhcpd[739]: Failed to send to ff02::1%br-lan (Operation not permitted) Wed May 22 21:46:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:28 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:46:28 2019 kern.info kernel: [612186.432000] send: nf_ct_get failed Wed May 22 21:46:28 2019 kern.info kernel: [612186.432000] recv: nf_ct_get failed Wed May 22 21:46:12 2019 kern.info kernel: [612170.368000] send: nf_ct_get failed Wed May 22 21:46:12 2019 kern.info kernel: [612170.368000] recv: nf_ct_get failed Wed May 22 21:46:05 2019 kern.info kernel: [612163.660000] send: nf_ct_get failed Wed May 22 21:46:05 2019 kern.info kernel: [612163.660000] recv: nf_ct_get failed Wed May 22 21:46:04 2019 kern.info kernel: [612162.352000] send: nf_ct_get failed Wed May 22 21:46:04 2019 kern.info kernel: [612162.352000] recv: nf_ct_get failed Wed May 22 21:46:02 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:46:02 2019 local5.info geoip-daemon[7329]: {"t":612160985,"ip":1220316423,"category":"wd","distance":3959, "lat": 28, "lng": -81, "rtt": 0, "islan2wan": true } Wed May 22 21:46:00 2019 kern.info kernel: [612158.340000] send: nf_ct_get failed Wed May 22 21:46:00 2019 kern.info kernel: [612158.340000] recv: nf_ct_get failed Wed May 22 21:45:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:45:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:45:58 2019 kern.info dpiclass-daemon: Kill flow due to timeout Wed May 22 21:45:58 2019 kern.info kernel: [612156.340000] send: nf_ct_get failed Wed May 22 21:45:58 2019 kern.info kernel: [612156.340000] recv: nf_ct_get failed Wed May 22 21:45:57 2019 kern.info kernel: [612155.340000] send: nf_ct_get failed Wed May 22 21:45:57 2019 kern.info kernel: [612155.340000] recv: nf_ct_get failed Wed May 22 21:45:56 2019 kern.info kernel: [612154.840000] send: nf_ct_get failed Wed May 22 21:45:56 2019 kern.info kernel: [612154.840000] recv: nf_ct_get failed Wed May 22 21:45:56 2019 kern.info kernel: [612154.568000] send: nf_ct_get failed Wed May 22 21:45:56 2019 kern.info kernel: [612154.568000] recv: nf_ct_get failed Wed May 22 21:45:56 2019 kern.info kernel: [612154.324000] send: nf_ct_get failed Wed May 22 21:45:56 2019 kern.info kernel: [612154.324000] recv: nf_ct_get failed Wed May 22 21:45:55 2019 kern.info kernel: [612153.976000] recv: nf_ct_get failed Wed May 22 21:45:50 2019 daemon.info dnsmasq-dhcp[1578]: DHCPACK(br-lan) 192.168.88.237 Wed May 22 21:45:50 2019 daemon.info dnsmasq-dhcp[1578]: DHCPINFORM(br-lan) 192.168.88.237 Wed May 22 21:45:48 2019 local5.info geoip-daemon[7329]: verdict 1 524288 Wed May 22 21:45:48 2019 local5.info geoip-daemon[7329]: {"t":612146974,"ip":1828455801,"category":"wd","distance":5492, "lat": 30, "lng": -98, "rtt": 0, "islan2wan": true } Wed May 22 21:45:46 2019 local5.info geoip-daemon[7329]: verdict 1 524288
  9. No, it only shows me a couple of minutes when I open the dashboard, and the downloaded log is also the same size. if I leave it open it appear to continue to log though, so I'll try leaving it open and hopefully I can catch one of these incidents.
  10. I keep getting intermittent connection losses of a couple of seconds, but by the time I pull up the dashboard and get to the log it has scrolled past any useful information that might help me diagnose the connection loss.
  11. Yeah, I don't think they are "trying" to hide them, but that is effectively what happens and those teams always have a networking advantage it seems. That said, this little trick about putting yourself in the ocean and setting ping assist to something reasonable has resulted in SUPERB connections so far in PVP - I can't remember the last time my connection was so good. I had previously tried ping assist with my actual location set and that resulted in some dubious connections, even the ones marked as ping assist on the map. I don't know if Bungie sees us differently for some reason or this is just a placebo effect - but I am loving it!
  12. Geofilter isn't the problem, the way Bungie tunnels connections (and hides 4 stacks by running them through their servers) around the world is the problem imo. If I have Geo on, get connected with less than the expected number of players for the match then move my radius to the entire world I often find that I am connected overseas to someone - this was not visible when flying in. I don't know if it starts showing due to a server handoff or what, but it has happened way too many times to be a glitch.
  13. Is it hidden somewhere, or has it just disappeared? If the latter, please please bring it back.
  14. I have been unable to use any of the following ! @ # $ % ^ & * : " ; '
  15. I just upgraded to the latest beta from 1.03.6j. I went to change my router password back to what I had it set to prior to the upgrade and at the first special character I type it says "invalid password". It appears that any special character that requires the shift key is disallowed? Hoping this is a bug, but looking for clarification... Thanks!
  16. Starting with a fresh r1 today after reverting from the beta...sigh The 2nd of these is definitely a locked icon in Virginia. The first I think might be another one, but it could also have been a peer in tight proximity to the locked server. ID: ff3621ecd39e9fa4 Distance: 973mi ID: f0364611d38f9fa4 Distance: 880mi Also, if anybody can point me to the latest and greatest D2 settings I would appreciate it. After going back to 1.03.6 things have been rocky to say the least...
  17. Oh wow, that defeats the entire purpose for me (finding laggy peers in D2) - going to have to downgrade.
  18. On the old R1 I could see the ping graph of all the players in a match (Destiny 2) - is that feature gone now? It appears that I can only view the ping of one client at a time or the host? I can no longer autoping host and ping a client at the same time? Hoping I am just confused or oblivious like I was with the reboot location...
  19. Thank you! I assumed those were all help tips - never would have found it!
  20. I know I am probably just being blind, but where is reboot located? I've clicked through every module and on every menu button I could find, but I don't see it.
  21. One of the biggest parts of the problem, imo, is that Destiny will match you to players outside of the geofilter through their servers. When strict works it works wonders. I had a streak and a half in competitive (solo) on Sat and it was a blast everything was crisp and perfect, no laggy players. I was working on another one on Sun - at some point in the afternoon something changed on their servers, or at least the one I was connecting to, and everything went to crap again, shots wouldn't register movement felt sluggish, laggy players, etc. Started getting booted with strict on, then suspended because of the beaver errors. So frustrating....yet I keep playing.
×
×
  • Create New...