James #FFFFFF jamesmacwhite

GL-MT6000 and Aquiss PPPoE Broadband

The following gist provides instructions on configuring an Aquiss PPPoE broadband connection on a GL-MT6000 Flint 2 router.

Note: This was tested from the stock firmware to flashing a vanilla OpenWrt 25.12.6 build (not the default GL.iNet firmware).

OpenWrt build: 25.12.6
Broadband: Aquiss Business Full Fibre 330/50 (Openreach)

General OpenWrt information for this router including flashing a vanilla OpenWrt build is available on the OpenWrt Wiki

Aquiss FTTP with OpenWrt

A guide for configuring an Aquiss FTTP connection on OpenWrt. There isn't much information specifically for Aquiss broadband and OpenWrt. The good news is that the setup is a typical PPPoE/DHCPv6 configuration.

Router used: Linksys WRT3200ACM
OpenWrt version tested: 21.02.3 r16554-1d4dea6d4f

ℹ️ This information has also been provided to Aquiss for inclusion in their customer knowledgebase for anyone else who uses a router running OpenWrt.

Prerequisites

Protecting Sonarr Calendar feed requests

It was recently discovered that Sonarr does not protect Calendar feed requests when authentication is disabled. This discovery has identified a slightly misleading behaviour because the calendar feed URL appends the apikey parameter in the UI, which could lead you to assume means it can only be accessed with the API key parameter set in the URL to your Sonarr API. This is however not the case. With authentication disabled, the calendar feed path does not require anything related to the API key to access and in fact you can access it without any URL parameters at all. What is slightly more confusing is other apps like Radarr have changed this behaviour to require the API key.

While having the calendar feed URL publicly available isn't too much of an issue in terms of security (given it's read only), it does mean that anyone can use it and this might not be desirable.

Authentication should typically not be disabled

Andrews and Arnold (AAISP) L2TP tunnel setup on OpenWrt

This is a guide for setting up the L2TP service from AAISP on an OpenWrt router. AAISP have an official OpenWrt guide for this but it is outdated and looks to have been originally written for OpenWrt 15.01/15.05 (Chaos Calmer), which is a long unsupported firmware build.

I have previously contacted AAISP about their documentation being out of date, however it has not been changed. It is technically not wrong, but under newer versions of OpenWrt you can simplify some of the configuration compared to the official documentation and there are also a few potential issues you might come across in OpenWrt land which are worth mentioning and saving someone else from bashing their head against a wall for hours, until you realise that the Linux kernel just hates you.

This has been tested on the latest stable OpenWrt 19.07 release branch.

	#!/bin/sh
	# mwan3-nft-update.sh
	#
	# Query GitHub releases for https://github.com/dl12345/mwan3 (and,
	# optionally, its companion https://github.com/dl12345/luci-app-mwan3),
	# find the .apk asset(s) matching this router, download to /tmp and
	# install with apk.
	#
	# Target: OpenWrt 25.12 (apk-based package manager). POSIX/ash only,
	# no bash-isms, no jq/curl assumed present.

	{
	"$schema": "http://json-schema.org/draft-07/schema#",
	"title": "Craft Cloud Config File",
	"type": "object",
	"required": [
	"php-version"
	],
	"properties": {
	"php-version": {
	"type": "string",

	blueprint:
	name: Update notifications
	description: Send notifications for new updates and install or skip on action
	homeassistant:
	min_version: 2022.4.0
	domain: automation
	input:
	update_entities:
	name: Update entities
	description:

	Windows Registry Editor Version 5.00

	[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727]
	"SystemDefaultTlsVersions"=dword:00000001
	"SchUseStrongCrypto"=dword:00000001

	[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
	"SystemDefaultTlsVersions"=dword:00000001
	"SchUseStrongCrypto"=dword:00000001

	Windows Registry Editor Version 5.00

	[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Client]
	"DisabledByDefault"=dword:00000001
	"Enabled"=dword:00000000

	[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server]
	"DisabledByDefault"=dword:00000001
	"Enabled"=dword:00000000