Su -c "iptables -t nat -A PREROUTING -s 192.168.1.161 -p tcp -dport 443 -j REDIRECT -to-port 444" Su -c "iptables -t nat -A PREROUTING -s 192.168.1.162 -p tcp -dport 80 -j REDIRECT -to-port 81" Su -c "iptables -t nat -A PREROUTING -s 192.168.1.161 -p tcp -dport 80 -j REDIRECT -to-port 81" My start-stop-status start_daemon () accounts for two Apple TVs: start_daemon () You can add your iptables declarations to the function to automatically insert them every time the PlexConnect daemon starts. Line 17 defines the start_daemon () subroutine. The /var/packages/plexconnect/scripts/start-stop-status script controls the commands when the PlexConnect package starts. Unfortuantely, the iptables command isn’t permanent–it will reset after a server restart.
So now, any requests from 192.168.1.161 on port 80 and 443 will be redirected locally to port 81 and 444, the PlexConnect ports.
# iptables -t nat -A PREROUTING -s 192.168.1.161 -p tcp -dport 80 -j REDIRECT -to-port 81 # iptables -t nat -A PREROUTING -s 192.168.1.161 -p tcp -dport 443 -j REDIRECT -to-port 444 Upon connecting to the Diskstation via SSH: $ sudo su Using the magic of iptables it’s possible to redirect TCP requests from a certain source on a specific interface to redirect to a different local port using command: iptables -t nat -A PREROUTING -s -p tcp -dport -j REDIRECT -to-port įor example, my Apple TV has a static IP of 192.168.1.161. Unfortunately, the reverse proxy isn’t going to work if Synology WebStation is already serving on 80/443.
Oh noes! The problemīy default, PlexConnect runs a web server on port 81 and 444, with an nginx reverse proxy set to serve on port 80 and 443. I already have WebStation serving websites on those ports, so there’s a conflict. I want to run PlexConnect on my Synology NAS, but it requires access to port 80 and 443. It turns out you can use PlexConnect to link Plex with your Apple TV. I’m using Plex to manage my totally legal home movies.
0 kommentar(er)
