This is repeatable every time. After a boot the .45 alias does not pass any traffic, its ports are closed. It will answer a ping, and shows up in "ifconfig -A" (or em0) and in netstat. The other 3 addresses work normally. Restarting the interface with "sh /etc/netstart em0" brings the .45 alias back to an active state.
On Sun, May 7, 2023 at 8:43 PM Sonic <sonicsm...@gmail.com> wrote: > > After doing a "sh /etc/netstart em0" that alias is back up and > working. The problem occurs after boot. > > On Sun, May 7, 2023 at 7:23 PM Sonic <sonicsm...@gmail.com> wrote: > > > > Hello, > > > > Upgrade a system to the latest snapshot - 1175 - and am seeing a > > problem with an alias address. > > The outside IP is part of a /29 (not actual addresses) : > > inet 51.67.20.41 netmask 0xfffffff8 broadcast 51.67.20.47 > > inet 51.67.20.42 netmask 0xffffffff > > inet 51.67.20.43 netmask 0xffffffff > > inet 51.67.20.45 netmask 0xffffffff > > The address 51.67.20.44 is used by another device connected to the > > same cable modem. > > All was working well until the upgrade and now the alias 51.67.20.45 > > will answer a ping but shows ports that should be open as closed, and > > traffic does not pass. > > The other 3 addresses (main and aliases) continue to work normally. > > > > Thanks for any assistance. > > Chris
