Jump to content

THE_DEAD_POOL

Members
  • Content Count

    105
  • Joined

  • Last visited


Reputation Activity

  1. Like
    THE_DEAD_POOL reacted to RT Turn Clyde in Cannot Receive/Send Picture Messages through the R1 (Reopened?)   
    So I had this issue also. After a little trial and error testing, I found that the wifi calling feature on the iPhone is getting stuck on without any indication of it being on.
     
    The best way I found to ensure wifi calling is off and have the ability to send MMS when connected to the Duma is to do the following;
     
    1. Ensure wifi calling is disabled
    2. Connect to your Wifi.
    3. Disable your wifi in the settings menu not the quick menu that you drag up (important!! This method didn't work).
    4. Enable wifi calling, wait ~10 seconds.
    5. Disable wifi calling
    6. Reconnect to your wifi.
     
    Unfortunately you have to do this everytime you enable wifi calling
     
    This was done on an iPhone 6S plus with software IOS 11.3
  2. Like
    THE_DEAD_POOL got a reaction from Netduma Fraser in Cannot Receive/Send Picture Messages through the R1 (Reopened?)   
    Thanks RT Turn Clyde!!
     
    So far so good. Following your steps I have not had issues sending MMS messages. Seems you and Modbox were correct that WiFi calling was not being truly disabled!
     
    Sure is nice not having to deal with that hassle anymore. Cheers Mate!
  3. Like
    THE_DEAD_POOL got a reaction from Netduma Admin in Cannot Receive/Send Picture Messages through the R1 (Reopened?)   
    Thanks RT Turn Clyde!!
     
    So far so good. Following your steps I have not had issues sending MMS messages. Seems you and Modbox were correct that WiFi calling was not being truly disabled!
     
    Sure is nice not having to deal with that hassle anymore. Cheers Mate!
  4. Like
    THE_DEAD_POOL got a reaction from Netduma Jack in Cannot Receive/Send Picture Messages through the R1 (Reopened?)   
    Makes sense. Thanks guys for the help. 
     
    Hopefully DumaOS is released sometime this year to resolve these bugs.
  5. Like
    THE_DEAD_POOL reacted to XSXS in Netduma worth it ?   
    TBH, it is not worth $200 right now, the hardware is old and can be had for $72 with out the Netduma software which is what you are paying a premium for.  The Duma firmware is very temperamental. 
     
    I would say it is worth it if one of two things happen:
    1.  The new Duma OS comes out and fixes a lot of the bugs and makes the interface more stream line. (been waiting over a year for this)
    2.  Netduma releases a an updated router with their software on it.
     
    However even if the Duma OS is revolutionary, if you have a gigabit connection, you may have speed issues. No matter how great the software is it will be limited by the hardware.
     
    I would say the Netduma is probably worth about $150 if you are in the market for a new router.
     
    With that being said, I know of people who have Asus, Netgear routers etc who just rekt in COD so once again it will always depend how good your ISP and line quality is.
  6. Like
    THE_DEAD_POOL got a reaction from XSXS in Netduma worth it ?   
    It's worth it. Just not $200 worth it. 
     
    For me before the Netduma, I would get around 5/10 good games (fair/low lag/untouchable games).
     
    With the Netduma I tend to get about 6 or 7 good games (fair/low lag/untouchable games) out of 10 . 
     
    It does help, but you are still at the mercy of the connection quality of the players in the lobby. You can only do so much with the Netduma. You may encounter fewer WTF moments, but there will still be plenty. Ensuring your line quality is good is probably the most important.
     
    I'm sure you will see a difference, just don't expect a massive improvement in gameplay. Yes the Geo-Filter, bandwidth sliders, and hyper traffic etc are nice features, but you can still connect to crappy connections within your geo-filter range, hence ruining the gaming experience. Sliders can help with bufferbloat, but unless your saturating your connection you shouldn't worry about that. Hyper Traffic is one of the few true QoS features out there and would help if there are a lot of users on your home network. 
  7. Like
    THE_DEAD_POOL got a reaction from Alex49H in Call of duty : Florida Dedicated Server   
    I would think you could set your geo-filter only over the location of the dedi, turn ping assist off, and turn strict mode on. It may take a while for a lobby to open up, but eventually I would think you would connect to that server.
     
    I would do that to connect to a California Dedi on Black Ops 2 for the PS 3 with great success. 
  8. Like
    THE_DEAD_POOL got a reaction from XSXS in Lag Compensation Problems? (not sure what this is tbh)   
    Yeah good read. Nice to know what those actually mean.
  9. Like
    THE_DEAD_POOL reacted to XSXS in Lag Compensation Problems? (not sure what this is tbh)   
    Good stuff Modbox! Nice read!
  10. Like
    THE_DEAD_POOL reacted to iAmMoDBoX in Lag Compensation Problems? (not sure what this is tbh)   
    http://www.zcorum.com/docsis-codeword-errors-and-their-effect-on-rf-impairments/
  11. Like
    THE_DEAD_POOL got a reaction from Monzo in Lag Compensation Problems? (not sure what this is tbh)   
    I wouldn't worry about hiding the Netduma. If you run the ping plotter test with only the modem hooked up and you have packet loss or jitter issues, then the Netduma is of no concern. Take a screenshot of the ping plotter test to show the tech. Also take a screen shot of your modem levels page. You will probably have some uncorrectables on there. I believe they can test your modem as well.
     
    I think the general consesus is that either you have some issues going on with your lines or your modem has gone south. The only way to differentiate between the two will be to have a tech come out and check out the lines. Be sure to follow them around and they can show you what they're looking at. You do not want to have any ingress on any of the lines. If your lines check out good and their side of the line checks out good, I would bet your modem is bad. In which case you could look at the TP-Link TC-7610. Seems to be the best, cheapest alternative if your ISP supports it. I think it gives you the best bang for the buck at $40. I had pretty good luck with mine, but I think there's something going on with the ISP side of things again.
  12. Like
    THE_DEAD_POOL got a reaction from Monzo in Lag Compensation Problems? (not sure what this is tbh)   
    I noticed you have around 30-40k uncorrectables across each channel. When I was having line issues, there were quite a few uncorrectables across all channels. I was also seeing significant packet loss pinging Google DNS 8.8.8.8 on pingplotter. Someone may be able to correct me if I'm wrong, but I believe uncorrectables are more or less lost packets. After you reset your modem, how soon did the uncorrectables start appearing?
     
    Also have you run a ping plotter test with only the modem? If you're seeing packet loss, then I would bet its a line issue.
     
    Fortunately I've been pretty lucky with my ISP service. Here is a quick sum up of my line quality issue..
     
    1. December: Bought the house in December, started noticing issues and lag with online COD gameplay. Also pings were all over the place.
    2. January: Set up internet (50/5) and cable services with Cox. Kept my same ASUS RT-N56U router and CIsco DPQ3212 modem. Modem was split from same line has cable box in room. 
    3. February: Discovered how to check modem levels. Mine were around -10dB.
    4. March: Encountered more lag issues and assumed router was old and done for. Bought the Netduma R1. (Gameplay improved slightly)
    5. March: Downloaded ping plotter and noticed my jitter was all over the place and was seeing random, although rare, packet loss. 
    6. March: Discovered buffer bloat and noticed I could not achieve an A+ rating no matter the setting on the Netduma.
    7. April: Had ISP tech come by and check lines. Discovered tons of noise on all lines. ISP ran new lines for the house at no charge (lucky!). Modem levels improved to -6dB.
    8. April: Lag issues endured. Removed splitter for cable box and modem. Modem levels improved to -3dB. No improvement in lag.
     
    9. May: Replaced the Cisco DPQ3212 with the TP-Link TC-7610. Slight Improvement in Modem levels. Consistent A+ bufferbloat. Jitter was much improved. Pings dropped a few ms. Gameplay was off the hook. I was untouchable for about a week. The following week, the gameplay lag was out of control. Choppy gameplay and almost no hit detection. Constant insta-deaths. Ran ping plotter and noticed I was losing packets almost every few seconds. The modem level screen was showing over 20k uncorrectables every 10 minutes. By the next day I had over 1 million uncorrectables across the 8 channels. Called cox and they ran a test in which I only received 30/50 packets sent. They had a tech out the following day.
     
    Must have been a decent Tech. He checked all the new lines and noticed no issues. No noise or issues from the local tap to the house. He went ahead and tested the Cox side of the line for a good 15+ min sending 15,000 packets or so. He also mentioned the amplifier for the tap may be bad as well. From that he noticed it was on their side as he was seeing over 10% packet loss on his side. He put in a work order to have the main line repair guys look into the issue. They came out the following week and noticed that one of the main neighborhood taps/node that feeds my cul de sac tap had been run over by someone at some point. The main line going to it was leaking pretty heavily and the box was heavily damaged. He went ahead and repaired that. Modem levels improved to 0dB. Packet loss was non existant. Gameplay connection improved. Unfortunately my jitter has gotten worse and my overall connection quality has degraded over the past month, so I'm having a tech come out again to check everything out and check out that amplifier. Maybe I can convince them to put me on the least congested node.
     
    Sorry for the wall of text. Your issue sounds similar to mine which was a line issue. Hopefully you get a good tech out there that actually cares like I did. Make sure he looks at the tap and thoroughly checks his side of the line. Not just show up, run a few quick tests, and 5 minutes later he's gone.
     
    Also, if you haven't already, run a ping plotter test to either twitter.com or google.com with only the modem connected. If you're seeing packet loss on that, take a screenshot on your phone and show it to the tech. Also show them a screenshot of your modem levels with the uncorrectables. That should be proof enough that their is a line issue going on. If everything checks out good. Then I would say it's your modem. 
  13. Like
    THE_DEAD_POOL got a reaction from XSXS in Lag Compensation Problems? (not sure what this is tbh)   
    I noticed you have around 30-40k uncorrectables across each channel. When I was having line issues, there were quite a few uncorrectables across all channels. I was also seeing significant packet loss pinging Google DNS 8.8.8.8 on pingplotter. Someone may be able to correct me if I'm wrong, but I believe uncorrectables are more or less lost packets. After you reset your modem, how soon did the uncorrectables start appearing?
     
    Also have you run a ping plotter test with only the modem? If you're seeing packet loss, then I would bet its a line issue.
     
    Fortunately I've been pretty lucky with my ISP service. Here is a quick sum up of my line quality issue..
     
    1. December: Bought the house in December, started noticing issues and lag with online COD gameplay. Also pings were all over the place.
    2. January: Set up internet (50/5) and cable services with Cox. Kept my same ASUS RT-N56U router and CIsco DPQ3212 modem. Modem was split from same line has cable box in room. 
    3. February: Discovered how to check modem levels. Mine were around -10dB.
    4. March: Encountered more lag issues and assumed router was old and done for. Bought the Netduma R1. (Gameplay improved slightly)
    5. March: Downloaded ping plotter and noticed my jitter was all over the place and was seeing random, although rare, packet loss. 
    6. March: Discovered buffer bloat and noticed I could not achieve an A+ rating no matter the setting on the Netduma.
    7. April: Had ISP tech come by and check lines. Discovered tons of noise on all lines. ISP ran new lines for the house at no charge (lucky!). Modem levels improved to -6dB.
    8. April: Lag issues endured. Removed splitter for cable box and modem. Modem levels improved to -3dB. No improvement in lag.
     
    9. May: Replaced the Cisco DPQ3212 with the TP-Link TC-7610. Slight Improvement in Modem levels. Consistent A+ bufferbloat. Jitter was much improved. Pings dropped a few ms. Gameplay was off the hook. I was untouchable for about a week. The following week, the gameplay lag was out of control. Choppy gameplay and almost no hit detection. Constant insta-deaths. Ran ping plotter and noticed I was losing packets almost every few seconds. The modem level screen was showing over 20k uncorrectables every 10 minutes. By the next day I had over 1 million uncorrectables across the 8 channels. Called cox and they ran a test in which I only received 30/50 packets sent. They had a tech out the following day.
     
    Must have been a decent Tech. He checked all the new lines and noticed no issues. No noise or issues from the local tap to the house. He went ahead and tested the Cox side of the line for a good 15+ min sending 15,000 packets or so. He also mentioned the amplifier for the tap may be bad as well. From that he noticed it was on their side as he was seeing over 10% packet loss on his side. He put in a work order to have the main line repair guys look into the issue. They came out the following week and noticed that one of the main neighborhood taps/node that feeds my cul de sac tap had been run over by someone at some point. The main line going to it was leaking pretty heavily and the box was heavily damaged. He went ahead and repaired that. Modem levels improved to 0dB. Packet loss was non existant. Gameplay connection improved. Unfortunately my jitter has gotten worse and my overall connection quality has degraded over the past month, so I'm having a tech come out again to check everything out and check out that amplifier. Maybe I can convince them to put me on the least congested node.
     
    Sorry for the wall of text. Your issue sounds similar to mine which was a line issue. Hopefully you get a good tech out there that actually cares like I did. Make sure he looks at the tap and thoroughly checks his side of the line. Not just show up, run a few quick tests, and 5 minutes later he's gone.
     
    Also, if you haven't already, run a ping plotter test to either twitter.com or google.com with only the modem connected. If you're seeing packet loss on that, take a screenshot on your phone and show it to the tech. Also show them a screenshot of your modem levels with the uncorrectables. That should be proof enough that their is a line issue going on. If everything checks out good. Then I would say it's your modem. 
  14. Like
    THE_DEAD_POOL reacted to XSXS in Best Gaming Modems [Opinions]   
    THE_DEAD_POOL, on 20 Jul 2017 - 06:13 AM, said:
    I came across a Netgear CM600 for $60. It is 24x8 which would also work if your ISP supports it. So far I have not noticed much of a difference in performance between the CM600 and the TP-Link TC-7610 compatibility wise with the Netduma R1. Modem Levels, Speeds, gameplay, Netduma Features, Bufferbloat, Puma 6 test, Jitter, and Pings are pretty much identical between the two. The main difference is with the CM600, I can consistently lock in to channels in the 800hz frequency range. The TP-Link seemed to have a hard time getting out of the 900hz range. The CM600 is a bit of overkill for my current internet plan (150/10), but for the price I figured I would try it out. It is rated up to 960Mbps.
     
    The CM600 also runs the Broadcom chipset. They usually run around $100, but I got lucky on craigs and found mine for $60."
     
    I quoted another user dead pool for you
  15. Like
    THE_DEAD_POOL got a reaction from ColonicBoom in My Netduma IS a Lemon!   
    Pings are usually in the mid 20's. The Duma usually has a lower ping. Also server location such as the Google fiber test, is located in Atlanta. The ping from AZ to GA will be a little higher. Speedtest.net server pings can bounce around.  
    I did order some new cables and will be having a tech come out to check for noise and to see what can be done to improve my SNR. Those don't have anything to do with speeds though.
     
    Tests were done with:
    Speedtest.net
    Dslreports.com
    Google Fiber Speedtest
    Testmy.net (ModBox Recommendation)
    ATT Speedtest
  16. Like
    THE_DEAD_POOL got a reaction from Netduma Fraser in Slow Speeds with Netduma After Recommended Setup (Bad Unit?   
    That will work.
  17. Like
    THE_DEAD_POOL got a reaction from Monzo in Lag Compensation Problems? (not sure what this is tbh)   
    Which Modem are you using? 
     
    Also I'm assuming you have the Nighthawk set up as an Access Point correct?
     
    I would set it up as Mod Box recommended. 70% download 70% upload. Reset your distribution and input your speeds into the download and upload boxes. Have you tried out Ping Plotter? This can give you an idea of what your ping is and reveal line issues. Also take a look at your modem levels. With most modems type 192.168.100.1 into your internet browser. The login should be admin and the password either admin or password. You're going to want to make sure those are in the desirable range. Another thing you might want to look for on your Modem status page, is if you have a large amount of uncorrectables (100k+). This is a clear sign of excessive packet loss. It wouldn't hurt to have an ISP tech come out and check everything out for you. There may be line issues going on.
     
    Use the sliders to dial in your bufferbloat as well on dslreports. This may help reduce the WTF moments if you can get A+'s across the board.
     
    Hyper Traffic: Under the Device Manager screen I would try and name your devices. This makes it easier to tell what is what. Then you can select your hyper-traffic devices (consoles) and add them to one of the slots. Then for the service either select PSN or XBOX depending on whether it's a Playstation or XBOX.
     
    I sorted my line issues out, and my gameplay improved dramatically. It sounds to me like you have some line issues going on.
  18. Like
    THE_DEAD_POOL got a reaction from XSXS in Lag Compensation Problems? (not sure what this is tbh)   
    I agree. I thought it was supposed to have been released nearly a year ago. I'm dealing with my fair share of bugs that are supposed to be squashed by DumaOS. 
     
    This comment might trigger the fanboys. Watch out! 
  19. Like
    THE_DEAD_POOL reacted to Monzo in Lag Compensation Problems? (not sure what this is tbh)   
    Look, I hope to God I'm not coming off as an a******, but this update's waiting time is taking way too long with no exact reason except for "oh, we're trying to perfect it, that's why it's not out yet". Look, I love you guys and the router to an extent, but to perfect this should NOT be taking up to 2 years of production. This update has been in effect, or as an idea to your company way before we knew about it and as far as I know, it was being made in production a little after the latest update came out, which was almost 2 years ago. To perfect something like this, has I think already been made by a couple of companies (dont remember exactly who, but apparently they're doing better than you guys with this kind of idea, but I still love you and am not leaving ). The point I'm making, is that too many people are having the exact problem I'm having because we can't have what everyone else like A7 and others are getting. Everyone who owns a Duma of course isn't going to get the same results due to having different modems, connections, internet packages and cable and so on, but apparently, according to you guys, this update is supposed to fix THAT exact problem, which is why I've been so excited for two years for this release, but have been disappointed every time I get told that the release date is being extended. In my opinion, there should options to fix this problem of making everyone with my problem wait, and I think someone else has mentioned this before, but I will try to give my idea and use my words to explain it. 
     
    1. Fix a couple of the problems you guys are claiming to have at a quicker rate unless already doing so. Release a beta to everyone who owns the Duma so that we can all help test out to make this process go quicker. If a beta is released now, we can all keep the firmware, and every time you guys have a fix, update it until its perfected and make it one huge update.
     
    2. You also said that with the release of the new DumaOS, it should be a lot easier to update firmware and software and to keep us posted a lot easier, correct? Well, if that's what DumaOS does, but is still not perfected, why can't we just say "screw the minor bugs" and just release it? You guys said yourselves that Duma OS decreases the amount of time for bugs to be fixed dramatically compared to what we have now. So why aren't we doing this? Why are we forced to wait another year (which I can only imagine that we will because you've done this before) just so that new customers can't come in and lose a few in the process?
     
    I've seen people get rid of their Duma because of the amount of time it's taking to release this update, plus other companies are coming out with better ideas a lot faster, and surprisingly are near perfect compared to what we are getting here. I know people are going to tell me that they aren't leaving or aren't going to leave, but there are some that have, and that's not good. And the people who left are those who are suffering with the same problems as I am. I also feel that there are answers to these problems, but we aren't being given the right answer at all. I know that seems easier said than done, but there has to be a way to help us out in better ways if we're going to procrastinate with this update. I'm sorry if I sound like a jerk, but I feel as if others might agree with me on this in a professional matter. I love you guys, but this whole thing could be resolved if you take my advice.
     
    Either do a beta like iPhone's do where before the release of a new iOS, they update the beta frequently until it's perfected.
    or
    Release DumaOS NOW and just update frequently until perfected. it seems as if you guys are already near perfection, so what's the hold up? Does it really matter if there's a few minor bugs here and there that isn't going to heavily affect us? we're adults, I think we can handle a couple of issues here and there, but discuss it appropriately in the forums so that all Admins are informed and can resolve it.
  20. Like
    THE_DEAD_POOL got a reaction from e38BimmerFN in Best Gaming Modems [Opinions]   
    I came across a Netgear CM600 for $60. It is 24x8 which would also work if your ISP supports it. So far I have not noticed much of a difference in performance between the CM600 and the TP-Link TC-7610 compatibility wise with the Netduma R1. Modem Levels, Speeds, gameplay, Netduma Features, Bufferbloat, Puma 6 test, Jitter, and Pings are pretty much identical between the two. The main difference is with the CM600, I can consistently lock in to channels in the 800hz frequency range. The TP-Link seemed to have a hard time getting out of the 900hz range. The CM600 is a bit of overkill for my current internet plan (150/10), but for the price I figured I would try it out. It is rated up to 960Mbps.
     
    The CM600 also runs the Broadcom chipset. They usually run around $100, but I got lucky on craigs and found mine for $60. 
  21. Like
    THE_DEAD_POOL got a reaction from Netduma Fraser in Cannot Receive/Send Picture Messages through the R1 (Reopened?)   
    Makes sense. Thanks guys for the help. 
     
    Hopefully DumaOS is released sometime this year to resolve these bugs.
  22. Like
    THE_DEAD_POOL got a reaction from fuzzy clam in Best Gaming Modems [Opinions]   
    I'm running a the TP-Link TC-7610 and can say it has been a night and day difference over the Cisco DPQ3212 it replaced. Although I seem to have developed some line issues, which are now being resolved by Cox. Hopefully I can get back to beasting and feasting with the TC-7610 + R1 once these line issues are taken care of. 
×
×
  • Create New...