| 8 Jul 2025 |
 hexa | tri-band | 15:04:55 |
| hexa | finally mlo | 15:05:03 |
 adamcstephens | I'm not sure I even have any clients that could use the third band | 15:09:49 |
 K900 | OpenWRT Two Soon(tm) | 15:10:43 |
| K900 | Also you will not be happy with it lol | 15:10:51 |
| hexa | the openwrt was a weird compromise as well | 15:11:05 |
| hexa | well, weird for my use cases | 15:11:13 |
| hexa | ax211 in the laptop and pixel 6a can both do 6ghz in theory, but I don't have anything 802.11be, so no MLO | 15:11:41 |
| hexa | honestly, gl-inet feels like a much better fit for production | 15:13:21 |
| hexa | what they do is much closer already to what openwrt people want | 15:13:31 |
 emily | the one and two both seem like there's no reason to buy them over just a normal BPI board | 15:14:08 |
| hexa | you mean the bpi-r4 pro? | 15:15:34 |
| hexa | how are your arm adventures with that board coming along? | 15:17:17 |
| emily | but like | 15:18:04 |
| emily | it's the same stuff | 15:18:08 |
| emily | the OpenWrt One/Two are just BPI boards | 15:18:14 |
| emily | R4 also works fine on OpenWrt, the reason we're having adventures is running our own kernel stack that tries to be close to mainline etc. | 15:18:35 |
| emily | people buying OpenWrt-branded stuff so they don't have to flash firmware aren't going to have issues :p | 15:19:08 |
| hexa | beyond the two and the bpi board being MT7988 based, why would gl-inet use a bpi board? | 15:20:18 |
| emily | wait I'm confused | 15:24:28 |
| emily | oh | 15:24:51 |
| emily | I think it's that the One was by bpi | 15:24:54 |
| emily | and the Two is GL.iNet | 15:24:57 |
| emily | yeah | 15:25:02 |
| emily | the Two looks nicer than I remember although I wish it had more than one SFP+ | 15:25:42 |
 aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) | Looking for tests and reviews on
https://github.com/NixOS/nixpkgs/pull/398587
nixos/firewalld: init | 18:57:37 |
 Charles | does anyone have mdns working with systemd-resolved+networkmanager | 20:31:43 |
| Charles | https://discourse.nixos.org/t/systemd-resolved-cant-resolve-mdns-local-names-avahi-can/60540/2?u=cobaltcause i tried this advice here which really seems like it should work, on 2 machines to attempt to publish and resolve, but it doesn't work | 20:32:18 |
| K900 | It Depends(tm) | 20:32:27 |
| K900 | The fun thing is that some applications will only talk to avahi | 20:32:31 |
