Asus RT-AC68U – Original Firmware Install Procedure

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.

 

Tagged with:

Configure a Point-to-Site connection to a VNet using native Azure certificate authentication: Azure portal

https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal

Tagged with:

Connecting the Home Lab to Azure on the Cheap

http://www.jandjnet.com/connecting-the-home-lab-to-azure-on-the-cheap-6/

Tagged with:

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 1

 

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

Tagged with: ,

Step-By-Step: Configuring a site-to-site VPN Gateway between Azure and On-Premise

Step-By-Step: Configuring a site-to-site VPN Gateway between Azure and On-Premise

Tagged with: , ,

Site-To-Site Routed VPN Between Two or More Routers using dd-wrt/openvpn

Site-To-Site Routed VPN Between Two or More Routers using dd-wrt/openvpn

Tagged with: , ,

Windscribe – Setup Guides

https://windscribe.com/guides

Tagged with: ,

Build a .NET Core and SQL Database web app in Azure App Service on Linux

https://docs.microsoft.com/en-us/azure/app-service/containers/tutorial-dotnetcore-sqldb-app

Client-side SSL

Client-side SSL

For excessively paranoid client authentication.

Using self-signed certificate.

Create a Certificate Authority root (which represents this server)

Organization & Common Name: Some human identifier for this server CA.

openssl genrsa -des3 -out ca.key 4096
openssl req -new -x509 -days 365 -key ca.key -out ca.crt

Create the Client Key and CSR

Organization & Common Name = Person name

openssl genrsa -des3 -out client.key 4096
openssl req -new -key client.key -out client.csr
# self-signed
openssl x509 -req -days 365 -in client.csr -CA ca.crt -CAkey ca.key -set_serial 01 -out client.crt

Convert Client Key to PKCS

So that it may be installed in most browsers.

openssl pkcs12 -export -clcerts -in client.crt -inkey client.key -out client.p12

Convert Client Key to (combined) PEM

Combines client.crt and client.key into a single PEM file for programs using openssl.

openssl pkcs12 -in client.p12 -out client.pem -clcerts

Install Client Key on client device (OS or browser)

Use client.p12. Actual instructions vary.

Install CA cert on nginx

So that the Web server knows to ask for (and validate) a user’s Client Key against the internal CA certificate.

ssl_client_certificate /path/to/ca.crt;
ssl_verify_client optional; # or `on` if you require client key

Configure nginx to pass the authentication data to the backend application:

Using CACert Keys

 

 

Original posting: https://gist.github.com/mtigas/952344#client-side-ssl

Tagged with:

Install the Windows Subsystem for Linux

https://docs.microsoft.com/en-us/windows/wsl/install-win10

Top