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

908 readers

1 users here now

you know the computer thing is it plugged in?

Moved to [email protected].

founded 2 years ago

MODERATORS

[email protected]

797

"Works on my machine". (lemm.ee)

submitted 2 weeks ago by [email protected] to c/[email protected]

101 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 32 points 2 weeks ago (3 children)

OK listen hear me out. Perfect opportunity for guests to learn how to ssh tunnel to port forward to their local device 😅

[–] stembolts 17 points 2 weeks ago* (last edited 2 weeks ago) (2 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] 10 points 2 weeks ago (1 children)

ip a a 127.0.0.2/8 dev lo

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

[–] stembolts 13 points 2 weeks ago* (last edited 2 weeks 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.