Jump to content
Bohemia Interactive Forums

RogueBlade

Member
 View Profile  See their activity

  • Content Count

    194

  • Joined

  • Last visited

  • Medals

Posts posted by RogueBlade

  3. Posted

    Ok well I spoke with Netgear on the phone today again. The dude is incredibly helpful and cool.

    He says the engineering department at hq have tried to replicate the issue at their California offices AND their UK offices (I'm in the UK) and failed to replicate my issue.

    So, that's unfortunate and he says maybe it has to do with the ISP, the phone line, or maybe the router model itself. He said its too bad that no one else has created support tickets like mine because he said that would REALLY help them with being able to compare the data of 2+ users with the same problem. So I really hope you create a ticket djdanny2008 :)

    So we decided to do an RMA of my router because thats last solution they have. (apart from finding someone else with the problem) We are doing the RMA to see if naybe there is a bad batch of the routers, one with a certain serial or something along those lines.

    So when the new router arrives (another DGN1000), if the problem still exists (dropping small packets) then we can be pretty sure its the router, but cannot be 100% sure until Netgear have other uses to compare data with.

  7. Posted

    Alright so I sat on the phone for an hour with a Netgear guy tonight and we talked over everything! He told me about you $able (I know your real name zomg!).

    So anyway we set up a remote viewing tool so he could see my screen and we did some ping tests of packet sizes that worked, and tests of the packet sizes that didn't and saved all the text logs and cfg txt files.

    Also took screenshots of all the routers config pages and fired them over. He's gonna send all the info over to the engineering department will get back to me!

  8. Posted

    Its like Utes island. That is pretty bad to release something that small and expect payment. Addon makers regularly make better maps for free!

    Will a map this small not make the British mini campaign really linear? I know the normal campaigns are really linear as well but it should be more of a problem here. A case of "oh we are moving down this road for the fifth time".

    Wow, you selfish pick.
    Grow up.

    Or are you the type of person who buys every DLC even those crappy Call of Duty map packs without a second thought of quality?

    I'll remind you that I am not obligated to buy from BIS it is up to them to market something to me. For 8 quid it is almost a third of the price of OA itself, is it a third of the content?

    Calling me a selfish prick made my day and gave me a good chuckle :o

    Grow up? Look at your post. Who are you to say it is 'bad to release something for the price it is'? And who are you to say it's 'small'. And wtf, how could you compare it to MW2 who's map packs are nothing but ported maps and cost more than this DLC anyway.

    No you're not obligated to buy this from BIS, no one said you are. But your crappy opinion of what makes a DLC worth while is irrelevant and pointless if you're going to word it like that.

    It's not even out and your whining about how the campaign is going to turn out. Spoiled little gamer.

  11. Posted

    Its like Utes island. That is pretty bad to release something that small and expect payment. Addon makers regularly make better maps for free!

    Will a map this small not make the British mini campaign really linear? I know the normal campaigns are really linear as well but it should be more of a problem here. A case of "oh we are moving down this road for the fifth time".

    Wow, you selfish pick.

  20. Posted

    Will try this as soon as I get home. Really it's only instructions for the latest firmware update....so I don't have much hope. This was a personal email not the tech support ticket, so hopefully I can reply to it. If you have the DGN1000, read on.

    Dear Josh,

    My name is Jay and I am following up on your support case.

    After reviewing the information that you provided, I think I have a better understanding of your issue. Here are some troubleshooting steps that I suggest you try:

    Please click on the link below and follow the steps to download and upgrade the latest firmware to the router.

    http://kb.netgear.com/app/answers/detail/a_id/15458

    NOTE: In this window you see the option "Right click and save to download" right click on it and select the option "save target as" and save it to the desktop.

    You can upgrade by using the Web interface Router Upgrade menu. Firmware upgrade should be done with the wired computer (connect your computer to any of the four LAN ports of the NETGEAR router and follow the steps to upgrade the firmware).

    1) Open Internet Explorer or any other browser and access the site: http://192.168.0.1 or http://routerlogin.com/basicsetting.htm. By default, the User Name is admin and Password is password (If you have changed the password then try with that password).

    2) Click “ROUTER UPGRADE†under MAINTENANCE on the left side of the Router page.

    3) Click Browse and locate the upgrade file for your firewall router saved in the desktop.

    4) Click Upload and Wait for the router to reboot.

    5) Once the Firmware is upgraded, we have to reset the router to Factory default settings and reconfigure it.

    Reset & reconfigure the router:

    Please reset your router by holding down the reset button for 30 seconds with a paper clip, which you could find on rear panel of the router. Now power off & power back the router.

    1) Open the browser (Internet Explorer or Netscape), access the router using http://192.168.0.1 or http://routerlogin.com/basicsetting.htm By default the User Name is admin Password is password (If you have changed the password then try with that password).

    2) Click Setup Wizard and then select your country and language and then click on "Yes".

    3) Click on "Next" in the detection window.

    4) It should give you a "PPPoA Detected" and then click next.

    5) Then under login and password type in your login/password for your ADSL account (the user name should be full like user@pipex.co.uk) and click Apply.

    6) Click on router status under maintenance and check whether you have IP address under ADSL port.

    If there is a valid IP address under ADSL port then check whether you can able to access internet.

    Please do visit http://kb.netgear.com for any technical queries regarding NETGEAR products.

    We hope that the steps provided above would help resolve the problem/case. Please feel free to contact us again if you require further assistance.

    Thanks again for choosing NETGEAR. Have a great day!

    Regards,

    Jay

    Technical Support

    NETGEAR Inc.

  22. Posted

    Dear Josh,

    My name is Jay and I am following up on your support case.

    Based on the complexity of this case, it may be appropriate for me to seek additional resources. I recommend escalating your case to the next level for further review and response and they will get back shortly.

    This message is for your information only. There is no additional action needed from you at this time. The next level agent will update the case and you will be notified.

    Again, thanks for choosing NETGEAR. We appreciate your continued patience. We will be working hard to get back to you shortly.

    Regards,

    Jay

    NETGEAR Support

    Sounds like a good thing? 0_o

  23. Posted

    Well I got a reply from NETGEAR support and the guy confirms that

    "I understand that small UDP packets of size 5-10 bytes are getting dropped while using NETGEAR DGN1000 Router."

    He asked for this info which I gave him:

    1) Do you have any firewall software's running in your computers? if yes, please disable it.

    2) Have you tried resetting and reconfiguring the NETGEAR DGN1000 Router after updating the latest firmware?

    3) Who is your internet service provider?

    4) What is the ADSL port ip address and Router firmware?

    So hoping for a useful response. I told him with my old router no such issue existed

  25. Posted · Edited by RogueBlade

    Read this thread: http://forums.bistudio.com/showthread.php?t=103247. I had reports of the DGN1000 causing this problem before, so there definitely seems to be a serious issue with this model.

    It means that your router is dropping small packets, which shouldn't be happening.

    Could you please create a support ticket at https://my.netgear.com/myNETGEAR/support.asp and refer to my ticket #12632987 in it (simply say you have the very problem I described there)? So far Netgear refused to escalate this issue to their dev team, because they want a user of this router to test a few things first. Another user that I talked to said that he talked to them on the phone, and after trying a few things they said it was the ISP's fault. However, I had another report about a user fixing this issue by using another router, so this can't really be true.

    Also, what sort of router did you have before? And are you sure you had the same problem back then?

    Ok ticket submitted. My router before hand was another modem/router in one which was the Netgear DG834G v3. Now that I think about it. When I was using that, I was playing AAS (Battle Eye) servers just fine! But I can't use the old router anymore because it is my landlords.

    So yes, despite my initial claims, this must be a router issue. What more can I do?

    Microsoft Windows [Version 6.1.7600]

    Copyright © 2009 Microsoft Corporation. All rights reserved.

    C:\Users\Josh>ping bistudio.com -l 0

    Pinging bistudio.com [81.0.236.117] with 0 bytes of data:

    Reply from 81.0.236.117: bytes=0 time=64ms TTL=49

    Reply from 81.0.236.117: bytes=0 time=64ms TTL=49

    Reply from 81.0.236.117: bytes=0 time=64ms TTL=49

    Reply from 81.0.236.117: bytes=0 time=65ms TTL=49

    Ping statistics for 81.0.236.117:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

    Minimum = 64ms, Maximum = 65ms, Average = 64ms

    C:\Users\Josh>ping bistudio.com -l 1

    Pinging bistudio.com [81.0.236.117] with 1 bytes of data:

    Reply from 81.0.236.117: bytes=1 time=66ms TTL=49

    Reply from 81.0.236.117: bytes=1 time=64ms TTL=49

    Reply from 81.0.236.117: bytes=1 time=65ms TTL=49

    Reply from 81.0.236.117: bytes=1 time=65ms TTL=49

    Ping statistics for 81.0.236.117:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

    Minimum = 64ms, Maximum = 66ms, Average = 65ms

    C:\Users\Josh>ping bistudio.com -l 2

    Pinging bistudio.com [81.0.236.117] with 2 bytes of data:

    Reply from 81.0.236.117: bytes=2 time=64ms TTL=49

    Reply from 81.0.236.117: bytes=2 time=64ms TTL=49

    Reply from 81.0.236.117: bytes=2 time=64ms TTL=49

    Reply from 81.0.236.117: bytes=2 time=65ms TTL=49

    Ping statistics for 81.0.236.117:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

    Minimum = 64ms, Maximum = 65ms, Average = 64ms

    C:\Users\Josh>ping bistudio.com -l 3

    Pinging bistudio.com [81.0.236.117] with 3 bytes of data:

    Reply from 81.0.236.117: bytes=3 time=64ms TTL=49

    Reply from 81.0.236.117: bytes=3 time=64ms TTL=49

    Reply from 81.0.236.117: bytes=3 time=64ms TTL=49

    Reply from 81.0.236.117: bytes=3 time=64ms TTL=49

    Ping statistics for 81.0.236.117:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

    Minimum = 64ms, Maximum = 64ms, Average = 64ms

    C:\Users\Josh>ping bistudio.com -l 4

    Pinging bistudio.com [81.0.236.117] with 4 bytes of data:

    Reply from 81.0.236.117: bytes=4 time=64ms TTL=49

    Reply from 81.0.236.117: bytes=4 time=64ms TTL=49

    Reply from 81.0.236.117: bytes=4 time=64ms TTL=49

    Reply from 81.0.236.117: bytes=4 time=64ms TTL=49

    Ping statistics for 81.0.236.117:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

    Minimum = 64ms, Maximum = 64ms, Average = 64ms

    C:\Users\Josh>ping bistudio.com -l 5

    Pinging bistudio.com [81.0.236.117] with 5 bytes of data:

    Request timed out.

    Request timed out.

    Request timed out.

    Request timed out.

    Ping statistics for 81.0.236.117:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:\Users\Josh>ping bistudio.com -l 6

    Pinging bistudio.com [81.0.236.117] with 6 bytes of data:

    Request timed out.

    Request timed out.

    Request timed out.

    Request timed out.

    Ping statistics for 81.0.236.117:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:\Users\Josh>ping bistudio.com -l 7

    Pinging bistudio.com [81.0.236.117] with 7 bytes of data:

    Request timed out.

    Request timed out.

    Request timed out.

    Request timed out.

    Ping statistics for 81.0.236.117:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:\Users\Josh>ping bistudio.com -l 8

    Pinging bistudio.com [81.0.236.117] with 8 bytes of data:

    Request timed out.

    Request timed out.

    Request timed out.

    Request timed out.

    Ping statistics for 81.0.236.117:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:\Users\Josh>ping bistudio.com -l 9

    Pinging bistudio.com [81.0.236.117] with 9 bytes of data:

    Request timed out.

    Request timed out.

    Request timed out.

    Request timed out.

    Ping statistics for 81.0.236.117:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:\Users\Josh>ping bistudio.com -l 10

    Pinging bistudio.com [81.0.236.117] with 10 bytes of data:

    Request timed out.

    Request timed out.

    Request timed out.

    Request timed out.

    Ping statistics for 81.0.236.117:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:\Users\Josh>

    Everything after 4 times out.

×