Bug#759481: Patches for sorting radiobuttons and deprecating SHA-1
Just trying to understand the implications: - This bug was not fixed yet in the package (0.7.5) that is in debian 8, right?- Having this bug means all the certificates I create with a non fixed version will stop working in 2016 (which is in less than 2 months). If that's all true, could you please fix it soon. Thank youJochen
Bug#685382: mysql-server: bind :: results in listening to IPv6 only
Package: mysql-server Version: 5.5.24+dfsg-6 Severity: important Dear Maintainer, when trying to make mysql listen on both interfaces like described here: http://dev.mysql.com/doc/refman/5.5/en/ipv6-server-config.html it will listen on IPv6 ONLY! $ mysqld --bind-address=:: $ netstat -ltpn|grep -i mysql tcp6 0 0 :::3306 :::*LISTEN 27119/mysqld When setting bind-address=:: in the my.cnf it's the exact same behaviour. Since it is a very basic requirement I consider this a major bug. Thank you -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages mysql-server depends on: ii mysql-server-5.5 5.5.24+dfsg-6 mysql-server recommends no packages. mysql-server suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#571634: [Pkg-xen-devel] Bug#571634: bridge loosing connection
Unfortunately I'm not able to replace the kernel since grub in the domU doesn't recognize my xvda drive. /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/xvda2. Check your device.map. I then inserted (hd0) /dev/xvda into the /boot/grub/devices.map but with no luck. I'm still getting the bridge-breakdowns. The bridge itself seems to be up but only restarting the domU helps. /etc/init.d/networking restart has no effect nor does ifconfig eth1 down ifconfig eth1 up. Please help. Am 06.09.10 11:21, schrieb Pasi Kärkkäinen: On Mon, Sep 06, 2010 at 10:31:28AM +0200, Jochen Demmer wrote: Hi, I'm not sure but I think I suffer under the same problem with a bit different setup with squeeze testing and xen 4.0rc5. In fact I'm using bridges in the dom0 and the connections to the domU get lost sporadically. In don't see where's a solution to the problem... Is it now a bug? When it's an iptables bug, where's the corresponding bug in the iptables bugtracker and what exactly is iptables doing wrong. You stated ...but as the syslog message clearly indicates this rule works perfectly when the traffic is bridged. I'm using bridges but it's not working obviously. I don't really see any errors in the log below. Have you tried using different kernel in the domU? If network is fine from dom0, then this sounds like a bug in the domU kernel. What kernel are you running in the domU? -- Pasi /etc/network/interfaces auto br0 allow-hotplug br0 iface br0 inet static address 10.100.200.20 netmask 255.255.255.0 dns-nameservers 10.100.200.3 gateway 10.100.200.3 bridge_ports eth0 allow-hotplug br1 auto br1 iface br1 inet manual bridge_ports eth1 This is my logs: Sep 6 09:47:14 elise kernel: [71970.564974] br1: port 2(vif1.1) entering disabled state Sep 6 09:47:14 elise kernel: [71970.578040] br1: port 2(vif1.1) entering disabled state Sep 6 09:47:14 elise kernel: [71970.718785] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:14 elise kernel: [71970.718797] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:14 elise kernel: [71970.718803] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:14 elise kernel: [71970.724864] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:14 elise kernel: [71970.724874] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:15 elise kernel: [71970.871846] br0: port 2(vif1.0) entering disabled state Sep 6 09:47:15 elise kernel: [71970.890073] br0: port 2(vif1.0) entering disabled state Sep 6 09:47:15 elise kernel: [71971.010275] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:15 elise kernel: [71971.010286] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:15 elise kernel: [71971.016391] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:17 elise kernel: [71972.912040] device vif3.0 entered promiscuous mode Sep 6 09:47:17 elise kernel: [71972.915898] br0: port 2(vif3.0) entering learning state Sep 6 09:47:17 elise kernel: [71972.948656] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:17 elise kernel: [71972.953266] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:17 elise kernel: [71972.953273] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:17 elise kernel: [71972.986255] device vif3.1 entered promiscuous mode Sep 6 09:47:17 elise kernel: [71972.990441] br1: port 2(vif3.1) entering learning state Sep 6 09:47:17 elise kernel: [71973.011096] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:17 elise kernel: [71973.011102] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported
Bug#571634: bridge loosing connection
Hi, I'm not sure but I think I suffer under the same problem with a bit different setup with squeeze testing and xen 4.0rc5. In fact I'm using bridges in the dom0 and the connections to the domU get lost sporadically. In don't see where's a solution to the problem... Is it now a bug? When it's an iptables bug, where's the corresponding bug in the iptables bugtracker and what exactly is iptables doing wrong. You stated ...but as the syslog message clearly indicates this rule works perfectly when the traffic is bridged. I'm using bridges but it's not working obviously. /etc/network/interfaces auto br0 allow-hotplug br0 iface br0 inet static address 10.100.200.20 netmask 255.255.255.0 dns-nameservers 10.100.200.3 gateway 10.100.200.3 bridge_ports eth0 allow-hotplug br1 auto br1 iface br1 inet manual bridge_ports eth1 This is my logs: Sep 6 09:47:14 elise kernel: [71970.564974] br1: port 2(vif1.1) entering disabled state Sep 6 09:47:14 elise kernel: [71970.578040] br1: port 2(vif1.1) entering disabled state Sep 6 09:47:14 elise kernel: [71970.718785] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:14 elise kernel: [71970.718797] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:14 elise kernel: [71970.718803] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:14 elise kernel: [71970.724864] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:14 elise kernel: [71970.724874] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:15 elise kernel: [71970.871846] br0: port 2(vif1.0) entering disabled state Sep 6 09:47:15 elise kernel: [71970.890073] br0: port 2(vif1.0) entering disabled state Sep 6 09:47:15 elise kernel: [71971.010275] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:15 elise kernel: [71971.010286] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:15 elise kernel: [71971.016391] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:17 elise kernel: [71972.912040] device vif3.0 entered promiscuous mode Sep 6 09:47:17 elise kernel: [71972.915898] br0: port 2(vif3.0) entering learning state Sep 6 09:47:17 elise kernel: [71972.948656] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:17 elise kernel: [71972.953266] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:17 elise kernel: [71972.953273] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:17 elise kernel: [71972.986255] device vif3.1 entered promiscuous mode Sep 6 09:47:17 elise kernel: [71972.990441] br1: port 2(vif3.1) entering learning state Sep 6 09:47:17 elise kernel: [71973.011096] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:17 elise kernel: [71973.011102] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:17 elise kernel: [71973.016383] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:17 elise kernel: [71973.016392] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:17 elise kernel: [71973.016398] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Sep 6 09:47:18 elise kernel: [71974.706987] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi) Sep 6 09:47:18 elise kernel: [71974.734701] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi) Sep 6 09:47:32 elise kernel: [71987.913527] br0: port 2(vif3.0) entering forwarding state Sep 6 09:47:32 elise kernel: [71987.988031] br1: port 2(vif3.1) entering forwarding state
