Conversation

Notices

1. Machismo (zerglingman@freespeechextremist.com)'s status on Tuesday, 10-Oct-2023 18:47:20 JST Machismo
   This is impressive, I have a router connected to my server, it has an IP (but doesn't do DHCP, whatever), and I can portscan it, but I can't actually connect to it because everything times out. I can't ping it either, but nmap somehow can. I think nmap is magic, except that it's giving the responses I expect; it's just everything else is failing. (And nmap takes much longer than it should to give me responses, too.)
   • Lelouche 🌸 (lelouchebag@shitposter.club)'s status on Thursday, 12-Oct-2023 16:37:04 JST Lelouche 🌸

     in reply to
     @Zerglingman Ehhh it's probably just not replying to ICMP requests, but nmap does quite a few different tests for if a port is "live"
     Machismo likes this.
   • Machismo (zerglingman@freespeechextremist.com)'s status on Thursday, 12-Oct-2023 16:37:20 JST Machismo

     in reply to

     • Lelouche 🌸
     @lelouchebag What about a host?
     Anyway, if it were just that, you'd expect curl to actually connect.
   • Lelouche 🌸 (lelouchebag@shitposter.club)'s status on Thursday, 12-Oct-2023 16:42:59 JST Lelouche 🌸

     in reply to
     @Zerglingman Is port 80/443 live according to nmap? It could also be the router is configured not to respond to something like curl's "give me your shit" request (hence the timeout), but is open to "hey you up" requests on the port
     Machismo likes this.
   • Machismo (zerglingman@freespeechextremist.com)'s status on Thursday, 12-Oct-2023 16:44:49 JST Machismo

     in reply to

     • Lelouche 🌸
     @lelouchebag 80, yes, but it took like 30 seconds to scan, over LAN...
     It could be, but it's specifically meant to be offering a web interface for firmware flashing.
   • Lelouche 🌸 (lelouchebag@shitposter.club)'s status on Thursday, 12-Oct-2023 20:13:44 JST Lelouche 🌸

     in reply to
     @Zerglingman May be entirely dumb to ask, but does going to it via browser bring anything when specifying http://? I'd almost pop open burp suite or some sort of packet checker to see if it has some weird auth requirements
     >took over 30 seconds
     Is that for a 1024 common port scan or just for 80? If it's just that one port taking so long it might be the server getting spammed somehow or really bad programming on the backend
     Machismo likes this.
   • Machismo (zerglingman@freespeechextremist.com)'s status on Thursday, 12-Oct-2023 20:16:37 JST Machismo

     in reply to

     • Lelouche 🌸
     @lelouchebag Just port 80 lol, the 1024 takes like 10 minutes.
     >does going to it via browser bring anything when specifying http://
     Rather moot question here. It's connected to my server and nothing else; I set up a proxy on my server (and so I now know how to bind to an interface when proxying with nginx), and it exhibited the same behaviour when testing with palemoon from my PC.