vale(4) [freebsd man page]
VALE(4) BSD Kernel Interfaces Manual VALE(4) NAME
vale -- a very fast Virtual Local Ethernet using the netmap API SYNOPSIS
device netmap DESCRIPTION
vale is a feature of the netmap(4) module that implements multiple Virtual switches that can be used to interconnect netmap clients, includ- ing traffic sources and sinks, packet forwarders, userspace firewalls, and so on. vale is implemented completely in software, and is extremely fast. On a modern machine it can move almost 20 Million packets per second (Mpps) per core with small frames, and about 70 Gbit/s with 1500 byte frames. OPERATION
vale dynamically creates switches and ports as clients connect to it using the netmap(4) API. vale ports are named vale[bdg:][port] where vale is the prefix indicating a VALE switch rather than a standard interface, bdg indicates a specific switch (the colon is a separator), and port indicates a port within the switch. Bridge and port names are arbitrary strings, the only constraint being that the full name must fit within 16 characters. See netmap(4) for details on the API. LIMITS vale currently supports up to 4 switches, 16 ports per switch, with 1024 buffers per port. These hard limits will be changed to sysctl vari- ables in future releases. SYSCTL VARIABLES
vale uses the following sysctl variables to control operation: dev.netmap.bridge The maximum number of packets processed internally in each iteration. Defaults to 1024, use lower values to trade latency with throughput. dev.netmap.verbose Set to non-zero values to enable in-kernel diagnostics. EXAMPLES
Create one switch, with a traffic generator connected to one port, and a netmap-enabled tcpdump instance on another port: tcpdump -ni vale-a:1 & pkt-gen -i vale-a:0 -f tx & Create two switches, each connected to two qemu machines on different ports. qemu -net nic -net netmap,ifname=vale-1:a ... & qemu -net nic -net netmap,ifname=vale-1:b ... & qemu -net nic -net netmap,ifname=vale-2:c ... & qemu -net nic -net netmap,ifname=vale-2:d ... & SEE ALSO
netmap(4) http://info.iet.unipi.it/~luigi/vale/ Luigi Rizzo, Giuseppe Lettieri: VALE, a switched ethernet for virtual machines, June 2012, http://info.iet.unipi.it/~luigi/vale/ AUTHORS
The vale switch was designed and implemented in 2012 by Luigi Rizzo and Giuseppe Lettieri at the Universita` di Pisa. vale was funded by the European Commission within FP7 Projects CHANGE (257422) and OPENLAB (287581). BSD
July 27, 2012 BSD
Check Out this Related Man Page
SHOREWALL6-NETMAP(5) [FIXME: manual] SHOREWALL6-NETMAP(5) NAME
netmap - Shorewall6 NETMAP definition file SYNOPSIS
/etc/shorewall/netmap DESCRIPTION
This file is used to map addresses in one network to corresponding addresses in a second network. It was added in Shorewall6 iin 4.4.23.3. Warning To use this file, your kernel and ip6tables must have RAWPOST table support included. The columns in the file are as follows (where the column name is followed by a different name in parentheses, the different name is used in the alternate specification syntax). TYPE - {DNAT|SNAT}:{P|O|T} Must be DNAT or SNAT followed by :P, :O or :T to perform stateless NAT. Stateless NAT requires Rawpost Table support in your kernel and iptables (see the output of shorewall6 show capabilities). If DNAT:P, traffic entering INTERFACE and addressed to NET1 has its destination address rewritten to the corresponding address in NET2. If SNAT:T, traffic leaving INTERFACE with a source address in NET1 has it's source address rewritten to the corresponding address in NET2. If DNAT:O, traffic originating on the firewall and leaving via INTERFACE and addressed to NET1 has its destination address rewritten to the corresponding address in NET2. If DNAT:P, traffic entering via INTERFACE and addressed to NET1 has its destination address rewritten to the corresponding address in NET2. If SNAT:P, traffic entering via INTERFACE with a destination address in NET1 has it's source address rewritten to the corresponding address in NET2. If SNAT:O, traffic originating on the firewall and leaving via INTERFACE with a source address in NET1 has it's source address rewritten to the corresponding address in NET2. NET1 - network-address Network in CIDR format (e.g., 2001:470:b:227/64). Beginning in Shorewall6 4.4.24, exclusion[1] is supported. INTERFACE - interface The name of a network interface. The interface must be defined in shorewall6-interfaces[2](5). Shorewall allows loose matches to wildcard entries in shorewall6-interfaces[2](5). For example, ppp0 in this file will match a shorewall6-interfaces[2](8) entry that defines ppp+. NET2 - network-address Network in CIDR format NET3 - network-address Optional - added in Shorewall 4.4.11. If specified, qualifies INTERFACE. It specifies a SOURCE network for DNAT rules and a DESTINATON network for SNAT rules. PROTO (Optional - protocol-number-or-name Only packets specifying this protocol will have their IP header modified. DEST PORT(S) (dport) - port-number-or-name-list Destination Ports. An optional comma-separated list of Port names (from services(5)), port numbers or port ranges; if the protocol is icmp, this column is interpreted as the destination icmp-type(s). ICMP types may be specified as a numeric type, a numberic type and code separated by a slash (e.g., 3/4), or a typename. See http://www.shorewall.net/configuration_file_basics.htm#ICMP. If the protocol is ipp2p, this column is interpreted as an ipp2p option without the leading "--" (example bit for bit-torrent). If no PORT is given, ipp2p is assumed. An entry in this field requires that the PROTO column specify icmp (1), tcp (6), udp (17), sctp (132) or udplite (136). Use '-' if any of the following field is supplied. SOURCE PORT(S) (sport) - port-number-or-name-list Optional source port(s). If omitted, any source port is acceptable. Specified as a comma-separated list of port names, port numbers or port ranges. An entry in this field requires that the PROTO column specify tcp (6), udp (17), sctp (132) or udplite (136). Use '-' if any of the following fields is supplied. FILES
/etc/shorewall/netmap SEE ALSO
http://shorewall.net/netmap.html http://shorewall.net/configuration_file_basics.htm#Pairs NOTES
1. exclusion http://www.shorewall.net/manpages6/shorewall6-exclusion.html 2. shorewall6-interfaces http://www.shorewall.net/manpages6/shorewall6-interfaces.html [FIXME: source] 06/28/2012 SHOREWALL6-NETMAP(5)