Jump to content

FQs19

Members
  • Content count

    617
  • Joined

  • Last visited

About FQs19

  • Rank
    Senior Member

Profile Information

  • Gender
    Male
  • Location
    Aldan, Pennsylvania

Recent Profile Visitors

4,161 profile views
  1. FQs19

    Black Ops 4 - Getting P2P Only? Post Here!

    On Xbox, Console deleted from Geo-Filter, DumaOS on R1, Open NAT shown in Game, This is what I get when searching for any game in Multiplayer: Thu Nov 29 21:36:27 2018 daemon.warn odhcpd[740]: Failed to send to ff02::1%br-lan (Operation not permitted) Thu Nov 29 21:36:16 2018 kern.info kernel: [ 442.136000] send: nf_ct_get failed Thu Nov 29 21:36:16 2018 kern.info kernel: [ 442.136000] recv: nf_ct_get failed Then the game boots me back to the main screen saying Lobby was full.
  2. BO4 on Xbox takes forever to connect to a Peer host and has a bunch of graphical errors on-screen. I can't connect to a Dedi at all. Geo-filter is disabled. BO3 on PS4 works perfectly fine. So I say it's a BO4 issue. Not DumaOS.
  3. I disabled the Geofilter and restarted my xbox, I'm still only getting Peer hosts. It's not just DumaOS users.
  4. I have. I let it use the G1100 automatic DNS from Verizon and tried 1.1.1.1 too. Neither worked.
  5. There's no way to enter the IP address on my devices like my LG OLED TV Plex app or my Nvidia Shield TV Plex app. They simply ask you to sign into your account and connect automatically. This is the error I get when Diagnosing my Network connection on the PC which is connected to the R1:
  6. If I place the Plex server PC on the G1100 network, then I'm not able to take advantage of the R1's QoS. My friends have access to my Plex content, so I could be playing online games while my friends are watching my Plex content, which could cause me lag issues.
  7. I access the server through the PC which is the server. My clients are unable to connect to the server so I can view the content. I am connecting through WAN essentially since the client I'm trying to view my Plex content on is on the WAN side of the R1, but the server is fully accessible outside my network. It worked with the XR700 in the same configuration. So I'm not understanding why it won't work with the R1 with DumaOS.
  8. My setup: Internet>Verizon G1100 gateway>R1 (DMZ'd in the G1100)>Plex server (on a pc) I'm running a Plex server on a pc that is wired to the R1 which is DMZ'd in my Verizon G1100 router. I can not connect to my Plex server from anything on my local network, but I can connect to my Plex from outside my network. There seems to be a problem with NAT and I can't figure out how to fix it. I've tried manually port forwarding everything I could think of, but nothing has worked. To be more specific, I'm trying to connect to my Plex server from devices that are under my Verizon G1100 which are on 192.168.1.x subnet. The R1 is running a dhcp server on 192.168.88.x subnet. When I had the XR700 in this same configuration, I had zero issues with Plex. It worked perfectly. I could connect to my Plex from both locally and remotely. Could a dev take a look at what is different between the XR700 and the R1 running DumaOS to see why NAT traffic isn't working within the local network. Thanks My Plex Server status My R1 port forwarding the correct ports My Macbook Pro on the G1100 subnet not being able to connect to the Plex Server on the R1 subnet The most recent logs Fri Nov 23 15:16:50 2018 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory. Fri Nov 23 15:15:54 2018 kern.info kernel: [47920.212000] recv: nf_ct_get failed Fri Nov 23 15:14:54 2018 kern.info dpiclass-daemon: Kill flow due to timeout Fri Nov 23 15:14:54 2018 kern.info dpiclass-daemon: Kill flow due to timeout Fri Nov 23 15:12:56 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri Nov 23 15:09:34 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri Nov 23 15:07:41 2018 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory. Fri Nov 23 15:07:34 2018 kern.info kernel: [47420.188000] recv: nf_ct_get failed Fri Nov 23 15:05:27 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri Nov 23 14:59:17 2018 kern.info kernel: [46923.100000] recv: nf_ct_get failed Fri Nov 23 14:57:23 2018 kern.info dpiclass-daemon: Kill flow due to timeout Fri Nov 23 14:57:09 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri Nov 23 14:56:53 2018 kern.info dpiclass-daemon: Kill flow due to timeout Fri Nov 23 14:56:53 2018 kern.info dpiclass-daemon: Kill flow due to timeout Fri Nov 23 14:56:53 2018 kern.info dpiclass-daemon: Kill flow due to timeout Fri Nov 23 14:56:20 2018 daemon.warn dnsmasq[1120]: possible DNS-rebind attack detected: 192-168-88-15.8cbab343d9204bc98b1d780de2885481.plex.direct Fri Nov 23 14:56:20 2018 daemon.warn dnsmasq[1120]: possible DNS-rebind attack detected: 192-168-1-243.a587e45deb5b4b239d14bfa023a5f0a9.plex.direct Fri Nov 23 14:49:33 2018 kern.info kernel: [46338.688000] recv: nf_ct_get failed Fri Nov 23 14:48:59 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri Nov 23 14:44:09 2018 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory. Fri Nov 23 14:40:21 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri Nov 23 14:40:09 2018 kern.info kernel: [45775.308000] recv: nf_ct_get failed Fri Nov 23 14:33:18 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri Nov 23 14:30:58 2018 kern.info kernel: [45223.988000] recv: nf_ct_get failed Fri Nov 23 14:23:29 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri Nov 23 14:21:26 2018 kern.info kernel: [44651.848000] recv: nf_ct_get failed Fri Nov 23 14:18:26 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri Nov 23 14:12:25 2018 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted) Fri Nov 23 14:12:24 2018 kern.info kernel: [44109.788000] recv: nf_ct_get failed Fri Nov 23 14:06:51 2018 kern.info dpiclass-daemon: Kill flow due to timeout Fri Nov 23 14:04:51 2018 kern.info dpiclass-daemon: Kill flow due to timeout Fri Nov 23 14:02:49 2018 kern.info kernel: [43534.608000] recv: nf_ct_get failed
  9. FQs19

    gigabit internet

    Yeah, DumaOS is much easier to run than the original firmware, so you can get pretty good speeds. That's the R1 with DumaOS, running behind my Verizon G1100 router, with QoS disabled.
  10. FQs19

    gigabit internet

    I can get 500mb down and up with the R1 if you set your speeds to 1000mb d/u and disable the QoS.
  11. Netgear finally sent me a request to sign up for a Beta they have for the XR700. They say it fixes some of my issues. Not sure what 'issues' they think they've fixed. Unfortunately, My 30 day return is up tomorrow and I can not allow myself to Beta test a $500 router, so I'm returning the router without trying their beta. I've asked them to clarify what the beta supposedly fixes, but if you guys could get in touch with Netgear and post something about what they think the problem was and how they fixed it, I would purchase the XR700 in the future. I am in agreement with a bunch of users who think Netduma should release their DumaOS on another Mikrotik product or even design your own router. Hopefully one that incorporates all the specs and hardware of a 2018/19 router would/should.
  12. Would also love to get 'Access from WAN' implemented as soon as possible. Thanks
  13. They know about the return window. They also know my current xr700 is a replacement for the first one which had the same issues. Working 12hr shifts for 10 days in a row isn't helping our communication. Which is why the return window is closing before they can get a clear picture of what's happening.
  14. Finally got a day off to troubleshoot this router some more with Level 2 Netgear Support. First they had me install the newest firmware, 1.0.1.2. Then I had to factory reset the router. Then they had me go to the Debug Page, enable the LAN/WAN packet capture, then Start Capture. I ran like that for almost two days while running Ping Plotter to Verizon.com which showed a whole bunch of packet loss on a wired connection. I wasn't able to see if my wan connection dropped because the logs filled up with non-important stuff and just kept getting cleared out. I saved the debug log and sent it to them along with the Ping Plotter .pp2 file for their review. This is what ping plotter captured on my pc wired to the XR700 behind my Verizon Fios G1100: After they received my logs, they used TeamViewer to copy down my network diagnostics, both wireless and wired, from my Macbook Pro. Then they had me change the XR700 MTU to 1400 from the default of 1500 which i've been using forever with broadband internet. They want me to see if changing the MTU stops the disconnections and packet loss from happening. All of this info is being sent up to their next level of support. Unfortunately, my 30 day return period is approaching, so I must return it. I can't use a router with this many problems even if Netgear is willing to work with me on troubleshooting it. I don't have the time to be their beta tester. I'll update this thread if Netgear responds with anything of value. XR700 with 1.0.1.2 firmware verizon.com.pp2
  15. So returning it is my only option. Thanks for the help.
×