Cogent & FDCServers: Knowingly aiding and abetting fraud and theft?

Fri Sep 6 21:12:13 UTC 2019

Hello Ronald,

if you'd open the traceroute you just sent you'd see that the target is route looping and not actually used by their alleged customer? Since the loop is actually between the FDC aggregation router and Cogent's backbone router. Also, what would the target IP have been in this case, since it was omitted?
On Sep. 6 2019, at 11:06 pm, Ronald F. Guilmette <rfg at tristatelogic.com> wrote:
> In message <23540.1567802066 at segfault.tristatelogic.com>, I wrote:
>
> > Is anyone disputing that 168.198.0.0/16 belongs to the Australian
> > national government, or that AS174, Cogent was, until quite recently,
> > routing that down to their pals at FDCServers who then were routing
> > it down to their customer, Elad Cohen? If so, I ask that people look
> > up this network in the RIPE Routing history tool and ALSO that folks
> > have a look at, and explain, the following traceroute from August 23:
> >
> > https://pastebin.com/raw/2nJtbwjs
> My apologies. In my furious haste, I botched that one URL. Here is the
> correct file conatining my traceroute to 168.198.12.242 as performed by
> me on August 23rd:
>
> https://pastebin.com/raw/TrLbGZuW
>
> Regards,
> rfg
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190906/4f9979ed/attachment.html>