pwnagotchi VS gluetun

Merged and corrcted in jan could try that or as mentioned in another comment w solved this a while back in the forums remember to run the demo on your unit to verify what drivers it needs etc but it's been solved long ago https://github.com/evilsocket/pwnagotchi/issues/1134

yeah cause when you enable pwnagotchi to use pwngrid all you actually did was tell pwnagotchi to use api/pwnagotchi.ai which is down so your pwnagotchi will now try to connect to the internet, then it will try to send data to the API at pwnagotchi.ai and that API has been removed from the site. this is like telling the babysitter to call grandma but grandmas phone got cut off after a bad storm you can dial the number all day the wire to the house got cut there's no way for you to connect that way right now...

ok so all the Drivers for all the supported boards are added to the lib folder during build so if you add that stuff to the repo you download before you build it into an image. then adjust the display.py file to have a call back for your new drivers then you can set config to call up your screens drivers. After that you may need to adjust voice.py in order for screen element to display correctly based on your eink resolution.

Use the same config from pwnagotchi.ai but use this Image

1st Image used: https://github.com/evilsocket/pwnagotchi/releases/tag/v1.5.5

fatal: unable to access 'https://github.com/evilsocket/pwnagotchi.git/': Could not resolve host: github.com

healthcheck: # https://github.com/qdm12/gluetun/issues/641#issuecomment-933856220 test: "curl -sf https://example.com || exit 1" interval: 1m timeout: 10s retries: 2

I have containers a,b,c. Container C is running Gluetun (https://github.com/qdm12/gluetun) which is a VPN container.

The last couple of years I have been donating to Gluetun.

One option I could find is Gluetun, which looks very popular and actively maintained. In this case we have one single point of contact with VPN provider. The other containers should be run with network_mode: service:gluetun. If I understand correctly, those container will use VPN for every network operation, even for inter-container communication. Would they be visible for the containers not attached to gluetun (e.g. the SWAG reverse proxy)?

Try setting it up. https://github.com/qdm12/gluetun See if it works for your needs.

After some digging around, I found this project, which I think should get a lot more light on itself. It allows to setup port-forwarding on linux very easily, together with a lot of other things !

I setup Gluetun with qbittorrent in docker. Gluetun connects to the nord via manual login and I get to choose the specific servers I want it to you in its environment variables.

Hi guys, I have a dumb question: according to their github page, one of the features is the killswitch. It is not clear to me whether this would shutdown other containers (connected to it) when vpn drops, or only when the whole internet connection goes down

# See https://github.com/qdm12/gluetun/wiki