One of my readers sent me this remark (probably while trying to work on the EBGP Sessions over the IPv6 LLA Interfaces lab):
I did attempt some of your labs, like IPv6 link-local-only BGP with FRR hosts, but FRR seemed not to play ball, or I was just doing it wrong.
As he was already using netlab, I could send him a cheat code:
One of my readers sent me this remark (probably while trying to work on the EBGP Sessions over the IPv6 LLA Interfaces lab):
I did attempt some of your labs, like IPv6 link-local-only BGP with FRR hosts, but FRR seemed not to play ball, or I was just doing it wrong.
As he was already using netlab, I could send him a cheat code:
Yesterday, I explained how you can run netlab examples in GitHub codespaces and mentioned that they work best with vendors who understand the value of frictionless downloads. But what if you’d like to use a device from one of the good guys who provide the container images but require a registration?
It turns out the solution is trivial:
Yesterday, I explained how you can run netlab examples in GitHub codespaces and mentioned that they work best with vendors who understand the value of frictionless downloads. But what if you’d like to use a device from one of the good guys who provide the container images but require a registration?
It turns out the solution is trivial:
Good morning! How are you?
I’d like to talk about keynotes, again. You know, one of my favorite subjects. I’ve been watching them intently for the past few years just hoping that we’re going to see something different. As a technical analyst and practitioner I love to see and hear the details behind the technology that drive the way our IT companies develop. Yet every year I feel more and more disappointed by the way that keynotes take everything and push it into the stratosphere to get an 80,000 foot view of the technology. It’s almost like the keynotes aren’t written for practitioners. Why? The answer lies in the statement at the top of this post.
When most people ask someone how their day is going they’re not actually looking for a real response. They most certainly aren’t asking for details on how exactly the person’s day is going. They’re usually looking for one of two things:
Any more than that drags someone down into a conversation that they don’t want to have. Asking someone about their day is a polite way of acknowledging them and making a bit of small Continue reading
In this article, we explore the capabilities and limitations of the Luma AI Dream Machine. […]
The post Testing Luma AI Dream Machine first appeared on Brezular's Blog.
Segment Routing was supposed to make MPLS easier and give more power to network operators. Sadly, vendors decided to make it harder by selling weird protocols and over-engineered controller bloatware.
Despite some anti-MPLS marketing from SD-WAN …
In my opinion, learning cloud networking is easier compared to traditional networking. You’ll see why as we go through the posts. Even if you're completely new to the cloud, you can get a simple lab up and running within a few hours. You don't need physical devices, cables, or complex topologies to get started.
Of course, you won’t become an expert in a few months, but you will build a solid foundation from which you can grow. The key is to start small, understand the basics, and experiment as you go.
There are multiple cloud providers out there, such as AWS, Azure, GCP, Alibaba Cloud, and so on. At a basic level, they all function the same from a networking point of view, though each has its own nuances and differences. As long as you're familiar with one provider, the knowledge is usually transferable. That said, our focus here is AWS. AWS has the largest market share in the cloud space, and it's also where I got started.
If you're brand new to AWS, don't worry. This post focuses on the basics of AWS networking. General networking knowledge is helpful but not required - I'll try to explain things Continue reading
A few days ago, someone asked me about the IPv4 next-hop details of running interface EBGP sessions. I pointed him to a blog post explaining them, adding, “And of course, you can test that in netlab.” A few minutes later, it hit me: instead of asking him to set up netlab locally, I could enable him to do that in a minute with GitHub codespaces.
Setting that up was easy: copy the .devcontainer directory from the BGP labs repository into the netlab examples repository and commit the change. After a short yak-shaving exercise (writing README files and rearranging a few folders), I successfully started the codespace and was ready for this blog post. There was just one gotcha…
A few days ago, someone asked me about the IPv4 next-hop details of running interface EBGP sessions. I pointed him to a blog post explaining them, adding, “And of course, you can test that in netlab.” A few minutes later, it hit me: instead of asking him to set up netlab locally, I could enable him to do that in a minute with GitHub codespaces.
Setting that up was easy: copy the .devcontainer directory from the BGP labs repository into the netlab examples repository and commit the change. After a short yak-shaving exercise (writing README files and rearranging a few folders), I successfully started the codespace and was ready for this blog post. There was just one gotcha…
How many times have you found yourself perfectly comfortable in your current job, only to be tempted by a new opportunity? We’ve all been there. It’s tough to leave a place where you know everyone and everything feels familiar. The new job might turn out to be fantastic, or it could be less than ideal. So, how do we overcome these fears and make the right choice? In this post, I’ll share my own journey, exploring what I learned from my experiences. Hopefully, my story can help you navigate your own career decisions with a bit more confidence.
I kicked off my career back in 2017, filled with an eagerness to learn and make rapid progress. During those early days, I was truly engaged in my work, often pulling long hours because all I could think about was advancing in my field. After spending a Continue reading
Added 11 new lessons in June:
Hi all, welcome back to yet another Palo Alto Firewall blog. Have you ever wanted to load partial config from one Palo Alto Firewall to another or from a Firewall to Panorama and vice versa? There could be times when you just want to import all address objects from one Firewall to another, for example. We could do this in multiple ways, but there is a simple way of doing this. Let’s get into how you can achieve this with just a few steps.
To demonstrate this, I have a firewall and Panorama. On the firewall, there are a few address objects, address groups, and a security policy that I want to import into Panorama, inside a specific device group. Let’s walk through the steps.