Most of this diff is just formatting edits, are you using a weird gofmt? Ideally the diff only has the real change! Otherwise doing git blame and etc becomes a lot harder in the future

Hi @benjojo , apologies, I'm not sure why vscode made all of those extra formatting edits. I'm just using stock extensions for go and nothing else. For what its worth just running gofmt outside of the IDE in the master branch shows that it would actually change several files so it seems perhaps the code isn't formatting properly to start with:

$ gofmt -l .
cmd/rtrdump/rtrdump.go
cmd/rtrmon/rtrmon.go
cmd/stayrtr/stayrtr_test.go
lib/server.go
lib/server_test.go
ossec/constrain.go
prefixfile/prefixfile.go
prefixfile/slurm.go
$ go version
go version go1.24.2 darwin/arm64

Later today I can try to push a change without the formatting edits to make my specific change easier to consume.

Ah, if "stock" go fmt wants to do that, then could you just make a commit go fmt-ing everything, and then put your change on top, otherwise this PR looks good to me (thank you!)

@benjojo I force-pushed a change that omits the extra formatting. There was also one minor tweak in moving the client read loop into a dedicated function so the Start() routine looks more tidy.
I figure if we want to handle formatting changes we can do that in another PR/change