All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Bruin <jmdebruin@xmsnet.nl>
To: Jesse Gross <jesse@nicira.com>
Cc: LKML <linux-kernel@vger.kernel.org>, netdev <netdev@vger.kernel.org>
Subject: Re: [regression] 2.6.37+ commit 0363466866d9.... breaks tcp ipv6
Date: Tue, 18 Jan 2011 22:42:03 +0100	[thread overview]
Message-ID: <4D36092B.1090406@xmsnet.nl> (raw)
In-Reply-To: <AANLkTinejKw0pY5HncB2e0ocjqYuCwTBUwd2xkroWu+E@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3491 bytes --]

On 01/18/2011 09:06 PM, Jesse Gross wrote:
> On Tue, Jan 18, 2011 at 11:52 AM, Hans de Bruin<jmdebruin@xmsnet.nl>  wrote:
>> On 01/16/2011 09:24 PM, Hans de Bruin wrote:
>>>
>>> After last nights compile i lost the possibility to connect to ssh and
>>> http over ipv6. The connection stops at syn_sent. connections to my
>>> machine end in syn_recv. ping6 still works.
>>>
>>
>> The bisect ended in:
>>
>> 0363466866d901fbc658f4e63dd61e7cc93dd0af is the first bad commit
>> commit 0363466866d901fbc658f4e63dd61e7cc93dd0af
>> Author: Jesse Gross<jesse@nicira.com>
>> Date:   Sun Jan 9 06:23:35 2011 +0000
>>
>>     net offloading: Convert checksums to use centrally computed features.
>>
>>     In order to compute the features for other offloads (primarily
>>     scatter/gather), we need to first check the ability of the NIC to
>>     offload the checksum for the packet.  Since we have already computed
>>     this, we can directly use the result instead of figuring it out
>>     again.
>>
>>     Signed-off-by: Jesse Gross<jesse@nicira.com>
>>     Signed-off-by: David S. Miller<davem@davemloft.net>
>>
>>
>> ssh ::1  still works. And since dns still works I guess udp is not affected.
>> My nic is a:
>>
>> 09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit
>> Ethernet PCI Express (rev 02)
>
> Are you using vlans?  If so, can you please test this patch?
> http://patchwork.ozlabs.org/patch/79264/
>

No I am not using vlans. The option is even not set in the config file. 
Except for the disk less bit is a straightforward setup:

   bash-4.1# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
     inet 127.0.0.1/8 scope host lo
     inet6 ::1/128 scope host
        valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP 
qlen 1000
     link/ether 00:1c:23:2d:73:87 brd ff:ff:ff:ff:ff:ff
     inet 10.10.0.6/16 brd 10.10.255.255 scope global eth0
     inet6 2001:610:76e:0:21c:23ff:fe2d:7387/64 scope global dynamic
        valid_lft 86399sec preferred_lft 14399sec
     inet6 fe80::21c:23ff:fe2d:7387/64 scope link
        valid_lft forever preferred_lft forever
3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
     link/sit 0.0.0.0 brd 0.0.0.0
bash-4.1# ip route show
10.10.0.0/16 dev eth0  proto kernel  scope link  src 10.10.0.6
default via 10.10.0.1 dev eth0
bash-4.1# ip -6 route show
2001:610:76e::/64 dev eth0  proto kernel  metric 256  expires 86404sec
fe80::/64 dev eth0  proto kernel  metric 256
ff00::/8 dev eth0  metric 256
default via fe80::230:18ff:feae:75d8 dev eth0  proto kernel  metric 1024 
  expires 29sec hoplimit 64
bash-4.1# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
bash-4.1# ip6tables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
bash-4.1# brctl show
bridge name     bridge id               STP enabled     interfaces
bash-4.1# cat /proc/cmdline
root=/dev/nfs nfsroot=10.10.0.2:/nfs/root/psion/,v3,tcp ro ip=::: ::dhcp 
BOOT_IMAGE=nightlybuild-psion

-- 
Hans


[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 14483 bytes --]

  reply	other threads:[~2011-01-18 21:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-16 20:24 Possible ipv6 regression Hans de Bruin
2011-01-18 19:52 ` [regression] 2.6.37+ commit 0363466866d9.... breaks tcp ipv6 Hans de Bruin
2011-01-18 20:06   ` Jesse Gross
2011-01-18 21:42     ` Hans de Bruin [this message]
2011-01-18 22:03       ` Eric Dumazet
2011-01-19 13:17         ` Hans de Bruin
2011-01-21 19:47         ` Hans de Bruin
2011-01-21 19:55           ` Eric Dumazet
2011-01-21 20:38             ` Hans de Bruin
2011-01-21 22:15               ` Brandeburg, Jesse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D36092B.1090406@xmsnet.nl \
    --to=jmdebruin@xmsnet.nl \
    --cc=jesse@nicira.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.