summaryrefslogtreecommitdiff
path: root/astraceroute.8
AgeCommit message (Expand)AuthorFilesLines
2014-04-22man: astraceroute: Fix closing quotation markTobias Klauser1-1/+1
2014-03-14man: manpage warning fixesKartik Mistry1-3/+2
2013-08-21astraceroute: Support binding to a specific IP address.Oliver Smith1-0/+4
2013-07-29man: Align synopsis with other sectionsTobias Klauser1-1/+1
2013-06-17man: add colophon to the end of each document.Daniel Borkmann1-0/+4
2013-06-11man: astraceroute: minor: remove two trailing whitespacesDaniel Borkmann1-2/+2
2013-06-11man: improvements to astraceroute.8, inconsistent use of and ''Stephen Wadeley1-7/+7
2013-06-11man: improvements to language for astraceroute.8Stephen Wadeley1-28/+30
2013-05-30man: manpages hyphen and spelling mistakesKartik Mistry1-4/+4
2013-05-27man: minor: astraceroute: add .PPsDaniel Borkmann1-49/+49
2013-05-22man: astraceroute: minor edits all overJon Schipp1-19/+18
2013-05-16man: astraceroute: Make wording in description for --version consistentTobias Klauser1-1/+1
2013-05-15man: trafgen: Minor fixesTobias Klauser1-2/+2
2013-05-06man: finish astraceroute man pageDaniel Borkmann1-2/+65
2013-05-05man: start man page of astracerouteDaniel Borkmann1-0/+140
x path expects a vni in the packet with dst_metadata and relies on learnt or static forwarding information table to forward the packet - Bridge driver changes: per vlan dst_metadata support: - Our use case is vxlan and 1-1 mapping between vlan and vni, but I have kept the api generic for any tunnel info - Uapi to configure/unconfigure/dump per vlan tunnel data - new bridge port flag to turn this feature on/off. off by default - ingress hook: - if port is a tunnel port, use tunnel info in attached dst_metadata to map it to a local vlan - egress hook: - if port is a tunnel port, use tunnel info attached to vlan to set dst_metadata on the skb Other approaches tried and vetoed: - tc vlan push/pop and tunnel metadata dst: - though tc can be used to do part of this, these patches address a deployment case where bridge driver vlan filtering and forwarding information database along with vxlan driver forwarding information table and learning are required. - making vxlan driver understand vlan-vni mapping: - I had a series almost ready with this one but soon realized it duplicated a lot of vlan handling code in the vxlan driver ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat
-rw-r--r--drivers/net/vxlan.c196
-rw-r--r--include/linux/if_bridge.h1
-rw-r--r--include/net/ip_tunnels.h1
-rw-r--r--include/uapi/linux/if_bridge.h11
-rw-r--r--include/uapi/linux/if_link.h1
-rw-r--r--include/uapi/linux/neighbour.h1
-rw-r--r--net/bridge/Makefile5
-rw-r--r--net/bridge/br_forward.c2
-rw-r--r--net/bridge/br_input.c8
-rw-r--r--net/bridge/br_netlink.c140
-rw-r--r--net/bridge/br_netlink_tunnel.c296
-rw-r--r--net/bridge/br_private.h12
-rw-r--r--net/bridge/br_private_tunnel.h83
-rw-r--r--net/bridge/br_vlan.c24
-rw-r--r--net/bridge/br_vlan_tunnel.c203
15 files changed, 863 insertions, 121 deletions
diff --git a/drivers/net/vxlan.c b/drivers/net/vxlan.c