Engineer distributes resume via IPv6 traceroute (opens in new tab)

It’s because practical experience with technologies like BGP is difficult to acquire without sufficient capital to run a network. You can of course purchase a /24 and dabble (search HN for blog posts describing exactly that). And you can experiment with large deployments in simulators. But network optimization is inherently more of a practical pursuit than a theoretical one, so most broad and consistent learning opportunities are siloed to large organizations where you can accrue daily experience with the stack.

This is really unfortunate, and I mostly blame Cisco and Juniper. They suffocated an entire academic discipline with obfuscated terminology driven more by their business models than anything resembling the OSI model or open standards. That’s why WireGuard feels like such a breath of fresh air after 20 years of L2TP/IPSec.

I applaud companies like Cloudflare and Fly.io for their openness in sharing techniques and open sourcing so much of their code. It goes a long way toward lowering the barriers to self-teaching and experimenting with the latest networking software. And I’m sure HR is happy about the increasingly large applicant pool of qualified networking engineers – even if some hires do eventually leave by advertising their resume to anyone who sends them an IPv6 trace-route :)

This is a very old and oft-repeated trick though.

https://github.com/blechschmidt/fakeroute

https://github.com/antifork/hopfake

https://github.com/jprenken/rickroute

https://github.com/sams-gleb/ipv4-traceroute-fake

https://github.com/job/ipv6-traceroute-faker

And so on…

I remember being a 13yo kid sitting on IRC doing exactly this for fun years ago back when IP addresses were cheap and easy to come by. But spoofing military IPs in the traceroute was more fun.

Not sure how he did it, but my first guess would be just a bunch of virtual interfaces on a linux box with a->b->c->d->e->etc routing, and something like the tc command[1] to add enough latency to each one that traceroute sees them all.

If he's scripted it to do all the virtual nic creation and dns ptr entries, it would be interesting to see.

[1] https://bencane.com/2012/07/16/tc-adding-simulated-network-l...

Feels like we’re a dying bread with everything cloud first and serverless.

It is not length of experience that counts, but skill. Some people with 100ms experience have just done the same millisecond over and over.

It's contracting work, so the short duration makes sense!

Will age just like the famous quotes about 640K of memory is enough.

they never anticipated the internet of internet of things. What a shame.

> Host mail.jobs.at.poinsignon.org not found: 3(NXDOMAIN)

(A bit of a missed opportunity; the author should really set a AAAA record there IMHO)

There's no actual requirement that your PTR records resolve back to the same IP. Historically very little software bothered to check, and most of the Unix-y diagnostic software has never been updated to do so...

you could have multiple IPs attached to a domain which could mess up this trick.

I also wonder why not use use the domain, much easier.

Bad copy/paste

I bet if he can do this trace route thing, he can get all those emails going to his own domain regardless of who they are addressed to

Not really. From the lines above one can deduce that the dot represents space or colon, for obvious technical reasons. As such, I'd interpret

  mail.jobs.at.poinsignon.org

as

  mail: jobs@poinsignon.org

My interpretation was mail: jobs@poinsignon.org

Really, you're arguing about the email in a traceroute CV being somewhat ambiguous? Having to traceroute the thing is going to be a much bigger filter. And it's quite clear if you just read it out as spoken text and then try to get the address from that. Really, anyone actually interested in contacting the guy will manage just fine.

It's probably more accurate to "Oh noes this HN post is going to get this guy a few dozen really lucrative job offers".

Doxxing usually implies ill intent but having your personal information broadcast to HN is likely only to result in a few of the hiring managers that haunt here sending a cold offer.

Pandoc does a good job of generating docx files from markdown

Went through this. Gave up and remade it in Word. Practical beats pure sometimes. Tough for us HN types.

I gave up, I now generate my CV in docx from JSON, and convert that to PDF.

I work for a company that was acquired by Leidos relatively recently. Hello fellow coworker.

You're going to be sitting there for a while waiting for blocking random to fill 19MB. You want urandom.

It's only a /27, they were quite affordable a year or ten ago. A full /24 went for about $2500 back in 2015 when this was made and you can subdivide that to 8 customers who all get 30 usable addresses. Bit expensive for a joke, but not unmaintainably so.

It's silly that ISPs have messed up their IPv6 deployment so badly that there's a "shortage" of IPv4 addresses now. Of course, IPv4 was never going to be enough; there are too many people on earth.

I wonder whether you could do this with a lower number of IPs, just repeating them in the traceroute reply. You might not be able to build a real network like that, but if you're manually replying to ICMP with a raw socket, this should be possible, I doubt the client tries to de-duplicate based on addresses.

I guess you didn't really look; these are IPv6 addresses.

The typo was fixed a few hours later

Another implementation https://blog.benjojo.co.uk/post/traceroute-haikus and I've seen many more.

Doesn't seem to be the case, apple.com does not have an AAAA record. :(

Also shame on Microsoft for no full IPv6 support in WSL2.

(The CV posted above is outdated, this is what the traceroute shows today)

  8    37 ms    36 ms    36 ms  hello [2001:bc8:3eff:c0::1]
  9    32 ms    32 ms    31 ms  My.name.is.Louis.Poinsignon [2001:bc8:3eff:c0::2]
 10    33 ms    32 ms    31 ms  I.am.a.network.and.systems.engineer [2001:bc8:3eff:c0::3]
 11    35 ms    36 ms    35 ms  This.is.my.resume.over.traceroute [2001:bc8:3eff:c0::4]
 12    37 ms    35 ms    36 ms  o---Experience---o [2001:bc8:3eff:c0:ee::]
 13    36 ms    35 ms    35 ms  2021.Apple.Engineer.SF.USA [2001:bc8:3eff:c0:ee::714]
 14    33 ms    34 ms    31 ms  2018.Cloudflare.Engineer.SF.USA [2001:bc8:3eff:c0:ee::cf3]
 15    32 ms    34 ms    33 ms  2017.Cloudflare.Engineer.London.UK [2001:bc8:3eff:c0:ee::cf2]
 16    38 ms    36 ms    35 ms  2016.Cloudflare.Engineer.Intern.SF.USA [2001:bc8:3eff:c0:ee::cf1]
 17    36 ms    35 ms    34 ms  o---Education---o [2001:bc8:3eff:c0:ed::]
 18    36 ms    35 ms    34 ms  2015-2016.DrexelUni.Exchange.CE.Philadelphia.USA [2001:bc8:3eff:c0:ed::1]
 19    37 ms    32 ms    32 ms  2011-2016.UTT.Master.CE.France [2001:bc8:3eff:c0:ed::2]
 20    37 ms    34 ms    35 ms  o---Skills---o [2001:bc8:3eff:c0:51::]
 21    36 ms    36 ms    34 ms  Golang.C.Python [2001:bc8:3eff:c0:51::1]
 22    36 ms    34 ms    36 ms  Networks.Linux.Automation.Kafka.Clickhouse.Kubernetes [2001:bc8:3eff:c0:51::2]
 23    33 ms    33 ms    33 ms  Statistics.Maths [2001:bc8:3eff:c0:51::3]
 24    31 ms    32 ms    31 ms  o---Various---o [2001:bc8:3eff:c0:7a::]
 25    34 ms    35 ms    35 ms  Swimming.Karate.Piano [2001:bc8:3eff:c0:7a::1]
 26    36 ms    34 ms    35 ms  o---Contact---o [2001:bc8:3eff:c0:c0::]
 27    32 ms    34 ms    31 ms  mail.jobs.at.poinsignon.org [2001:bc8:3eff:c0:c0::1]
 28    33 ms    35 ms    30 ms  cv6.poinsignon.org [2001:bc8:3eff:c0::ff]

>If you had a block of 20 IPv4 addresses, I don't see anything stopping you from doing the exact same thing.

A block isn't necessary at all, even on IPv4. Traceroute can easily show internal address or just be lied to. Just recently we've seen a different example of this on HN:

https://news.ycombinator.com/item?id=32566730

Netflix and friends won’t work over them. But with some clever routing, you can get it to work… I just got native ipv6 last winter and had to use tunnels like this for years.

No, should be a native IPv6 consumer ISP... But now that you mention it, most other IPv6 sites act like this as well. Sorry, it's probably my ISP or maybe my router. Guess I haven't been tracerouting IPv6 much since getting native IPv6 connectivity.

lol