On 2024-10-18, Stuart Henderson <stu.li...@spacehopper.org> wrote: > On 2024-10-17, Qingyao Sun <sunqingyao19970...@icloud.com> wrote: >> >> Besides FTP (port 21), I also cannot use SSH or access websites via = >> HTTPS (port 443). However, I can somehow connect to HTTP (port 80) on = >> remote servers. >> >> werebane# nc -z google.com 80; echo $? =20 >> Connection to google.com (132.236.61.7) 80 port [tcp/www] succeeded! > > This will be some restriction imposed by the network you're on. > > Do you actually get that website, or does it redirect you to a captive portal?
Oh, well actually it's clear from reverse DNS of that IP: $ dig -x 132.236.61.7 ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53627 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; ANSWER SECTION: 7.61.236.132.in-addr.arpa. 43183 IN PTR reg-www-prep.cit.cornell.edu. ;; Received 85 bytes from 127.0.0.1#53(127.0.0.1) in 1 ms > Some networks do not permit internet access unless you've authenticated > (possibly by captive portal in a web browser, possibly by 802.1x). -- Please keep replies on the mailing list.
