Just another WordPress site

I did a bunch of research and testing and found a solution for a hardware like kill switch within DD-WRT. This is where you want to basically block traffic when the VPN conection fails or gets blocked for many reasons.

This was some of the things I tested for:

1. When the OpenVPN process dies all LAN/wireless traffic will not leak to the WAN port and bypass the VPN tunnel.
2. When the router boots up LAN/wireless traffic will not leak to the WAN port and bypass the VPN tunnel.
3. When OpenVPN is blocked downstream, ex. blocking UDP 1194, LAN/wireless traffic will not leak to the WAN port and bypass the VPN tunnel.
4. Unplugging/plugging any port on the router will not cause LAN/wireless traffic to leak to the WAN port and bypass the VPN tunnel.

I use a regular router, router #1, downstream (Fios router from Verizon) and use DD-WRT, router #2, only when I want to use the VPN. I connect the WAN port of the DD-WRT router into the LAN port of the Fios router. I then manually connect devices which I want to use the VPN into the LAN ports OR associate them with the wireless AP in the DD-WRT router.

If you only wanted to use one router and not two as I have described above, then you would need to use a policy based solution where some devices would tunnel over the VPN and other you could selectively allow to bypass the VPN. See my comments at the very end for this solution.

These are the firewall commands I added to my WZR-HP-G300NH v1 router (ADMINISTRATION – COMMANDS):

The last line is a duplicate from the OP, but doesn’t seem to cause any issue. I also own a whr-g54s which required the same above command, but eth1 was replaced with vlan1. Each router will have different interfaces, so these firewall commands might be different for your router. You can use the route command to see what interfaces you have.

NOTE: You will need to substitute “http://mywebsiteexample.com/jwplayer/jwplayer.js” with the absolute path where the self-hosted player is located. Also, “my key code goes here” is found in your JW Player account/dashboard.

You will need to clearly substitute, “mediaspaceaaaa”, “http://mywebsiteexample.com/movies/aaaa.mp4”, “http://mywebsiteexample.com/movies/aaaa.jpg”, and the personal preference for the width and height.

NOTE: The downside here is that the WYSIWYG-compose tab will NOT work in Blogger since the <main></main> is not processed. So the only way you will see your video is by posting the post as public. The exception being the cloud-hosted player will show in the preview view, but not the self-hosted player. Oh well. Maybe someone can chime in here.

Lastly, WordPress (WITHOUT a plugin):

NOTE: I do NOT add the self/cloud hosted code/script to the <main> HTML. I added it to the beginning of each post, but only once, the top as you might have 3 videos in one post 🙂

NOTE: You will need to substitute “/jwplayer/jwplayer.js” with the relative path to the file on your local WordPress install/machine or absolute path (http://mywebsiteexample.com/jwplayer/jwplayer.js) if the file is located on another site/machine. Also, “my key code goes here” is found in your JW Player account/dashboard.

You will need to clearly substitute, “mediaspaceaaaa”, “/stuff/movies/SANY0315.flv”, “/stuff/movies/SANY0315.jpg”, and the personal preference for the width and height.

You will notice that the URLs for both “file” and “image” are relative. This URL is relative because the files are hosted on the same WordPress machine, otherwise you would need to provide the absolute full URL path, ex. “http://mywebsiteexample.com/stuff/movies/SANY0315.flv”

Lastly, if you intend to use HTML5 video, the safest codec/containers is mp4 H.264 with AAC audio. Make certain your mp4 file is “web optimized” (Handbrake) or faststart is enabled (FFmpeg). These encoders need the metadata at the beginning of the file:

Interlaced handbrake 0.9.8 support:
1) set to dvd preset
2) add :tff OR :bff in the advanced tab, put at end (append).
3) turn off all filters: set to off, set fps to same as source and constant.
Use mediainfo and set to sheet to find if tff or bff
4) feel free to set resolution, etc

This will allow your TV or device to perform the de-interlacing which is far superior than removing half the motion resolution as 98% people and/or software encoders do by default.

ATTN GOOGLE APPS CUSTOMERS: You need to manually add a temporary gmail account to your android phone (This would be under settings -> “Accounts & sync”, “Add account” -> “Google” -> “Next” -> “Create” -> etc…). Once that happens, you will see the button on the home screen of sipdroid to configure your PBXes account.

Use your temporary gmail account username and password. You will ALSO need to select a username for PBXes.org.

Once this process completes, you will now be able to use outbound calling ONLY since your temp account will NOT have a Google voice number, but who cares, keep reading…

Log into PBXes.org with your username you selected on registration an the password from your temp gmail account, re-read that twice.

Once you are in, select “trunks” from the left menu and click on “GTALK/tempgamail@gmail.com. From there, change your username and password from the temp gmail account to your Google apps account. Click “Submit Changes”.

From there you may have to reload Sipdroid, but outgoing and incoming calls should work fine. Be certain that Google Chat (your google apps mail address) is selected/enabled as a forwarded phone (inside Google Voice web portal) in order for inbound calling to work on Sipdroid.

Feel free to delete your temporary gmail account from Google’s site AND remove the account from your android phone as a sync account. This would be under settings -> “Accounts & sync”, select the temp gmail account, and touch “Remove account”. Cheers.

The above chart and cable are just for component video. You will also need to use either the RCA stereo audio cables that came with your XDS or connect to your TV or receiver with your own digital audio cable.

Pinout information here is:
1 = Ground, 2 = Red, 3 = Blue, 4 = Green. Also verified that it is the same as the component cable supplied with the WD TV Live and Live+ units. For reference, pin 1 being closest to the jacket and pin 4 being the tip of the jack.