this post was submitted on 23 Apr 2025
696 points (99.4% liked)

[Moved to [email protected], check pinned post.] iiiiiiitttttttttttt.

871 readers
440 users here now

you know the computer thing is it plugged in?

Moved to [email protected].

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] stembolts 12 points 1 day ago* (last edited 1 day ago) (1 children)

I'll save noobies some time.

for (( i=1; i<65536; i++ ));do  
  for (( j=1; j<256; i++ ));do  
    ssh -L $j$i:127.0.0.1:$i -N 192.168.1.$j &  
  done  
done  

What could go wrong?

Okay clearly this won't work because there aren't enough local ports to match to 16 bits of ports on potentially 255 machines, but with some slight modification I could add in a test to only increment the local port if the forward is successful and thereby create the dumbest-ass port forwarding script ever.

[–] [email protected] 7 points 1 day ago (1 children)

ip a a 127.0.0.2/8 dev lo

You have a whole /8 subnet of localhost, do it.

[–] stembolts 9 points 1 day ago* (last edited 1 day ago)

I like where your head is at.

We could also save some time just parsing something like..

nmap --top-ports 100 192.168.1.0/24 | grep -e "report" -e "open"  

We have the technology, we can be stupid.