Possible to create a local to remote proxy tunnel? [closed]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I'm using a emulator program that allows for a proxy, but doesn't allow a proxy with authentication and regardless of that, I need to be able to change the proxy on the fly using a terminal command.



Similar to how 'tor' opens a localhost port that tunnels to the first node in the tor chain, is there a way to setup a tunnel (say localhost:1234) that connects to a proxy with authentication? That way, I could just put localhost:1234 in the emulator's proxy settings and have separate control of the proxy settings?



(I thought socat might do it but it seems like while it can tunnel through an authenticated proxy, it requires a static endpoint to be connecting to..)










share|improve this question













closed as too broad by Ipor Sircer, JigglyNaga, nwildner, RalfFriedl, Thomas Dec 11 at 5:02


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.


















    up vote
    0
    down vote

    favorite












    I'm using a emulator program that allows for a proxy, but doesn't allow a proxy with authentication and regardless of that, I need to be able to change the proxy on the fly using a terminal command.



    Similar to how 'tor' opens a localhost port that tunnels to the first node in the tor chain, is there a way to setup a tunnel (say localhost:1234) that connects to a proxy with authentication? That way, I could just put localhost:1234 in the emulator's proxy settings and have separate control of the proxy settings?



    (I thought socat might do it but it seems like while it can tunnel through an authenticated proxy, it requires a static endpoint to be connecting to..)










    share|improve this question













    closed as too broad by Ipor Sircer, JigglyNaga, nwildner, RalfFriedl, Thomas Dec 11 at 5:02


    Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I'm using a emulator program that allows for a proxy, but doesn't allow a proxy with authentication and regardless of that, I need to be able to change the proxy on the fly using a terminal command.



      Similar to how 'tor' opens a localhost port that tunnels to the first node in the tor chain, is there a way to setup a tunnel (say localhost:1234) that connects to a proxy with authentication? That way, I could just put localhost:1234 in the emulator's proxy settings and have separate control of the proxy settings?



      (I thought socat might do it but it seems like while it can tunnel through an authenticated proxy, it requires a static endpoint to be connecting to..)










      share|improve this question













      I'm using a emulator program that allows for a proxy, but doesn't allow a proxy with authentication and regardless of that, I need to be able to change the proxy on the fly using a terminal command.



      Similar to how 'tor' opens a localhost port that tunnels to the first node in the tor chain, is there a way to setup a tunnel (say localhost:1234) that connects to a proxy with authentication? That way, I could just put localhost:1234 in the emulator's proxy settings and have separate control of the proxy settings?



      (I thought socat might do it but it seems like while it can tunnel through an authenticated proxy, it requires a static endpoint to be connecting to..)







      proxy






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 10 at 3:15









      Max

      163




      163




      closed as too broad by Ipor Sircer, JigglyNaga, nwildner, RalfFriedl, Thomas Dec 11 at 5:02


      Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.






      closed as too broad by Ipor Sircer, JigglyNaga, nwildner, RalfFriedl, Thomas Dec 11 at 5:02


      Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          I think you'd use OpenSSH for your needs, ad a decently recent version.
          What you need comes from these options (and related configuration options):




          • -L for local-to-remote tunnel (actually a TCP port forwarding)


          • -D for local-to-remote SOCKSv5 proxy

          Please, see the OpenSSH client man page for more details to adapt this hint to your very situation.



          I'd like you to give a read to a post of mine here for a very specific case.



          For other SSH implementations your mileage may vary but the concepts should still hold true.



          Finally, it's not clear, though, how would you handle the proxy authentication once you reach it with the tunneling.






          share|improve this answer




















          • The authentication is normally handled in the connection url itself.. example: “user:pass@someproxyIP:port”. Ill try that..
            – Max
            Dec 10 at 17:01

















          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          0
          down vote













          I think you'd use OpenSSH for your needs, ad a decently recent version.
          What you need comes from these options (and related configuration options):




          • -L for local-to-remote tunnel (actually a TCP port forwarding)


          • -D for local-to-remote SOCKSv5 proxy

          Please, see the OpenSSH client man page for more details to adapt this hint to your very situation.



          I'd like you to give a read to a post of mine here for a very specific case.



          For other SSH implementations your mileage may vary but the concepts should still hold true.



          Finally, it's not clear, though, how would you handle the proxy authentication once you reach it with the tunneling.






          share|improve this answer




















          • The authentication is normally handled in the connection url itself.. example: “user:pass@someproxyIP:port”. Ill try that..
            – Max
            Dec 10 at 17:01














          up vote
          0
          down vote













          I think you'd use OpenSSH for your needs, ad a decently recent version.
          What you need comes from these options (and related configuration options):




          • -L for local-to-remote tunnel (actually a TCP port forwarding)


          • -D for local-to-remote SOCKSv5 proxy

          Please, see the OpenSSH client man page for more details to adapt this hint to your very situation.



          I'd like you to give a read to a post of mine here for a very specific case.



          For other SSH implementations your mileage may vary but the concepts should still hold true.



          Finally, it's not clear, though, how would you handle the proxy authentication once you reach it with the tunneling.






          share|improve this answer




















          • The authentication is normally handled in the connection url itself.. example: “user:pass@someproxyIP:port”. Ill try that..
            – Max
            Dec 10 at 17:01












          up vote
          0
          down vote










          up vote
          0
          down vote









          I think you'd use OpenSSH for your needs, ad a decently recent version.
          What you need comes from these options (and related configuration options):




          • -L for local-to-remote tunnel (actually a TCP port forwarding)


          • -D for local-to-remote SOCKSv5 proxy

          Please, see the OpenSSH client man page for more details to adapt this hint to your very situation.



          I'd like you to give a read to a post of mine here for a very specific case.



          For other SSH implementations your mileage may vary but the concepts should still hold true.



          Finally, it's not clear, though, how would you handle the proxy authentication once you reach it with the tunneling.






          share|improve this answer












          I think you'd use OpenSSH for your needs, ad a decently recent version.
          What you need comes from these options (and related configuration options):




          • -L for local-to-remote tunnel (actually a TCP port forwarding)


          • -D for local-to-remote SOCKSv5 proxy

          Please, see the OpenSSH client man page for more details to adapt this hint to your very situation.



          I'd like you to give a read to a post of mine here for a very specific case.



          For other SSH implementations your mileage may vary but the concepts should still hold true.



          Finally, it's not clear, though, how would you handle the proxy authentication once you reach it with the tunneling.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Dec 10 at 10:29









          EnzoR

          242129




          242129











          • The authentication is normally handled in the connection url itself.. example: “user:pass@someproxyIP:port”. Ill try that..
            – Max
            Dec 10 at 17:01
















          • The authentication is normally handled in the connection url itself.. example: “user:pass@someproxyIP:port”. Ill try that..
            – Max
            Dec 10 at 17:01















          The authentication is normally handled in the connection url itself.. example: “user:pass@someproxyIP:port”. Ill try that..
          – Max
          Dec 10 at 17:01




          The authentication is normally handled in the connection url itself.. example: “user:pass@someproxyIP:port”. Ill try that..
          – Max
          Dec 10 at 17:01


          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Bahrain

          Postfix configuration issue with fips on centos 7; mailgun relay