![]() ![]() You can simply comment out the 2xx check, which gets it past that point, but. Ever since they lost the port forwarding capability, this curl request has produced results other than the 2xx that the script looks for. There is probably a way around that part but I'm not there yet either. The logs for the binhex containers show you a list of available PIA port forwarding hostnames that are currently available. I also had to adjust my app's designated port number too. Now you need to return to pfsense and input the assigned port number. ![]() If you don't see the port number in the browser window just reload the page anytime (the two minute window no longer matters if successful) and it should report the assigned port number. If successful a port number will be returned. If you do it later than two minutes it reports site unreachable. What I want to do is have qBittorrent automatically change the listening/connection port based on the contents of that file. Gluetun automatically retrieves this port and can store it in a file using the environment variable I posted in the op. In one tab you need to call up pfSense and log in and in the other tab paste the url string.īack in the pfSense tab restart the VPN or restart the entire router and within two minutes of the VPN coming back online send the URL string from the other tab. Im using PIAs port forwarding feature through the VPN where PIA provides the port with a 60 day expiry. Note: Keep this URL string around for reuse as the PIA assigned port is released when the VPN connection goes down.įrom any computer on the VPN network open a web browser and call up two tabs/windows. This hash is nothing more than your personal key. Set up the VPN with the instructions provided.Ĭreate a SHA256 hash anyway that you want and append that hash to the URL provided in the instructions. It is included in the instructions indicated on this thread. The trick it seems is to get a PIA assigned forwarding port for the session. I couldn't get this to work at all thus the manual method. The instructions you identify in your original post seems to indicate there is a way to make this happen automatically on every boot and adjust the port forwarding rules to match the assigned PIA port. In any case once you get a hash (any hash) you move on to setting up pfsense. I'm most likely wrong on that score though. The port assigned by PIA is not static will be different every time you connect the VPN. ![]() With every establishment of the VPN to PIA a request needs to be sent for port assignment and the forwarding rules adjusted appropriately. In Linux you can use console commands to get the different parameters from the pia application. The script seems to only generate a SHA256 hash and not much else. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |