Our Power Networks Distribution Centre (PNDC) has won a Cybersecurity & Resilience Award for its work bringing the latest cybersecurity research to real power networks: https://pndc.co.uk/pndc-wins-cybersecurity-and-resilience-award/ #CNI #CyberSecurity #Resilience #PNDC #PowerNetworks

CNI/EZLN u.a.: Brief an die Mütter, Väter, Familien Sucher*innen #CNI #EZLN #chiapas98 https://www.chiapas.eu/news.php?id=12660

Ruth Cadbury MP, chair of House of Commons transport committee, said they would quiz the companies involved “once the dust settles”, adding: “We need to ask serious questions about resilience and how we can ensure nothing like this happens again at #Heathrow or other airports.” #fire #CNI #resilience
https://www.thetimes.com/article/26c1cdb8-972e-4154-bf84-291c015a6c75?shareToken=749b90f84b150ff56cbfc2ab161700b1

Confidence in Cybersecurity Among UK CNI Leaders Amid 95% Breach Rate - https://www.redpacketsecurity.com/uk-cni-security-leaders-express-confidence-in-cybersecurity-despite-95-breach-rate/

#Question

What #CNI do you recommend for #HomeLab?

I have experience with:
- #Istio
- #Calico
- #Cilium *
- #Flannel *

*: I didn't configured them manually, they came with #k3s and I left them on defaults

I finally managed to create a new cluster with #Talos, and want to configure CNI for it.

New From #CNI: “Meeting the #Climate Emergency: University Information #Infrastructure for Researching Wicked Problems” (Final Report) https://www.infodocket.com/2025/03/14/new-from-cni-meeting-the-climate-emergency-university-information-infrastructure-for-researching-wicked-problems-final-report/ #climatechange #libraries #librarians @cni

From October 2024: #CNI

'Throughout history, including during World War II, reliance on its rail network for military logistics has created an “Achilles’ Heel” exploitable through contemporary unconventional warfare.

'... rail networks are relatively centralized, with key nodes, bridges, and junctions acting as chokepoints. Understanding this, Ukrainian special operators and intelligence services operating by, with, and through various Russian resistance groups have strategically targeted these key nodes to great effect.

'“Stop the Wagons” and the “Combat Organization of Anarcho-Communists” are the two most prominent Russian political groups expressing their opposition to the war by sabotaging railway infrastructure.

'These disruptions create logistical headaches for the Russian military, forcing them to reroute transport through longer or less efficient paths, further straining their already challenged logistics capabilities.

'Russia’s military doctrine relies on a consistent flow of supplies to sustain its forces at the front. Any interruption, particularly in the context of a war where Russian forces are already stretched thin, can have cascading effects on operations.

'... focus on railway depots, maintenance yards, and switching stations, though less vulnerable, play an essential role in the smooth functioning of the rail network and would create longer-lasting disruptions if damaged'.
https://irregularwarfare.org/articles/ukraines-railway-wars-how-to-sabotage-russian-military-logistics/

is Cilium native routing mode supposed to publish pod IPs on the interfaces in the host network namespace?

That would make sense to me as using the native network layer 2/3 routing.

Or am I required to turn on SNAT using the IP masquerading feature?

Pods are getting valid IPv6 GUAs in the LAN/host subnet, but of course nothing can return to them...

Good on the Canadians.

#CNI
https://www.canada.ca/en/natural-resources-canada/news/2025/03/canada-invests-in-the-next-generation-of-canadian-made-clean-affordable-nuclear-energy0.html