Udhcpc running, bouncing my links, and messing up my mesh network

The manual is not completely clear on this, though I suppose if I read it and thought enough about it, well maybe I would have figured it out. However, I would expect that if I set "Static Address" as the protocol of an interface, that nothing would attempt to run DHCP on the interface. It seems to me that my hand-configured setting on the interface would be enough to override what mesh11sd was doing, even to fetch the gateway.

I understand the autoconfig capability, where if someone just installs something and it comes up with no configuration that it will just work. But if I've configured something, I expect it to respect that I've configured.

I am not sure, but it also seems that on 22.05.6 that mesh11sd was upgraded from 2.x.x to 3.x.x. I'm guessing that's what screwed up my meshes and led me down this road in the first place, but I don't have 22.05.6 installed anyplace any more to look. If that is the case, that's a rather abrupt and surprising change.

Thanks for the info. However, I set auto_config to 0:

root@router3:~# uci show mesh11sd
mesh11sd.setup=mesh11sd
mesh11sd.setup.auto_config='0'
mesh11sd.mesh_params=mesh11sd
mesh11sd.mesh_params.mesh_fwding='1'
mesh11sd.mesh_params.mesh_rssi_threshold='-80'
mesh11sd.mesh_params.mesh_gate_announcements='1'
mesh11sd.mesh_params.mesh_hwmp_rootmode='4'
mesh11sd.mesh_params.mesh_hwmp_rann_interval='5000'
mesh11sd.mesh_params.mesh_hwmp_root_interval='5000'
mesh11sd.mesh_params.mesh_hwmp_active_path_timeout='5000'
mesh11sd.mesh_params.mesh_hwmp_active_path_to_root_timeout='6000'
mesh11sd.mesh_params.mesh_max_peer_links='16'
mesh11sd.mesh_params.mesh_connected_to_as='1'
mesh11sd.mesh_params.mesh_connected_to_gate='1'

and udhcpc still gets run. In fact, I set enabled to 0 (and verified it with mesh11sd status) and it doesn't affect the behavior at all. I'm wondering if I even needs mesh11sd, but it seems some mesh parameters can't be set without it.

Everything works fine without mesh11sd installed. I was pretty sure I needed it on 22.05.6, but it appears to no longer be necessary.

No, it was not, because the official status of 22.03 is:

The OpenWrt 22.03 release is considered outdated but will still receive limited security and bug fixes for some time.

Yes it does as portal detect is still active. You can consider this a bug and it has indeed been fixed in the new 3.1.1 release (see my earlier post). You can now also download it from master/snapshot if you want it from an "approved" source.
It will be available on 23.05 once the CI problem that is blocking merging of all updates for 23.05 is fixed there.

You will find it works up to a point with node to node communications becoming unstable and some nodes dropping out of the mesh at random as HWMP mac-routing will not be configured correctly. If you have just 2 nodes, you might get away with it.

...and 'for some time' is defined as ending to be this month, so upgrading to 23.05.x is strongly recommended very soon.

Yes indeed, so no version upgrades for packages there either.

Note though the OP says he had already moved to 23.05.3.

Thank you for the reply. I am just using point-to-point connections, but when the new version comes out I will install it and try it out. I was suspicious that there were things that wouldn't work, but my setup is simple.