![]() You’ll see a option to add a new port forward here which looks something like this. You can pretty much leave this as it is and just click add. Air will assign you a free port automatically. With multiple connections DDNS doesn’t work so feel free to leave that blank too, for torrent use it won’t matter as our client will be configured to use our specific port number anyway.Īfter clicking Add you will see your new port forward summary, make a note of the local port as you will need this later on, in my case its 56777. ![]() As my connection makes use of three simultaneous connections to provide some load balancing and failover protection there are three servers represented here. You’ll notice there are three grey circles next to the TCP test button. If you select the TCP test now they will remain grey as there isn’t a port forward in place on our local network to enable a response yet. Log into pfSense and navigate to Firewall > Aliases > IPĬreate a new alias to specify the torrent server Configure pfSense VPN_WAN port forwardįirst let setup up some basic parameters in aliases which makes life easier if we need to amend anything later on. IP or FQDN = IP address of your torrent machine, or if you have local DNS resolution, the FQDN.Ĭreate a new alias to specify the torrent client port.Port = the number of the port allocated from AirVPN, in my case it was 56777.Comment = Inbound torrent port (AirVPN).Filter rule association: Add associated filte rule.ĭescription: VPN_WAN: Torrent client port forward.Redirect target port: Other, TorrentInboundPort.Destination to port: TorrentInboundPort.Destination from port: TorrentInboundPort.Navigate to Firewall > NAT > Port Forward Now we’ll set up the port forward for our first VPN tunnel. Mouse over the port forward rule and move it above the default blocks.Verify your port forward rule summary looks like thisĪs part of creating this forward, an associated firewall rule was created in the VPN_WAN interface we specified. Remember rules are processed from top to bottom so the order is important. Verify your firewall rules look like thisĬonfigure Deluge client to use the forwarded port. I’m going to focus on setting up the ports rather than the whole Deluge client here as your setup may require some subtle differences from mine depending on which tracker you use. Verify VPN_WAN port forward functionality Load up your Deluge client and navigate to preferences > Network. Verify the grey circle turns green signalling the port forward is configured correctly.ĭuplicate VPN_WAN settings to other VPN interfaces.Select check besides your VPN_WAN connection server.Head back to AirVPN > Client Area > Forwarded ports. Log back in to pfSense and navigate to Firewall > NAT > Port forwards To provide some load balancing and failover protection, lets make use of our three VPN tunnels and enable them all to handle torrent traffic. Verify your port forward rules look like this when completeĪdjust VPN2_WAN and VPN3_WAN firewall rules BIGLYBT PORT FORWARDING TORRENTĭescription = VPN3_WAN: Torrent client port forward.Now make another duplicate for VPN_WAN3, click the duplicate icon next to the VPN_WAN rule again but this time make the following changes Description = VPN2_WAN: Torrent client port forward.Make the following changes to the duplicate rule Click the duplicate icon under actions to the right of the VPN_WAN rule to create a duplicate rule.We know that existing port forward works correctly so lets duplicate it to the two other VPN interfaces. We need to make a similar adjustment to the firewall rule ordering for those two new port forward rules which have been created. Mouse over the port forward rule and move it above the default blocks.Īnd again for VPN3_WAN, navigate to firewall > rule > VPN3_WAN.Select ‘Check’ besides your VPN2_WAN and VPN3_WAN connection servers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |