Editorial principles
Three rules govern what gets published. Primary sources first: every factual claim is checked against the manufacturer's documentation, the ISP's published technical specification, or the actual device. Where a manufacturer page contradicts the device label, we say so and explain which one we trust. Specifics over generalities: "most routers use admin/admin" is less useful than naming the brands that do and the brands that do not. We name them. Aged content is liability: credentials, default IPs, and firmware behaviour drift over time, so every page carries a "Last updated" stamp and goes back through review on a fixed cadence.
Where the data comes from
Different content categories use different source hierarchies.
- Router admin credentials and default IPs. First source: the manufacturer's official support documentation for the specific model series (TP-Link, ASUS, Netgear, Linksys, D-Link, Huawei, Xiaomi, Cisco, Tenda, ZTE, Mercusys, Ubiquiti, Belkin and 30+ others). Second source: physical device verification on commonly-deployed models. Third source: ISP firmware deployment notes when ISP-supplied units differ from retail. Conflicting reports between sources are flagged in the page text rather than hidden.
- IP address reference (RFC 1918, CIDR ranges, NAT behaviour). IETF RFC documents are the authoritative source. Where IETF terminology has shifted (e.g. RFC 6890 obsoleting parts of RFC 3330), the most recent governing RFC is cited.
- ISP-specific guides. Public technical specifications from the provider, customer-portal documentation, and field reports from the deployed gateways. VLAN tags, PPPoE handling, and DOCSIS provisioning are verified against the ISP's own engineering documentation where it is published, and from the gateway's admin panel where it is not.
- Speed test results and methodology. Where we publish throughput numbers, the measurement uses the open M-Lab NDT7 protocol. The speed test methodology page covers test parameters, server selection, and known limitations.
- APN settings. Carrier-published APN documentation, MCC/MNC values from the GSMA registry, plus device-side verification where the carrier's documentation is ambiguous.
Review and update cadence
Pages enter the publication pipeline as drafts. A second editor reviews each draft against the primary sources before the page is marked live. Once live, content is reviewed for currency on a fixed schedule:
- Every 6 months for ISP-specific pages, because plans, gateway models, and credentials change frequently with each provider refresh cycle.
- Every 12 months for router brand pages, default IP references, and networking concept articles. Firmware revisions can change default behaviour, so the annual sweep is non-negotiable.
- As needed when a reader correction comes in, a manufacturer publishes a firmware advisory, or an ISP announces a gateway swap. Out-of-cycle updates are stamped with the same "Last updated" mechanism.
Every page on the site carries the last-reviewed date in the byline. If a date looks stale relative to the cadence above, the page is overdue and the corrections inbox is the fastest way to flag it.
Corrections
If you find a mistake, send it to editor@hanoilug.org with the page URL and the specific correction (ideally with a primary-source link). Factually-wrong content gets fixed within 7 days; the byline date is bumped at the same time. We do not silently re-edit corrections: when a page changes materially, the diff is referenced in the next byline update.
Conflicts of interest
HanoiLUG does not currently run affiliate links, sponsored placements, or paid product reviews. Recommendations of one router, ISP, or tool over another are based on the testing or sourcing described in the page itself. If this changes, the relationship will be disclosed on every affected page and listed here.
What we do not do
HanoiLUG is not a help desk and does not provide individual troubleshooting. If your specific router is not working, the brand directory, IP directory, and ISP guides cover the diagnostic paths; beyond that, the manufacturer's support line or your ISP's support are the right escalation. The contact page covers what kinds of inquiries we do respond to.
We also do not publish lists of credentials or exploits intended to bypass authentication on networks you do not own. The default-credential content exists so that the legitimate owner can recover access and immediately rotate the password.