Re: [bitfolk] problem setting up SSH

Top Page

Reply to this message
Author: Alarig Le Lay
Date:  
To: users
Subject: Re: [bitfolk] problem setting up SSH
Hi,

On Sat 25 Sep 2021 22:35:56 GMT, Andy Smith wrote:
> > Traceroute shows the following....
> >
> > ian@hobsoni:~$ traceroute -4 109.51.83.178
> > traceroute to 109.51.83.178 (109.51.83.178), 30 hops max, 60 byte packets
> > 1 macallan.bitfolk.com (85.119.80.25) 0.249 ms 0.636 ms 0.566 ms
> > 2 jump-gw-3.lon.bitfolk.com (85.119.80.3) 3.064 ms 3.533 ms 3.931 ms
> > 3 t2.jump.net.uk (194.153.169.238) 0.370 ms 0.360 ms 0.400 ms
> > 4 as2914.jump.net.uk (194.153.169.185) 0.601 ms 0.483 ms 0.658 ms
> > 5 195.219.23.72 (195.219.23.72) 0.977 ms 0.862 ms 0.758 ms
> […]


> The IP 195.219.214.18 belongs to TATA communications but since you
> aren't their customer and neither is BitFolk, it would be best for
> you to ask your ISP why you can't reach the BitFolk IP and show them
> your traceroute, since you are their customer and they should listen
> to you.


109.51.64.0/18 is annonced by AS2860 (NOS_COMUNICACOES) to AS35280
(ACORUS) and AS6453 (TATA). So Ian is indirectly a customer of TATA.
https://lg.as208627.net/prefix_bgpmap/lg/ipv4?q=109.51.83.178

Jump isn’t a customer of TATA, but the hop #4 is from AS2914 (NTT),
which is a transit of Jump. So the route is 100% legit.

Regarding the * * * at the end of the traceroute, I can’t even have an
mtr (with ICMP) response from other ASes, so my guess is the Ian’s ISP
is doing nasty filtering, which is indeed not a good practice.

--
Alarig