Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

n2n 1.1 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News n2n 1.1 (Default branch)
# 1  
Old 04-09-2008
n2n 1.1 (Default branch)
n2n (network-to-network) is a layer-two peer-to-peer virtual private network (VPN) that allows users to exploit features typical of P2P applications at network instead of application level. This means that users can gain native IP visibility (e.g. two PCs belonging to the same n2n network can ping each other) and be reachable with the same network IP address regardless of the network where they currently belong. License: GNU General Public License v3 Changes:
A bug that prevented n2n from communicating with direct peers was fixed. Major code changes were made to pave for support of IPv6. Big-endian platforms are supported (in addition to x86). Updates were made to the Linux port so that it works like Mac OS X or Win32.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT SUNOS

veth

veth(4) 						     Linux Programmer's Manual							   veth(4)

NAME

       veth - Virtual Ethernet Device

DESCRIPTION

       The veth devices are virtual Ethernet devices.  They can act as tunnels between network namespaces to create a bridge to a physical network
       device in another namespace, but can also be used as standalone network devices.

       veth devices are always created in interconnected pairs.  A pair can be created using the command:

	   # ip link add <p1-name> type veth peer name <p2-name>

       In the above, p1-name and p2-name are the names assigned to the two connected end points.

       Packets transmitted on one device in the pair are immediately received on the other device.  When either devices is down the link state	of
       the pair is down.

       veth  device  pairs are useful for combining the network facilities of the kernel together in interesting ways.	A particularly interesting
       use case is to place one end of a veth pair in one network namespace and the other end in another network namespace, thus allowing communi-
       cation between network namespaces.  To do this, one first creates the veth device as above and then moves one side of the pair to the other
       namespace:

	   # ip link set <p2-name> netns <p2-namespace>

       ethtool(8) can be used to find the peer of a veth network interface, using commands something like:

	   # ip link add ve_A type veth peer name ve_B	 # Create veth pair
	   # ethtool -S ve_A	     # Discover interface index of peer
	   NIC statistics:
		peer_ifindex: 16
	   # ip link | grep '^16:'   # Look up interface
	   16: ve_B@ve_A: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc ...

SEE ALSO

       clone(2), network_namespaces(7), ip(8), ip-link(8), ip-netns(8)

COLOPHON

       This page is part of release 4.15 of the Linux man-pages project.  A description of the project, information about reporting bugs, and  the
       latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.

Linux								    2018-02-02								   veth(4)