Fight the Lag! - with metrics

Started by Jeshin, November 17, 2011, 09:00:31 AM

Quote from: Booya on December 07, 2011, 04:06:36 PM
What does that mean? Might it be because i'm in England, UK?

Most people will have different traceroutes based on exactly that (different locations means that you go through different connections/different servers to reach your destination).  I am assuming here that perhaps the next hop that you can't reach is another server prior to reaching the VPS host we use.  I could be wrong, though...
Quote from: LauraMars on December 15, 2016, 08:17:36 PMPaint on a mustache and be a dude for a day. Stuff some melons down my shirt, cinch up a corset and pass as a girl.

With appropriate roleplay of course.

No connecting for me either, also UK

traceroute 206.72.207.140
traceroute to 206.72.207.140 (206.72.207.140), 64 hops max, 52 byte packets
1  192.168.1.1 (192.168.1.1)  1.174 ms  0.882 ms  0.855 ms
2  10.121.28.1 (10.121.28.1)  9.939 ms  7.995 ms  7.444 ms
nrwh-cam-1b-ge92.network.virginmedia.net (81.100.32.129)  18.921 ms  9.421 ms  7.364 ms
pete-core-1b-ge-013-0.network.virginmedia.net (195.182.178.217)  12.522 ms  13.165 ms  20.655 ms
popl-bb-1b-as6-0.network.virginmedia.net (212.43.163.221)  16.583 ms  20.377 ms  16.931 ms
popl-bb-1a-ae0-0.network.virginmedia.net (213.105.174.229)  17.952 ms  29.247 ms  36.878 ms
brnt-bb-1b-as4-0.network.virginmedia.net (62.255.81.238)  27.942 ms  36.509 ms  25.113 ms
brnt-tmr-1-ae5-0.network.virginmedia.net (213.105.159.50)  20.116 ms  17.422 ms  31.832 ms
telc-ic-1-as0-0.network.virginmedia.net (62.253.185.74)  19.381 ms  19.233 ms  21.394 ms
10  te1-3.ccr01.lon04.atlas.cogentco.com (130.117.15.69)  38.427 ms  19.609 ms  20.123 ms
11  te7-7.mpd02.lon01.atlas.cogentco.com (154.54.38.69)  24.942 ms
    te9-7.ccr01.lon01.atlas.cogentco.com (154.54.38.81)  34.861 ms
    te7-7.mpd02.lon01.atlas.cogentco.com (154.54.38.69)  20.557 ms
12  * te0-0-0-4.mpd21.lon13.atlas.cogentco.com (154.54.57.102)  95.858 ms
    te0-2-0-4.mpd22.lon13.atlas.cogentco.com (154.54.57.165)  98.178 ms
13  te0-6-0-3.mpd21.jfk02.atlas.cogentco.com (154.54.45.229)  94.838 ms
    te0-3-0-4.ccr22.bos01.atlas.cogentco.com (154.54.5.122)  97.470 ms
    te0-3-0-4.ccr21.bos01.atlas.cogentco.com (154.54.30.129)  101.187 ms
14  * te2-3.mpd01.jfk01.atlas.cogentco.com (154.54.24.145)  94.807 ms
    te9-1.mpd01.jfk01.atlas.cogentco.com (154.54.1.173)  96.358 ms
15  te2-3.ccr02.jfk01.atlas.cogentco.com (154.54.24.149)  99.490 ms
    te3-3.mpd01.jfk01.atlas.cogentco.com (154.54.1.210)  97.078 ms
    te2-3.ccr02.jfk01.atlas.cogentco.com (154.54.24.149)  101.414 ms
16  vl3907.na31.b017536-1.jfk01.atlas.cogentco.com (38.20.42.66)  96.804 ms
    te7-2.mag02.jfk01.atlas.cogentco.com (154.54.80.98)  96.933 ms
    te7-1.mag02.jfk01.atlas.cogentco.com (154.54.80.94)  98.210 ms
17  vl3907.na31.b017536-1.jfk01.atlas.cogentco.com (38.20.42.66)  107.226 ms
    vl3607.na31.b017536-1.jfk01.atlas.cogentco.com (38.20.42.62)  97.741 ms
    vl3907.na31.b017536-1.jfk01.atlas.cogentco.com (38.20.42.66)  102.444 ms
18  38.105.245.50 (38.105.245.50)  92.946 ms *  93.222 ms
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *

December 07, 2011, 04:39:44 PM #153 Last Edit: December 07, 2011, 04:41:58 PM by Nyr
My next-to-last hop is 206.72.207.130.  Try to tracert to that.

actually here's my tracert out of FL:


 6    29 ms    29 ms    30 ms  pos3-1.gw3.orl1.alter.net [157.130.86.145]
 7    30 ms    31 ms    30 ms  0.so-2-0-3.xl3.orl4.alter.net [152.63.81.34]
 8    58 ms    59 ms    58 ms  0.xe-8-0-0.xl1.mia19.alter.net [152.63.85.114]
 9    60 ms    58 ms    66 ms  0.xe-10-0-0.br1.mia19.alter.net [152.63.85.82]
10    68 ms    73 ms    72 ms  204.255.168.238
11    53 ms    54 ms    56 ms  ge-1-0-0.mpr1.mia1.us.above.net [64.125.30.193]

12    79 ms    80 ms    98 ms  xe-4-3-0.cr1.dca2.us.above.net [64.125.30.198]
13   114 ms   113 ms   114 ms  xe-2-2-0.cr1.lga5.us.above.net [64.125.26.98]
14    75 ms    76 ms   102 ms  xe-1-0-0.cr2.lga5.us.above.net [64.125.29.46]
15    75 ms    75 ms    76 ms  xe-1-0-1.er2.lga5.us.above.net [64.125.26.166]
16    89 ms    95 ms    75 ms  64.124.44.213.interserver.com [64.124.44.213]
17    75 ms    76 ms    76 ms  edge-12-teb1.us.as19318.net [64.20.32.78]
18    81 ms    75 ms    76 ms  openvz17.interserver.net [206.72.207.130]
19    76 ms    75 ms    77 ms  206.72.207.140

Trace complete.


Try to hit any of the server addresses between 11 and 19.
Quote from: LauraMars on December 15, 2016, 08:17:36 PMPaint on a mustache and be a dude for a day. Stuff some melons down my shirt, cinch up a corset and pass as a girl.

With appropriate roleplay of course.

I didn't try them all from 11, but the ones I tried were fine until your 18th hop:

Tracing route to openvz17.interserver.net [206.72.207.130]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    44 ms    36 ms    30 ms  10.122.220.1
  3     8 ms    29 ms     8 ms  brig-cam-1a-v109.network.virginmedia.net [80.3.66.73]
  4    28 ms     7 ms    16 ms  brig-core-1a-ge-012-0.network.virginmedia.net [195.182.178.157]
  5    10 ms    11 ms    12 ms  brig-core-2a-ae2-0.network.virginmedia.net [212.43.162.221]
  6    13 ms    11 ms    10 ms  glfd-bb-1a-ae6-0.network.virginmedia.net [213.105.159.153]
  7    75 ms    37 ms    58 ms  brnt-bb-1b-ae2-0.network.virginmedia.net [212.43.163.90]
  8    69 ms    39 ms    32 ms  brnt-tmr-1-ae5-0.network.virginmedia.net [213.105.159.50]
  9    25 ms    10 ms    18 ms  telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
10    41 ms    32 ms    32 ms  te1-3.ccr01.lon04.atlas.cogentco.com [130.117.15.69]
11    15 ms    12 ms    14 ms  te7-7.mpd02.lon01.atlas.cogentco.com [154.54.38.69]
12   106 ms    92 ms   115 ms  te0-1-0-4.ccr22.lon13.atlas.cogentco.com [154.54.57.177]
13    95 ms   113 ms    90 ms  te0-5-0-1.ccr22.jfk02.atlas.cogentco.com [154.54.30.134]
14    93 ms   112 ms    88 ms  te2-3.ccr02.jfk01.atlas.cogentco.com [154.54.24.149]
15    91 ms   102 ms   122 ms  te7-2.mag02.jfk01.atlas.cogentco.com [154.54.80.98]
16    92 ms   101 ms    91 ms  vl3907.na31.b017536-1.jfk01.atlas.cogentco.com [38.20.42.66]
17   196 ms   143 ms   102 ms  38.105.245.50
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
etc.


This is all on mac terminal just in case anyone was wondering about the format:


traceroute 206.72.207.130
traceroute to 206.72.207.130 (206.72.207.130), 64 hops max, 52 byte packets
1  192.168.1.1 (192.168.1.1)  1.474 ms  0.894 ms  0.836 ms
2  10.121.28.1 (10.121.28.1)  8.930 ms  17.228 ms  11.085 ms
nrwh-cam-1b-ge92.network.virginmedia.net (81.100.32.129)  7.737 ms  11.453 ms  9.449 ms
pete-core-1b-ge-013-0.network.virginmedia.net (195.182.178.217)  11.497 ms  30.280 ms  28.686 ms
popl-bb-1b-as6-0.network.virginmedia.net (212.43.163.221)  16.901 ms  20.538 ms  20.713 ms
popl-bb-1a-ae0-0.network.virginmedia.net (213.105.174.229)  27.455 ms  22.046 ms  17.673 ms
brnt-bb-1b-as4-0.network.virginmedia.net (62.255.81.238)  19.438 ms  35.132 ms  19.911 ms
brnt-tmr-1-ae5-0.network.virginmedia.net (213.105.159.50)  20.561 ms  20.777 ms  98.868 ms
telc-ic-1-as0-0.network.virginmedia.net (62.253.185.74)  47.724 ms  25.558 ms  20.655 ms
10  te1-3.ccr01.lon04.atlas.cogentco.com (130.117.15.69)  22.233 ms  25.643 ms  20.478 ms
11  te9-7.ccr01.lon01.atlas.cogentco.com (154.54.38.81)  32.576 ms
    te7-7.mpd02.lon01.atlas.cogentco.com (154.54.38.69)  40.286 ms
    te9-7.ccr01.lon01.atlas.cogentco.com (154.54.38.81)  37.467 ms
12  te0-0-0-4.ccr21.lon13.atlas.cogentco.com (154.54.57.110)  102.254 ms
    te0-1-0-4.ccr22.lon13.atlas.cogentco.com (154.54.57.177)  99.715 ms
    te0-0-0-4.ccr21.lon13.atlas.cogentco.com (154.54.57.110)  98.375 ms
13  te0-1-0-4.ccr22.bos01.atlas.cogentco.com (130.117.0.185)  112.147 ms
    te0-0-0-4.ccr21.bos01.atlas.cogentco.com (154.54.5.161)  98.578 ms
    te0-5-0-1.ccr22.jfk02.atlas.cogentco.com (154.54.30.134)  121.557 ms
14  te9-1.ccr02.jfk01.atlas.cogentco.com (154.54.40.33)  97.759 ms
    te0-0-0-3.ccr22.jfk02.atlas.cogentco.com (154.54.6.10)  100.625 ms
    te9-8.ccr02.jfk01.atlas.cogentco.com (154.54.40.37)  97.676 ms
15  te7-2.mag01.jfk01.atlas.cogentco.com (154.54.80.90)  106.714 ms
    te9-8.ccr02.jfk01.atlas.cogentco.com (154.54.40.37)  106.618 ms
    te2-3.mpd01.jfk01.atlas.cogentco.com (154.54.24.145)  99.356 ms
16  te7-2.mag02.jfk01.atlas.cogentco.com (154.54.80.98)  99.565 ms
    vl3907.na31.b017536-1.jfk01.atlas.cogentco.com (38.20.42.66)  96.032 ms
    vl3607.na31.b017536-1.jfk01.atlas.cogentco.com (38.20.42.62)  97.076 ms
17  vl3907.na31.b017536-1.jfk01.atlas.cogentco.com (38.20.42.66)  99.658 ms  121.189 ms
    38.105.245.50 (38.105.245.50)  90.930 ms
18  * 38.105.245.50 (38.105.245.50)  99.227 ms  104.904 ms
19  * * *
20  * * *
21  *

December 07, 2011, 11:50:48 PM #156 Last Edit: December 07, 2011, 11:55:11 PM by DustMight
100% loss over here.  Could give ya' a tracert, doubt it will be more helpful than what you've got.
(Vermont, btw)

Ah, here it is:
Tracing route to 206.72.207.140 over a maximum of 30 hops

  1     2 ms     1 ms    <1 ms  10.0.0.1
  2     1 ms     1 ms    <1 ms  <supersecret>
  3    10 ms     9 ms    10 ms  Springfield-NPEG1-2.vermontel.net [216.66.108.198]
  4    10 ms    10 ms    10 ms  vtelinet-216-66-108-206.vermontel.net [216.66.108.206]
  5    10 ms    10 ms     9 ms  vtelinet-216-66-108-10.vermontel.net [216.66.108.10]
  6    14 ms    15 ms    14 ms  vtelinet-216-66-105-18.vermontel.net [216.66.105.18]
  7    15 ms    13 ms    14 ms  te0-6-0-5.ccr21.bos01.atlas.cogentco.com [38.99.222.137]
  8    20 ms    19 ms    19 ms  te0-2-0-1.mpd22.jfk02.atlas.cogentco.com [154.54.44.21]
  9    20 ms    21 ms    20 ms  te3-3.mpd01.jfk01.atlas.cogentco.com [154.54.1.210]
10    20 ms    20 ms    20 ms  te7-1.mag01.jfk01.atlas.cogentco.com [154.54.80.86]
11    21 ms    20 ms    22 ms  vl3607.na31.b017536-1.jfk01.atlas.cogentco.com [38.20.42.62]
12    20 ms    20 ms    19 ms 38.105.245.50
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *

Same server as Spoon.






Tracing route to 206.72.207.140 over a maximum of 30 hops

 

  3     *     1167 ms  1220 ms  mdr-fid-int.akbr5.global-gateway.net.nz [202.37.
244.222]
  4    43 ms    43 ms    44 ms  ae4-10.akbr5.global-gateway.net.nz [202.37.244.2
21]
  5    43 ms    44 ms    43 ms  ae1-2.akbr4.global-gateway.net.nz [202.50.232.77
]
  6    44 ms    43 ms    44 ms  ae1-10.tkbr9.global-gateway.net.nz [202.50.232.3
7]
  7   170 ms   168 ms   168 ms  ae2-3.labr5.global-gateway.net.nz [203.96.120.14
2]
  8   170 ms   167 ms   199 ms  ae0-3.lebr6.global-gateway.net.nz [203.96.120.86
]
  9   170 ms   168 ms   168 ms  205.158.79.141.ptr.us.xo.net [205.158.79.141]
10   168 ms   199 ms   167 ms  te1-0-0d0.cir1.la3-ca.us.xo.net [207.88.15.29]
11   173 ms   223 ms   170 ms  207.88.14.217.ptr.us.xo.net [207.88.14.217]
12   242 ms   243 ms   248 ms  vb15.rar3.dallas-tx.us.xo.net [207.88.12.45]
13   281 ms   276 ms   251 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]

14   248 ms   252 ms   251 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.1
2.10]
15   240 ms   262 ms   240 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
16   241 ms   240 ms   241 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
17   240 ms   239 ms   238 ms  207.239.51.86
18   239 ms   238 ms   239 ms  edge-12-teb1.us.as19318.net [64.20.32.78]
19   241 ms   270 ms   238 ms  openvz17.interserver.net [206.72.207.130]
20   239 ms   238 ms   238 ms  206.72.207.140

Trace complete.

Well this looks like it's getting there?
But I'm not...


traceroute to 206.72.207.140 (206.72.207.140), 30 hops max, 60 byte packets
1  unknown (192.168.1.1)  13.047 ms  14.064 ms  14.045 ms
2  10.229.64.1 (10.229.64.1)  40.562 ms  40.562 ms  40.542 ms
network-024-029-002-149.cinci.rr.com (24.29.2.149)  40.523 ms  40.504 ms  40.539 ms
tge8-1-1.tr00.clmkohpe.mwrtn.rr.com (65.25.137.225)  40.517 ms  40.505 ms  40.486 ms
ae-4-0.cr0.chi30.tbone.rr.com (66.109.6.68)  51.348 ms  51.335 ms  51.313 ms
6  107.14.17.147 (107.14.17.147)  51.292 ms ae-1-0.pr0.chi10.tbone.rr.com (66.109.6.155)  51.709 ms  73.888 ms
216.156.72.157.ptr.us.xo.net (216.156.72.157)  73.822 ms 216.156.72.133.ptr.us.xo.net (216.156.72.133)  99.321 ms  99.314 ms
207.88.14.201.ptr.us.xo.net (207.88.14.201)  73.799 ms  74.891 ms  74.873 ms
ae0d0.mcr1.nyc-ny.us.xo.net (216.156.0.18)  73.719 ms  73.702 ms  73.737 ms
10  207.239.51.86 (207.239.51.86)  99.158 ms  77.086 ms  77.063 ms
11  edge-12-teb1.us.as19318.net (64.20.32.78)  77.057 ms  77.021 ms  77.016 ms
12  openvz17.interserver.net (206.72.207.130)  72.117 ms  72.160 ms  72.018 ms
13  206.72.207.140 (206.72.207.140)  72.033 ms !X  72.029 ms !X  72.101 ms !X


Same thing?
Fredd-
i love being a nobles health points

DNS is working for me now.

What happens when you try to connect, and what client are you trying to connect with?
Quote from: LauraMars on December 15, 2016, 08:17:36 PMPaint on a mustache and be a dude for a day. Stuff some melons down my shirt, cinch up a corset and pass as a girl.

With appropriate roleplay of course.

Tried to connect with Mushclient, doesn't work. I could connect through this though: http://www.mudconnect.com/fmud/

Also can't access the homepage. DNS is ginka.armageddon.org right?

Tracing route to ginka.armageddon.org [206.72.207.140]
over a maximum of 30 hops:

  1     3 ms     1 ms     1 ms  192.168.1.1
  2     6 ms     7 ms    19 ms  10.122.220.1
  3     8 ms     8 ms     8 ms  brig-cam-1b-v109.network.virginmedia.net [80.3.66.201]
  4    23 ms    13 ms    10 ms  brig-core-1b-ge-012-0.network.virginmedia.net[195.182.178.161]
  5     7 ms     9 ms     9 ms  brig-core-2b-ae2-0.network.virginmedia.net [212.43.162.225]
  6    13 ms    12 ms    12 ms  popl-bb-1b-ae14-0.network.virginmedia.net [213.105.159.157]
  7    11 ms    11 ms    11 ms  popl-bb-1a-ae0-0.network.virginmedia.net [213.105.174.229]
  8    11 ms    15 ms    11 ms  brnt-bb-1b-as4-0.network.virginmedia.net [62.255.81.238]
  9    35 ms    11 ms    11 ms  brnt-tmr-1-ae5-0.network.virginmedia.net [213.105.159.50]
10    24 ms    12 ms    12 ms  telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
11    11 ms    12 ms    13 ms  te1-3.ccr01.lon04.atlas.cogentco.com [130.117.15.69]
12    12 ms    12 ms    12 ms  te7-7.mpd02.lon01.atlas.cogentco.com [154.54.38.69]
13    89 ms   105 ms    88 ms  te0-2-0-4.mpd22.lon13.atlas.cogentco.com [154.54.57.165]
14    89 ms    88 ms    89 ms  te0-2-0-4.ccr22.bos01.atlas.cogentco.com [154.54.43.57]
15   100 ms   102 ms    98 ms  te0-0-0-3.ccr22.jfk02.atlas.cogentco.com [154.54.6.10]
16   108 ms    91 ms    89 ms  te2-3.ccr02.jfk01.atlas.cogentco.com [154.54.24.149]
17    93 ms    96 ms    91 ms  te7-2.mag02.jfk01.atlas.cogentco.com [154.54.80.98]
18    90 ms    90 ms   106 ms  vl3907.na31.b017536-1.jfk01.atlas.cogentco.com [38.20.42.66]
19    87 ms    99 ms    92 ms  38.105.245.50
20     *        *        *     Request timed out.
21     *        *        *     Request timed out.
etc.

Trace complete.

December 08, 2011, 09:22:09 AM #161 Last Edit: December 08, 2011, 09:34:43 AM by DustMight
Quote from: Booya on December 08, 2011, 09:09:53 AM
...stuff...

Same here.  Exactly, down to the IP where everything is dying.

Update at 0903 EST - unable to connect via mudconnector now also.  Poor character is link dead! 

We are engaging in discussion with the ISP that is having issues routing to our new IP.
Quote from: LauraMars on December 15, 2016, 08:17:36 PMPaint on a mustache and be a dude for a day. Stuff some melons down my shirt, cinch up a corset and pass as a girl.

With appropriate roleplay of course.

Getting 100% pings back here in VT.  FYI.
Morg and team - you are all great.  Considering, especially, you are working for free!

Yup, working for me now too  :)

Here's a tracert just for the hell of it:

Tracing route to 206.72.207.140 over a maximum of 30 hops

  1     3 ms     1 ms     1 ms  192.168.1.1
  2     7 ms     8 ms    41 ms  10.122.220.1
  3     9 ms    27 ms    18 ms  brig-cam-1b-v109.network.virginmedia.net [80.3.66.201]
  4    38 ms    23 ms     7 ms  brig-core-1b-ge-012-0.network.virginmedia.net [195.182.178.161]
  5    38 ms    11 ms    19 ms  brig-core-2b-ae2-0.network.virginmedia.net [212.43.162.225]
  6    37 ms    11 ms    12 ms  popl-bb-1b-ae14-0.network.virginmedia.net [213.105.159.157]
  7    90 ms    10 ms    29 ms  popl-bb-1a-ae0-0.network.virginmedia.net [213.105.174.229]
  8    15 ms    15 ms    51 ms  brnt-bb-1b-as4-0.network.virginmedia.net [62.255.81.238]
  9    38 ms    11 ms    11 ms  brnt-tmr-1-ae5-0.network.virginmedia.net [213.105.159.50]
10    37 ms    13 ms    35 ms  telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
11    33 ms    21 ms    13 ms  te1-3.ccr01.lon04.atlas.cogentco.com [130.117.15.69]
12     *       34 ms    14 ms  te7-7.mpd02.lon01.atlas.cogentco.com [154.54.38.69]
13    89 ms    90 ms    90 ms  te0-2-0-4.mpd22.lon13.atlas.cogentco.com [154.54.57.165]
14    90 ms    91 ms    95 ms  te0-2-0-4.ccr22.bos01.atlas.cogentco.com [154.54.43.57]
15   102 ms   100 ms   122 ms  te0-0-0-3.ccr22.jfk02.atlas.cogentco.com [154.54.6.10]
16    94 ms   102 ms   106 ms  te2-3.ccr02.jfk01.atlas.cogentco.com [154.54.24.149]
17   111 ms    96 ms    92 ms  te7-2.mag02.jfk01.atlas.cogentco.com [154.54.80.98]
18   106 ms   110 ms   103 ms  vl3907.na31.b017536-1.jfk01.atlas.cogentco.com [38.20.42.66]
19   101 ms    87 ms   111 ms  38.105.245.50
20    99 ms   113 ms    91 ms  vl569.cr2.teb1.us.as19318.net [64.20.32.181]
21   100 ms    89 ms    93 ms  64.20.32.8
22    93 ms    86 ms    90 ms  vl521.cr1.teb1.us.as19318.net [64.20.32.1]
23   100 ms    86 ms    87 ms  edge-12-teb1.us.as19318.net [64.20.32.78]
24    95 ms    97 ms    87 ms  openvz17.interserver.net [206.72.207.130]
25    87 ms   108 ms    95 ms  206.72.207.140

Thanks guys.

Our provider has fixed the issue.  Thank you ALL for your willingness to help sort this out.
Morgenes

Producer
Armageddon Staff


Quote from: Nyr on December 08, 2011, 08:33:14 AM
DNS is working for me now.

What happens when you try to connect, and what client are you trying to connect with?

KildClient and hitting a performing a SSL handshake.
Fredd-
i love being a nobles health points

I can connect with Mudlet, but not with KClient.
Fredd-
i love being a nobles health points

Quote from: Barsook on December 08, 2011, 07:36:28 PM
Quote from: Nyr on December 08, 2011, 08:33:14 AM
DNS is working for me now.

What happens when you try to connect, and what client are you trying to connect with?

KildClient and hitting a performing a SSL handshake.

Your telnet client is trying to work over SSL?  ???
Quote from: nessalin on July 11, 2016, 02:48:32 PM
Trunk
hidden by 'body/torso'
hides nipples

Dunno, I think that's how KClient is programed.

(To staff: I think this bit of topic needs to be split and made into another in Ask the Players -B)
Fredd-
i love being a nobles health points

Arm 1 does not work with SSL.
Morgenes

Producer
Armageddon Staff

I figured.  I dunno what's the problem.  I just switched to Mudlet and I will stay on that one.
Fredd-
i love being a nobles health points

If you're having lag, remember. Metrics.