Ivy - Revision history

Ghattenb at 09:11, 24 August 2023

2023-08-24T09:11:15Z

← Older revision		Revision as of 03:11, 24 August 2023
Line 5:		Line 5:
	Paparazzi software applications default to binding to locahost and thus unable to communicate with peers residing elsewhere on the local area network. Ivy and subsequently the paparazzi software applications can be directed to bind to a local network interface instead, thereby permitting LAN communication with peers by simply supplying a bus designation command-line argument shown below. These can be saved in a Paparazzi Center session for persistence.		Paparazzi software applications default to binding to locahost and thus unable to communicate with peers residing elsewhere on the local area network. Ivy and subsequently the paparazzi software applications can be directed to bind to a local network interface instead, thereby permitting LAN communication with peers by simply supplying a bus designation command-line argument shown below. These can be saved in a Paparazzi Center session for persistence.

	Including the libivy headers and library and using a predefined set of messages, it is possible for any software component to take part in communication in a Paparazzi biotope. Ivy, the protocol itself is developed independently of the Paparazzi project and can be obtained along with examples and documentation from https://~~www~~.~~eei~~.~~cena.fr/products/ivy~~/ .		Including the libivy headers and library and using a predefined set of messages, it is possible for any software component to take part in communication in a Paparazzi biotope. Ivy, the protocol itself is developed independently of the Paparazzi project and can be obtained along with examples and documentation from https://ivybus.gitlab.io/ .

	== Ivy Networks ==		== Ivy Networks ==

Openuas: Cena has not implemented http to https autoforwarding, thus adjusted this wikipage

2022-06-20T05:58:39Z

Cena has not implemented http to https autoforwarding, thus adjusted this wikipage

← Older revision		Revision as of 23:58, 19 June 2022
Line 5:		Line 5:
	Paparazzi software applications default to binding to locahost and thus unable to communicate with peers residing elsewhere on the local area network. Ivy and subsequently the paparazzi software applications can be directed to bind to a local network interface instead, thereby permitting LAN communication with peers by simply supplying a bus designation command-line argument shown below. These can be saved in a Paparazzi Center session for persistence.		Paparazzi software applications default to binding to locahost and thus unable to communicate with peers residing elsewhere on the local area network. Ivy and subsequently the paparazzi software applications can be directed to bind to a local network interface instead, thereby permitting LAN communication with peers by simply supplying a bus designation command-line argument shown below. These can be saved in a Paparazzi Center session for persistence.

	Including the libivy headers and library and using a predefined set of messages, it is possible for any software component to take part in communication in a Paparazzi biotope. Ivy, the protocol itself is developed independently of the Paparazzi project and can be obtained along with examples and documentation from ~~http~~://www.eei.cena.fr/products/ivy/ .		Including the libivy headers and library and using a predefined set of messages, it is possible for any software component to take part in communication in a Paparazzi biotope. Ivy, the protocol itself is developed independently of the Paparazzi project and can be obtained along with examples and documentation from https://www.eei.cena.fr/products/ivy/ .

	== Ivy Networks ==		== Ivy Networks ==

Ghattenb at 15:40, 4 January 2017

2017-01-04T15:40:54Z

← Older revision		Revision as of 09:40, 4 January 2017
Line 5:		Line 5:
	Paparazzi software applications default to binding to locahost and thus unable to communicate with peers residing elsewhere on the local area network. Ivy and subsequently the paparazzi software applications can be directed to bind to a local network interface instead, thereby permitting LAN communication with peers by simply supplying a bus designation command-line argument shown below. These can be saved in a Paparazzi Center session for persistence.		Paparazzi software applications default to binding to locahost and thus unable to communicate with peers residing elsewhere on the local area network. Ivy and subsequently the paparazzi software applications can be directed to bind to a local network interface instead, thereby permitting LAN communication with peers by simply supplying a bus designation command-line argument shown below. These can be saved in a Paparazzi Center session for persistence.

	Including the libivy headers and library and using a predefined set of messages, it is possible for any software component to take part in communication in a Paparazzi biotope. Ivy, the protocol itself is developed independently of the Paparazzi project and can be obtained along with examples and documentation from http://www.~~tls~~.cena.fr/products/ivy/ .		Including the libivy headers and library and using a predefined set of messages, it is possible for any software component to take part in communication in a Paparazzi biotope. Ivy, the protocol itself is developed independently of the Paparazzi project and can be obtained along with examples and documentation from http://www.eei.cena.fr/products/ivy/ .

	== Ivy Networks ==		== Ivy Networks ==

Mcurrie: /* Extending Ivy Networks */

2015-07-29T00:59:30Z

Extending Ivy Networks

← Older revision		Revision as of 18:59, 28 July 2015
Line 33:		Line 33:
	Ivy requires that all peers in the network reside within the same local area network (it does not support routing). This can be solved by two different approaches.		Ivy requires that all peers in the network reside within the same local area network (it does not support routing). This can be solved by two different approaches.

	1) Virtual Private Network (VPN)		==== 1 - Virtual Private Network (VPN) ====

	By employing a standard IP VPN, remote hosts may communicate within the Ivy network permitting the VPN configuration is BRIDGED and not ROUTED. Many (routed) VPN configurations provide a network subnet for VPN clients and then route the traffic to the remote network. While this is approach is inline with best practices for IT systems, it does not permit Ivy to operate.		By employing a standard IP VPN, remote hosts may communicate within the Ivy network permitting the VPN configuration is BRIDGED and not ROUTED. Many (routed) VPN configurations provide a network subnet for VPN clients and then route the traffic to the remote network. While this is approach is inline with best practices for IT systems, it does not permit Ivy to operate.

	2) Ivy Bridging		==== 2 - Ivy Network Bridging ====

			[[TCP_Aircraft_Server\|TCP Aircraft Server]]

	-- looking for more information		-- looking for more information

Mcurrie at 00:47, 29 July 2015

2015-07-29T00:47:16Z

← Older revision		Revision as of 18:47, 28 July 2015
Line 1:		Line 1:
	Ivy is a [https://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern Publish-Subscribe (or pub/sub)] bus used in Paparazzi to link the different components of the ground network together. See [[Overview#System_Architecture System Architecture]] and [[DevGuide/Server_GCS_com]] for a general overview of its role in the Paparazzi UAS.		Ivy is a [https://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern Publish-Subscribe (or pub/sub)] bus used in Paparazzi to link the different components of the ground network together. See [[Overview#System_Architecture\|System Architecture]] and [[DevGuide/Server_GCS_com]] for a general overview of its role in the Paparazzi UAS.

	Ivy is text-based (ASCII) and features [https://en.wikipedia.org/wiki/Regular_expression regular expression] based message subscription. Ivy ~~agents (software applications)~~ announce their presence on the local network by UDP broadcast and share subscriptions. ~~Messages~~ are communicated thereafter via TCP ~~sockets~~. While the traffic is TCP, the use of UDP broadcast requires that peers reside within the same network subnet.		Ivy is text-based (ASCII) and features [https://en.wikipedia.org/wiki/Regular_expression regular expression] based message subscription. Software applications employing Ivy announce their presence on the local network by UDP broadcast and share subscriptions. All messages are communicated thereafter via direct TCP connections. While the traffic is TCP, the use of UDP protocol for broadcast announcements requires that peers reside within the same network subnet.

	Paparazzi software applications default to binding to locahost and thus ~~will not~~ communicate with peers residing elsewhere on the local area network. ~~Most~~ paparazzi ~~components~~ can be directed to bind to a local network interface thereby permitting LAN communication with peers by simply supplying a bus designation ~~commandline~~ argument shown below. These can be saved in a Paparazzi Center session for persistence.		Paparazzi software applications default to binding to locahost and thus unable to communicate with peers residing elsewhere on the local area network. Ivy and subsequently the paparazzi software applications can be directed to bind to a local network interface instead, thereby permitting LAN communication with peers by simply supplying a bus designation command-line argument shown below. These can be saved in a Paparazzi Center session for persistence.

	Including the libivy headers and library and using a predefined set of messages, it is possible for any software component to take part in communication in a Paparazzi biotope. Ivy, the protocol itself is developed independently of the Paparazzi project and can be obtained along with examples and documentation from http://www.tls.cena.fr/products/ivy/ .		Including the libivy headers and library and using a predefined set of messages, it is possible for any software component to take part in communication in a Paparazzi biotope. Ivy, the protocol itself is developed independently of the Paparazzi project and can be obtained along with examples and documentation from http://www.tls.cena.fr/products/ivy/ .
Line 15:		Line 15:
	Examples:		Examples:

	192.168.0.0/24 (192.168.0.x network) UDP/2010		192.168.0.0/24 (192.168.0.x network) UDP/2010; The following are all valid:

	The following are all valid:

	program -b 192.168.0.255		program -b 192.168.0.255
Line 24:		Line 22:
	program -b 192.168.0:2010		program -b 192.168.0:2010

	10.0.0.0/8 (10.x.x.x or 10.255.255.255)		10.0.0.0/8 (10.x.x.x or 10.255.255.255); The following are all valid:

	program -b 10		program -b 10

Mcurrie at 00:42, 29 July 2015

2015-07-29T00:42:41Z

@@ Line 1: / Line 1: @@
-Ivy is a text-based software bus featuring regular expression based message subscription and is used as the Paparazzi project's components' principal communication cord. Including the libivy headers and library and using a predefined set of messages it is possible for any software component to take part in communication in a Paparazzi biotope. The protocol itself is independent of the Paparazzi project and can be obtained along with examples and documentation from http://www.tls.cena.fr/products/ivy/ .
+Ivy is a [https://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern Publish-Subscribe (or pub/sub)] bus used in Paparazzi to link the different components of the ground network together.  See [[Overview#System_Architecture System Architecture]] and [[DevGuide/Server_GCS_com]] for a general overview of its role in the Paparazzi UAS.
-Ivy is used in Paparazzi as a bus to link the different programs of the ground network. See [[Overview#System_Architecture]]. Also see [[DevGuide/Server_GCS_com]] for some more details.
+Ivy is text-based (ASCII) and features [https://en.wikipedia.org/wiki/Regular_expression regular expression] based message subscription.  Ivy agents (software applications) announce their presence on the local network by UDP broadcast and share subscriptions.  Messages are communicated thereafter via TCP sockets.  While the traffic is TCP, the use of UDP broadcast requires that peers reside within the same network subnet.
 == Tools ==
-=== ivyprobe ===
-ivyprobe is a nice debug tool that lets you display messages sent on the Ivy bus as specified by a regex.
+=== Ivyprobe ===
 Run it with the '''-h''' option to display the help:

Flixr: ivyprobe

2015-03-10T15:40:41Z

ivyprobe

← Older revision		Revision as of 09:40, 10 March 2015
Line 1:		Line 1:
	Ivy is a text-based software bus featuring regular expression based message subscription and is used as the Paparazzi project's components' principal communication cord. Including the libivy headers and library and using a predefined set of messages it is possible for any software component to take part in communication in a Paparazzi biotope. The protocol itself is independent of the Paparazzi project and can be obtained along with examples and documentation from http://www.tls.cena.fr/products/ivy/ .		Ivy is a text-based software bus featuring regular expression based message subscription and is used as the Paparazzi project's components' principal communication cord. Including the libivy headers and library and using a predefined set of messages it is possible for any software component to take part in communication in a Paparazzi biotope. The protocol itself is independent of the Paparazzi project and can be obtained along with examples and documentation from http://www.tls.cena.fr/products/ivy/ .

			Ivy is used in Paparazzi as a bus to link the different programs of the ground network. See [[Overview#System_Architecture]]. Also see [[DevGuide/Server_GCS_com]] for some more details.

			== Tools ==
			=== ivyprobe ===
			ivyprobe is a nice debug tool that lets you display messages sent on the Ivy bus as specified by a regex.

			Run it with the '''-h''' option to display the help:
			$ ivyprobe -h

			E.g. to simply display all messages:
			$ ivyprobe '(.*)'

	[[Category:Communication]]		[[Category:Communication]]

Flixr: fix link

2013-05-07T20:16:30Z

fix link

← Older revision		Revision as of 14:16, 7 May 2013
Line 1:		Line 1:
	Ivy is a text-based software bus featuring regular expression based message subscription and is used as the Paparazzi project's components' principal communication cord. Including the libivy headers and library and using a predefined set of messages it is possible for any software component to take part in communication in a Paparazzi biotope. The protocol itself is independent of the Paparazzi project and can be obtained along with examples and documentation from http://~~www2~~.tls.cena.fr/products/ivy/ .		Ivy is a text-based software bus featuring regular expression based message subscription and is used as the Paparazzi project's components' principal communication cord. Including the libivy headers and library and using a predefined set of messages it is possible for any software component to take part in communication in a Paparazzi biotope. The protocol itself is independent of the Paparazzi project and can be obtained along with examples and documentation from http://www.tls.cena.fr/products/ivy/ .

	[[Category:Communication]]		[[Category:Communication]]

Opt at 11:51, 25 May 2011

2011-05-25T11:51:55Z

New page

Ivy is a text-based software bus featuring regular expression based message subscription and is used as the Paparazzi project's components' principal communication cord. Including the libivy headers and library and using a predefined set of messages it is possible for any software component to take part in communication in a Paparazzi biotope. The protocol itself is independent of the Paparazzi project and can be obtained along with examples and documentation from http://www2.tls.cena.fr/products/ivy/ .

[[Category:Communication]]