Eighteen Lines, One PBX, and a Very Long Day Photo 1. Grandstream HT818 & HT802 for VoIP I already had a 2-port ATA in place, and for a while, that was enough. But as more phones started coming in—especially additional rotary phones, a pair of teletype machines, and a pair of crank phones being brought to life—it quickly became clear that two lines wasn’t going to cut it. I had been using a…

frkq Asus routers are painful, and open vpn isn't intuitive like a network appliance like a cisco router would work.

Most configuration is pushed server side including the satellite site routes.

ASUS OE firmware is dynamically generate each boot and apply so you have to work your configuration into the UI and jffs parition.

*Note I haven’t bother with security key authentication since its just a small test network

Topology

ASUS Router Headend 192.168.1.0/24

Ubuntu Raspberry PI Satelight. 192.168.200/24

UI

client-config-dir /jffs/openvpn/ccd      #jffs persistant partition  topology subnet client-config-dir ccd client-to-client username-as-common-name # Remote routes route 192.168.200.0 255.255.255.0 10.8.0.2 # These routes are pushed out to other connecting clients/site and hairpin via the headend push "route 192.168.200.0 255.255.255.0 10.8.0.1" #end

JFFS files *on the server side

filename -> site cn name

ifconfig-push 10.8.0.2 255.255.255.0

iroute 192.168.200.0  255.255.255.0

Satelight Client Config

topology subnet

route-metric 50

route 192.168.1.0 255.255.255.0

push "route 192.168.200.250"

push "route 192.168.200.0 255.255.255.0"

pull-filter ignore "route 0.0"

pull-filter ignore redirect-gateway

Running OpenVPN Client as a Service w PWD

/etc/systemd/system/openvpn-client.service

ExecStart=/usr/sbin/openvpn --suppress-timestamps --nobind --config /etc/openvpn/client.ovpn --auth-user-pass /etc/openvpn/login.conf

DNSMasq Forwarding Local Domain

Place autorun file on a usb drive to hack ASUS mount autorun script on boot.

/jffs/configs/dnsmasq.conf.add

server=/home.local/192.168.200.250

.asusrouter

#!/bin/sh

killall dnsmasq

cat /jffs/configs/dnsmasq.conf.add >> /etc/dnsmasq.conf

#DNS #caching and beyond, in #CentOS #RHEL 7 and 8. Clean use of #dnsmasq

By default, RHEL performs no DNS caching at all. Why this is so, is beyond mystery.

One could only guess that the rationale for lack of DNS caching in RHEL is the arguable efficiency for those systems which aren’t network connected or simply don’t need to make any DNS lookups.

There are of course such cases where you don’t need (many) DNS resolutions. I can think of:

a dedicated DB server

a…

( Original text by FEDERICO DE MEO )

I’ve been meaning to work on this little project for quite some time, but life got in the way and I was always too busy. Now I finally got some time back for myself and I’m here talking about it.

Quite some time ago I checked out the Wireless LAN Security Megaprimer course by Vivek Ramachandran (very nice, highly recommended) and incidentally in the same…

How to protect your systems from newly-discovered Dnsmasq vulnerabilities

Google recently announced that they have discovered seven new vulnerabilities in the Domain Name System software package Dnsmasq, which provides DNS name resolution services to translate domain names to their corresponding IP addresses for connectivity purposes. A post on the company’s security blog said that the team “found three potential remote code executions, one information leak, and three…