Archive

Category Archives for "Networking"

VyOS 1.2.0 Epa2 Realased

Finally, VyOS 1.2 epa2 ISO live image is released to subscribers. VyOS is a Linux-based network operating system that provides software-based network routing, firewall, and VPN functionality.

Free subscription is available for contributors, nonprofits and educational and research institutions, and both long-time contributors. Everyone who contributed before the release model change gets a perpetual subscription, the amount of contributions doesn’t matter. After that, contributing within a given year will give us a yearly subscription. If you are not a subscriber you can still download VyOS rolling release or built the ISO image from the source code.

You can use my Bash and Expect scripts to automatize VyOS 1.2.0 installation to VMware disk image. The scripts are available in the Script (1.1) section. Firstly, run the script  deploy_vyos-1.2.0.sh and after the ISO images boots up, you can run the second script  install_vyos-1.2.0.sh. You can run the image using GNS3 project and test open-source routing.

Large Layer-2 Domains Strike Again…

I started January 2018 blogging with a major service provider failure. Why should 2019 be any different? Here’s what Century Link claimed was causing two-day outage (more comments here).

Supposedly it was a problem with the management network used by their optical gear, but it looks a lot like a layer-2 network spanning 15 data centers and no control-plane policing on the managed devices… proving yet again that large-scale layer-2 networks are a really bad idea.

Read more ...

StackStorm ChatOps Integration

StackStorm is IFTTT for ops. Its original claim to fame was popularizing chat driven workflows for ops know as ChatOps. In this post I will cover integrating ST2 with Slack to enable ChatOps. Lab Environment The ST2 instance connects out to Slack which is a SAAS application. This means...

Whither Network Engineering? (Part 3)

In the previous two parts of this series, I have looked at the reasons I think the networking ecosystem is bound to change and why I think disaggregation is going to play a major role in that change. If I am right about the changes happening, what will become of network engineers? The bifurcation of knowledge, combined with the kinds of networks and companies noted in the previous posts in this series, point the way. There will, I think, be three distinct careers where the current “network engineer” currently exists on the operational side:

  1. Moving up the stack, towards business, the more management role. This will be captured primarily by the companies that operate in market verticals deep and narrow enough to survive without a strong focus on data, and hence can survive a transition to black box, fully integrated solutions. This position will largely be focused on deploying, integrating, and automating vertically integrated, vendor-driven systems and managing vendor relationships.
  2. Moving up the stack, towards software and business, the disaggregated network engineering role (I don’t have a better name for this presently). This will be in support of companies that value data to the point of focusing on its management Continue reading

Because Our Future Depends On It

Esther is a youth leader passionate about gender, digital literacy, and grassroots advocacy. She is founder of the SAFIGI Outreach Foundation and President of Digital Grassroots.

She is also a 2019 IFF Community Development fellow, a 2019 Engineers Without Borders Canada Kumvana fellow, a Mozilla Open Leader, an Internet Society 2017 Youth@IGF fellow, an open knowledge advocate, and a champion for capacity building of youth and girls.

Esther graduated summa cum laude in multimedia journalism, and is a contributor on Impakter.com and Africa.com.  She is an emerging African writer, working on her debut fantasy novel and does photography in her free time.

Born in 1994, about the same time Tim Berners-Lee founded the World Wide Web Consortium and a commercialized Internet started to take form, the Internet has inextricably shaped my life and career.

At 16 years old, I got my first job at an Internet café. I had taught myself to type, and that was all I needed to teach people that they couldn’t just guess a password if they had not already set up an email account. Many young people in developing nations are still grappling to learn the computer (it’s Continue reading

io_submit: The epoll alternative you’ve never heard about

io_submit: The epoll alternative you've never heard about

My curiosity was piqued by an LWN article about IOCB_CMD_POLL - A new kernel polling interface. It discusses an addition of a new polling mechanism to Linux AIO API, which was merged in 4.18 kernel. The whole idea is rather intriguing. The author of the patch is proposing to use the Linux AIO API with things like network sockets.

Hold on. The Linux AIO is designed for, well, Asynchronous disk IO! Disk files are not the same thing as network sockets! Is it even possible to use the Linux AIO API with network sockets in the first place?

The answer turns out to be a strong YES! In this article I'll explain how to use the strengths of Linux AIO API to write better and faster network servers.

But before we start, what is Linux AIO anyway?

io_submit: The epoll alternative you've never heard about
Photo by Scott Schiller CC/BY/2.0

Introduction to Linux AIO

Linux AIO exposes asynchronous disk IO to userspace software.

Historically on Linux, all disk operations were blocking. Whether you did open(), read(), write() or fsync(), you could be sure your thread would stall if the needed data and meta-data was not ready in disk cache. This usually isn't Continue reading