I put the pi in the PFI section, which makes sense to me, at least. And used "sunss", not "sunss-pi", since the machine type is not really relevant.

Putting pi in PFI section is ok to me as there is no other place proper, and would it be worth modifying document by changing

164.96/27 (.164.96 - .164.127): PFI

to

164.96/27 (.164.96 - .164.127): PFI (Top ring)

or something?

OK, Merged at 95eaf19

I am not sure just how dnsmasq updates are applied at Subaru. The directory seems to be populated by root umask 022, but does have a .git directory. Can someone at Subaru do the update? The one non-LAM, non-JHU change since the Subaru version is from moving a configuration line into the site-specific config file. That should be fine, but I'd like someone who can do a `git fetch` to confirm that.

And agreed about the ics_doc change. Can that just be done live on master?

I can do the update, during this week's downtime. The configuration of the production dnsmasq server at the telescope has been diverged from the master branch due to some temporary local modifications. The issue with the master/main branch is that it still contains hosts-subaru/pfs.hosts.

If you need to modify any files in hosts-subaru/ or macs-subaru/, please do: changes there will not affect operations anywhere else.

The summit dnsmasq configuration has been updated with the sunss host entry and the service has been restarted.