The ifstate git repository on #Codeberg has been moved from my personal account into the RouterKit project at https://codeberg.org/routerkit/ifstate
With moving the project it gains access to CI/CD runners and the first step is to use them to provide #Debian packages from the upcoming 2.2.4 release 🥳
https://codeberg.org/routerkit/-/packages/debian/ifstate/
I already use it in prod for haproxy setups on Debian trixie using different network namespaces for listeners and server access.
I don't like to maintain packaging upstream, but… I required netns configuration support on Debian for using network namespaces with haproxy!
Sadly I had to use dh_virtualenv because pyroute2 in Debian sid+stable is to old to have all required netns related features.
Haproxy has namespace support for listeners and servers which allows one to easily build multi-tenant load-balancing setups. 😎
The ifstate 2.2 release - a tool for declarative network configuration for Linux - is available in the most recent stable releases of Alpine Linux 3.23 and NixOS 25.11. 🥳
Fun fact: this is the first NixOS release where you can use a declarative network configuration out of the box 😉
#ifstate 2.2.[01] - a tool for declarative network configuration for Linux - was released:
https://codeberg.org/liske/ifstate/releases/tag/2.2.0
https://codeberg.org/liske/ifstate/releases/tag/2.2.1
This release includes:
- support for vlan_flags (loose_binding, …)
- the wgnlpy python dependency has been dropped
…and it also contains several fixes, the most import is a regression: interface defaults were not applied since ifstate 2.0
(already available in @alpinelinux edge + v3.23 and #nixpkgs unstable + 25.11)
Tìm kiếm công cụ trực quan hóa cấu trúc mạng phức tạp, kết hợp Docker, LXC và Linux. Người dùng muốn xem các kết nối veth, bridge giữa các container. Atlas chỉ hỗ trợ Docker. Có gợi ý nào không? #networktopology #visualizetool #docker #lxc #linuxnetworking #networking #cấutrúc mạng #trựcquanchung #tinhtech
https://www.reddit.com/r/selfhosted/comments/1p1i04c/visualize_network_topology/
🐧💻 "Escape the Linux Networking Stack" – because understanding it makes it vanish! Poof! 💨 The author attempts to unravel the mystery, but spoiler alert: nobody truly escapes, not even Cloudflare's blog notifications. 🐟🔍
https://blog.cloudflare.com/so-long-and-thanks-for-all-the-fish-how-to-escape-the-linux-networking-stack/ #LinuxNetworking #EscapeTheStack #Cloudflare #TechMystery #NetworkingInsights #HackerNews #ngated
#ifstate 2.1.0 - a tool for declarative network configuration for Linux - was released:
https://codeberg.org/liske/ifstate/releases/tag/2.1.0
This release includes:
- support for IP address IFA (local, proto, …)
- support for PtP link IP addressing
- wireguard: auto generation of peer routes from allowsips
- improved handling of LLA
…and it also contains some bugfixes 😉
(already available in @alpinelinux edge, the #nixpkgs unstable PR is still pending https://github.com/NixOS/nixpkgs/pull/460206 )
#TIL that there is a nice tool to determine the encapsulation overhead, the Visual packet size calculator by @dmbaturin
#ifstate 1.13.9 - a tool for declarative network configuration for Linux - was released:
https://codeberg.org/liske/ifstate/releases/tag/1.13.9
This maintenance release for the old 1.x branch fixes an exception when reconfiguring tc filters when using pyroute2 0.9.1+
(already available in @alpinelinux 3.22 + 3.21 + 3.20 + 3.19)
2/2
#ifstate 2.0.2 - a tool for declarative network configuration for Linux - was released:
https://codeberg.org/liske/ifstate/releases/tag/2.0.2
This maintenance release contains mostly fixes for traffic control (TC) settings:
- fixes a regression breaking cshaper configurations
- fixes exceptions when reconfiguring tc filters when using pyroute2 0.9.1+
1/2
#ifstate 2.0 - a tool to for declarative network configuration for Linux - was released:
https://codeberg.org/liske/ifstate/releases/tag/2.0.0
https://codeberg.org/liske/ifstate/releases/tag/2.0.1
The new major release contains various breaking changes and the config file schema has been refactored to better match the requirements. The new documentation contains a overview on the breaking changes when upgrading from ifstate 1.x: https://ifstate.net/2.0/docs/upgrades/#ifstate-20
This thread will highlight some of the most important changes!
1/4
Essential nmcli Command Examples To Manage Network Connections On Linux #nmcli #NetworkManager #LinuxNetworking #Linuxadmin #linuxhowto #linuxbasics #linuxcommands #commandline
https://ostechnix.com/linux-nmcli-command-examples/
#ifstate 1.13.8 - a tool to for declarative network configuration for Linux - was released:
https://codeberg.org/liske/ifstate/releases/tag/1.13.8
(already available in @alpinelinux 3.22 + 3.21 + 3.20 + 3.19 and in @m4rc3l's Nix flake https://codeberg.org/m4rc3l/ifstate.nix)
This maintenance release contains mostly bug fixes that are already included in the recent ifstate 2.0 release
#ifstate 2.0.0rc4 is available:
https://codeberg.org/liske/ifstate/releases/tag/2.0.0rc4
Yet another RC:
- the python dep for jsonschema is now optional to allow a lower footprint for #nix packaging
- contributions to bugfixes 🙏
Most work was put into the documentation:
- ported from jekyll to mkdocs-material
- updated to reflect ifstate 2.0 schema changes
- enabled versioned documentation, so you can easily compare ifstate 1.x vs. 2.0
Hmm am I the only one who think this doesn't make much sense?
On one side, I have to make changes to network configuration using the ip utility. But then to make them persistent, I have to play with systemd-networkd stuff. The problem's that I have to learn two things. Why not have a system with which you could configure your network through the same CLI tool using the same syntax?
Not that I want to join the anti systemd train. I haven't tweaked my PC at this level before. But recently I'm doing so and I wished I didn't have to spend few hours to get the thing working. Maybe it could be good if there was a system with which you could configure networking stuff on boot using the same ip utility?
Or maybe I'm doing it the wrong way and there is a way to make changes done with ip persistent?
Any enlightening comment is welcome!
#systemd #Linux #FOSS #LinuxNetworking #Networking #CLI #sysadmin #systemadministration
#ifstate 2.0.0rc3 is available:
https://codeberg.org/liske/ifstate/releases/tag/2.0.0rc3
Yet another RC:
- contains #nix module contributed by @m4rc3l 🙏
- net.ipv6.conf.all.optimistic_dad is now enabled by default
There will be at least another RC for https://codeberg.org/liske/ifstate/issues/111
#ifstate 2.0.0rc2 is available:
https://codeberg.org/liske/ifstate/releases/tag/2.0.0rc2
This pre-release contains some major breaking changes. You *need* to update your old config to make it work with the new config schema of ifstate 2.0+ (hint: `ifstatecli show`).
I'm especially looking for feedback on the schema update: https://ifstate.net/schema/2.0/
Known issues are/will be tagged with the 2.0.0 milestone here: https://codeberg.org/liske/ifstate/milestone/5087
Thanks! 🙏
#ifstate 1.13.7 was released:
https://codeberg.org/liske/ifstate/releases/tag/1.13.7
(already available in @alpinelinux edge + 3.22 + 3.21 + 3.20 + 3.19 and in @m4rc3l's Nix flake https://codeberg.org/m4rc3l/ifstate.nix)
This maintenance release fixes some minor netns and routing related issues.
There is an open issue when using ifstate as a notify fifo script in keepalived: https://codeberg.org/liske/ifstate/issues/105 - when keepalived is reloaded any changes on vrrp constraint settings in ifstate may not apply.
#LTMLinuxTips - Day 5
🗺️ Check your public IP From terminal (with more detail):
curl -s https://ipinfo.io
Useful for remote access or VPN checks.
