Re: Growl 1.4 - Not detecting all local IPv4 Addresses

[Daniel Siemer]

Really weird. The UI element is not necessarily guaranteed to be 100%
accurate, and is not directly bound in list to what the sockets really
will accept (its based on monitoring changes in any network state),
but the two in combination makes me think there is something funky
going on. Generally speaking, the external server socket is bound to
*:23053, meaning any interface, any address on port 23053 comes to
that server connection (with the exception of localhost, which we
start first with a separate socket). We generally handle switches
from say, wired to wifi fine. As a test when it isn't working after
starting the VPN, can you try toggling Listen for Incoming Network
Connections off and back on in the Network tab of Growl's
Preferences? This will restart the socket that listens on *:23053 and
should cause a refresh of the IP address info.

If it was just the UI problem, it would probably something in our IP
address monitor isn't handling the VPN right on addition (and it still
might be partly that). The socket though is listed properly by system
tools as being any address on any interface, and that should include
any changes to any interfaces. Have you ever seen other apps require
restarting to work with the VPN? As a warning, this may be difficult
for us to track down, as I have no VPN to test with. We do want to be
sure it works though in as wide a variety of situations as possible
though, so if you work with us on it, Im sure we can figure it out.

On Aug 14, 6:57 am, Robert Derelanko <fidgety...@gmail.com> wrote:
> This is likely not a common use of growl, but often I'm connected through a
> VPN while at work. My network supplies my machine the same IP I would use
> if on LAN while using the VPN. Most Growl supporting applications I use
> make use of this local IP. The problem is, while connected through the VPN
> my address is not a valid address in Growl's server tab UNLESS I quit and
> restart grow. Then it shows up.
>
> Is there a way to make this list of "you can connect manually to one of
> these addresses" list automatically update without having to restart growl
> each time I connect to my VPN?
>
> Part of my testing proves that unless the IP is in that list, the machine
> will not accept notifications even if any other application on my network
> can talk to the machine. If I restart growl, it detects the IP and all of
> my applications can now send notifications through the VPN.

[FidgetyRat]

Thanks for the reply.

I performed the test of unchecking the listen checkbox and rechecking it. No change, the IP is not in the list, and the application that sends the notification cannot establish a connection to the machine through the VPN connection. I wonder if Growl is listening for interface changes that are not posted normally. I use OpenVPN which establishes a TAP interface on the machine. Growl detects it and its interface just fine when restarted, and if the VPN connection is terminated, growl detects that and removes the IP from the list of available IPs, but does not seem to establish one on its own when the VPN connection is first established. 

Maybe some kind of auto-refresh in that part of the code?