Source: linux-image-3.16-2-powerpc Severity: important Tags: upstream Dear Maintainer,
I'm running Debian sid on PowerPC (Mac Mini) with a Sun GEM ethernet adapter. The system is running a bridge configuration (brctl and friends) as an OpenVPN server. Last monday I upgraded to version 3.16 of the kernel (I was at 3.14). After a reboot, everything seemed fine, no error messages, no strangeness. That same day I connected to the OpenVPN service on the box and noticed that stuff didn't work as it did before the upgrade; specifically, I could only reach the server itself and other connected clients (read: everything on the tap0 part of the bridge) and nothing on the network (read: everything behing the eth0 part of the bridge). Initially I thought it might be a setup bug. Last two days I've rechecked everything, routing rules, firewalling stuff, etc; I verified the bridge worked within the host, but nothing traversed to/from the eth0 part of the bridge. Today, I downgraded the kernel to 3.2.60 (package from stable) as the previous 3.14 kernel was not avalable anymore (and of course, I deinstalled it..). After installation of the 3.2.60 kernel, my bridge setup works normally again. I'm pretty sure this is a bug in either the kernel bridge (tun) or ethernet (sungem) driver, or otherwise a bug in openvpn related to bridging on 3.16. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 3.2.0-4-powerpc Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
