[08:27:05] <blancadesal>	 morning
[08:27:30] <blancadesal>	 arturo: very quick review https://gitlab.wikimedia.org/repos/cloud/toolforge/jobs-api/-/merge_requests/126
[08:32:53] <arturo>	 👀
[08:39:04] <arturo>	 blancadesal: +1¡d
[08:41:19] <blancadesal>	 thanks!
[13:03:17] <arturo>	 topranks: because the debuging session from the other day, I created this https://github.com/aborrero/nftables-tracer
[13:04:54] <topranks>	 arturo: ooooh  
[13:04:57] <topranks>	 that's awesome! 
[13:05:12] <topranks>	 really nice idea, I'm a sucker for colour output in my terminal too <3
[13:05:42] <arturo>	 and now with increased nftables usage across the servers, it may be of additional help somewhere else
[13:07:10] <topranks>	 yeah totally 
[13:07:34] <topranks>	 so, just trying to understand it fully 
[13:08:08] <topranks>	 you create a matching rule in raw that the packet will hit first, with "nftrace set 1" on it?
[13:08:27] <topranks>	 which means that subsequent rules that same packet hits are traced?
[13:09:05] <arturo>	 yeah, basically the script automates the steps in here https://wiki.nftables.org/wiki-nftables/index.php/Ruleset_debug/tracing
[13:09:12] <arturo>	 plus colors, plus cleanup when done
[13:09:16] <topranks>	 cool, that's really nice yeah 
[13:09:48] <topranks>	 I moved my home router from iptables to nftables about a year ago 
[13:09:58] <topranks>	 was somewhat painful getting all the rules right 
[13:10:09] <topranks>	 Really wish I had of known about the tracing functionality back then!!
[13:11:49] <arturo>	 I have used this many times here for neutron, cloudgw, even kubernetes
[14:08:44] <blancadesal>	 arturo: not urgent, but review appreciated when you have a moment: https://gitlab.wikimedia.org/repos/cloud/toolforge/lima-kilo/-/merge_requests/200
[14:13:01] <arturo>	 👀
[14:16:03] <arturo>	 blancadesal: +1'd
[14:16:14] <blancadesal>	 thanks arturo
[16:00:25] * arturo offline