I’m looking to try some hands-on experience setting up proxies. However, the proxy I want to setup is a bit unique. My end goal is to be able to do the following:

  • Connect a Raspberry Pi to a network using Ethernet or Wi-Fi
  • Automatically have the Raspberry Pi (as soon as it is powered on and connected) send its own public IP address (and other relevant proxy information, where applicable) to a home server (and periodically retry sending this information if the server is down)
  • Be able to proxy my connection from a separate network through the Raspberry Pi (by simply entering in the IP address and port as a normal proxy) so that my public IP address will now show up as that of the network the Raspberry Pi is connected to

I want to avoid configuring port forwarding for networks the Raspberry Pi is connected to. I can configure port forwarding for the network my home server is connected to, but if possible I would like to avoid that as well (for convenience and security).

I also want to avoid using a third party service (e.g. Linode) to manage the proxy for me. I want the Raspberry Pi to do all the work here, ideally using open source software such as Privoxy or Squid. I want this to be an HTTP proxy. If possible, I would like to encrypt the proxy connection.

I’m not sure if any of this would be possible without port forwarding. Maybe some sort of reverse proxy would help with this. Like with most things, I understand how a proxy such as this could have the potential for misuse. I’m making this post for educational purposes only, so that I can better my understanding of proxies and network security.

Any guides or videos on how to set this up are greatly appreciated. I found a few, but none quite capture what I’m describing here. Most don’t talk about using this across separate networks, only local networks.

Thank you!

  • Oisteink@feddit.nlEnglish
    0·
    3 days ago

    To me it seems like he wants to be able to «bring along» his homenet services without exposing them on the internet.

    Tip for OP is to explain wanted outcome, not process to get there. Its hard to do, but gives better results

    • The 8232 Project@lemmy.mlOPEnglish
      0·
      3 days ago

      Tip for OP is to explain wanted outcome, not process to get there. Its hard to do, but gives better results

      Besides being able to learn about all of this, this would be the ideal outcome:

      • Send the Raspberry Pi to a friend who knows about this
      • Have the friend plug in the Raspberry Pi to his Ethernet
      • Use the friend’s network as a VPN/proxy/whatever to obscure my home IP address

      I wouldn’t want to make the friend set up port forwarding or configure the Raspberry Pi himself, I want to do as much as I can on my own. And, if that friend ever relocates his residence or changes his ISP, setting it up again should be as easy as him plugging in the Raspberry Pi to the new network and I reconfigure it from my end.

      • IsoKiero@sopuli.xyzEnglish
        0·
        2 days ago

        Use the friend’s network as a VPN/proxy/whatever to obscure my home IP address

        And then your friend is responsible for your actions on the internet. The end goal you described is so vague that at least I wouldn’t let your raspberry connect on my network.

        There’s a ton of VPN services which give you the end result you want without potential liability or other issues for your friend. If you just want to tinker, this thread has quite a bit of information to get you started.

        • emeralddawn45@discuss.tchncs.deEnglish
          0·
          2 days ago

          I have a feeling OP’s “friends” wont necessarily even be aware hes connected the device to their network. It sounds to me like he wants something he can hide places to take advantage of unsecured or public networks without having to sit there with his laptop doing whatever shady shit he has planned.

      • Oisteink@feddit.nlEnglish
        0·
        3 days ago

        Then an exit node is what you want. You can set up with vpn like wireguard using port forward on your side. The raspberry would connect using static ip or dynamic dns.

        You can get tailscale basic tier for free, and that will provide an easy to use solution