[nznog] Re: routing problem?

2022-05-11 Thread Richard Hector

On 11/05/22 20:46, Nathan Ward wrote:



On 11/05/2022, at 8:06 PM, Richard Hector  wrote:

Hi all,

Hopefully this is acceptable here ...

I have a VPS (with a well-known NZ provider) which I can ping, but can't ssh 
to. tcptraceroute stops a couple of hops in (I think the first to not respond 
is our immediate ISP's immediate upstream).

From a different house/ISP, I can connect fine, and from here, I can connect to 
a different VPS (same provider, different network block)

I'm reasonably confident it's not firewall, partly from extensive testing, and 
partly because the same behaviour is shown when running tcptraceroute to the 
gateways of the respective VPS.

Any thoughts?

The fact that the traces make it part way suggest to me that it's a routing 
problem, but then how does ping work?

I could include tcptraceroute results, but is it considered ok to reveal ISPs 
etc? My email probably reveals it all anyway, of course ... :-)


Yeah post away. I would suggest run mtr once with tcp, once with udp, once with 
icmp.
mtr has tcp, udp and icmp modes these days and I find it better than 
traditional tcptraceroute - if for no other reason than it’s got a nice 
consistent interface regardless what protocol you’re testing with.

It may be that the hop that tcptraceroute “stop” at is actually just a router 
that’s dropping your tcp from hitting the control plane, and higher TTL packets 
continue through, so let them run their course and see if you get hops after 
that.

Probably also be worth hitting up your ISP, if that’s relevant, as it sounds 
like it’s an issue with them.


Thanks Nathan.

From home (2degrees):
richard@citrine:~$ mtr -tr 103.6.212.12
Start: 2022-05-11T20:59:07+1200
HOST: citrine Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- void.home  0.0%100.5   0.5   0.4   0.7 
  0.1
  2.|-- 65.7.69.111.static.snap.n  0.0%103.3   3.5   1.5   8.6 
  2.3
  3.|-- voyager.wix.nzix.net   0.0%102.2   2.5   2.0   3.5 
  0.6
  4.|-- ae-0-447.cr2.wgn.vygr.net  0.0%102.7   2.8   2.1   4.2 
  0.7
  5.|-- xe-2-0-3-0.cr1.wgn.vygr.n  0.0%104.0   2.8   2.0   4.6 
  0.8
  6.|-- xe-1-1-0-0.cr2.mdr.vygr.n  0.0%10   13.4  12.5  11.9  13.4 
  0.5
  7.|-- ae-1-0.cr1.mdr.vygr.net0.0%10   12.4  12.9  11.8  15.3 
  1.2
  8.|-- et-0-0-0-0.cr1.qst.vygr.n  0.0%10   12.7  15.0  11.8  34.0 
  6.7
  9.|-- et-0-0-3-0.cr2.qst.vygr.n  0.0%10   14.1  14.2  11.7  21.1 
  3.5
 10.|-- et-0-0.3.cr2.qst.vygr.net  0.0%10   14.6  12.6  11.7  14.6 
  0.9
 11.|-- xe-0-1-0.cr2.pmd.vygr.net  0.0%10   13.1  15.2  12.0  37.9 
  8.0
 12.|-- 113.21.224.23  0.0%10   12.3  12.5  12.2  13.3 
  0.4
 13.|-- akl-host1.backend.net.nz   0.0%10   13.3  14.0  12.1  22.5 
  3.1

richard@citrine:~$ mtr -trT 103.6.212.12
Start: 2022-05-11T21:00:58+1200
HOST: citrine Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- void.home  0.0%100.5   0.6   0.5   0.7 
  0.0
  2.|-- 65.7.69.111.static.snap.n  0.0%10   32.1   5.8   2.1  32.1 
  9.3
  3.|-- ???   100.0100.0   0.0   0.0   0.0 
  0.0

richard@citrine:~$ mtr -tru 103.6.212.12
Start: 2022-05-11T21:01:25+1200
HOST: citrine Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- void.home  0.0%100.5   0.5   0.5   0.7 
  0.1
  2.|-- 65.7.69.111.static.snap.n  0.0%102.0   2.1   1.6   3.4 
  0.6
  3.|-- ???   100.0100.0   0.0   0.0   0.0 
  0.0


From a different home (Spark):
richard@kereru:~$ mtr -tr 103.6.212.12
Start: 2022-05-11T21:04:56+1200
HOST: kereru  Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- fibre-router   0.0%100.6   0.5   0.4   0.6 
  0.1
  2.|-- 219-88-156-1-vdsl.sparkbb  0.0%107.9   4.0   1.7   7.9 
  1.7
  3.|-- ???   100.0100.0   0.0   0.0   0.0 
  0.0
  4.|-- 122.56.113.6   0.0%10   12.7  12.1  10.7  13.7 
  1.0
  5.|-- voyager-dom.akcr11.global  0.0%10   13.7  14.7  11.5  28.7 
  5.1
  6.|-- et-0-0-0-0.cr1.qst.vygr.n  0.0%10   14.8  16.0  11.7  22.6 
  3.7
  7.|-- et-0-0-3-0.cr2.qst.vygr.n  0.0%10   12.0  13.5  11.0  18.8 
  2.3
  8.|-- et-0-0.3.cr2.qst.vygr.net  0.0%10   27.6  15.6  11.4  27.6 
  4.5
  9.|-- xe-0-1-0.cr2.pmd.vygr.net  0.0%10   14.3  14.5  11.4  21.3 
  2.7
 10.|-- 113.21.224.23  0.0%10   14.3  13.7  11.7  15.2 
  1.3
 11.|-- akl-host1.backend.net.nz   0.0%10   11.2  12.9  11.2  15.2 
  1.4

richard@kereru:~$ mtr -trT 103.6.212.12
Start: 2022-05-11T21:06:04+1200
HOST: kereru  Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- fibre-router   0.0%100.6   0.7   0.6   1.3 
  0.2
  2.|-- 219-88-156-1-vdsl.sparkbb  0.0%104.0   4.3   1.9   8.8 
  2.0
  3.|-- ???   100.0100.0   0.0   0.0   0.0 
  0.0
  

[nznog] Re: routing problem?

2022-05-11 Thread Nathan Ward

> On 11/05/2022, at 8:06 PM, Richard Hector  wrote:
> 
> Hi all,
> 
> Hopefully this is acceptable here ...
> 
> I have a VPS (with a well-known NZ provider) which I can ping, but can't ssh 
> to. tcptraceroute stops a couple of hops in (I think the first to not respond 
> is our immediate ISP's immediate upstream).
> 
> From a different house/ISP, I can connect fine, and from here, I can connect 
> to a different VPS (same provider, different network block)
> 
> I'm reasonably confident it's not firewall, partly from extensive testing, 
> and partly because the same behaviour is shown when running tcptraceroute to 
> the gateways of the respective VPS.
> 
> Any thoughts?
> 
> The fact that the traces make it part way suggest to me that it's a routing 
> problem, but then how does ping work?
> 
> I could include tcptraceroute results, but is it considered ok to reveal ISPs 
> etc? My email probably reveals it all anyway, of course ... :-)

Yeah post away. I would suggest run mtr once with tcp, once with udp, once with 
icmp.
mtr has tcp, udp and icmp modes these days and I find it better than 
traditional tcptraceroute - if for no other reason than it’s got a nice 
consistent interface regardless what protocol you’re testing with.

It may be that the hop that tcptraceroute “stop” at is actually just a router 
that’s dropping your tcp from hitting the control plane, and higher TTL packets 
continue through, so let them run their course and see if you get hops after 
that.

Probably also be worth hitting up your ISP, if that’s relevant, as it sounds 
like it’s an issue with them.

--
Nathan Ward

___
NZNOG mailing list -- nznog@list.waikato.ac.nz
To unsubscribe send an email to nznog-le...@list.waikato.ac.nz