Search the Community
Showing results for tags 'packet'.
Found 15 results
-
Hi, I have the following packet trace generated from wireshark. Using pandas and matplotlib, I have to make an explanation if the packet arrival rate is poisson or not. Can someone please give a descriptive insight about this?
-
Hello, I am having strange issue since I replaced my old laggy router. Right now im owning TP-Link Archer C5. It is connected via rj45 cat. 5E to my PC. Problem is when I am playing / using teamspeak once an hour or two im getting like 1-2 seconds packet loss or insane ping jump. When im pinging my default gateway it shows almost always 1ms or <1ms but after hour of pinging it shows one that has 11-12ms latency I have no idea how to fix this issue, any help :P?
-
Will using a seperate modem on my network lead to more or less packet loss? Provided that both the router and modem are of the same performance.
-
Does anyone know of a working linux driver to achieve packet injection with alfa awus036ach card? I've searched high and low and come up empty.
-
So just recently I've ran into a bit of a networking problem. I'm an avid Heroes of the Storm player so bear with me. While playing this week I suffered from disconnections and huge latency spikes, which isn't really anything new. However, now the problems are more repetitive. So upon noticing this I decided to run a ping test. The exact command I entered into cmd was "ping www.google.com -n 1000". This test gave me the following statistics: Packets: Sent = 1000, Received = 876, Lost = 124 (12% loss), Approximate round trip times in milli-seconds: Minimum = 38ms, Maximum = 3938ms, Average = 346 ms The average actually surprises me, often while watching the ping test I would see the latency jump to over 1000ms. The 12% packet loss is new, when I would run this test just a week ago I would have 0% packet loss. Recently in Wisconsin, we've had very strong storms, I don't know if I should attribute the packet loss to these storms? Would this community suggest I call my ISP and complain? Just earlier this week a family on the other side of the street lost a tree that cut just their own cable/internet/phone line. They had it replaced just the day after, could this have created some sort of interference? Being the curious person I am, I decided to run the same cmd command on a computer that is close enough to be physically connected to the router via an ethernet cable, as my main computer connects over Wi-Fi and at least at this point in time a physical connection is not possible. This computer offered completely different results: 0% packet loss, average = 38ms, minimum = 37ms, maximum = 50 ms. I understand that the BEST result would be for me to just buy a long enough ethernet cable to physically connect my computer to the router. However, I would still like to know why this problem just started now, when before my average ms for latency was around 45ms with 0% packet loss. In my case would a Wi-Fi extender be a good option?
-
Just for curious, is these data shown of WiFi Good for gaming? 32 Bytes of data: Ping 192.168.0.1 (Using 32 Bytes of data): Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time=1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time=1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time=1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time=1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time=1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time=1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time=1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time=1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time=2ms TTL=64 Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64 Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64 192.168.0.1 的 Ping Stats Data: Packets: Sent = 24，Received = 24, Lost = 0 (0% Lost)， Average Time (miliseconds): Minimum = 0ms，Maximum = 2ms，Avg. = 0ms Control-C 10000 Bytes of data Ping 192.168.0.1 (Used 10000 Bytesof data): Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=4ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=5ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=8ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=86ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=4ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=7ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=8ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=4ms TTL=64 Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64 192.168.0.1 的 Ping Static: Packets: Sent = 35，Received = 35, Lost = 0 (0% Lost)， Average Time (Miliseconds): Minimum = 2ms，Maximum = 86ms，Average = 5ms Control-C 65500 Bytes: Ping 192.168.0.1 (Used 65500 Bytes的Data): Return from 192.168.0.1: Bytes=65500 Time=15ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=42ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=28ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=16ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=19ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=37ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=54ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=51ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=17ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=30ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=19ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=33ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=14ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=10ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=11ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=15ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=13ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=10ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=13ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=21ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=10ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=10ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=10ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=46ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=11ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=11ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=16ms TTL=64 Return from 192.168.0.1: Bytes=65500 Time=11ms TTL=64 192.168.0.1 的 Ping 統計資料: Packets: Sent = 28，Recieved = 28, Lost = 0 (0% Lost)， Average Time(Miliseconds): Minimum = 10ms，Maximum = 54ms，Average = 21ms Control-C Are these good? Because I know that Ethernet will be <1 ms in anyways between Client and Server BTW the wifi is over 40Mhz, channel 44 and its away like 3.5 metres.
-
Hello, recently I've been experiencing latency issues with regards to watching streams and playing games. Gave my ISP a call and they basically said there is nothing they can do to solve this- they even told me to upgrade my package to "try" and fix it. Anyways, I stumbled upon my modem's 'system log' where I see entries like this: 2018-12-28 17:36:29.00 [DOS]UDP Packet - Source:192.168.0.3,2007 Destination:192.168.0.255,2007. Am I getting DoS'd or is this normal? Any help or general information on what this means is appreciated.
-
Hi, so my internet has always been bad but this keeps happening. I always ping google to see how the internet is doing today, but this won't stop happening. We have had 4 different routers, this is the only one this happens to. I am plugged into the router via ethernet and when I plug directly into the modem, ping is completely fine; consistently under 100ms and no packet loss at all. I've gone through many cables so I'm wondering what the problem is. I do reset the modem to try to fix it but it fixes it usually for about 30 seconds, then back to being awful. My current fix right now is factory resetting the router every time, this seems to fix it for a day, but I want a more permanent fix.
-
hello guys i have a few questions about my internet 1) is packet loss and internet speed related? 2) if i have the internet on full load i.e. i m using full available bandwidth will packet loss occur on another device or same 3) is it necessary that i will have packet loss over wireless connection rather than wired. 4) if i get loss on wireless what kind of loss will that be (packet loss or speed loss or something else )?? my ISP is trying to dodge the issue i need something to prove my point of having packet loss.
-
I need a usb wifi adapter that can di packet capture, $30 at max, prefer it to come with an extension
-
I'm looking for a software that will be able to tell me the percentage of packet loss my network is experiencing.
-
As the title say i got super high ping(usually about 90ms but i got spikes from 1000 to 4000) and packet loss (spikes from 1% to 50%) playing dota 2 for about 2 weeks today... so as i saw the absurde high ping and packet loss i contacted my isp and told them, they said that they are only resposable for internet browsing and not for games... i don't know what to do... i tried to ping trought cmd the servers i usually connect to for about 2 hours and i got average ping 39(wich seems strange) max ping 696(......) and 8% packet loss; the problem is i cannot change my isp cause my isp have all the country internet under his propriety so even if i change isp i would still use their cables... anyone got some tips to try to resolve my problem ? i don't know if here is the right forum's session so let me know thx
-
Hello to everyone! I hope You are having a great day/night! So, regarding my problem, I have searched hours for now and I simply can't find a solution relevant to my situation, so any help will be Highly Appreciated! I recently got a switch, and used my old PC as a file/movie server. I also want to be able to turn it on from shut down remotely, via Magic Packet. The way I have everything set up right now goes like this: The Modem (which is also a router), and then the switch is connected to that modem (Also I forgot to mention, it's an unmanageable switch), and then my server connected to the switch. Since the switch is unmanageable, the IP addresses given to all the devices connected to the switch are basically controlled and given by The Modem/Router. Now, I also have a wireless router (with stronger signal) connected to that same switch, and the goal here is to send a magic packet from that second router to the server connected one level above. The Modem/Router is giving addresses 192.168.100.XXX to the devices connected to the switch, and so the file/movie server PC is 192.168.100.77 (Static IP). The second router connected to that same switch gives out IP addresses 192.168.2.XXX. However, the problem here seems that a Magic Packet cannot pass through that router to the switch, and hence the File/Movie server can't be turned on. This is not the case when I am connected to the Modem/Router, then the Wake-On-LAN works, but if it's possible, I would really like to be able to turn it on when I'm connected to the second Router (higher wireless signal). In addition, connecting the File/Movie server to the second router is also not an option for me due to transfer speed reasons. :\ Any help would be really much appreciated, because I have been stuck on this for a while now and I can't seem to figure it out. Looking forward to all of Your replies! Thank You in Advance! Have a nice Day/Night!
-
Hello PC enthusiast community! It all started yesterday when i started playing battlefield and noticed that i was getting significant packet loss while playing. I did not change any settings to anything, all while still getting great up / down speeds. Any input would be greatly appreciated, and thank you in advanced! Your fellow PC enthusiast, MyCampGround
-
Little bit of info: I'm a total networking noob and know nothing but the basics like how to get the not so glorious pc masterrace xbox360 work on an open NAT type while playing MW2 online and how to setup a modem for a single user. So don't rip me into shreds if I use the wrong terminology =p Rello ppl! So I've had some packet loss time to time in cs go, but earlier it has fixed itself. Now lately it's been on and off every week and I'm about to shove 2 liter coke bottle up my ISP's ass if I can't find a solution to this problem. The packet loss doesn't only limit to cs go as I open cmd.exe and type in ping -n 200 ping.funet.fi and after it has completed that command it shows I have around 2% packet loss (in-game around 1-7%, depending whether 64- or 128-tick). So I'm asking you, the masters of wire dungeons, (also known as back of the living room, behind the sofa where the modem and the router lay at on big pile of wires) do you have any ideas/tips how I could get packet loss to 0 as I've had a really nice growth sprint when it comes to cs rank and now is not the time to take breaks on gaming....
