| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <495BFEAF.6000006@haveacry.com>
Date: Thu, 01 Jan 2009 08:22:23 +0900
From: Speedster <speedster@...eacry.com>
To: Ilpo Järvinen <ilpo.jarvinen@...sinki.fi>
CC: Netdev <netdev@...r.kernel.org>, bugme-daemon@...zilla.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [Bugme-new] [Bug 12327] New: Intermittent TCP issues with =>
2.6.27
Ilpo Järvinen wrote:
> On Mon, 29 Dec 2008, Andrew Morton wrote:
>
>> (switched to email. Please respond via emailed reply-to-all, not via the
>> bugzilla web interface).
>>
>> On Mon, 29 Dec 2008 18:52:40 -0800 (PST) bugme-daemon@...zilla.kernel.org wrote:
>>
>>> http://bugzilla.kernel.org/show_bug.cgi?id=12327
>>>
>>> Summary: Intermittent TCP issues with => 2.6.27
>>> Product: Networking
>>> Version: 2.5
>>> KernelVersion: 2.6.27
>>> Platform: All
>>> OS/Version: Linux
>>> Tree: Mainline
>>> Status: NEW
>>> Severity: normal
>>> Priority: P1
>>> Component: IPV4
>>> AssignedTo: shemminger@...ux-foundation.org
>>> ReportedBy: speedster@...eacry.com
>>>
>>>
>>> Latest working kernel version: 2.6.26.8
>>> Earliest failing kernel version: 2.6.27
>>> Distribution: Ubuntu
>>> Hardware Environment: amd64, KVM
>>> Software Environment:
>>> Problem Description:
>>>
>>> As reported in LP #296767
>>> (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/296767) I am experiencing
>>> intermittent TCP issues over a PPP ADSL2+ connection with the only change being
>>> an upgrade to 2.6.27.
>>>
>>> A number of websites, ping, traceroute work correctly but I simply can't
>>> connect to several including:
>>>
>>> - store.apple.com
>>> - youtube.com
>>> - ANZ internet banking (anz.com.au)
>>> - MSN messenger
>>>
>>> I have also tried compiling a generic 2.6.28-rc4 kernel and this still suffers
>>> from the same issue, however if I reboot into the previous Ubuntu kernel
>>> (2.6.24) or a vanilla 2.6.26 kernel the issue disappears.
>>>
>>> Steps to reproduce:
>>>
>>> 1. Use a KVM guest as a gateway to a PPP internet connection
>>> 2. Boot with kernel <= 2.6.26
>>> 3. Observe functioning networking
>>> 4. Boot into 2.6.27+
>>> 5. Observe broken networking
>
> Can you please describe the full topology (which is connected to where and
> using what, and locations of nats, tun/taps, netfilter things, etc.)...
> There's some contradiction between the ubuntu report description and what
> you're giving here.
>
> Based on your dumps I find it unlikely that the problem would be in the
> end host tcp but I'll verify the packets field by field still to be
> absolutely sure. I'd guess that either the sent packet or reply gets
> lost somewhere since it never arrives with 2.6.27/2.6.28-rcx.
>
The gateway machine (whinge) runs as a KVM guest, and shares a physical
host with three other guests (one Windows, two Linux). Below are the
outputs of bridge topology and VLAN tagging on the physical host.
speedster@...mper:~$ brctl show
bridge name bridge id STP enabled interfaces
dmz 8000.364121864f53 no vnet0
vnet4
external 8000.00801e14ffc8 no vlan50
vnet3
internal 8000.00801e14ffc8 no vlan200
vnet1
vnet2
vnet5
-----------------------------------
speedster@...mper:~$ sudo cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLAN_NAME_TYPE_PLUS_VID_NO_PAD
vlan50 | 50 | eth1
vlan200 | 200 | eth1
vlan201 | 201 | eth1
vlan202 | 202 | eth1
-----------------------------------
Whinge (gateway) has three interfaces - one each that connect as taps on
the DMZ (vnet4), internal (vnet5) and external (vnet3) bridges. vlan50
is connected to the ADSL2 modem. vlan200 is connected to a physical
switch that laptops, access points, other computers connect to.
Ifconfig output from whinge:
speedster@...nge:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:3e:24:f7:a1
inet6 addr: fe80::216:3eff:fe24:f7a1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:20302278 errors:0 dropped:0 overruns:0 frame:0
TX packets:21094867 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13224666138 (13.2 GB) TX bytes:19329455294 (19.3 GB)
eth0:1 Link encap:Ethernet HWaddr 00:16:3e:24:f7:a1
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
eth1 Link encap:Ethernet HWaddr 00:16:3e:58:27:c4
inet addr:203.26.xxx.xxx Bcast:203.26.xxx.xxx
Mask:255.255.255.240
inet6 addr: fe80::216:3eff:fe58:27c4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1602092 errors:0 dropped:0 overruns:0 frame:0
TX packets:1352585 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1078162279 (1.0 GB) TX bytes:636885252 (636.8 MB)
eth2 Link encap:Ethernet HWaddr 00:16:3e:61:48:91
inet addr:192.168.200.1 Bcast:192.168.200.255
Mask:255.255.255.0
inet6 addr: fe80::216:3eff:fe61:4891/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21355818 errors:0 dropped:0 overruns:0 frame:0
TX packets:20024872 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:18440347046 (18.4 GB) TX bytes:13623311915 (13.6 GB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:115 errors:0 dropped:0 overruns:0 frame:0
TX packets:115 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:36784 (36.7 KB) TX bytes:36784 (36.7 KB)
ppp0 Link encap:Point-to-Point Protocol
inet addr:202.72.xxx.xxx P-t-P:202.72.xxx.xxx
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:2053229 errors:0 dropped:0 overruns:0 frame:0
TX packets:1432508 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:1837869380 (1.8 GB) TX bytes:637947402 (637.9 MB)
-----------------------------------
eth1 -> ppp0 does not pass through NAT; it is simply routed.
eth2 -> ppp0 passes through netfilter MASQUERADE in POSTROUTING
There is a netfilter firewall running on whinge, but I have tried
removing all rules, setting policies to ACCEPT and running a simple
masquerade rule from eth2 to ppp0
When the issue manifests itself there are connection issues to sites
from both physical machines, as well as KVM guests connected to both the
DMZ and internal bridges.
I'd like to reiterate that throughout my testing, only whinge had
changes made to it (change kernel/reboot). The KVM host and network
topology remained unchanged throughout testing.
Please let me know if there is any more information required.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists