Live data from Hacker News

Engineer distributes resume via IPv6 traceroute

cv6.poinsignon.org

71–80 of 162 posts

Re: Engineer distributes resume via IPv6 traceroute

#71
post #60

Earlier quoted context omitted.

> Cloudflare.NetworkEngineer Ah, that explains a lot. Not that anyone else couldn't do such a thing, but I feel like even amongst more "hacker" types it takes a relatively specialized background to pull a trick like this (at least statistically; I'm sure there are outliers).

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…

Believe it or not, you might have very specific interests :)

Re: Engineer distributes resume via IPv6 traceroute

#72
post #42
post #21

Earlier quoted context omitted.

So is that mail.jobs@ or mail+jobs@... or jobs@ A total flop on the last line

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

I still think it's mail.jobs@ - so I'd hope the engineer set up collection on both addresses.

It'd probably be a lot safer to just have the line be "jobs.at.[...]"

Edited to add: Oh also - from the same line you can infer that a dot means a dot - the ".org" at the end confuses the meaning. Perhaps it'd be clearer if they went 100% slashdot and had ".DOT.org"

Re: Engineer distributes resume via IPv6 traceroute

#73

Earlier quoted context omitted.

> Cloudflare.NetworkEngineer Ah, that explains a lot. Not that anyone else couldn't do such a thing, but I feel like even amongst more "hacker" types it takes a relatively specialized background to pull a trick like this (at least statistically; I'm sure there are outliers).

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 oppo…

44Net and hamnet are also interesting to those with radio amateur licenses. Many folks run their own AS an BGP in that range.

Re: Engineer distributes resume via IPv6 traceroute

#75
Doesn't work properly here, I get a very local IPv6, then one row of stars, then the third hop is the destination?

  % traceroute6 -w1 cv6.poinsignon.org
  traceroute to cv6.poinsignon.org (2001:bc8:3eff:c0::ff), 30 hops max, 80 byte packets
   1  2a01:x:x:x::1 (2a01:x:x:x::1)  0.794 ms  0.913 ms  0.737 ms
   2  * * *
   3  2001:bc8:3eff::1 (2001:bc8:3eff::1)  39.555 ms  39.668 ms  39.560 ms
Not sure why "traceroute6" stops at the "...::1" but "mtr" shows an equivalent 3-hop route but actually shows "...::ff" for the third and final hop? (Edit: Using "-I" with "traceroute6" makes the third and final hop also show up as "::ff". Strange that ICMP vs UDP would give different IP addresses for the final hop?)

Re: Engineer distributes resume via IPv6 traceroute

#76
post #68
post #59

Earlier quoted context omitted.

I would presume a better way would be to not make people feel unsure of what it is, and just pick something thats super clear.

Or it's a filter. No need to send anything if you are unsure.

I didn't realize that arbitrary interpretation of vague text was a criteria for a great employer

Re: Engineer distributes resume via IPv6 traceroute

#77
post #18

Earlier quoted context omitted.

Why have you traceroute ip instead of domain?

> 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...

> Historically very little software bothered to check

For some reason, most IRC servers tend to do this.

Re: Engineer distributes resume via IPv6 traceroute

#78
post #63
post #62

Earlier quoted context omitted.

Except this doesn't have custom text. All the IP addresses correspond to real domain names

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

Awesome, this one works

Re: Engineer distributes resume via IPv6 traceroute

#80
post #7

Here's what it looks like: $ traceroute cv6.poinsignon.org traceroute to cv6.poinsignon.org (2001:bc8:3eff:c0::ff), 30 hops max, 80 byte packets 1 gateway 0.795 ms 0.789 ms [...] 8 hello (2001:bc8:3eff:c0::1) 1.431 ms 1.202 ms 9 My.name.is.Louis.Poinsignon (2001:bc8:3eff:c0::2) 1.649 ms 1.274 ms 10 I.am.a.network.and.systems.Engineer (2001:bc8:3eff:c0::3) 1.695 ms 2.090 ms 11 This.is.my.resume.over.traceroute (2001:b…

Remember when they said we'd never run out of IPV6 addresses?

Good times.

Post reply on HN