latency of connection monitoring
-
Your wan connection measures the latency to your gateway out of the box, or any other monitor IP you might want to use..
-
Thank you, it is for my em2. I do not know where the Xbox is connecting but i have latency issues with it despite an open NAT. Only the box on that Ethernet card.
So I wanted to find out what IPs is the game using and what is my real latency for it.... -
Latency to where your game is going to be is going to be different than what the latency to your gateway is.
Latency on your lan, ie from your xbox to pfsense should be in less than 1 ms.. Is a lan - if your wifi it could be a bit higher - problem with wifi is it normally has a lot of jitter, etc.
Shouldn't your game your playing tell you what it is showing for latency?
Ping pfsense from some device on your network. What does it answer back with for time?
PING 192.168.3.253 (192.168.3.253) 56(84) bytes of data. 64 bytes from 192.168.3.253: icmp_seq=1 ttl=64 time=0.433 ms 64 bytes from 192.168.3.253: icmp_seq=2 ttl=64 time=0.419 ms 64 bytes from 192.168.3.253: icmp_seq=3 ttl=64 time=0.409 ms 64 bytes from 192.168.3.253: icmp_seq=4 ttl=64 time=0.455 ms 64 bytes from 192.168.3.253: icmp_seq=5 ttl=64 time=0.406 ms 64 bytes from 192.168.3.253: icmp_seq=6 ttl=64 time=0.403 ms ^C --- 192.168.3.253 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5225ms rtt min/avg/max/mdev = 0.403/0.420/0.455/0.032 msSo latency to pfsense is less than .5 ms...
-
Yrs the game tells me, however only if i pull up a menu while in multiplayer... it's BO4. I suspect, however there to be quite a bit of variation and i would be interested in finding out exactly when i suffer form it more.
The box tells me it's 25/30ms. but at times i catch it with over 400ms latency, Are bursts of it. -
What does the quality graph show you for latency to your gateway - does it fluctuate a lot?
If you saturate your line that latency can for sure go up.. Is your xbox wireless.. LIke I said jitter on wireless can be high..
Once the packet leaves pfsense - how long it takes to get to answer depends on a whole lot of shit... The only thing you can do to control latency locally is going is to make sure your local network is not the problem..
-
here is the graph. I do not use wireless. I prefer wired.
PING 172.16.1.1 (172.16.1.1): 56 data bytes
64 bytes from 172.16.1.1: icmp_seq=0 ttl=64 time=0.047 ms
64 bytes from 172.16.1.1: icmp_seq=1 ttl=64 time=0.025 ms
64 bytes from 172.16.1.1: icmp_seq=2 ttl=64 time=0.031 ms
64 bytes from 172.16.1.1: icmp_seq=3 ttl=64 time=0.022 ms
64 bytes from 172.16.1.1: icmp_seq=4 ttl=64 time=0.021 ms
64 bytes from 172.16.1.1: icmp_seq=5 ttl=64 time=0.022 ms
64 bytes from 172.16.1.1: icmp_seq=6 ttl=64 time=0.028 ms
64 bytes from 172.16.1.1: icmp_seq=7 ttl=64 time=0.026 ms
64 bytes from 172.16.1.1: icmp_seq=8 ttl=64 time=0.022 ms
64 bytes from 172.16.1.1: icmp_seq=9 ttl=64 time=0.019 ms -
.02 to .04 ms??
WTF dude are you running? Never seen even lan ping times that low..
0.00003 seconds... Come on...
Are you pinging the boxes own IP? That is not really a test of network latency..
That is pfsense pinging itself.. Sure ok if that was high then something major wrong.. But that doesn't tell you how long it takes to get from pfsense to where your going and back ;) -
yes. what should i ping? The problem is i do nto know which is the server i am connecting too...
That is why i wanted a monitoring tool so that i can check what the box connects to.
LOL, my bad, i am a bit unprepared. . . -
Ping the IP of the game server, ping pfsense IP from a device ON your network.. Not pfsense pinging itself ;)
Ping your isp gateway from device on your network... That would show you if pfsense slowing you down..
-
PING google.com (172.217.0.14): 56 data bytes
64 bytes from 172.217.0.14: icmp_seq=0 ttl=56 time=12.121 ms
64 bytes from 172.217.0.14: icmp_seq=1 ttl=56 time=13.553 ms
64 bytes from 172.217.0.14: icmp_seq=2 ttl=56 time=11.940 ms
64 bytes from 172.217.0.14: icmp_seq=3 ttl=56 time=12.815 ms
64 bytes from 172.217.0.14: icmp_seq=4 ttl=56 time=11.876 ms
64 bytes from 172.217.0.14: icmp_seq=5 ttl=56 time=11.871 ms
64 bytes from 172.217.0.14: icmp_seq=6 ttl=56 time=11.564 ms
64 bytes from 172.217.0.14: icmp_seq=7 ttl=56 time=14.100 ms
64 bytes from 172.217.0.14: icmp_seq=8 ttl=56 time=13.572 ms
64 bytes from 172.217.0.14: icmp_seq=9 ttl=56 time=12.026 ms -
Yeah that looks pretty typical.. and not bad..
That is some IP on the internet - is that your game server your playing on... That is pretty good to be honest..
That is a google IP ;)
Here is that IP from me
PING 172.217.0.14 (172.217.0.14) 56(84) bytes of data. 64 bytes from 172.217.0.14: icmp_seq=1 ttl=53 time=13.4 ms 64 bytes from 172.217.0.14: icmp_seq=2 ttl=53 time=12.0 ms 64 bytes from 172.217.0.14: icmp_seq=3 ttl=53 time=13.0 ms 64 bytes from 172.217.0.14: icmp_seq=4 ttl=53 time=11.5 ms 64 bytes from 172.217.0.14: icmp_seq=5 ttl=53 time=12.5 ms 64 bytes from 172.217.0.14: icmp_seq=6 ttl=53 time=12.9 ms 64 bytes from 172.217.0.14: icmp_seq=7 ttl=53 time=11.4 ms 64 bytes from 172.217.0.14: icmp_seq=8 ttl=53 time=10.6 ms 64 bytes from 172.217.0.14: icmp_seq=9 ttl=53 time=15.0 ms 64 bytes from 172.217.0.14: icmp_seq=10 ttl=53 time=13.7 ms 64 bytes from 172.217.0.14: icmp_seq=11 ttl=53 time=12.0 ms 64 bytes from 172.217.0.14: icmp_seq=12 ttl=53 time=11.4 ms ^C --- 172.217.0.14 ping statistics --- 12 packets transmitted, 12 received, 0% packet loss, time 11016ms rtt min/avg/max/mdev = 10.667/12.495/15.031/1.167 ms -
no, i pinged google. I do not know the address of the server i play on, how can i find that out?
-
look in the game.. What is the FQDN of it - how do you connect to it? Look in pfsense for the connection to the port you use int he state table, etc.
-
the xbox does not tell me where i am connected to unfortunately, i have to use PfSense for it, and i am not sure i know how....
Everything in Xbox is handled behind the hood. I just launch the game and the multplayer part is activated by default. I select matchmaking and the box handles the deal... but i fear that at times i may be connected quite far away, and that impacts a bit how the game plays. -
So do you know what port(s) the game uses? Pretty sure you could look it up for firewall for the game... Then look in your state table for destination IPs going to those port(s)
-
Sure,
TCP: 53, 80, 3074
UDP: 53, 88, 500, 3074, 3075, 3544, 4500 -
Yeah some of those are BS.. 53 and 88..
But ok look for some sates in your state table for say 3074 while playing the game..
-
Here are some,
185.34.107.128:3074 outgoing
184.155.109.165:3074 incoming
99.45.180.232:3074 incomingPlus these
172.16.1.10:3074 -> 13.89.46.200:3544
13.89.46.201:3544 -> 172.16.1.10:3074Quite a few states have around 10 packets or just over it. some states have kbps.
-
Great then ping those - what is the latency..
-
Like most console games it's likely using p2p for multiplayer, which means one of the players is also the host. So latency will always vary, based on who is hosting the match and how their network holds up/is used. So if your connection is fine there is not much more you can do.
