Notices by halcy​:icosahedron: (halcy@icosahedron.website), page 81

(P.S. 1) yes bitcoin is hilarious but also 2) there exist people who are losing their life savings over this shitty-gamble-pushed-as-good-investment-by-greedy-nerds and that is depressing)

https://m.youtube.com/watch?v=obsD_1i2Tb4

after figuring out that I was setting the port wrong, we now have a traceroute that shows that yes the cs faculty router routes packages that go to a private range to our internal network. what

is bitcoin still crashing

also, out of spec, but I guess people do not care about that, huh

or I guess maybe it just allows no TTL exceeded replies At All Ever actually, that's way simpler

@pasqui023 know of any common traceroute utilities that allow you to run the TTL in reverse, or in a random order? >>

@pasqui023 I guess maybe some threshold for minimum ttl or whatever or something that specifically murders traceroute-looking packets a r g h

@pasqui023 I can connect to the target host just fine during all this so ? ? ?

@dotUser yeah but the way traceroute in tcp mode works it should STILL not reject these packages unless, as @pasqui023 says, it is stateful and detects traceroute specifically

okay the unis edge firewall just drops every packet coming in via traceroute, apparently (how even? I'm doing a tcp traceroute with a port that's open on the target machine, shouldn't that hit it eventually??)

wait 30 is just the default max hops innit. lets crank that up.

traceroute shows the packets mucking about for 30 hops, none of which send any reply, until everything it finally reaches it's destination. this is for a server that should be like three hops away tops

next up in Mysteries We Are Debugging Today: why is this private (10.101.*) IP somehow reachable from a computer that is not in that subnet like what is happening here.

@jk @Murkrow jeans with cape: jape

doing important scientific work today such as "debugging a FTP server" and "installing a computer and some furniture"

@aeonofdiscord I mean that is how FTP (also IRC DCC) work: client: "hey give me file X", server: "okay client, listen on port 256*11+32 and I will send it to that port", or in passive mode "okay I am listening on port 256*2+63"

@theoutrider @tom I mean that is how FTP (also IRC DCC) work: client: "hey give me file X", server: "okay client, listen on port 256*11+32 and I will send it to that port", or in passive mode "okay I am listening on port 256*2+63"

why did people think "listen on a random port" type protocols were ever a good idea oh my god