Updating a Cloudflare Gateway Network via API Cloudflare Gateway is part of the Cloudflare One platform and helps organizations apply security policies to internet-bound traffic. You can update Gateway configurations programmatically via the Cloudflare API, which is especially useful for automation or managing large environments. This post will walk you through how to update a Gateway configuration using the Cloudflare API, including how to find the required IDs. 📌 What You Need To perform the update, you’ll need the following:

Here are my current top tracks on spotify:

If you’re running a Hugo site and want to embed Spotify tracks, albums, or playlists easily into your posts, you can create a custom shortcode to streamline the process. Something like this: I recently came across a helpful gist by j-un, and I’ll walk you through how to use it. 🛠️ Step-by-Step: Create the Spotify Shortcode 1. Create the shortcode file Navigate to your Hugo site’s root and create the following file:

Displaying DHCP Lease Information on Your XSIAM Broker VM via Live Terminal When working with your XSIAM Broker VM, there are times you might need to quickly verify its network configuration, especially details pertaining to its DHCP lease. Some of this info is available from the UI however not all of it. Whether you’re troubleshooting connectivity issues, ensuring the correct IP assignment, or simply confirming network parameters, accessing this information directly from a live terminal can be incredibly useful.

With the help ChatGPT I put together a go program. It ran fine on the macOS machine I compiled it on, however once it was transferred to another machine, via the internet it wouldn’t run on the other machine. When you move around compiled binaries between machines, especially on macOS, you might run into an annoying little issue: getCertInfo can’t be opened because Apple cannot check it for malicious software. This software needs to be updated.

In today’s IT environments, automation and integration are essential components of an efficient workflow. Whether you’re managing cloud services, auditing system logs, or interacting with other online services, you’ll often need to access APIs. One of the key challenges is ensuring that these API requests are secure and authenticated. In this post, we’ll walk through how to use PowerShell to send a request to an API endpoint while passing authentication headers, specifically using an API token for authorization.

If you’ve encountered the error: [info] error: RPC failed; HTTP 400 curl 22 The requested URL returned error: 400 Typically this occurs due to large file sizes being pushed to a remote repository, leading to an issue with the buffer size Git uses for HTTP operations. This turned up recently on macOS; I have no idea why or what changed in my repo. Solution: Increasing the Post Buffer Size To resolve this problem, increase Git’s HTTP buffer size using the http.

After upgrading PANOS on my firewall from 10.1 from 10.2, I was no longer able to SSH into the firewall. Trying to SSH into management interface resulted in the following SSH error: ❯ ssh [email protected] Unable to negotiate with 192.168.1.1 port 22: no matching host key type found. Their offer: ssh-rsa The issue is related to weak host key algorithms from the firewall and updated SSH clients (I’m not sure why this has changed from 10.

It can be a pain managing previously downloaded PANOS software images. Especially on the smaller firewalls with limited storage, the old versions just take up valuable space. Rather than using the API to do this at scale, one option is to limit the number to versions each firewall will keep at download time: set max-num-images count 2 Now at download time only two active images will be kept, where the number is the amount you want to keep.

When connected to a SSL VPN on macOS sometimes you want to find which physical network interface the VPN is using. Listing network interfaces using ifconfig doesn’t help as it is just a list of adapters and if they are linked or not. Looking up the default route with route get 1.1.1.1 only shows you the tun adapter the VPN is using: ❯ route get 1.1.1.1 route to: one.one.one.one destination: default mask: default gateway: my-mac interface: utun0 flags: <UP,GATEWAY,DONE,STATIC,PRCLONING,GLOBAL> recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire 0 0 0 0 0 0 1400 0 In this case the VPN is using “utun0” which is the virtual adapter.