1 |
[quote]
|
1 |
[quote]
|
2 |
try to ping yourself
|
2 |
try to ping yourself
|
3 |
ping 127.0.0.1
|
3 |
ping 127.0.0.1
|
4 |
if u get good response it isn't zk
|
4 |
if u get good response it isn't zk
|
5 |
[/quote]
|
5 |
[/quote]
|
6 |
\n
|
6 |
\n
|
7 |
wat
|
7 |
wat
|
8 |
\n
|
8 |
\n
|
9 |
This will return <1ms for any machine/OS from the last 20 years (probably more), completely useless.
|
9 |
This will return <1ms for any machine/OS from the last 20 years (probably more), completely useless.
|
10 |
\n
|
10 |
\n
|
11 |
Slightly better to try
|
11 |
Slightly better to try
|
12 |
\n
|
12 |
\n
|
13 |
ping zero-k.info
|
13 |
ping zero-k.info
|
14 |
\n
|
14 |
\n
|
15 |
But still basically useless for debugging this. For reference, I get ~150ms roundtrips even with transoceanic lag.
|
15 |
But still basically useless for debugging this. For reference, I get ~150ms roundtrips even with transoceanic lag.
|
16 |
\n
|
16 |
\n
|
17 |
The
most
important
fact
in
this
case
is
that
Princey
is
the
only
UK
person
appearing
to
have
this
problem.
This
indicates
that
Princey
(
or
his
rig/connection/ISP/torrent)
is
responsible
for
any
perceived
lag.
|
17 |
The
most
important
fact
in
this
case
is
that
Princey
is
the
only
UK
person
appearing
to
have
this
problem.
This
indicates
that
Princey
(
or
his
rig/connection/ISP/torrent/malware)
is
responsible
for
any
perceived
lag.
|