• emberpunk@lemmy.ml
    link
    fedilink
    English
    arrow-up
    31
    arrow-down
    1
    ·
    19 hours ago

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

    • stembolts@programming.dev
      link
      fedilink
      arrow-up
      11
      arrow-down
      1
      ·
      edit-2
      17 hours ago

      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.

        • stembolts@programming.dev
          link
          fedilink
          arrow-up
          8
          ·
          edit-2
          17 hours 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.