ecute(), trim the skb to the L3 length before higher-layer
processing.
Signed-off-by: Ed Swierk
---
net/openvswitch/conntrack.c | 34 ++
1 file changed, 34 insertions(+)
diff --git a/net/openvswitch/conntrack.c b/net/openvswitch/conntrack.c
index d558e88
efore any L3+ conntrack
processing.
Signed-off-by: Ed Swierk
---
net/openvswitch/conntrack.c | 4
1 file changed, 4 insertions(+)
diff --git a/net/openvswitch/conntrack.c b/net/openvswitch/conntrack.c
index d558e88..1d24709 100644
--- a/net/openvswitch/conntrack.c
+++ b/net/openvswitch
netfilter hooks.
Currently the openvswitch receive path does not perform such trimming,
which will be fixed by the next patch. In preparation, this patch adds
a generic skb_network_trim() function.
Signed-off-by: Ed Swierk
---
include/linux/skbuff.h | 2 ++
net/core/skb
On 1/6/18 10:57, Pravin Shelar wrote:
> On Fri, Jan 5, 2018 at 10:59 PM, Ed Swierk wrote:
>>
>>
>> On Jan 5, 2018 22:17, "Pravin Shelar" wrote:
>>
>> On Fri, Jan 5, 2018 at 3:20 PM, Ed Swierk
>> wrote:
>>> On Fri, Jan 5, 2018 at 10:14
On Thu, Jan 4, 2018 at 7:36 PM, Pravin Shelar wrote:
> On Wed, Jan 3, 2018 at 7:49 PM, Ed Swierk wrote:
>> On Fri, Dec 22, 2017 at 3:31 PM, Pravin Shelar wrote:
>>> On Thu, Dec 21, 2017 at 7:17 AM, Ed Swierk
>>> wrote:
>>>> IPv4 and IPv6 packets may arri
On Fri, Dec 22, 2017 at 3:31 PM, Pravin Shelar wrote:
> On Thu, Dec 21, 2017 at 7:17 AM, Ed Swierk wrote:
>> IPv4 and IPv6 packets may arrive with lower-layer padding that is not
>> included in the L3 length. For example, a short IPv4 packet may have
>> up to 6 bytes of pad
On Fri, Dec 22, 2017 at 3:31 PM, Pravin Shelar wrote:
> On Thu, Dec 21, 2017 at 7:17 AM, Ed Swierk wrote:
>> IPv4 and IPv6 packets may arrive with lower-layer padding that is not
>> included in the L3 length. For example, a short IPv4 packet may have
>> up to 6 bytes of pad
_conntrack and nf_nat is that skb->len
reflects the length of the L3 header and payload, so there is no need
to refer back to ip_hdr->tot_len or ipv6_hdr->payload_len.
This change brings OVS into line with other netfilter users, trimming
IPv4 and IPv6 packets prior to L3+ netfilter
_conntrack and nf_nat is that skb->len
reflects the length of the L3 header and payload, so there is no need
to refer back to ip_hdr->tot_len or ipv6_hdr->payload_len.
This change brings OVS into line with other netfilter users, trimming
IPv4 and IPv6 packets prior to L3+ netfilter process
On Wed, Dec 13, 2017 at 4:58 PM, Pravin Shelar wrote:
> On Tue, Dec 12, 2017 at 8:17 AM, Ed Swierk wrote:
>> A short IPv4 packet may have up to 6 bytes of padding following the IP
>> payload when received on an Ethernet device.
>>
>> In the normal IPv4 receive path, i
On Tue, Dec 12, 2017 at 10:34 AM, Stephen Hemminger
wrote:
> Why not add to netdevsim rather than cluttering up a normal driver
> with test support. We just pulled a bunch of test stuff out of dummy
> for the same reason.
My test setup to trigger an openvswitch conntrack issue
(https://marc.info
m.
With this change, OVS conntrack trims IPv4 and IPv6 packets prior to
L3 processing.
Signed-off-by: Ed Swierk
---
net/openvswitch/conntrack.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/net/openvswitch/conntrack.c b/net/openvswitch/conntrack.c
index d558e882
leave it off by
default. Enable padding only when the otherwise unused IFF_AUTOMEDIA
flag is set (e.g. by writing 0x5003 to flags in sysfs).
Signed-off-by: Ed Swierk
---
drivers/net/veth.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/net/veth.c b/drivers/net/veth.c
index
I have a Linux kernel 4.4 system hosting a number of kvm VMs. Physical
interface eth0 connects to an 802.1Q trunk port on an external switch. Each VM
has a virtual interface (e1000 or virtio-net) connected to the physical NIC
through a macvtap interface and a VLAN interface; traffic between the
I'm trying to migrate from the Octeon SDK to a vanilla Linux 4.4
kernel for a Cavium OCTEON II (CN6880) board running in 64-bit
little-endian mode. So far I've gotten most of the hardware features I
need working, including XAUI/RXAUI, USB, boot bus and I2C, with a
fairly small set of patches.
https
On 12/13/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> Does this patch actually fix any observeable problem?
Without the patch, ifconfig down leaves the physical link up, which
confuses datacenter users who expect the link lights both on the NIC
and the switch to go out when they bring an interfa
On 9/19/07, Ayaz Abdulla <[EMAIL PROTECTED]> wrote:
> It seems that you are powering down the phy even if WOL is enabled.
Right; I've updated the patch to skip powering down the phy when wol is enabled.
> Secondly, can you powerdown the phy at the same time you start
> performing autoneg restart?
Log "no link during initialization" at KERN_INFO as it's not an error,
and occurs every time the interface comes up (when the
forcedeth-phy-power-down patch is applied).
Signed-off-by: Ed Swierk <[EMAIL PROTECTED]>
forcedeth-open-no-link-printk.patch
Description: Binary data
Bring the physical link down when the interface is down, by placing
the PHY in power-down state. This mirrors the behavior of other
drivers including e1000 and tg3.
Signed-off-by: Ed Swierk <[EMAIL PROTECTED]>
forcedeth-phy-power-down.patch
Description: Binary data
On 9/11/07, Herbert Xu <[EMAIL PROTECTED]> wrote:
> Please make it 65535 without an Ethernet header and 65521
> with an Ethernet header.
Here is a revised patch that allows MTUs up to 65535 for tap
interfaces and up to 65521 for tun interfaces.
(If I set the MTU to 65521 on a tun interface, ping
the value used by the e1000 driver, so it seems
like a safe upper limit.
Signed-off-by: Ed Swierk <[EMAIL PROTECTED]>
---
tap-change-mtu.patch
Description: Binary data
21 matches
Mail list logo
