similar to: VM''s on tunnels

Displaying 20 results from an estimated 11000 matches similar to: "VM''s on tunnels"

2003 Oct 13
0
PATCH : [Re: [Fwd: broadcast over gre tunnel?]]
Hi Guys, Here is our patch to allow broadcast packets over a GRE tunnel. Hopefully it might be accepted into the source someday. You need to enabled bridging and GRE tunnels in your kernel. No other options are required. The gre patch determines what type of protocol type to put in the GRE header based on the whether the packet is forwarded from a bridge or not. To use the patch: # Create
2008 Nov 22
2
[Bridge] bridge changes id on addif - is that normal?
hi i've setup the following on debian etch with bridge-utils 1.4 (backported) and kernel 2.6.26 from backports.org: vlan10 with raw device eth0 vlan20 with raw device eth0 br10 with initial port vlan10 br20 with initial port vlan20 i've set hw addr to DE:AD:BE:EF:34:10 for br10 and DE:AD:BE:EF:34:20 for br20 the bridges are used to connect virtual machine nic's. "brctl
2014 Dec 17
0
[PATCH 01/10] core: Split out UFO6 support
Split IPv6 support for UFO into its own feature similiar to TSO. This will later allow us to re-enable UFO support for virtio-net devices. Signed-off-by: Vladislav Yasevich <vyasevic at redhat.com> --- include/linux/netdev_features.h | 7 +++++-- include/linux/netdevice.h | 1 + include/linux/skbuff.h | 1 + net/core/dev.c | 35
2014 Dec 17
0
[PATCH 01/10] core: Split out UFO6 support
Split IPv6 support for UFO into its own feature similiar to TSO. This will later allow us to re-enable UFO support for virtio-net devices. Signed-off-by: Vladislav Yasevich <vyasevic at redhat.com> --- include/linux/netdev_features.h | 7 +++++-- include/linux/netdevice.h | 1 + include/linux/skbuff.h | 1 + net/core/dev.c | 35
2014 Dec 17
0
[PATCH 01/10] core: Split out UFO6 support
On 12/17/2014 05:45 PM, Michael S. Tsirkin wrote: > On Wed, Dec 17, 2014 at 01:20:46PM -0500, Vladislav Yasevich wrote: >> Split IPv6 support for UFO into its own feature similiar to TSO. >> This will later allow us to re-enable UFO support for virtio-net >> devices. >> >> Signed-off-by: Vladislav Yasevich <vyasevic at redhat.com> >> --- >>
2014 Dec 17
0
[PATCH 01/10] core: Split out UFO6 support
On 12/17/2014 05:45 PM, Michael S. Tsirkin wrote: > On Wed, Dec 17, 2014 at 01:20:46PM -0500, Vladislav Yasevich wrote: >> Split IPv6 support for UFO into its own feature similiar to TSO. >> This will later allow us to re-enable UFO support for virtio-net >> devices. >> >> Signed-off-by: Vladislav Yasevich <vyasevic at redhat.com> >> --- >>
2005 Jul 08
1
gre tunnel between networks with same subnet
/-----------------------\ | | |eth0 |eth0 |-------| |-------| | |eth1 eth1 | | -------- A |____ _______| B |----- | | \ / | | --------| | | --------| | | | |
2011 Mar 31
1
[PATCH] virtio_net: convert to hw_features
Signed-off-by: Micha? Miros?aw <mirq-linux at rere.qmqm.pl> --- drivers/net/virtio_net.c | 46 +++++++++++++++++++--------------------------- 1 files changed, 19 insertions(+), 27 deletions(-) This is an example conversion to hw_features when constraints are constant and can be detected at init time. Build tested only. diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
2011 Mar 31
1
[PATCH] virtio_net: convert to hw_features
Signed-off-by: Micha? Miros?aw <mirq-linux at rere.qmqm.pl> --- drivers/net/virtio_net.c | 46 +++++++++++++++++++--------------------------- 1 files changed, 19 insertions(+), 27 deletions(-) This is an example conversion to hw_features when constraints are constant and can be detected at init time. Build tested only. diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
2014 Dec 17
2
[PATCH 01/10] core: Split out UFO6 support
On Wed, Dec 17, 2014 at 01:20:46PM -0500, Vladislav Yasevich wrote: > Split IPv6 support for UFO into its own feature similiar to TSO. > This will later allow us to re-enable UFO support for virtio-net > devices. > > Signed-off-by: Vladislav Yasevich <vyasevic at redhat.com> > --- > include/linux/netdev_features.h | 7 +++++-- > include/linux/netdevice.h | 1
2014 Dec 17
2
[PATCH 01/10] core: Split out UFO6 support
On Wed, Dec 17, 2014 at 01:20:46PM -0500, Vladislav Yasevich wrote: > Split IPv6 support for UFO into its own feature similiar to TSO. > This will later allow us to re-enable UFO support for virtio-net > devices. > > Signed-off-by: Vladislav Yasevich <vyasevic at redhat.com> > --- > include/linux/netdev_features.h | 7 +++++-- > include/linux/netdevice.h | 1
2015 Jan 26
0
[PATCH 3/3] Revert "drivers/net: Disable UFO through virtio"
This reverts commit 3d0ad09412ffe00c9afa201d01effdb6023d09b4. Now that UFO functionality can correctly track the fragment id has been selected and select a fragment id if necessary, we can re-enable UFO on tap/macvap and virtio devices. Signed-off-by: Vladislav Yasevich <vyasevic at redhat.com> --- drivers/net/macvtap.c | 13 ++++++++----- drivers/net/tun.c | 19
2015 Jan 26
0
[PATCH 3/3] Revert "drivers/net: Disable UFO through virtio"
This reverts commit 3d0ad09412ffe00c9afa201d01effdb6023d09b4. Now that UFO functionality can correctly track the fragment id has been selected and select a fragment id if necessary, we can re-enable UFO on tap/macvap and virtio devices. Signed-off-by: Vladislav Yasevich <vyasevic at redhat.com> --- drivers/net/macvtap.c | 13 ++++++++----- drivers/net/tun.c | 19
2015 Jan 30
0
[PATCH v2 3/3] Revert "drivers/net: Disable UFO through virtio"
This reverts commit 3d0ad09412ffe00c9afa201d01effdb6023d09b4. Now that GSO functionality can correctly track if the fragment id has been selected and select a fragment id if necessary, we can re-enable UFO on tap/macvap and virtio devices. Signed-off-by: Vladislav Yasevich <vyasevic at redhat.com> --- drivers/net/macvtap.c | 13 ++++++++----- drivers/net/tun.c | 19
2015 Jan 30
0
[PATCH v2 3/3] Revert "drivers/net: Disable UFO through virtio"
This reverts commit 3d0ad09412ffe00c9afa201d01effdb6023d09b4. Now that GSO functionality can correctly track if the fragment id has been selected and select a fragment id if necessary, we can re-enable UFO on tap/macvap and virtio devices. Signed-off-by: Vladislav Yasevich <vyasevic at redhat.com> --- drivers/net/macvtap.c | 13 ++++++++----- drivers/net/tun.c | 19
2014 Dec 18
0
[PATCH 01/10] core: Split out UFO6 support
On 12/18/2014 02:54 AM, Michael S. Tsirkin wrote: > Cc Dave, pls remember to do this next time otherwise > your patches won't get merged :) > > On Wed, Dec 17, 2014 at 06:31:50PM -0500, Vlad Yasevich wrote: >> On 12/17/2014 05:45 PM, Michael S. Tsirkin wrote: >>> On Wed, Dec 17, 2014 at 01:20:46PM -0500, Vladislav Yasevich wrote: >>>> Split IPv6 support
2014 Dec 18
0
[PATCH 01/10] core: Split out UFO6 support
On 12/18/2014 02:54 AM, Michael S. Tsirkin wrote: > Cc Dave, pls remember to do this next time otherwise > your patches won't get merged :) > > On Wed, Dec 17, 2014 at 06:31:50PM -0500, Vlad Yasevich wrote: >> On 12/17/2014 05:45 PM, Michael S. Tsirkin wrote: >>> On Wed, Dec 17, 2014 at 01:20:46PM -0500, Vladislav Yasevich wrote: >>>> Split IPv6 support
2014 Oct 27
0
[PATCH net 1/2] drivers/net: Disable UFO through virtio
IPv6 does not allow fragmentation by routers, so there is no fragmentation ID in the fixed header. UFO for IPv6 requires the ID to be passed separately, but there is no provision for this in the virtio net protocol. Until recently our software implementation of UFO/IPv6 generated a new ID, but this was a bug. Now we will use ID=0 for any UFO/IPv6 packet passed through a tap, which is even
2014 Oct 27
0
[PATCH net 1/2] drivers/net: Disable UFO through virtio
IPv6 does not allow fragmentation by routers, so there is no fragmentation ID in the fixed header. UFO for IPv6 requires the ID to be passed separately, but there is no provision for this in the virtio net protocol. Until recently our software implementation of UFO/IPv6 generated a new ID, but this was a bug. Now we will use ID=0 for any UFO/IPv6 packet passed through a tap, which is even
2003 Jul 22
7
broadcast over gre tunnel?
Hello, I connected the network 192.168.1.0 with 192.168.2.0 over the internet trough a GRE-Tunnel. I don''t know if I set up all things right: The client-pcs in both networks have a subnet mask of 255.255.255.0 and 192.168.2.x''s default gateway is the server wich has started the tunnel. The 192.168.1.x''s default gateway is 192.168.1.250 wich routes traffic destinated to