Asus RT-AC68U – Original Firmware Install Procedure

Posted on January 21, 2018 by Angel

This is the procedure to recover to the original firmware after unsuccessful firmware update (courtesy of dd-wrt.com)

Preparation:

1) On a Microsoft windows computer download and install the ASUS recovery tool from:http://www.asus.com/Networking/RTAC68U/HelpDesk_Download/

2) Download the original Asus stock firmware from: http://www.asus.com/Networking/RTAC68U/HelpDesk_Download/

3) Set your windows network settings to a static IP of 192.168.1.5, and subnet 255.255.255.0 (Gateway and DNS not needed).

Recovery Mode Flashing Instructions:

1) Power off the unit.

2) Press and hold on to the WPS button.

3) While holding down the WPS button, power on the unit.

4) Keep holding the WPS button until the power led starts to blink a few times.

5) When the power led starts blinking / flashing, release the WPS button.

6) Power off the unit.

7) Press and hold on to the reset button.

8) While holding down the reset button, power on the unit.

9) Keep holding the reset button until the power led starts to blink on and off repeatedly. (This means the unit is now in emergency recovery mode)

10) Plug in your computer with the ASUS recovery tool directly into Lan port 1 on the router.

11) Run the ASUS Recovery software, and select the stock Asus firmware.

12) Click the “Upload” button.

13) The ASUSrecovery software should detect the router, and start to upload the firmware.

If the ASUS recovery software doesn’t detect the router, try disabling your windows firewall, and also disabling and then re-enabling your network adapter in windows networking settings.

14) Once the router has flashed and rebooted with the stock firmware, set your network adapter settings back to DHCP. Your computer should pick up an address from the router, and then you can navigate to 192.168.1.1 in the web browser to start re-configuring the router.

ON-PREMISES SITE 2 SITE VPN WITH AZURE USING TOMATO SHIBBY MOD (ENTWARE-NG AND STRONGSWAN SETUP) – PART 1

Posted on January 20, 2018 by Angel

On-Premises Site 2 Site VPN with Azure using Tomato Shibby Mod (Entware-ng and Strongswan setup) – part 1

On-Premises Site 2 Site VPN with Azure using Tomato Shibby Mod (Entware-ng and Strongswan setup) – part 2

Windscribe – Setup Guides

Posted on January 1, 2018 by Angel

https://windscribe.com/guides

NFC Ring

Posted on December 12, 2017 by Angel

http://www.instructables.com/id/NFC-Ring/?utm_source=newsletter&utm_medium=email

Letsencrypt + Certbot

Posted on April 27, 2017 by Angel

Letsencrypt provides free SSL certificates

Certbot automates re-newal and installation of the certificates

Install Certbot:

$ sudo add-apt-repository ppa:certbot/certbot
$ sudo apt-get update
$ sudo apt-get install python-certbot-apache

Generate and install the certificate

$ certbot --apache

Generate the certificate only

$ certbot --apache certonly

Generate wildcard certificate

$ sudo certbot certonly --manual --preferred-challenges=dns --email yourname@yourdomain.com --server https://acme-v02.api.letsencrypt.org/directory --agree-tos -d *.yourdomain.com

Renewal

The Certbot packages on your system come with a cron job that will renew your certificates automatically before they expire. Since Let’s Encrypt certificates last for 90 days, it’s highly advisable to take advantage of this feature.

$ sudo certbot renew --apache

Your connection is not private

Posted on February 12, 2017 by Angel

Update 2/19/2017: I got a new certificate from www.sslforfree.com Now the site should work with all browsers.

If you were trying to access my blog recently with Google Chrome or Mozilla Firefox the chance is you have seen this warning:

Please, do not get alarmed – I am not trying to steal your information as Google suggests.

I am using a SSL certificate issued by StartCom (www.startssl.com)

StartCom was bought by company called WoSign. Google found that WoSign ” have not maintained the high standards expected of CAs and will no longer be trusted by Google Chrome”. Read the full story here: Distrusting WoSign and StartCom Certificates

If you use Internet Explorer you will not see this warning (as of today 2/12/2017).

In fact if you use online SSL checkers you will see there is no problem with the certificate. These are just some of them:

SSLShopper

DigiCert

SSLLabs

The issue is that Google decided to punish WoSign and I have certificates issued by their daughter company StartCom.

At this moment I am not sure what I am going to do. I have multiple web sites and purchasing certificates from another (trusted) company can be expensive. Alternatively I might opt to not using SSL and HTTPS at all.

Until I decide what to do my suggestion to you is to use Internet Explorer when accessing my sites. Thanks!