Re: alias issue with snapshot #1175

2023-05-10 Thread Sonic
Sorry for the noise. It did turn out to be that the 3rd party device was squatting on the .45 address. Thanks to all!

Re: alias issue with snapshot #1175

2023-05-09 Thread Sonic
On Tue, May 9, 2023 at 2:24 AM Stuart Henderson wrote: > The only strange thing in there that I'm seeing is > > inet 10.68.73.1 255.255.255.248 > ... > !route add -inet /24 10.68.73.1 > !route add -inet /24 10.68.73.1 > > i.e. adding a route pointing at the local machine for those various > networ

Re: alias issue with snapshot #1175

2023-05-09 Thread Sonic
On Tue, May 9, 2023 at 12:35 AM Navan Carson wrote: > Do you have names that depend on DNS in pf.conf? No.

Re: alias issue with snapshot #1175

2023-05-08 Thread Stuart Henderson
On 2023/05/08 10:48, Sonic wrote: > On Mon, May 8, 2023 at 9:24 AM Stuart Henderson > wrote: > > There's not enough information really. /etc/hostname.* and maybe results > > of ifconfig -A and netstat -rn might give more clues. > > Here's that info - hopefully not munged beyond use. > Note that t

Re: alias issue with snapshot #1175

2023-05-08 Thread Navan Carson
> On May 8, 2023, at 5:32 PM, Sonic wrote: > > No real difference in the output of ifconfig or netstat before and > after restarting the network after a reboot. > The .45 alias refuses to accept/pass data other than answer a ping > after booting until the network, or at least the interface (e

Re: alias issue with snapshot #1175

2023-05-08 Thread Sonic
No real difference in the output of ifconfig or netstat before and after restarting the network after a reboot. The .45 alias refuses to accept/pass data other than answer a ping after booting until the network, or at least the interface (em0) that contains the alias is restarted. >From outside tes

Re: alias issue with snapshot #1175

2023-05-08 Thread Sonic
On Mon, May 8, 2023 at 9:24 AM Stuart Henderson wrote: > There's not enough information really. /etc/hostname.* and maybe results > of ifconfig -A and netstat -rn might give more clues. Here's that info - hopefully not munged beyond use. Note that this is after the interface has been restarted (s

Re: alias issue with snapshot #1175

2023-05-08 Thread Stuart Henderson
On 2023-05-08, Sonic wrote: > 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

Re: alias issue with snapshot #1175

2023-05-08 Thread Sonic
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 bac

Re: alias issue with snapshot #1175

2023-05-07 Thread Sonic
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 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 (no

alias issue with snapshot #1175

2023-05-07 Thread Sonic
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 0xfff8 broadcast 51.67.20.47 inet 51.67.20.42 netmask 0x inet 51.67.20.43 net