You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The MQTT Traffic channel protocol has changed; node information is now sent in a separate subchannel,
and flow information uses node id's instead of the full node data
Added RPC functionality: some information and functionality can now directly be accessed. If UBUS is
available, SPIN uses that. Otherwise, it will listen for JSON-RPC commands on /var/run/spin_rpc.sock.
An overview of the RPC methods can be requested by the RPC method 'list_rpc_methods'
The web API now provides and endpoint for all RPC methods as JSON-RPC
The SPIN/commands channel is no longer used for interactive commands, and all functionality in spind
handling commands here has been replaced by the RPC mechanism
The bubble app now uses the web API rpc endpoint for commands and direct information retrieval (except
traffic data). This improves performance and reliability, but it does mean that both spind and
spin_webui must be running.
'Most recent flows' information can now be retrieved for devices on the network
SPIN (and the bubble app) now provide functionality to block traffic between two specific nodes (in
addition to the existing 'all traffic from and to one node').
Added an 'extsrc' source, where pcap data can be sent to SPIN directly
The 'mqtt_host' on the bubble app now defaults to the host of the app itself
Bugfixes and refactoring: see the git repository for details