cocoaforge

From the control panel it appears that Growl supports notifications over networks. I had a quick look around but couldn't find much information.

Can one use, for example a remote web app, to open a sockets connection and display a growl notification on a remote system? If so, what port is Growl binded to and what format does it require the data to be in?

-jp

IngmarStein wrote:http://growl.info/documentation/developer/protocol.php

Many thanks, sorry I didn't find that earlier.

-jp

Is it possible to control WHICH notifications are forwarded to other computers? It would make sense to have that setting in the application settings. Failing that, perhaps programatically -- when growl notifcation commands are sent out to have a flag that they should be forwarded or not.

furthermore, in the developer link above, it is not enitrely clear whether both TCP and UDP are needed, and thus whether both ports have to be opened on the listening computer.

more detailed documentation of the network feature would be much appreciated by many i think.

cheers.

Such granularity is not currently supported.

bgannin wrote:Such granularity is not currently supported.

OK, understood. Currently I can't most of the basic network features to work, except growlnotify.

Note that I'm at a bit of a loss for terminology below. I use "main" and "remote" where I originally had "host" and "client" (respectively) but then realized it was probably the reverse -- the listening computers are actually hosts or servers and the broadcasting computer is a client? This is confusing to me, a fairly experienced person, so I imagine not too easy for a novice!

Anyway...

On the "main" computer I have "forward" checked and "use" checked for 2 computers on the LAN with a password entered. On the "remote" computers, I have "listen" checked and a server password entered. At first I didn't have "allow to register" checked, but found that with that checked, growl notify worked.

In sharing, I allowed both TCP 23052 and UDP 9887 on the "remote" computers.

On the "main" computer, I installed growlnotify. Now this works from bash:

growlnotify -m hey -H client1.local -P thepass

However, all other notifications shown on the "main computer" do not get forwarded to the "remotes".

Considering that I have allowed "remote application registration" on the "remotes", I wonder if the fact that these "remotes" have the same applications registered for local notifications causes anything to be mucked up?

And what about authentication? The "main" computer isn't authenticating normal notifications to the "remotes", or is it through the settings in the network tab of the growl pref pane?

And I still don't know whether both TCP and UDP are reqired -- if it's only for LAN I would prefer to keep TCP closed in the firewall.

Thanks for further help / clarification and I hope these comments are helpful for future improvements.

Wooden Brain Concepts wrote:

bgannin wrote:Such granularity is not currently supported.

OK, understood. Currently I can't most of the basic network features to work, except growlnotify.

Note that I'm at a bit of a loss for terminology below. I use "main" and "remote" where I originally had "host" and "client" (respectively) but then realized it was probably the reverse -- the listening computers are actually hosts or servers and the broadcasting computer is a client? This is confusing to me, a fairly experienced person, so I imagine not too easy for a novice!

Anyway...

On the "main" computer I have "forward" checked and "use" checked for 2 computers on the LAN with a password entered. On the "remote" computers, I have "listen" checked and a server password entered. At first I didn't have "allow to register" checked, but found that with that checked, growl notify worked.

In sharing, I allowed both TCP 23052 and UDP 9887 on the "remote" computers.

On the "main" computer, I installed growlnotify. Now this works from bash:

growlnotify -m hey -H client1.local -P thepass

However, all other notifications shown on the "main computer" do not get forwarded to the "remotes".

Considering that I have allowed "remote application registration" on the "remotes", I wonder if the fact that these "remotes" have the same applications registered for local notifications causes anything to be mucked up?

And what about authentication? The "main" computer isn't authenticating normal notifications to the "remotes", or is it through the settings in the network tab of the growl pref pane?

And I still don't know whether both TCP and UDP are reqired -- if it's only for LAN I would prefer to keep TCP closed in the firewall.

Thanks for further help / clarification and I hope these comments are helpful for future improvements.

This should have gone into a new thread...

Anyhow, our networking support right now is pretty bad. However, if it's all on the same subnet with no firewall in between the boxes, why are you wanting to open ports on the firewall?

This should have gone into a new thread...

Anyhow, our networking support right now is pretty bad. However, if it's all on the same subnet with no firewall in between the boxes, why are you wanting to open ports on the firewall?

If it should have gone into a new thread please feel free to move it.

As for opening ports on the firewall: I am not an expert, but in my limited experience with applications that require ports open, those ports have to be open even within the same subnet. Even ports required by iPhoto Bonjour, Printer Sharing, and such must be open on the "serving" computer.

Wooden Brain Concepts wrote:

This should have gone into a new thread...

Anyhow, our networking support right now is pretty bad. However, if it's all on the same subnet with no firewall in between the boxes, why are you wanting to open ports on the firewall?

If it should have gone into a new thread please feel free to move it.

As for opening ports on the firewall: I am not an expert, but in my limited experience with applications that require ports open, those ports have to be open even within the same subnet. Even ports required by iPhoto Bonjour, Printer Sharing, and such must be open on the "serving" computer.

As I said, unless you have a firewall in between the two boxes, you don't need to open ports



(box 1) (box 2)



______________________
Firewall
----------------------

Internets


If box 1 and box 2 are behind that firewall, then they don't need to open a port if they are not going to the internet.

well thanks but in any case in my experience they do need to be open, not sure what is unique about my configuration, then. but since they are now open, the cause of the failure to notify across the LAN as described above is not firewalls, but something else, which is what what has become of this thread is mainly about.

thanks.