| 23 May 2025 |
 matthewcroughan | I find it hard to believe they could manufacture electronics like this without testing that edge case | 12:10:50 |
| matthewcroughan | a friend in hackspace has to do way more stringent tests to get approved on his dainty little RFID products | 12:11:07 |
 emily | I assume it's not going to start a fire… but I also assume you want the switch to keep running | 12:11:22 |
| emily | a bunch of RJ45 SFP+ modules will specifically tell you to space them out for heat reasons fwiw | 12:11:29 |
| emily | but anyway I'm not saying it's going to be a problem. I'm just saying I don't think you can say the TP-Link is definitely fine fanless and the XikeStor definitely isn't | 12:11:53 |
| emily | if I was worrying about cooling I'd definitely also be investing in ones with the Broadcom chip! since last time you were fine with one that hit 70 C at 10G | 12:15:10 |
 magic_rb | In reply to @emilazy:matrix.org
magic_rb: is now a good time to ask about your antenna config? :) oh yes, ill send pic | 22:40:50 |
| 24 May 2025 |
|  fromtheeast710 joined the room. | 05:10:19 |
|  prince213 joined the room. | 12:34:18 |
|  mjm joined the room. | 18:20:51 |
| matthewcroughan | is there any way to get the search domain of the network you're currently on? | 21:59:28 |
| matthewcroughan | like whether I am reachable at foo.lan or foo.localdomain or foo.bar | 22:00:08 |
 Jeff | sometimes a DHCP server will send you that information, otherwise there's no automated way | 22:08:52 |
| Jeff | and it's unlikely that a random computer connecting to a random network will get a DNS entry added to the DNS servers (not impossible, but certainly not to be relied on). | 22:10:08 |
| matthewcroughan | resolvectl tells you about these domains anyway which is nice | 22:12:38 |
| Jeff | only if the DHCP server tells your system | 22:20:03 |
| 25 May 2025 |
| prince213 | Can I have anyone review this PR? I know it's a review request but I'm looking for people with networking knowledge. | 12:09:06 |
| prince213 | https://github.com/NixOS/nixpkgs/pull/398587 | 12:09:07 |
| prince213 | Thanks in advance. | 12:09:15 |
| emily | cc K900 who expressed some interest in firewalld? | 13:05:15 |
| emily | ah already pinged on the PR I see | 13:05:28 |
| prince213 | It's quite a list | 13:06:19 |
| prince213 | But haven't seen any review yet | 13:06:28 |
| emily | looks like a very substantive PR, thanks for putting in all this work! I don't have time to review fully right now (and I'm not a networking expert), but a few suggestions:
- is it intended to be reviewed commit-by-commit? maybe some commits could be squashed to ease review, especially if some intermediate states may be broken (I approve of granular commits in general though!)
- could some of this be split up into separate PRs? it looks like there are parts that just make some modules/tests more abstracted over various firewalls rather than assuming one implementation? so if those could be reviewed and landed separately it may be easier to get this through. similarly, the commits that are adding additional features to the module, or adding support for it in other modules, could be split out (simple "add the package to the list" commits could all go in one PR to handle that in bulk, say; not saying one commit per PR)
| 13:08:27 |
| emily | large PRs are pretty daunting to review so if you can take advantage of the commit granularity to split out stuff that is obvious cleanups/improvements, and chores for "after" the functionality exists, it makes it more likely that someone will find time to give a detailed review of the core functionality :) | 13:09:37 |
| prince213 | Thanks for the advice. It was originally carried over from my previous work https://git.sr.ht/~prince213/firewalld-nix and I've squash some commits together for easier reviewing, but well it's probably not enough. | 13:18:11 |
| prince213 | I should reorganize the commits then. 🤔 | 13:18:47 |
|  HaroldOllivier changed their profile picture. | 18:56:54 |
| 26 May 2025 |
|  ximnoise left the room. | 02:55:25 |
| ximnoise joined the room. | 02:57:38 |
