Heavy Networking 536: Arrcus Reimagines The Chassis Router With Its Virtualized Distributed Router (Sponsored)
Today's Heavy Networking dives into sponsor Arrcus's Virtualized Distributed Router, new software that transforms the monolithic chassis that can scale to thousands of ports while being operated and managed like a single device. Our guests are Murali Gandluru, Keyur Patel, and Nalin Pai from Arrcus.
The post Heavy Networking 536: Arrcus Reimagines The Chassis Router With Its Virtualized Distributed Router (Sponsored) appeared first on Packet Pushers.
Opening Up Remote Access with Opengear
The Opengear OM2200
If you had told me last year at this time that remote management of devices would be a huge thing in 2020 I might have agreed but laughed quietly. We were traveling down the path of simultaneously removing hardware from our organizations and deploying IoT devices that could be managed easily from the cloud. We didn’t need to access stuff like we did in the past. Even if we did, it was easy to just SSH or console into the system from a jump box inside the corporate firewall. After all, who wants to work on something when you’re not in the office?
Um, yeah. Surprise, surprise.
Turns out 2020 is the Year of Having Our Hair Lit On Fire. Which is a catchy song someone should record. But it’s also the year where we have learned how to stand up 100% Work From Home VPN setups within a week, deploy architecture to the cloud and refactor on the fly to help employees stay productive, and institute massive change freezes in the corporate data center because no one can drive in to do a reboot if someone forgets to do commit confirmed or reload in 5.
Remote Continue reading
JUNOS | Filter-Based Forwarding
Alright, so Filter-Based Forwarding is nothing new. The technology has been around for a while and is relatively well documented. However, I wanted to share a specific use case where Filter-Based Forwarding can be extremely useful. In this scenario, we’re going to use Filter-Based Forwarding to forward traffic to a dedicated VRF where it is then pushed through a DDOS appliance and back to the router via a different VRF.
This construct is very useful when you only need to pass specific ingress traffic through the DDOS appliance. For example, customer destination prefixes who are paying for a DDOS service. Or traffic from certain source prefixes that are known to be malicious. Return traffic in either scenario is not passed via the appliance and is routed directly back to the source.
Challenge Statement
Specific ingress traffic received from transit & peering providers, via the TRANSIT VRF, must be pushed to the DIRTY VRF. The traffic must then be forwarded back towards the TRANSIT VRF via an appliance for inspection. Once the traffic is received back into the TRANSIT VRF it is onward routed as normal.
Solution
The solution involves defining the prefixes that should be considered within the Filter-Based Forwarding Continue reading
Alibaba On The Bleeding Edge Of RISC-V With XT910
It was just over a year ago that the RISC-V Foundation, the group shepherding the chip architecture in what over the past decade has become an active and crowded processor market, ratified the base instruction set architecture (ISA) and related specifications. …
Alibaba On The Bleeding Edge Of RISC-V With XT910 was written by Jeffrey Burt at The Next Platform.
Mapping Intermediary Liability in Latin America
Thanks to our Chapters in Latin America, we now have a clearer map of the intermediary liability regulatory landscape across the region.
Intermediary liability answers the question, “Should Internet intermediaries (ISPs, web hosting and cloud services, social media platforms, etc.) be liable for content posted or for actions performed by others, such as, for example, their users?”
The success of the Internet depends on intermediary liability regimes that protect Internet providers – by ensuring responsibility for user behavior is on the users themselves, not on the intermediaries upon which they rely (both at the infrastructure and content layers).
The way legal frameworks deal with intermediary liability around the world can impact the Internet way of networking in different ways.
In some countries, intermediary liability legislation is well known: the 1996 US Communications Decency Act (Section 230) and the Brazilian Internet Bill of Rights, for example. But in much of the world it is covered by other more general-purpose regulations, such as tort law, consumer protection law, and child protection law.
We asked our local community to help us map and monitor the current regimes that apply to Internet intermediaries in their countries, so that our work can Continue reading
Technology Short Take 130
Welcome to Technology Short Take #130! I’ve had this blog post sitting in my Drafts folder waiting to be published for almost a month, and I kept forgetting to actually make it live. Sorry! So, here it is—better late than never, right?
Networking
- Here’s a walkthrough on using DNS over TLS on Fedora.
- Some Twitter followers recently pointed out
gnmic, a gNMI CLI client. gNMI, by the way, stands for gRPC Network Management Interface (more information on gNMI can be found here). I haven’t usedgnmic, but it certainly looks like an extremely useful tool.
Security
- Everyone’s favorite three-letter agency recently released some VPN security guidance, as reported by this InfoSecurity Magazine article. The article also provides some links to said guidance, for those that are interested.
- Matt Hamilton takes a closer look at a recent security vulnerability in the Harbor container registry. This vulnerability, known as a Server-Side Request Forgery, allowed Harbor project owners to scan the TCP ports of hosts on the Harbor server’s internal network.
- Ivan Pepelnjak discusses the security implications of so-called “Smart NICs.”
- Want to use a Yubikey to automatically lock and unlock your Linux system? See here.
Cloud Computing/Cloud Management
Working Collaboratively to Improve Emerging Network Time Security Implementations
Accurate and secure time is essential for the security and trustworthiness of the Internet. Many systems that we regularly interact with rely on accurate time to function properly. Accurate time also provides an essential foundation for online security, and many security mechanisms, such as digital certificates used for Transport Layer Security (TLS), depend on accurate timekeeping. The Network Time Protocol (NTP) provides time synchronization for clocks on computer networks.
NTP’s security mechanisms were designed back in an era when most Internet traffic was trusted, and the risk of attack was unlikely. Due to the continued exponential expansion of the Internet, these mechanisms became outdated and needed to be redesigned. The Internet Engineering Task Force (IETF) has been working on a specification for Network Time Security (NTS) for several years now. This specification was approved by the Internet Engineering Steering Group (IESG) in March of this year and is currently in the RFC editing process for the final publication. Over the course of the last couple of years, there have been a series of NTS projects held as part of the IETF Hackathons. These projects have worked to identify mistakes and ambiguities in the specification and to test and improve interoperability Continue reading
How Cloudflare uses Cloudflare Spectrum: A look into an intern’s project at Cloudflare
Cloudflare extensively uses its own products internally in a process known as dogfooding. As part of my onboarding as an intern on the Spectrum (a layer 4 reverse proxy) team, I learned that many internal services dogfood Spectrum, as they are exposed to the Internet and benefit from layer 4 DDoS protection. One of my first tasks was to update the configuration for an internal service that was using Spectrum. The configuration was managed in Salt (used for configuration management at Cloudflare), which was not particularly user-friendly, and required an engineer on the Spectrum team to handle updating it manually.
This process took about a week. That should instantly raise some questions, as a typical Spectrum customer can create a new Spectrum app in under a minute through Cloudflare Dashboard. So why couldn’t I?
This question formed the basis of my intern project for the summer.
The Process
Cloudflare uses various IP ranges for its products. Some customers also authorize Cloudflare to announce their IP prefixes on their behalf (this is known as BYOIP). Collectively, we can refer to these IPs as managed addresses. To prevent Bad Stuff (defined later) from happening, we prohibit managed addresses from Continue reading
Podcast: Trusting Routing Protocols
The can we trust routing protocols series of blog posts I wrote in April 2020 (part 1, part 2, response from Jeff Tantsura) culminated in an interesting discussion with Russ White and Nick Russo now published as The Hedge Episode 43.
Lessons from load balancers and multicast
In general I dislike operating load balancers and IP multicast: I’m a network engineer. Load balancers and IP multicast are very complicated, have a large amount of state, and they are hard to understand and debug. They lead to a lot of operational issues and outages. They have directly lead...Docker Desktop & WSL 2 – Backport Update
While we have continued to make improvements to our Windows experience on Docker Desktop for users of HyperV, we are excited to see that Microsoft has announced the backport of WSL 2 to Windows version 1903 and 1909. This means that as of today, Docker Desktop Edge users will be able to use Docker Desktop with WSL 2 rather than our legacy HyperV based backend. This is available not only for Windows Pro and Windows Enterprise, but also for Windows Home users. This is the first time that Docker has been available on Windows Home versions 1903 and 1909! 
This means that these developers will be able to take advantage of WSL 2 and Docker’s integration, allowing developers to store their code within their WSL 2 distro and run the Docker CLI from within this distro. This removes the need to access files stored on the Windows host and provides significant performance improvements for users.
To find out more about using Docker Desktop with WSL 2, check out Simon’s full tips and tricks article. If you want to learn more about how Docker developed the WSL 2 backend you can have a look through our history of the integration Continue reading
IPv6 Buzz 058: Tackling IPv6 Access Challenges
In this week's episode Ed, Scott, and Tom talk to Nico Schottelius, CEO of Ungleiich Glarus, a Swiss IT services company that has developed a VPN IPv6 IoT Router Box (VIIRB), allowing cheap and secure access to the IPv6 Internet from anywhere.IPv6 Buzz 058: Tackling IPv6 Access Challenges
In this week's episode Ed, Scott, and Tom talk to Nico Schottelius, CEO of Ungleiich Glarus, a Swiss IT services company that has developed a VPN IPv6 IoT Router Box (VIIRB), allowing cheap and secure access to the IPv6 Internet from anywhere.
The post IPv6 Buzz 058: Tackling IPv6 Access Challenges appeared first on Packet Pushers.
Introducing Deploy Buttons
When I first try out new development platforms, the first thing I do is get an OSS (Open Source Software) project I find on Github up and running. I used to start by following tutorials or digging through documentation. It’s a little bit counterintuitive. Let me share with you why. One reason is that Hello, World! examples rarely show the real “magic” of the platform. I want to feel excited and get a sense of how other people are creatively using the platform.
For example, I love it when I can build and deploy an OSS Pokedex app in a few minutes on Flutter to see if the platform actually lives up to the hype. It’s so much easier to do this than to spend a few hours following tutorials and documentation to get through the initial learning curve. You can think of it as shortening the time to first dopamine.
Another reason is that it makes learning the new platform much faster. Building off of an experienced developer’s work shows me which classes and functions are most useful to learn. There’s more nuance to building out full applications than is usually explained in the documentation. I can see how Continue reading