About QME Communications
QME Communications LLC is a network engineering practice in Cheltenham, PA. We design and operate IP and transport networks for internet service providers and regional telecommunications carriers, and we publish the reference configurations that come out of that work.
Why the catalogue exists
Carrier network configuration is largely tribal knowledge. A standard tells you that an external BGP speaker must not accept a route whose AS_PATH contains its own autonomous system number; it does not tell you which three lines of vendor syntax implement that on a particular software release, nor which operational command proves it is working. The gap between the standard and the running configuration is where outages come from.
We close that gap by publishing complete configurations with the reasoning attached. Each reference is something we have run in production or in a lab that mirrors production, stripped of customer identifiers and re-addressed into documentation space.
Editorial rules
| Validated, not theoretical | A reference is only published after the configuration has been applied to the stated platform and software version and the verification commands have been captured from the live device. |
|---|---|
| Complete | No elided sections, no "configure the rest as appropriate". If a reference needs a loopback interface, the loopback interface is in the text. |
| Sanitised | Addressing comes from RFC 5737 (IPv4 documentation prefixes), RFC 3849 (IPv6 documentation prefix) and RFC 6996 (private AS numbers). No customer name, no live address, no real credential ever appears. |
| Traceable | Settings that exist because a standard requires them cite the document and section. Settings that exist because of a platform quirk say so. |
| Defensive by default | References include the protective configuration that production needs — prefix limits, control-plane policing, authentication on routing adjacencies — rather than the minimum that makes a protocol come up. |
What we deliberately do not do
- We do not accept anonymous submissions and we do not host a public file store. Contributions arrive by email, are reviewed by a named engineer, and are published as edited pages under our own byline.
- We do not distribute vendor software, firmware images, licence keys or any other binary artefact. The catalogue is text.
- We do not publish material about defeating network controls. Configuration that exists to enforce a policy is in scope; configuration or technique aimed at evading one is not. See the acceptable use statement.
- We do not run advertising, behavioural analytics or third-party tracking. The site serves its own stylesheet and its own icon and nothing else.
Technical operation of the site
The catalogue is a static site. Pages are plain HTML generated from reviewed source, deployed by configuration management to a Linux virtual machine, and served by nginx over HTTPS with certificates issued by Let's Encrypt. Plain HTTP requests are redirected to HTTPS. There is no database, no server-side application, no user account system and no JavaScript, which is both a security posture and a deliberate simplification: there is very little on this site that can be attacked or misused.
Contact
Editorial correspondence, corrections and platform contributions: info@qmecom.com. Network abuse reports concerning this site or its hosting: abuse@qmecom.com. Security reports: security@qmecom.com or see /.well-known/security.txt. Postal address and telephone number are on the contact page.