https://blog.apnic.net/2021/10/28/openbsd-part-1-how-it-all-started/ Skip to content * Blog search [ ] Search Advanced Whois * Advanced Whois * Make a payment * Hi ! + MyAPNIC Dashboard + Personal Settings + Logout * Login * Select APNIC Direction + APNIC + Training + Academy + Blog + Internet Directory + NetOX + DASH APNIC APNIC home * Get IP + Get IP Addresses / ASN + Make a payment + Membership + FAQs * Manage IP + MyAPNIC + Transfer IP and ASNs + Using Whois + Go IPv6 + Reverse DNS + Routing Registry + Make a payment + FAQs * Training + About + Events + Courses + Sponsor + Fees + Videos + Community Trainers + APNIC Academy * Events + Conferences + Calendar + Sponsorship + Code of Conduct * Research + Labs + Internet Directory * Community + Policy Development + Addressing policies + Internet community + Code of Conduct + Technical Assistance + Root servers + Security at APNIC + ISIF Asia + APNIC Foundation + NRO NC + Mailing lists * Blog * Help Centre * About + APNIC Region + APNIC Membership + Executive Council + Service updates + Team + Annual Reports + Transparency + APNIC Survey + Corporate Documents + Publications Archive + Careers + Glossary * Contact * Select APNIC destination + APNIC + Training + Academy + Blog + Internet Directory + NetOX + DASH * Login Skip to the article What every IT person needs to know about OpenBSD Part 1: How it all started By Peter Hansteen on 28 Oct 2021 Category: Tech matters Tags: Guest Post, history, security, tools Tweet Blog home [OpenBSD_pufferfish_banner] 'Functional, free and secure by default', OpenBSD remains a crucial yet largely unacknowledged player in the open-source field. This series aims to highlight the project's signature security features and development practices -- razor-sharp focus on correct and secure code coupled with continuing code audit -- as well as the project's role as a source of innovation in security practices and an 'upstream' source for numerous widely-used components such as OpenSSH, PF, LibreSSL and others. This post will focus on the history, Part 2 will focus on usage and user experience, and Part 3 will look at that packet filter. If you only have a few minutes to spare, the highlights are: * OpenBSD has been around for more than 25 years (started October 1995). * OpenBSD is proactively secure with only two remote holes in default install in all those years. * OpenBSD pioneered using strong cryptography, the first free system to ship with IPSec (entangling itself in US export regulations in the process). * OpenBSD pioneered and is still leading in code audit, fixing similar bugs tree-wide when found. * OpenBSD has all security enhancements enabled by default, which are hard, going on impossible, to disable. * OpenBSD is open-source, free software and the project actively encourages independent verification of code quality and security. * Today, OpenBSD is used in many network-centric roles, even though it is a general-purpose operating system albeit with a particular emphasis on security. * OpenBSD has a high profile quality image based on actual code quality and proven performance in real-world use. * OpenBSD is the upstream (origin) for several widely used pieces of software such as OpenSSH, OpenBGPD, PF, OpenSMTPd, LibreSSL, iked, mandoc and several others. For a complete list, please see the OpenBSD Innovations page on the OpenBSD website. * OpenBSD has been 'growing up in the public' with code generally accessible via anonymous CVS (the first of its kind) since 1995 (transparent process, development discussions on public tech@ mailing list). * Developers would do well to study high quality (mainly) C-source and how the project runs a six-month release cycle like clockwork (with only a few notable exceptions). Note: If you are more of a slides person you will be happy to hear that indeed the presentation I used for this when given as a talk is available with the main highlights and little to no geek jokes. Now with that out of the way, let's step back to where it all started. OpenBSD: How it all started OpenBSD's history is, to a large extent, the history of the Internet itself. You may have heard of the time back in the 1980s when the likes of IBM and Digital were slugging it out in the corporate IT sphere and the US Department of Defense paid for experiments in distributed, device-independent networking. That's when a loosely organized group of hackers somewhat coordinated by researchers at the University of California's Berkeley campus rose to prominence with BSD Unix, which by a sequence of happy accidents, became the home of the reference implementation of the TCP/IP Internet protocols. By the early 1990s, commercialization of the Internet had started, and the Berkeley Computer Science Research Group (CSRG) that had coordinated the efforts was set to be disbanded. In addition to the net itself, the main tangible product out of Berkeley was the Berkeley Software Distribution (BSD), often distributed on tapes in the mail but also available on the net, which had started as a collection of software for AT&T's Unix but had over the years been extended to become a full-featured Unix operating system. Several different groups wanted BSD to go on even if the CSRG did not, and several things happened in fairly rapid succession: * Lynne and Bill Jolitz ported BSD to Intel x86 (actually 80386sx), creating 386BSD. This was chronicled in a series of articles in Dr Dobbs' Journal. * Next up, hackers started sharing improvements to the 386BSD code as 'patchkits', and two separate groups took the work further to form their projects -- the FreeBSD group would be working on bringing the best possible BSD to PC-style hardware, while the NetBSD group's ambition was to make BSD run on any hardware they could get their hands on. The two groups were only vaguely aware, if at all, that the other existed during the early days. * A group of former CSRG employees formed BSDi Inc. and marketed their product BSD/386 with, among other things, a contact phone number '1-800-ITS-UNIX'. The activities of an actual corporation, in turn, triggered a lawsuit from the owners of the UNIX trademark over code copyrights. The lawsuit was eventually settled -- only six files of several thousand in the tree were 'potentially encumbered' and had to be replaced, leaving both NetBSD and FreeBSD with a rush to replace the code. If I remember correctly, this was at least, in part, fairly central to the virtual memory subsystem. OpenBSD came into existence a couple of years later, from a fork of the NetBSD code base in October 1995, with the initial release in July 1996. From the very start, the OpenBSD project has been running a code audit of the entire tree, focusing on code correctness and security. We want secure, correct code that makes up a usable system with sane defaults and complete and readable documentation. And we want that code to be available under a free license and available to the world as soon as it is committed to the project's version control. One of the early achievements of the OpenBSD project was anonymous CVS, which makes it possible for anyone on the Internet to get the code with changes in near real-time. This was a major break with the normal practice of most projects of the time, which would typically work in relative isolation on private mailing lists, and at quasi-random intervals issue a release as a tarball on an FTP server somewhere. You are already an OpenBSD user! It is probably useful at this point to reveal that even if you do not know it, you are more likely than not using code with an OpenBSD origin right now. Your Apple product, be it an iPad, iPhone or Mac, your Android device, your Cisco router, Solaris, Linux or other Unix or even your Microsoft product has some or a lot of OpenBSD originated code in it. We will get back some detail on that later. OpenBSD: Code audit and security evolution The code audit activity runs roughly like this: * Read the code, understand what it does. * Look for unsafe behaviours, assume a hostile environment. * When you find a bug and fix it, look for similar code elsewhere in the tree and fix it everywhere. You will be amazed how much different programmers think alike and make the same mistakes. Wash, rinse, and repeat. That may sound somewhat unexciting, but careful study of how the code performs in real-life situations led to several innovations over the years, with a strong slant for being proactively secure, making it harder for bugs to do damage: * W^X -- memory can be writeable XOR executable. * Address space randomization (ASLR) so the jump targets and gaps will vary for each execution. * Random-sized gaps were inserted in the stack, again catching fixed-sized returns. * Unreadable, unwriteable guard pages at the end of malloc()ed chunks to catch overruns. * Privilege separation -- daemons run the bulk of their code as a non-privileged user, more likely than not in a shell-less chroot, coupled with privilege revocation, which means that daemons drop privilege as soon as possible. * The pledge(2) system call to declare a profile to restrict program behaviour to only specified operations and resources. * The unveil(2) system call to restrict file system access to specified paths and permissions only. * A fairly user-visible change came when OpenBSD 6.2 introduced the kernel address randomized link, or KARL, which sees to it that the kernel is relinked to a new, randomized layout for each boot. Once again, introducing randomness where none had been before is seen as a way to mitigate possible exploits based on code loading at predictable addresses. All of those features have been integrated into the OpenBSD source tree, and with the developers admonished to adhere to the rule 'where it is possible to spot damage, fail hard', poorly written software will crash a lot more often on OpenBSD than elsewhere. That in itself should make the platform attractive to developers. Exposing your code to a hostile environment and see it perform or fail can be quite entertaining and enlightening. Usable, portable and secure To complete the picture, it is useful to keep in mind that OpenBSD runs on a total of 14 platforms. All platforms are self-hosting. Cross-compiling is only used in the early phase of porting to a new platform. And, of course, in addition to purely maintaining existing code to run on diverse platforms, users and developers have real-world needs that are addressed by developing new software, extending the features of existing programs, adding new functionality or even replacing programs or entire subsystems. Security is a many-faceted topic. Early on, OpenBSD stood out as the system that included real crypto in the base system, to the extent that exporting OpenBSD source code from the US was technically illegal under its munitions export restrictions as they were defined at the time. Fortunately for us, the project was always coordinated from Canada by undisputed project leader Theo de Raadt. There is anecdotal evidence that US-based developers would trek across the border for hackathons with clean slate equipment to install OpenBSD while in Canada and hack -- that is, work on the system -- and would then legally bring the result back with them. One early application of crypto in OpenBSD was when a full IPSEC stack was included in the system in 1997. OpenBSD was the first free system to include IPSec by default in its base install. In a prime example of hacker humour of the time, a t-shirt featuring one of the early appearances of Puffy the blowfish that would become the project mascot touted the Blowfish password hashing algorithm. This remains the default on OpenBSD both with the picture caption 'So long and thanks for all the passwords' just below Puffy on the front, along with the full source code of the blowfish function on the back. Image showing Blowfish - the icon for OpenBSD.Figure 1 -- Hacker humor at its finest. The expectation was that the t-shirt would be illegal to re-export from the US. In addition to attention to security and code-correctness, one other important feature of OpenBSD is attention to intellectual integrity and insisting on clearly worded and unambiguous license to use and modify code and documentation that forms part of the system. That brings us to why OpenBSD is better for users and developers. I'll talk about that in Part 2. Peter N. M. Hansteen is a puffyist, daemon charmer and penguin wrangler. Adapted from original post which appeared on BSDLY. Rate this article --------------------------------------------------------------------- The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog. Leave a Reply Cancel reply Your email address will not be published. Required fields are marked * [ ] [ ] [ ] [ ] [ ] [ ] [ ] Comment[ ] Name * [ ] Email * [ ] Website [ ] [ ] Save my name, email, and website in this browser for the next time I comment. [ ] Yes, add me to your mailing list [ ] [Post Comment] Top Get Updates Please leave this field empty[ ] [ ] Show options [Subscribe!] Select list(s):[ ] Daily[*] Weekly Thanks for subscribing! Check your inbox or spam folder to confirm your subscription. Authors * Geoff Huston * Paul Wilson * A Khalil Azizi * AbdelRahman Abdou * Abhishek Jain * Achie Atienza * Adam Gosling * Adam McFillin * Adam Oest * Adeel Sadiq * Adiel Akplogan * Adisorn Lertsinsrubtavee * Adli Wahid * Adrian Wan * Afifa Abbas * Afsheen Saadat * Aftab Siddiqui * Agustin Formoso * Ahmad Darki * Ajay Kumar * Akimichi Ogawa * Alan Mauldin * Alden Hilton * Alec Muffett * Alex Band * Alex Boten * Alex Turing * Alexander Azimov * Alfred Arouna * Ali Abedi * Ali Norouzi * Amaury Van Bemten * Amrita Choudhury * Anand Buddhdev * Anant Shah * Andre Gelderblom * Andreas Dewes * Andreas Reuter * Andree Toonk * Andrei Robachevsky * Andrew Campling * Andrew Cushen * Andrew Gray * Andrew Sullivan * Andrew Toimoana * Andy Mindnich * Andy Newton * Anju Mangal * Anna Maria Mandalari * Annaliza Mulingbayan * Anosh Khan * Anriette Esterhuysen * Anthony Lee * Anup Changaroth * Anurag Bhatia * APNIC * Apoorv Shukla * Arash Molavi Kakhki * Arian Niaki * Aris Tzermias * Arjuna Sathiaseelan * Arth Paulite * Artyom Gavrichenkov * Asad Ali * Asanka Sayakkara * Ashil Oogarah * Ashwin Kumar * Ashwin Rangan * Audrey Randall * Aurelien Aptel * Austin Hounsel * Avery Pennarun * Ayesha Iftikhar * Ayush Mishra * Azfar Adib * Azhar Khuwaja * Azura Mat Salim * Baojun Liu * Baptiste Jonglez * Barry Greene * Bart Hogeveen * Basileal Imana * Ben Cox * Benjz Gerard Sevilla * Benno Overeinder * Bert Hubert * Bhadrika Magan * Bhumika Sapkota * Bikram Shrestha * Bill Hess * Bill Stearns * Bill Woodcock * Blake Anderson * Brenda Buwu * Brenden Kuerbis * Brent Carey * Brian Carpenter * Brian Nisbet * Brian Trammell * Byron Ellacott * Byungjin Jun * Cameron Steel * Carsten Strotmann * Caspar Schutijser * Cecilia Testart * Cengiz Alaettinoglu * CF Chui * Champika Wijayatunga * Che-Hoo Cheng * Cheeyong Tay * Cherie Lagakali * Chia Ling (Jolin) Chan * Chika Yoshimura * Ching-Heng Ku * Chris Amin * Chris Ritzo * Christoph Dietzel * Chuan Jiang * Ciprian Popoviciu * Clarence Filsfils * Claudio Jeker * Clemens Mosig * Colin Perkins * Constance Bommelaer * Constanze Dietrich * Craig Ng * Craig Rowland * Dale Roberts * Dan Fidler * Daniel Kopp * Danilo Giordano * Danny Alex Lachos Perez * Danny Pinto * Daryll Swer * Dave Mill * David Dawson * David Holder * David Holsgrove * David Huberman * Dean Pemberton * Debopam Bhattacherjee * Denesh Bhabuta * Dennis Baaten * Desiree Miloshevic * Dewangga Alam * Dewole Ajao * Dhruv Dhody * Di Ma * Diego Pino Garcia * Donatas Abraitis * Doug Madory * Doug Montgomery * Dr Bahaa Al-Musawi * Dr Govind * Drikus Brits * Duane Wessels * Duncan Macintosh * E. Marie Brierley * Edward Lewis * Edwin Sandys * Eliot Lear * Elizabeth Krumbach Joseph * Elly Tawhai * Elvin Prasad * Emile Aben * Emily Stark * Emir Beganovic * Eneken Tikk * Enno Rey * Enric Pujol * Eric Lawrence * Eric Loos * Eric Vyncke * Erik Hjelmvik * Erik Rye * Erin Scherer * Eshaan Bansal * Eunju Pak * Fabian Bustamante * Fakrul Alam * Farha Diba * Ferenc Fejes * Fernando Gont * Flavia Salutari * Florentin Rochet * Florian Streibelt * Foy Shiver * Franck Martin * Frane Maroevic * Frank Denis * Frank Herberg * Franziska Lichtblau * Fred Christopher * Ganga R Dhungyel * Gaurab Raj Upadhaya * Gautam Akiwate * Gavin Reid * Geoff Huston * George Kuo * George Michaelson * George Odagi * George Sadowsky * Gianmarco Pagani * Giovane Moura * Gonchig Altansukh * Greg Ferro * Gregory Mounier * Guangliang Pan * Guillermo Baltra * GZ Kabir * Ha Dao * Han Zhang * Hannah Durack * Harish Chowdhary * Helen Hollins * Hideyuki Sasaki * Hinne Hettema * Hiroki Kawabata * Hiroko Kamata * Hiromu Shiozawa * Hisham Ibrahim * Hoang Nguyen Phong * Houlin Zhao * Ignacio Castro * Ihita Gangavarpu * Ike Kunze * Ilker Nadi Bozkurt * Imtiaz Rahman * Ioana Livadariu * Italo Cunha * Ivan Ristic * Ivana Tomic * Ivo A. Ivanov * Ivy Yip * Izumi Okutani * Jaclyn Knight * Jahangir Hossain * Jake Bauer * Jake Flint * Jake Holland * James Ah Wai * James Pavur * James Richards * James Shank * Jamie Gillespie * Jan Harm Kuipers * Jan Ruth * Jan Zorz * Jari Arkko * Jason Livingood * Jason Smith * Jasper den Hertog * Jawad Ahmed * Jay Daley * Jay Ford * Jeff Fry * Jeff Man * Jen Linkova * Jenine Beekhuyzen * Jerry Lundstrom * Jessica Shen * Jessica Wei * Jethro Webston * Jia-Rong Low * Jim Forster * Jim Vella * Jimmy Lim * Jing Qiao * Joanna Kulesza * Joao L. Sobrinho * Joao Luis Silva Damas * Joao M. Ceron * Job Snijders * Joel Jaeggli * Johanna Amann * Johannes Krupp * Johannes Weber * John Bambenek * John Garrity * John Jack * John Kristoff * John Scudder * John Welborn * Jonathan Brewer * Jordan Carter * Jordan Jueckstock * Jordi Palet Martinez * Josef Gustafsson * Joseph Salowey * Joy Chan * Joyce Chen * Juan Ramon Santana * Juha Saarinen * Julian Martin Del Fiore * Julien Gamba * Jun Murai * Kaajal Kumar * Kaan Onarlioglu * Kanagaraj Krishna * Karel Hynek * Karl Lovink * Kasek Galgal * Kashyap Thimmaraju * Kathleen Moriarty * Katsuyasu Toyama * Kazunori Fujiwara * Ke Ma * Keisuke Kamata * Kemal Sanjta * Kenjiro Cho * Kenny Huang * Kensuke Fukuda * Kevin Bock * Kevin Ku * Kevin Meynell * Kevin Vermeulen * Kevon Swift * Khee Hong Loke * Klee Aiken * Kobayashi Masayuki * Koichi Kunitake * Koki Nakagawa * Konrad Wolsing * Korian Edeline * Kostas Zorbadelos * Kris Shrishak * Kurt Lindqvist * Kyle Drake * Kyle Schomp * Lan Wei * Lars Prehn * Lars-Johan Liman * Leandro Bertholdo * Leandro Navarro * Lee Howard * Leo Vegoda * Leonid Todorov * Leslie Daigle * Lia Hestina * Liangcheng Yu * Linjian Song * Lisa Corness * Lisandro Ubiedo * Lorenzo Cogotti * Louise Tromp * Luca Sani * Luuk Hendriks * Maarten Botterman * Maciej Korczynski * Madeline Carr * Maemura Akinori * Mai Thu Thuy * Major Hayden * Manaf Gharaibeh * Mansour Ganji * Marc Bruyere * Marcin Nawrocki * Marco Chiesa * Marco Cilloni * Marco Hogewoning * Marcus Keane * Mariko Kobayashi * Marilyn Zhang * Mario Loffredo * Mark Andrews * Mark Karpilovskij * Mark Nottingham * Mark Prior * Mark Smith * Markus Dahlmanns * Markus Legner * Marten Porte * Martin Hannigan * Martin Hoffmann * Martin Langer * Martin Thomson * Martin Winter * Mary Rose Ofianga-Rontal * Masataka Mawatari * Massimo Candela * Mat Ford * Matt Larson * Matt Oh * Matt Palmer * Matt Ringel * Matt Stith * Matthew Thomas * Matthias Wichtlhuber * Mattijs Jonker * Maxime Mouchet * Md Abdul Awal * Megan Baker * Melchior Aelmans * Merike Kaeo * Metin Acikalin * Michael Kende * Michael Rabinovich * Michael Schapira * Mika Kerttunen * Min Sung Jung * Miwa Fujii * Mohamad Dikshie Fauzie * Mohamed Boucadair * Mohammad Larosh Khan * Molay Ghosh * Moritz Muller * Mubashir Sargana * Muhammad Moinur Rahman * Muhammad Yasir Shamim * Muzamer Mohd Azalan * Nadir Hassan * Nafeez Islam * Nalini Elkins * Narayan G * Narelle Clark * Natale Bianchi * Nate Sales * Nathalie Trenaman * Neta Rozen Schiff * Nick Buraglio * Nick Hilliard * Nick Janetakis * Nico Schottelius * Nicola Rustignoli * Nicole Wajer * Nihit Tandon * Nikolai Hampton * Nikos Kostopoulos * Nirav Atre * Nurul Islam Roman * Nusenu * Nyamkhand Buluukhuu * Oky Tria Saputra * Olafur Gudmundsson * Olamide Omolola * Oliver Gasser * Oliver Michel * Olivier Tilmans * Ondrej Caletka * Ondrej Sury * Otto Moerbeek * Pablo Hinojosa * Paresh Khatri * Parkpoom Tripatana * Pasan Lamahewa * Patrick McManus * Patrik Faltstrom * Paul Dale * Paul Wilson * Pawel Foremski * Pawel Urbanek * Pedro Marcos * Pengxiong Zhu * Pete Sclafani * Pete Stevens * Peter Blee * Peter Hansteen * Peter Maynard * Peter Peele * Petr Spacek * Phil Lavin * Phil Mawson * Philip Homburg * Philip Paeps * Philip Smith * Philipp Richter * Pier Carlo Chiodi * Piotr Kijewski * Platon Kotzias * Pranav Kondala * Praneet Kaur * Pubudu Jayasinghe * Quincy Liao * Rafael Cintra * Raffaele Sommese * Raffaele Zullo * Rajnesh Singh * Ralph Dolmans * Ram Sundara Raman * Ramakrishna Padmanabhan * Rami Al-Dalky * Ran Ben Basat * Ranysha Ware * Raquel Rugani Lage * Raskia Nayanajith * Ray Bellis * Rebekah Houser * Remi Gacogne * Rene Bakker * Rene Wilhelm * Renee Burton * Richard Cziva * Richard Jimmerson * Richard Nelson * Richard Patterson * Richard Read * Rick McElroy * Robbie Mitchell * Robert Kisteleki * Roderick Fanou * Rohana Palliyaguru * Roland van Rijswijk-Deij * Romain Fontugne * Ron Bonica * Ron Winward * Ronald van Kleunen * Roy Arends * Rudiger Birkner * Russ White * Ryan Beckett * Sachin Ashok * Said Jawad Saidi * Said Zazai * Salvatore Cuzzilla * Samit Jana * Samuel Steffen * Sandra Davey * Sandra Siby * Sanjaya * Sara Dickinson * Sarah Escandor-Tomas * Sarmad Hussain * Sarvesh Mathi * Sasha Romijn * Satoru Matsushima * Satoru Tsurumaki * Scott Hollenbeck * Sebastian Castro * Sebastian Zander * Seiichi Kawamura * Seluvaia Kauvaka * Shah Sahari * Shahee Mirza * Shamim Reza * Shamsullah Shams * Shane Alcock * Shane Kerr * Sheetal Kumar * Sheikh Md Seum * Shermaine Yung * Sherry Shek * Sheryl Hermoso * Shian-Shyong Tseng * Shinoj Pittandavida * Shuai Hao * Shucheng Liu * Shumon Huque * Shusei Tomonaga * Siena Perry * Simon Baroi * Simon Bauer * Simran Patil * Siva Kesava * Sivaram Ramanathan * Sofia Silva Berenguer * Sonam Keba * Song Bing * Spiros Thanasoulas * Srikanth Sundaresan * Srimal Andrahennadi * Stanley Osao * Steinthor Bjarnason * Stephan Marwedel * Stephane Bortzmeyer * Stephen McQuistin * Stephen Ryan * Stephen Strowes * Steve Santorelli * Sue Graves * Suetena Faatuuala Loia * Suksit Sripitchayaphan * Sunny Chendi * Susan Forney * Svaradiva Devi * Swapneel Patnekar * Sylvain Cortes * Sylvia Cadena * Taejoong Chung * Taiji Kimura * Talha Paracha * Tan Kean Siong * Tashi Phuntsho * Teav Sovandara * Theo Jepsen * Theophilus A. Benson * Thomas Holterbach * Thomas Koch * Thomas Millar * Thomas Patzke * Thomas Scheffler * Thomas Wirtgen * Thymen Wabeke * Tim Bruijnzeels * Tim Fiola * Tim Raphael * Timm Bottger * Timothy Winters * Tobias Fiebig * Todd Arnold * Tom Barbette * Tom Carpay * Tom Do * Tom Harrison * Tom Hollingsworth * Tom Perrine * Tomas Krizek * Tomek Mrugalski * Tomoaki Tani * Tony Finch * Tony Li * Tony Scheid * Tony Smith * Torsten Zimmermann * Trinh Viet Doan * Truong Khanh Huyen * Tuan Nguyen * Tugsorshikh Badarch * Ulrich Speidel * Usama Naseer * Uta Meier-Hahn * Vashkar Bhattacharjee * Vasileios Giotsas * Vasileios Kotronis * Vasilis Chryssos * Veronika McKillop * Vesna Manojlovic * Vicky Risk * Vijay Sivaraman * Vijay Varadharajan * Vincent Bernat * Vittorio Bertola * Vivek Nigam * W K Shiu * Wanqing Tu * Warren Finch * Warren Kumari * Wassie Goushe * Wayne Thayer * Werachart Muttitanon * Wes Hardaker * Wilaiwan Phanarin * Wilhelm Boeddinghaus * Willem Toorop * William Lu * Willy Sutrisno * Winfried Tilanus * Wita Laksono * Wout de Natris * Wouter de Vries * Xiaohong Deng * Xiaoqi Chen * Xing Li * Yali Liu * Yeo Lee Chin * Yi Cao * Ying-Chu Chen * Yoshibumi Suematsu * Yoshitaka Aharen * Younghwan Choi * Yuedong Zhang * Yurie Ito * Yuta Takata * Zachary Bischof * Zaid Ali Kahn * Zaifeng Zhang * Zen Ng * Zhenyu Li * Zinan Lin * Zolzaya Shagdar * More Tags * APNIC Foundation * APNIC Training * ASNs * Australia * BGP * capacity development * CERTs * China * DNS * DNSSEC * Event Wrap * Guest Post * How to * IANA * ICANN * IETF * IGF * India * Indonesia * Internet Governance * Internet of Things * IPv4 * IPv6 * ISIF Asia * ITU * IXPs * Japan * measurement * networking * NOGs * NRO * Pacific * peering * Policy * RIPE NCC * RIRs * ROAs * routing * RPKI * security * Taiwan * TCP * Thailand * Three of the best * Whois Related Articles * How to: Getting started with Kea DHCP for IPv4 / IPv6How to: Getting started with Kea DHCP for IPv4 / IPv6 by Tomek Mrugalski March 6, 2020 Guest Post: Kea is an open-source DHCP server developed by the authors of ISC DHCP. * All the Gs, part 1: Governing the radio spectrumAll the Gs, part 1: Governing the radio spectrum by George Michaelson October 27, 2021 To understand broadband cellular network technology, it's important to appreciate the history of the radio spectrum. * Everything you wanted to know about LEO satellites, part 2: Constellations, gateways and antennasEverything you wanted to know about LEO satellites,... by Ulrich Speidel May 27, 2021 Guest Post: In part 2 of the LEO series, Ulrich Speidel examines some questions worth asking of LEO providers. * Everything you wanted to know about LEO satellites, part 3: Bandwidth, system capacity and inter-satellite routingEverything you wanted to know about LEO satellites,... by Ulrich Speidel June 2, 2021 Guest Post: The third part in the LEO satellite series examines issues surrounding the 'speed' of the connections. Connect with us * Facebook * Twitter * YouTube * Flickr * Weibo * Slideshare * LinkedIn * RSS (c) 2021 APNIC ABN 42 081 528 010 * Privacy * Contact * Help Centre * NRO News * Service Status * Careers