Snarl an JSON

[anton]

Hi,

Stumbled upon the network notification and found a great use for it!
Tx!

My question is relating to JSON over the network.

I have enabled JSON and the network notification - the firewall is off
etc.

If i netstat -an then the JSON listener only listens on 127.0.0.1 port
9889 but not
on my network ip - 192.168.10.126.

The network listener does however listen eg: 192.168.10.10 9887

TCP 127.0.0.1:9887 0.0.0.0:0 LISTENING
TCP 127.0.0.1:9889 0.0.0.0:0 LISTENING

TCP 192.168.10.126:2101 192.168.10.126:59042 ESTABLISHED
TCP 192.168.10.126:9887 0.0.0.0:0 LISTENING
TCP 192.168.10.126:58450 216.52.233.67:12975 ESTABLISHED

Is this by design?

Messages sent to localhost are working perfectly but i need to be able
to send to an IP address of a remote
user browsing the intranet.

Many thanks,

Anton

[Sven Walther]

Hi Anton,

I think it's by design as until now all implementation used a hidden
(i)frame in the webpages which pointed always to localhost (this is the
trick how any webpage can notifiy you regardless how your firewall is
setup to the outer evil world ;))

So when your users are browsing the Intranet - out of their it is
localhost where JSON notifications come from :)

If you have open network access to the PCs normally SNP is used (it is
"cleaner" and has more possibilities at all.

c u

Sven

[Chris Peel]

Yes, JSON is limited to localhost by design for the reason Sven has
given. Notification forwarding (hopefully coming in R2.3) will add
the ability for a Snarl client to forward notifications to a remote IP
which will probably give you the functionality you want with little
extra config.