On Tue, May 9, 2023 at 2:24 AM Stuart Henderson <s...@spacehopper.org> wrote: > The only strange thing in there that I'm seeing is > > inet 10.68.73.1 255.255.255.248 > ... > !route add -inet <rfc1918_a>/24 10.68.73.1 > !route add -inet <rfc1918_b>/24 10.68.73.1 > > i.e. adding a route pointing at the local machine for those various > networks, but that's not relating to the address where you mentioned > having the problem.
I guess it might be better to point the route to the peer. Works either way. > Perhaps diffing ifconfig -A (or maybe netstat -rn) between the working > and non-working state will give a clue. I just eyeballed it and they look the same but I'll run a diff to make sure. Was able to test another system with a /29 and had no issues leaving out an alias and having all the other addresses work fine, but in this case there was no 3rd party device connected to the cable modem utilizing that unused address. Hopefully by this weekend I can do some testing by unplugging the 3rd party device and see what transpires. Thanks! Chris