unix:networking:openwrt_routing
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
unix:networking:openwrt_routing [2014/04/30 05:26] ben [Split VPN routing with OpenWRT/Tomato] |
unix:networking:openwrt_routing [2014/08/14 06:40] ben [VPN Scripts] |
||
|---|---|---|---|
| Line 18: | Line 18: | ||
| </code> | </code> | ||
| - | Contents of Administration->Scripts->Init: | + | Contents of Administration->Scripts->Init: //(I don't use this anymore but figured I'd leave it documented)// |
| <code> | <code> | ||
| #Mount optware | #Mount optware | ||
| Line 51: | Line 51: | ||
| down /opt/etc/scripts/vpnroutedown.sh | down /opt/etc/scripts/vpnroutedown.sh | ||
| </code> | </code> | ||
| + | |||
| + | Two files are necessary: | ||
| Contents of pia.txt is VPN username on first line, password on second line. | Contents of pia.txt is VPN username on first line, password on second line. | ||
| + | Contents of pia_client_id is a random string: ''head -n 100 /dev/urandom | md5 > pia_client_id'' | ||
| ===== VPN Scripts ===== | ===== VPN Scripts ===== | ||
| Line 80: | Line 83: | ||
| for host in $vpndhosts;do for server in $dnsservers;do ip rule add from $host to $server lookup main;ip rule add from $server to $host lookup main;done;done | for host in $vpndhosts;do for server in $dnsservers;do ip rule add from $host to $server lookup main;ip rule add from $server to $host lookup main;done;done | ||
| - | /opt/etc/scripts/port_forward_update.sh | + | /opt/etc/scripts/port_forward_update.sh & |
| </code> | </code> | ||
| Line 92: | Line 95: | ||
| ===== Port-forward Script ===== | ===== Port-forward Script ===== | ||
| - | This is specific to Private Internet Access's method for getting a port forwarding port via an HTTPS request. It uses iptables PREROUTING to forward the port to the internal LAN address. Once the port is retrieved, if there's no forwarding enabled currently, it gets enabled. If it's different from what is currently forwarded, it replaces what's currently in place. Once the ports are setup it calls the script to update the transmission config. | + | This is specific to Private Internet Access's method for getting a port forwarding port via an HTTPS request. It uses iptables PREROUTING with the NAT table to forward the port to the internal LAN address. Once the port is retrieved, if there's no forwarding enabled currently, it gets enabled. If it's different from what is currently forwarded, it replaces what's currently in place. Once the ports are setup it calls the script to update the transmission config. |
| Contents of port_forward_update.sh: | Contents of port_forward_update.sh: | ||
| Line 157: | Line 160: | ||
| </code> | </code> | ||
| + | <note important>Fix needed: There's actually a logical flaw here- if the router goes down then the new port won't match and the sed match there will fail, not updating the port.</note> | ||
| ===== Scheduled port forward update ===== | ===== Scheduled port forward update ===== | ||
unix/networking/openwrt_routing.txt ยท Last modified: 2015/11/17 07:10 by ben
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
