#pyroute2 — Public Fediverse posts

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. 😎

https://codeberg.org/liske/ifstate/src/branch/master/debian

#linuxnetworking #ifstate #haproxy #pyroute2 #Debian

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. 😎

https://codeberg.org/liske/ifstate/src/branch/master/debian

#linuxnetworking #ifstate #haproxy #pyroute2 #Debian

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. 😎

https://codeberg.org/liske/ifstate/src/branch/master/debian

#linuxnetworking #ifstate #haproxy #pyroute2 #Debian

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. 😎

https://codeberg.org/liske/ifstate/src/branch/master/debian

#linuxnetworking #ifstate #haproxy #pyroute2 #Debian

Got memray working on #Buildroot. Not send-patch quality yet, but it's usable. Why does #pyroute2 need about 10MB in RAM if I'm only using it to query/set the wifi regulatory domain? Makes it very tempting to ignore the "do not screenscrape" warning from iw… ​:blobcateyes:​

Got memray working on #Buildroot. Not send-patch quality yet, but it's usable. Why does #pyroute2 need about 10MB in RAM if I'm only using it to query/set the wifi regulatory domain? Makes it very tempting to ignore the "do not screenscrape" warning from iw… ​:blobcateyes:​

Got memray working on #Buildroot. Not send-patch quality yet, but it's usable. Why does #pyroute2 need about 10MB in RAM if I'm only using it to query/set the wifi regulatory domain? Makes it very tempting to ignore the "do not screenscrape" warning from iw… ​:blobcateyes:​

Got memray working on #Buildroot. Not send-patch quality yet, but it's usable. Why does #pyroute2 need about 10MB in RAM if I'm only using it to query/set the wifi regulatory domain? Makes it very tempting to ignore the "do not screenscrape" warning from iw… ​:blobcateyes:​

Got memray working on #Buildroot. Not send-patch quality yet, but it's usable. Why does #pyroute2 need about 10MB in RAM if I'm only using it to query/set the wifi regulatory domain? Makes it very tempting to ignore the "do not screenscrape" warning from iw… ​:blobcateyes:​

#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! 🙏

#linuxnetworking #pyroute2

#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! 🙏

#linuxnetworking #pyroute2

#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! 🙏

#linuxnetworking #pyroute2

#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! 🙏

#linuxnetworking #pyroute2

#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! 🙏

#linuxnetworking #pyroute2

#ifstate 1.13.5 was released:
https://codeberg.org/liske/ifstate/releases/tag/1.13.5

(already available in @alpinelinux edge + 3.21 + 3.20 + 3.19 and in @m4rc3l's Nix flake https://codeberg.org/m4rc3l/ifstate.nix)

This maintenance release fixes an exception breaking ifstate when pyroute2 0.9.1+ is used.

#linuxnetworking #pyroute2

#ifstate 1.13.5 was released:
https://codeberg.org/liske/ifstate/releases/tag/1.13.5

(already available in @alpinelinux edge + 3.21 + 3.20 + 3.19 and in @m4rc3l's Nix flake https://codeberg.org/m4rc3l/ifstate.nix)

This maintenance release fixes an exception breaking ifstate when pyroute2 0.9.1+ is used.

#linuxnetworking #pyroute2

#ifstate 1.13.5 was released:
https://codeberg.org/liske/ifstate/releases/tag/1.13.5

(already available in @alpinelinux edge + 3.21 + 3.20 + 3.19 and in @m4rc3l's Nix flake https://codeberg.org/m4rc3l/ifstate.nix)

This maintenance release fixes an exception breaking ifstate when pyroute2 0.9.1+ is used.

#linuxnetworking #pyroute2

#ifstate 1.13.5 was released:
https://codeberg.org/liske/ifstate/releases/tag/1.13.5

(already available in @alpinelinux edge + 3.21 + 3.20 + 3.19 and in @m4rc3l's Nix flake https://codeberg.org/m4rc3l/ifstate.nix)

This maintenance release fixes an exception breaking ifstate when pyroute2 0.9.1+ is used.

#linuxnetworking #pyroute2

#ifstate 1.13.5 was released:
https://codeberg.org/liske/ifstate/releases/tag/1.13.5

(already available in @alpinelinux edge + 3.21 + 3.20 + 3.19 and in @m4rc3l's Nix flake https://codeberg.org/m4rc3l/ifstate.nix)

This maintenance release fixes an exception breaking ifstate when pyroute2 0.9.1+ is used.

#linuxnetworking #pyroute2

#ifstate 1.10.1 has been released:
https://github.com/liske/ifstate/releases/tag/1.10.1

(available in @alpinelinux edge)

This release fixes some minor issue on #netns handling. It also containes a port of #pyroute2's RTM_NEWNSID wrapper (from git HEAD) to make the netns feature work with the current pyroute2 release.

#linuxnetworking #release

#ifstate 1.10.1 has been released:
https://github.com/liske/ifstate/releases/tag/1.10.1

(available in @alpinelinux edge)

This release fixes some minor issue on #netns handling. It also containes a port of #pyroute2's RTM_NEWNSID wrapper (from git HEAD) to make the netns feature work with the current pyroute2 release.

#linuxnetworking #release

#ifstate 1.10.1 has been released:
https://github.com/liske/ifstate/releases/tag/1.10.1

(available in @alpinelinux edge)

This release fixes some minor issue on #netns handling. It also containes a port of #pyroute2's RTM_NEWNSID wrapper (from git HEAD) to make the netns feature work with the current pyroute2 release.

#linuxnetworking #release

#ifstate 1.10.1 has been released:
https://github.com/liske/ifstate/releases/tag/1.10.1

(available in @alpinelinux edge)

This release fixes some minor issue on #netns handling. It also containes a port of #pyroute2's RTM_NEWNSID wrapper (from git HEAD) to make the netns feature work with the current pyroute2 release.

#linuxnetworking #release

#ifstate 1.10.1 has been released:
https://github.com/liske/ifstate/releases/tag/1.10.1

(available in @alpinelinux edge)

This release fixes some minor issue on #netns handling. It also containes a port of #pyroute2's RTM_NEWNSID wrapper (from git HEAD) to make the netns feature work with the current pyroute2 release.

#linuxnetworking #release

While implementing the netns handling in ifstate I got aware that pyroute2 did not have a netlink RTM_NEWNSID request implementation.

I got https://github.com/svinota/pyroute2/pull/1121 merged into pyroute2 to add RTM_NEWNSID support.

Later I have noticed that my implementation does not work within netns (pyroute2 related, some details in issue https://github.com/svinota/pyroute2/issues/1123 ).

After this tangled journey ifstate netns dev branch now has its first netns superpowers 😎

#ifstate #linux #linuxnetworking #netlink #pyroute2