Fosstodon

Thomas Liske<a href="https://ibh.social/tags/ifstate" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifstate</a> 1.13.7 was released: <a href="https://codeberg.org/liske/ifstate/releases/tag/1.13.7" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/liske/ifstate/releases/tag/1.13.7</a>(already available in <a href="https://fosstodon.org/@alpinelinux" class="u-url mention" rel="nofollow noopener" target="_blank">@alpinelinux</a> edge + 3.22 + 3.21 + 3.20 + 3.19 and in <a href="https://c3d2.social/@m4rc3l" class="u-url mention" rel="nofollow noopener" target="_blank">@m4rc3l</a>'s Nix flake <a href="https://codeberg.org/m4rc3l/ifstate.nix" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/m4rc3l/ifstate.nix</a>)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: <a href="https://codeberg.org/liske/ifstate/issues/105" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/liske/ifstate/issues/105</a> - when keepalived is reloaded any changes on vrrp constraint settings in ifstate may not apply.<a href="https://ibh.social/tags/linuxnetworking" class="mention hashtag" rel="nofollow noopener" target="_blank">#linuxnetworking</a> <a href="https://ibh.social/tags/keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#keepalived</a> <a href="https://ibh.social/tags/AlpineLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a>

ck 👨‍💻For a HA setup <a href="https://noc.social/tags/KeepaliveD" class="mention hashtag" rel="nofollow noopener" target="_blank">#KeepaliveD</a> was installed on <a href="https://noc.social/tags/RHEL" class="mention hashtag" rel="nofollow noopener" target="_blank">#RHEL</a> 9. The virtual IP address was configured based on the example configuration from the package.After starting the service, the <a href="https://noc.social/tags/VIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#VIP</a> was correctly configured - however did not respond to any communication.Troubleshooting and analysis revealed that the vrrp_strict option - part of the example configuration - created an automatic firewall block rule on the VIP.<a href="https://www.claudiokuenzler.com/blog/1488/keepalived-vip-not-responding-rhel9-el9" rel="nofollow noopener" target="_blank">https://www.claudiokuenzler.com/blog/1488/keepalived-vip-not-responding-rhel9-el9</a>

Fink :antifa:TIL <a href="https://chaos.social/tags/keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#keepalived</a> allows using a password. And caps it to 8 characters. The debian manpage stats that IPsec/AH should not be used.

kurator88Настроил <a href="https://social.exo.icu/tags/keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#keepalived</a> c <a href="https://social.exo.icu/tags/vrrp" class="mention hashtag" rel="nofollow noopener" target="_blank">#vrrp</a> и сижу довольный Если мне лень вставать то x86 сервер может быстро выкушать запас ups и тогда dns будет раздавать малинка которая меньше ест и дольше живет

IndiealexhI spent probably a weeks worth of hours learning more <a href="https://tny.social/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#kubernetes</a> so I could save $60 a month.I have a nice 3 node kube cluster with a 2 node <a href="https://tny.social/tags/keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#keepalived</a> <a href="https://tny.social/tags/haproxy" class="mention hashtag" rel="nofollow noopener" target="_blank">#haproxy</a> TCP load balancer. All on <a href="https://tny.social/tags/ARM" class="mention hashtag" rel="nofollow noopener" target="_blank">#ARM</a> VPS.Haproxy ingress <a href="https://tny.social/tags/ExternalDNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ExternalDNS</a> operator <a href="https://tny.social/tags/CertManager" class="mention hashtag" rel="nofollow noopener" target="_blank">#CertManager</a> <a href="https://tny.social/tags/RookCeph" class="mention hashtag" rel="nofollow noopener" target="_blank">#RookCeph</a> <a href="https://tny.social/tags/ArgoCD" class="mention hashtag" rel="nofollow noopener" target="_blank">#ArgoCD</a> <a href="https://tny.social/tags/KeyCloak" class="mention hashtag" rel="nofollow noopener" target="_blank">#KeyCloak</a> <a href="https://tny.social/tags/ValKey" class="mention hashtag" rel="nofollow noopener" target="_blank">#ValKey</a> <a href="https://tny.social/tags/Mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mastodon</a> <a href="https://tny.social/tags/CloudNativePG" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudNativePG</a> <a href="https://tny.social/tags/Postgresql" class="mention hashtag" rel="nofollow noopener" target="_blank">#Postgresql</a>

HabrУстанавливаем кластер Kubernetes в LXC-контейнерах ProxmoxЕсли вы когда-либо разворачивали Kubernetes-кластер на виртуальных машинах (ВМ), то знаете, насколько это может быть ресурсоёмко. Особенно это ощущается на одноплатных компьютерах вроде Orange Pi 5 Plus, даже несмотря на его 16 ГБ оперативной памяти. Для домашнего лабораторного стенда или лёгкой продакшн-инфраструктуры хочется чего-то более лёгкого и быстрого<a href="https://habr.com/ru/articles/901260/" rel="nofollow noopener" translate="no" target="_blank">https://habr.com/ru/articles/901260/</a><a href="https://zhub.link/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#kubernetes</a> <a href="https://zhub.link/tags/keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#keepalived</a> <a href="https://zhub.link/tags/haproxy" class="mention hashtag" rel="nofollow noopener" target="_blank">#haproxy</a> <a href="https://zhub.link/tags/containerd" class="mention hashtag" rel="nofollow noopener" target="_blank">#containerd</a> <a href="https://zhub.link/tags/crio" class="mention hashtag" rel="nofollow noopener" target="_blank">#crio</a> <a href="https://zhub.link/tags/orange_pi" class="mention hashtag" rel="nofollow noopener" target="_blank">#orange_pi</a> <a href="https://zhub.link/tags/arm64" class="mention hashtag" rel="nofollow noopener" target="_blank">#arm64</a>

Malik.ShowersCurrently fighting with keepalived to cluster two proxy VMs. Including the variables of multicast traffic with VSphere and a Cisco switch, this has been a steep-learning-curve kinda week!Have managed to stand up the virtual ip and mac, just need failover to function correctly. Deep in the geek zone with this.<a href="https://techhub.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://techhub.social/tags/keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#keepalived</a>

Thomas Liske<a href="https://ibh.social/tags/ifstate" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifstate</a> 1.13.0 was released: <a href="https://codeberg.org/liske/ifstate/releases/tag/1.13.0" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/liske/ifstate/releases/tag/1.13.0</a>(available in <a href="https://fosstodon.org/@alpinelinux" class="u-url mention" rel="nofollow noopener" target="_blank">@alpinelinux</a> edge + 3.20 + 3.19 and in <a href="https://c3d2.social/@m4rc3l" class="u-url mention" rel="nofollow noopener" target="_blank">@m4rc3l</a>'s Nix flake <a href="https://codeberg.org/m4rc3l/ifstate.nix" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/m4rc3l/ifstate.nix</a>)Among other minor changes one major change is the refactoring of the vrrp-fifo action (which allows to use ifstate with keepalived's vrrp_notify_fifo_script option). This fixes a race condition breaking ip failover when using more than a single vrrp groups or instances with a netns were used.<a href="https://ibh.social/tags/ifstate" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifstate</a> <a href="https://ibh.social/tags/linuxnetworking" class="mention hashtag" rel="nofollow noopener" target="_blank">#linuxnetworking</a> <a href="https://ibh.social/tags/keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#keepalived</a>

ck 👨‍💻After setting up a new <a href="https://noc.social/tags/Keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#Keepalived</a> <a href="https://noc.social/tags/vrrp" class="mention hashtag" rel="nofollow noopener" target="_blank">#vrrp</a> setup on a <a href="https://noc.social/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> 12 (bookworm) machine, the track_scripts were ignored. As it turns out, the order in the config file is important! <a href="https://www.claudiokuenzler.com/blog/1430/keepalived-vrrp-warning-script-is-not-used-ignored" rel="nofollow noopener" target="_blank">https://www.claudiokuenzler.com/blog/1430/keepalived-vrrp-warning-script-is-not-used-ignored</a>

ItzTrain<a href="https://fosstodon.org/@OGSH" class="u-url mention" rel="nofollow noopener" target="_blank">@OGSH</a> No there was one clear master, but every time I stopped the process there would be no failover. If I stop the process and then restarted <a href="https://hachyderm.io/tags/keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#keepalived</a> , then it would fail over.. I think. I thought it would be in real time, but maybe that's not how it works. It was also the priority thing plus the weight thing threw me off. Couldn't find a good example of it either.

ItzTrainSpent way to long trying to get <a href="https://hachyderm.io/tags/keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#keepalived</a> to work with monitoring a process and failover if that process doesn't . I probably don't understand it cause that shit didn't do what I wanted it to do!! <a href="https://hachyderm.io/tags/fuck" class="mention hashtag" rel="nofollow noopener" target="_blank">#fuck</a> <a href="https://hachyderm.io/tags/ya" class="mention hashtag" rel="nofollow noopener" target="_blank">#ya</a> <a href="https://hachyderm.io/tags/life" class="mention hashtag" rel="nofollow noopener" target="_blank">#life</a>

HabrУмный дом на openHAB+MQTT+Arduino. Часть 1: КластерИзначально была мысль повысить доступность openHAB средствами виртуализации. Ставим два гипервизора, настраиваем High availability, при отказе хоста виртуалка с openHAB перезапустится на соседнем сервере. И все бы ничего, но для работы HA нужно общее хранилище. Какой-то NAS допустим у меня есть, но выход его из строя даже более вероятен, чем отказ хоста. А городить что-то на DRBD или подобном не хотелось. Поэтому было решено кластеризовать openHAB другим способом. см. рисунок ниже<a href="https://habr.com/ru/articles/804659/" rel="nofollow noopener" translate="no" target="_blank">https://habr.com/ru/articles/804659/</a><a href="https://zhub.link/tags/openhab" class="mention hashtag" rel="nofollow noopener" target="_blank">#openhab</a> <a href="https://zhub.link/tags/mqtt" class="mention hashtag" rel="nofollow noopener" target="_blank">#mqtt</a> <a href="https://zhub.link/tags/ethernet" class="mention hashtag" rel="nofollow noopener" target="_blank">#ethernet</a> <a href="https://zhub.link/tags/arduino" class="mention hashtag" rel="nofollow noopener" target="_blank">#arduino</a> <a href="https://zhub.link/tags/cluster" class="mention hashtag" rel="nofollow noopener" target="_blank">#cluster</a> <a href="https://zhub.link/tags/vrrp" class="mention hashtag" rel="nofollow noopener" target="_blank">#vrrp</a> <a href="https://zhub.link/tags/lsyncd" class="mention hashtag" rel="nofollow noopener" target="_blank">#lsyncd</a> <a href="https://zhub.link/tags/mosquito" class="mention hashtag" rel="nofollow noopener" target="_blank">#mosquito</a> <a href="https://zhub.link/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://zhub.link/tags/keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#keepalived</a>

Thomas Liske<a href="https://ibh.social/tags/ifstate" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifstate</a> 1.11.7 was released: <a href="https://codeberg.org/liske/ifstate/releases/tag/1.11.7" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/liske/ifstate/releases/tag/1.11.7</a>(available in <a href="https://fosstodon.org/@alpinelinux" class="u-url mention" rel="nofollow noopener" target="_blank">@alpinelinux</a> edge + 3.19)This is a small bug-fix release for setups where ifstate is run from keepalived using the `vrrp_notify_fifo_script` setting. <a href="https://ifstate.net/docs/vrrp/" rel="nofollow noopener" translate="no" target="_blank">https://ifstate.net/docs/vrrp/</a>There was a a race condition breaking reconfiguration on state changes if more than a single vrrp instance or group was used.<a href="https://ibh.social/tags/linuxnetworking" class="mention hashtag" rel="nofollow noopener" target="_blank">#linuxnetworking</a> <a href="https://ibh.social/tags/AlpineLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a> <a href="https://ibh.social/tags/keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#keepalived</a>

Thomas Liske<a href="https://ibh.social/tags/ifstate" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifstate</a> 1.11.2 has been released: <a href="https://github.com/liske/ifstate/releases/tag/1.11.2" rel="nofollow noopener" translate="no" target="_blank">https://github.com/liske/ifstate/releases/tag/1.11.2</a>(available in @alpinelinux edge)Since ifstate 1.9 the vrrp-fifo action to be used with <a href="https://ibh.social/tags/keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#keepalived</a> was completely broken 😱. On <a href="https://fosstodon.org/@alpinelinux" class="u-url mention" rel="nofollow noopener" target="_blank">@alpinelinux</a> it only had affected the edge branch.<a href="https://ibh.social/tags/linuxnetworking" class="mention hashtag" rel="nofollow noopener" target="_blank">#linuxnetworking</a>

Thomas Liske<a href="https://ibh.social/tags/ifstate" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifstate</a> 1.11.0 has been released: <a href="https://github.com/liske/ifstate/releases/tag/1.11.0" rel="nofollow noopener" translate="no" target="_blank">https://github.com/liske/ifstate/releases/tag/1.11.0</a>(available in <a href="https://fosstodon.org/@alpinelinux" class="u-url mention" rel="nofollow noopener" target="_blank">@alpinelinux</a> edge)With this release it is possible to add ethtool default settings for interfaces and configure routes and rules conditional for vrrp setups (to be used with <a href="https://ibh.social/tags/keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#keepalived</a>).It also fixes not working settings for `ethtool --change` (speed, duplex etc.).<a href="https://ibh.social/tags/linuxnetworking" class="mention hashtag" rel="nofollow noopener" target="_blank">#linuxnetworking</a>

Yes, I Know IT ! 🎓Load balancing with HAProxy, Nginx and Keepalived in Linux<a href="https://linuxhandbook.com/load-balancing-setup/" rel="nofollow noopener" translate="no" target="_blank">https://linuxhandbook.com/load-balancing-setup/</a> <a href="https://mastodon.social/tags/Nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nginx</a> <a href="https://mastodon.social/tags/HAProxy" class="mention hashtag" rel="nofollow noopener" target="_blank">#HAProxy</a> <a href="https://mastodon.social/tags/Keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#Keepalived</a> <a href="https://mastodon.social/tags/WebServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebServer</a> <a href="https://mastodon.social/tags/LoadBalancing" class="mention hashtag" rel="nofollow noopener" target="_blank">#LoadBalancing</a> <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>

Thomas Liske<a href="https://ibh.social/tags/ifstate" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifstate</a> 1.8.5 has been released: <a href="https://github.com/liske/ifstate/releases/tag/1.8.5" rel="nofollow noopener" target="_blank">https://github.com/liske/ifstate/releases/tag/1.8.5</a>This release contains a important fix: it could happen that link settings are not correctly applied while ifstate does not show any error. This happens when the kernel does not report any errors. One of this settings is the vlan_id for vlan links 😱 When running as <a href="https://ibh.social/tags/VRRP" class="mention hashtag" rel="nofollow noopener" target="_blank">#VRRP</a> fifo script for <a href="https://ibh.social/tags/keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#keepalived</a> it is now possible to trigger a config reload by SIGHUP.Updates are available for <a href="https://ibh.social/tags/AlpineLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a> edge + 3.18.<a href="https://ibh.social/tags/release" class="mention hashtag" rel="nofollow noopener" target="_blank">#release</a> <a href="https://ibh.social/tags/linuxnetworking" class="mention hashtag" rel="nofollow noopener" target="_blank">#linuxnetworking</a>

Yes, I Know IT ! 🎓Load balancing with HAProxy, Nginx and Keepalived in Linux<a href="https://linuxhandbook.com/load-balancing-setup/" rel="nofollow noopener" target="_blank">https://linuxhandbook.com/load-balancing-setup/</a> <a href="https://mastodon.social/tags/Nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nginx</a> <a href="https://mastodon.social/tags/HAProxy" class="mention hashtag" rel="nofollow noopener" target="_blank">#HAProxy</a> <a href="https://mastodon.social/tags/Keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#Keepalived</a> <a href="https://mastodon.social/tags/WebServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebServer</a> <a href="https://mastodon.social/tags/LoadBalancing" class="mention hashtag" rel="nofollow noopener" target="_blank">#LoadBalancing</a> <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>

ItzTrainAye! I was able to load up two load balancers on different nodes in the cluster. These two load balancers have keepalived between them so if one goes down the other pics up the ip.. These front end 2 caddy instances also on different cluster memebers. So I'm about to start shutting down loadbalancers to see if things stay up!! Looks like keepalived screws up some metrics that the lb can no longer see. Need to work on that.<a href="https://hachyderm.io/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://hachyderm.io/tags/minilab" class="mention hashtag" rel="nofollow noopener" target="_blank">#minilab</a> <a href="https://hachyderm.io/tags/keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#keepalived</a> <a href="https://hachyderm.io/tags/gobetween" class="mention hashtag" rel="nofollow noopener" target="_blank">#gobetween</a> <a href="https://hachyderm.io/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#networking</a> <a href="https://hachyderm.io/tags/loadbalancer" class="mention hashtag" rel="nofollow noopener" target="_blank">#loadbalancer</a>

Recent searches

Search options

Administered by:

Server stats:

#keepalived

Recent searches

Search options

Administered by:

Server stats:

KeepAliveD

#keepalived