These are taggart’s openwrt notes (for lack of a better place to put them).
This is sort of a “cerowrt lite” that gets you some of the recent innovation but still on openwrt where you can update to newer releases if you need to get particular things faster than they go into “cerowrt”.

Setting up openwrt with SQM


login and initial setup

openwrt base images are designed to be very minimal and then you add the things you need. The first thing we need to do is get logged in, setup password, ssh, and install the web UI (luci).

setup wireless

setup firewall

Other stuff

SQM – Smart Queue Management

Modern network devices suffer from a few problems that can periodically make the network completely unusable, generally referred to as Bufferbloat. The combination of large buffers on network devices (in your computer, the wireless access point, the router, etc), assymetric ISP network bandwidth(usually large download/small upload, and poor algorithm performance in the face of multiple users can cause serious, multi-second delays. This is particularly bad for things that need low latency like voice/video conferencing, network games, etc.

Lots of smart people figured this out and solved it (first in cerowrt, now available in openwrt and the Linux kernel). The solution is referred to as “Smart Queue Management” (aka SQM) and is a combination of:


The IETF released a document, called “Best Current Practices 38” (aka BCP38) that recommends all networks filter their outbound traffic to stop traffic with sender addresses that are not from their network. This is needed because hackers take over computers and use them to inject this illegitimate traffic in order to attack others. If everyone on the internet implemented BCP38 in their networks, it would really cut down on these sorts of attacks. It’s easy to setup so everyone should do so as part of being a good internet citizen.

Site specific stuff


Adding additional APs

If you have wired backhaul, setting up multiple wireless access points to provide the same ESSID and allow clients to seamlessly roam does not require any special setup, the roaming stuff is built in to the clients. All that is needed is for the access points’ wireless and wired switches to be on the same network, and only have one DHCP server and the other APs are just dumb devices that aren’t doing any routing/firewalling/dhcp/etc. Here is a good article explaining the details.

NOTE: if you don’t have wired backhaul and want to use the wireless itself as
backhaul then you need something like WDS.

Setting up additional AP