illy [Shrimple-mode] :protomoji_orange_flag_lesbian: (@illyBytes)

@aei@pleroma.envs.net

6d

dns over https should be going over port 443, no? cause i remember having it configured and it didn't work on the college wifi , and while i know that they blacklist domains manually and i dont believe they actively block the dns provider domains, i also know they have a port number whitelist

im very sure it should go through 443 and unless they block dns domains (which would be silly) it should work without problems

2

0

1

0

illy [Shrimple-mode]

@illyBytes@shrimp.imsofucking.gay

6d

@aei dns over https is indistinguishable from a normal https website, so the only way stuff cant block is with DPI

or... ik that my university has set their dns to google's (8.8.8.8) but it weirdly has restrictions google doesnt have, which might mean they have kinda hijacked the route to google's dns (they do own and operate their own AS) so maybe when DoH tries to connect, it asks the system dns for the route to DoH, my uni's hijacked google dns catches that and reroutes it to 127.0.0.1

what kind also supports my hypothesis is that if i start my browser on 4g, (browser handles DoH) then switch to the wifi it just straight up works lol

1

0

1

0

aei

@aei@pleroma.envs.net

6d

@illyBytes yeah thats what i thought. i vaguely remember using wireshark for checking but maybe i misremembered some stuff

some corporate networks are not super competently made and im sure this one of them. i assume uni networks are all slopped up and proxied for filtering purposes just enough to work, over here i figured out that they use a 10.x.x.x address for dns, and that they meddle around with CA certs here and there but im not exactly sure.

0

1

0