similar to: [Bridge] RFC: [PATCH] bridge vlan integration

Displaying 20 results from an estimated 130 matches similar to: "[Bridge] RFC: [PATCH] bridge vlan integration"

2017 Apr 15
11
[PATCH RFC (resend) net-next 0/6] virtio-net: Add support for virtio-net header extensions
Curreclty virtion net header is fixed size and adding things to it is rather difficult to do. This series attempt to add the infrastructure as well as some extensions that try to resolve some deficiencies we currently have. First, vnet header only has space for 16 flags. This may not be enough in the future. The extensions will provide space for 32 possbile extension flags and 32 possible
2017 Apr 15
11
[PATCH RFC (resend) net-next 0/6] virtio-net: Add support for virtio-net header extensions
Curreclty virtion net header is fixed size and adding things to it is rather difficult to do. This series attempt to add the infrastructure as well as some extensions that try to resolve some deficiencies we currently have. First, vnet header only has space for 16 flags. This may not be enough in the future. The extensions will provide space for 32 possbile extension flags and 32 possible
2010 Mar 03
1
[RFC][ PATCH 3/3] vhost-net: Add mergeable RX buffer support to vhost-net
This patch glues them all together and makes sure we notify whenever we don't have enough buffers to receive a max-sized packet, and adds the feature bit. Signed-off-by: David L Stevens <dlstevens at us.ibm.com> diff -ruN net-next-p2/drivers/vhost/net.c net-next-p3/drivers/vhost/net.c --- net-next-p2/drivers/vhost/net.c 2010-03-02 13:01:34.000000000 -0800 +++
2010 Mar 03
1
[RFC][ PATCH 3/3] vhost-net: Add mergeable RX buffer support to vhost-net
This patch glues them all together and makes sure we notify whenever we don't have enough buffers to receive a max-sized packet, and adds the feature bit. Signed-off-by: David L Stevens <dlstevens at us.ibm.com> diff -ruN net-next-p2/drivers/vhost/net.c net-next-p3/drivers/vhost/net.c --- net-next-p2/drivers/vhost/net.c 2010-03-02 13:01:34.000000000 -0800 +++
2010 Apr 06
1
[PATCH v3] Add Mergeable receive buffer support to vhost_net
This patch adds support for the Mergeable Receive Buffers feature to vhost_net. +-DLS Changes from previous revision: 1) renamed: vhost_discard_vq_desc -> vhost_discard_desc vhost_get_heads -> vhost_get_desc_n vhost_get_vq_desc -> vhost_get_desc 2) added heads as argument to ghost_get_desc_n 3) changed "vq->heads" from iovec to vring_used_elem, removed casts 4)
2010 Apr 06
1
[PATCH v3] Add Mergeable receive buffer support to vhost_net
This patch adds support for the Mergeable Receive Buffers feature to vhost_net. +-DLS Changes from previous revision: 1) renamed: vhost_discard_vq_desc -> vhost_discard_desc vhost_get_heads -> vhost_get_desc_n vhost_get_vq_desc -> vhost_get_desc 2) added heads as argument to ghost_get_desc_n 3) changed "vq->heads" from iovec to vring_used_elem, removed casts 4)
2007 Apr 18
4
[Bridge] [PATCH/RFC] Let {ip, arp}tables "see" bridged VLAN tagged {I, AR}P packets
Hi all, The patch below does four trivial changes and one big change Trivial changes, these are all in br_netfilter.c: - check ar_pln==4 when giving bridged ARP packets to arptables - delete unnecessary if in br_nf_local_in - add more logging for the "Argh" message - add some brag-comments in the file head comment Big change: let {ip,arp}tables see VLAN tagged {I,AR}P packets. This
2007 Jul 31
1
[Bridge] brctl uses incorrect sysfs path
Hi, I noticed that brctl (or more accurately, libbridge) is using the wrong path when doing various lookups in sysfs: e.g. /sys/class/net/brXXX/stp_state when it should use /sys/class/net/brXXX/bridge/stp_state. This doesn't cause any problems on most systems as it falls back to the ioctl when the sysfs attempt fails; however the ioctl method is apparently deprecated. I believe the
2017 Apr 15
0
[PATCH RFC (resend) net-next 5/6] virtio-net: Add support for vlan acceleration vnet header extension.
This extension allows us to pass vlan ID and vlan protocol data to the host hypervisor as part of the vnet header and lets us take advantage of HW accelerated vlan tagging in the host. It requires support in the host to negotiate the feature. When the extension is enabled, the virtio device will enabled HW accelerated vlan features. Signed-off-by: Vladislav Yasevich <vyasevic at
2009 Jul 13
1
[PATCH node] Adds vlan support to auto-installations for the node. bz#511056
If the vlan kernel argument is provided, then it is used during networking auto-configuration. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-config-networking | 56 ++++++++++++++++++++++++++++++++------ scripts/ovirt-early | 7 ++++- 2 files changed, 53 insertions(+), 10 deletions(-) diff --git a/scripts/ovirt-config-networking
2015 Sep 10
1
[PATCH] launch: libvirt: Better error when bridge / virbr0 doesn't exist (RHBZ#1262127).
The current diagnostic is terrible. This one tells the user how to diagnose and fix the problem. --- src/launch-libvirt.c | 47 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 47 insertions(+) diff --git a/src/launch-libvirt.c b/src/launch-libvirt.c index 1c0bfac..d4c4c47 100644 --- a/src/launch-libvirt.c +++ b/src/launch-libvirt.c @@ -181,6 +181,7 @@ static int is_blk (const
2013 Jan 09
16
[Bridge] [PATCH net-next V5 00/14] Add basic VLAN support to bridges
This series of patches provides an ability to add VLANs to the bridge ports. This is similar to what can be found in most switches. The bridge port may have any number of VLANs added to it including vlan 0 priority tagged traffic. When vlans are added to the port, only traffic tagged with particular vlan will forwarded over this port. Additionally, vlan ids are added to FDB entries and become
2015 Mar 03
1
Re: QEMU interface type=ethernet
2015-03-02 23:41 GMT+03:00 Brian Rak <brak@gameservers.com>: > In IRC, I was directed to this patch: > https://www.redhat.com/archives/libvir-list/2015-February/msg01212.html ... > which does exactly what I was looking for. It doesn't build cleanly in that > state, but it's pretty trivial fix (needs actualType added to the function > definition for
2018 Dec 06
2
[PATCH v2] Revert "launch: libvirt: Use qemu-bridge-helper to implement a full network (RHBZ#1148012)."
Let's actually compile and test the patch this time, rather than trusting the RHEL 7.6 patch to apply directly to head ... Rich.
2011 Aug 11
1
[PATCH] fix augtool calls
parse input augtool strings to oper,key,value --- scripts/network.py | 32 ++++++++++++++++---------------- 1 files changed, 16 insertions(+), 16 deletions(-) diff --git a/scripts/network.py b/scripts/network.py index f51ee7c..65b551c 100644 --- a/scripts/network.py +++ b/scripts/network.py @@ -165,11 +165,11 @@ class Network: ntpconf = ntpconf.split("\n") for line
2002 May 08
0
Security Advisory
--Qz2CZ664xQdCRdPu Content-Type: multipart/mixed; boundary="BI5RvnYi6R4T2M87" Content-Disposition: inline --BI5RvnYi6R4T2M87 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! Unfortunately there is a very unpopular announcement to be made on this list: A netfilter security advisory. Phillipe Biondi has been
2009 Oct 09
1
[PATCH node] validify ipv4/ipv6 static/dhcp choice else loop
If you select an option that's not listed during ipv4/ipv6 setup it will accept it without verification. This corrects that behavior and forces a valid option to be picked. --- scripts/ovirt-config-networking | 106 +++++++++++++++++++++------------------ 1 files changed, 58 insertions(+), 48 deletions(-) diff --git a/scripts/ovirt-config-networking b/scripts/ovirt-config-networking index
2008 Jul 16
6
vlans+bonding+bridging
hi, I have to configure Xen server and DomU''s which should be able to talk to different vlans - depending on services put on DomU''s. I would like to enslave 2 NICs via bond interface. Both NICs are on trunk ports which are configured in the same way, the same native vlan. I don''t know, if I have to add vlans tagging to eth* interfaces then enslave tagged eth*
2014 May 28
1
problem with bond/team network interfaces
Hello, I have VM attached to bridge br0. VM can see the network (ping works) when the bridge has ethernet interfaces. But when I create bond or team device and attach it to a bridge instead of eth interface, VM does not ping anymore. Any ideas why? Thanks, Nerijus
2007 Apr 18
1
[Bridge] Re: Bridge Digest, Vol 31, Issue 6
Hello You must add first: vlan (tagged) to eth2 eth2 interface is not tagged by default and not know vlan-s . It is like a cisco if you have 24 ports in cisco by default all ports are in vlan1. if you want to do trunk (with vlans) you myst add (vlans) to this ports (tagged or untagged) So you can compare that all interfaces in linux by default are in one vlan(but not tagged). (only for