Search the Community
Showing results for tags 'aws'.
Found 2 results
Heya, since recently it has become impossible to use the prime video service through a VPN service I look for another way to still access it (here in Europe). I am running pfsense on my router that is set up pretty much according to the guide that can be found here in the forum. The idea is to create an alias with all the IPs of the server hosting the prime video service and use a firewall rule to pass the traffic directly to the WAN interface and not through the VPN tunnel. The IP ranges of the Amazon webservices can be found here: https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html But how to determine which of them is actually used for the prime service here in germany? To put ALL the IPs of the AWS into an alias is for sure not a good idea. Maybe someone has done some testing already?
Hi, I wanted to make the default route through the tun0 interface to route all traffic through vpn. However, I want to keep the existing route (or access) on my aws instance in order to still ssh/rdp into the vm outside the VPN traffic by using the public ip assigned by AWS. Right now with defaults, not removing the gateway after the vpn connects forwards no traffic and removing the default gw kills the ssh/rdp connection. Whats the best way here using Eddie? I figured route is not enough since making a simple route add back to the previous default gw still breaks ssh after the vpn associates, like route add -net 172.31.0.0 netmask 255.255.255.0 gw 172.31.0.1 eth0, but that seems wrong. How can I do this?