supernode(1) [debian man page]

supernode(1)							   USER COMMANDS						      supernode(1)

NAME

       supernode - n2n supernode daemon

SYNOPSIS

       supernode -l <port> [-v]

DESCRIPTION

       N2N is a peer-to-peer VPN system. Supernode is a node introduction registry, broadcast conduit and packet relay node for the n2n system. On
       startup supernode begins listening on the specified UDP port for node registrations, and other packets to route. The supernode can  service
       any  number of communities and routes packets only between members of the same community. The supernode does not hold the community encryp-
       tion key and so cannot snoop or inject packets into the community.

       Supernode can service a number of n2n communities concurrently. Traffic does not cross between communities.

       All logging goes to stdout.

OPTIONS

       -l <port>
	      listen on the given UDP port

       -v     use verbose logging

EXAMPLES

       supernode -l 7654 -v
	      Start supernode listening on UDP port 7654 with verbose output.

RESTART

       When suprenode restarts it loses all registration information from associated edge nodes. It can take up to five minutes for the edge nodes
       to re-register and normal traffic flow to resume.

EXIT STATUS

       supernode is a daemon and any exit is an error

AUTHOR

       Luca Deri ( deri (at) ntop.org ), Richard Andrews ( andrews (at) ntop.org ), Don Bindner

SEE ALSO

       ifconfig(8) edge(8)

revision 3679							    Jan 3, 2009 						      supernode(1)

UDP(4P) 																   UDP(4P)

NAME

       udp - Internet User Datagram Protocol

SYNOPSIS

       #include <sys/socket.h>
       #include <netinet/in.h>

       s = socket(AF_INET, SOCK_DGRAM, 0);

DESCRIPTION

       UDP  is	a  simple, unreliable datagram protocol which is used to support the SOCK_DGRAM abstraction for the Internet protocol family.  UDP
       sockets are connectionless, and are normally used with the sendto and recvfrom calls, though the connect(2) call may also be  used  to  fix
       the destination for future packets (in which case the recv(2) or read(2) and send(2) or write(2) system calls may be used).

       UDP  address  formats  are  identical to those used by TCP. In particular UDP provides a port identifier in addition to the normal Internet
       address format.	Note that the UDP port space is separate from the TCP port space (i.e. a UDP port may not be "connected" to a  TCP  port).
       In  addition  broadcast	packets  may be sent (assuming the underlying network supports this) by using a reserved "broadcast address"; this
       address is network interface dependent.

       Options at the IP transport level may be used with UDP; see ip(4P).

DIAGNOSTICS

       A socket operation may fail with one of the following errors returned:

       [EISCONN]      when trying to establish a connection on a socket which already has one, or when trying to send a datagram with the destina-
		      tion address specified and the socket is already connected;

       [ENOTCONN]     when trying to send a datagram, but no destination address is specified, and the socket hasn't been connected;

       [ENOBUFS]      when the system runs out of memory for an internal data structure;

       [EADDRINUSE]   when an attempt is made to create a socket with a port which has already been allocated;

       [EADDRNOTAVAIL]
		      when an attempt is made to create a socket with a network address for which no network interface exists.

SEE ALSO

       getsockopt(2), recv(2), send(2), socket(2), intro(4N), inet(4F), ip(4P)

4.2 Berkeley Distribution					   May 16, 1986 							   UDP(4P)