Bug#696642: ifupdown: fails to bring up eth0.xx alias in bridge/vlan setup
Hello, On Mon, 25 Mar 2013 20:31:35 -0400 Michael Gilbert mgilb...@debian.org wrote: Just because it's getting close to the release doesn't mean you can just bypass maintainers when they're actively working on issues. Please stop pulling crap like this... What are you talking about? This bug stagnated for 2 months, then got done in an experimental upload, then got ignored for another 3 weeks. No. The fix was ready for two months already. It wasn't ignored, I waited for approval from Julien to upload it and other changes. Anyway, the nmu prodded the maintainer to get back to work, so ultimately, it was useful. No, it wasn't. I only made sure I can't trust you, and that your NMUs won't be acknowledged in the changelog. -- WBR, Andrew signature.asc Description: PGP signature
Bug#696642: ifupdown: fails to bring up eth0.xx alias in bridge/vlan setup
On Tue, Mar 26, 2013 at 3:34 AM, Andrew Shadura wrote: Hello, On Mon, 25 Mar 2013 20:31:35 -0400 Michael Gilbert mgilb...@debian.org wrote: Just because it's getting close to the release doesn't mean you can just bypass maintainers when they're actively working on issues. Please stop pulling crap like this... What are you talking about? This bug stagnated for 2 months, then got done in an experimental upload, then got ignored for another 3 weeks. No. The fix was ready for two months already. It wasn't ignored, I waited for approval from Julien to upload it and other changes. Anyway, the nmu prodded the maintainer to get back to work, so ultimately, it was useful. No, it wasn't. I only made sure I can't trust you, and that your NMUs won't be acknowledged in the changelog. That's an unkind attitude, but oh well, credit doesn't really matter to me anyway. By the way, have you read developers-reference 5.11.4? I think you may be misunderstanding nmu, but oh well. To each his own. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696642: ifupdown: fails to bring up eth0.xx alias in bridge/vlan setup
On Sat, Mar 23, 2013 at 15:28:02 -0400, Michael Gilbert wrote: Hi, It's getting close to the release now, so I've backported this fix from experimental and uploaded it as an nmu to unstable. Please see attached patch. Just because it's getting close to the release doesn't mean you can just bypass maintainers when they're actively working on issues. Please stop pulling crap like this... Cheers, Julien signature.asc Description: Digital signature
Bug#696642: ifupdown: fails to bring up eth0.xx alias in bridge/vlan setup
On Mon, Mar 25, 2013 at 6:05 AM, Julien Cristau jcris...@debian.org wrote: On Sat, Mar 23, 2013 at 15:28:02 -0400, Michael Gilbert wrote: Hi, It's getting close to the release now, so I've backported this fix from experimental and uploaded it as an nmu to unstable. Please see attached patch. Just because it's getting close to the release doesn't mean you can just bypass maintainers when they're actively working on issues. Please stop pulling crap like this... What are you talking about? This bug stagnated for 2 months, then got done in an experimental upload, then got ignored for another 3 weeks. Anyway, the nmu prodded the maintainer to get back to work, so ultimately, it was useful. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696642: ifupdown: fails to bring up eth0.xx alias in bridge/vlan setup
Hi, It's getting close to the release now, so I've backported this fix from experimental and uploaded it as an nmu to unstable. Please see attached patch. Best wishes, Mike ifupdown.patch Description: Binary data
Bug#696642: ifupdown: fails to bring up eth0.xx alias in bridge/vlan setup
Package: ifupdown Version: 0.7.5 Severity: normal Dear Maintainer, I am using Debian as the host OS in a KVM virtualization environment. In testing Wheezy, I've discovered the following issue where an ethernet alias is not brought up, and then a bridge alias is created rather than a new bridge. Also, the bridge alias is set up for a vlan rather than just the intended ethernet alias. To illustrate, I have set up squeeze and wheezy the same way and included output. Both machines installed with base+ssh server in tasksel with thees packages installed afterward: vlan bridge-utils qemu-kvm qemu-utils libvirt-bin ## interfaces file. except for IP, exact same on both machines. auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet manual auto eth0.4094 iface eth0.4094 inet manual vlan_raw_device eth0 auto br0 iface br0 inet static address 10.205.16.8 # 8 == wheezy, 9 == squeeze netmask 255.255.248.0 gateway 10.205.16.1 bridge_ports eth0 bridge_stp off bridge_fd 0 bridge_maxwait 0 auto br0.4094 iface br0.4094 inet manual bridge_ports eth0.4094 bridge_stp off bridge_fd 0 bridge_maxwait 0 Squeeze: expected outcome; vms added to br0 and br0.4094 work as expected. root@squeeze:~# ifconfig br0 Link encap:Ethernet HWaddr 00:1a:4b:33:f8:b0 inet addr:10.205.16.9 Bcast:10.205.23.255 Mask:255.255.248.0 inet6 addr: fe80::21a:4bff:fe33:f8b0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:194 errors:0 dropped:0 overruns:0 frame:0 TX packets:81 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:16684 (16.2 KiB) TX bytes:9842 (9.6 KiB) br0.4094 Link encap:Ethernet HWaddr 00:1a:4b:33:f8:b0 inet6 addr: fe80::21a:4bff:fe33:f8b0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:29 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1450 (1.4 KiB) TX bytes:468 (468.0 B) eth0 Link encap:Ethernet HWaddr 00:1a:4b:33:f8:b0 inet6 addr: fe80::21a:4bff:fe33:f8b0/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:1524 errors:0 dropped:0 overruns:0 frame:0 TX packets:93 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:203495 (198.7 KiB) TX bytes:11402 (11.1 KiB) Interrupt:16 Memory:f600-f6012800 eth0.4094 Link encap:Ethernet HWaddr 00:1a:4b:33:f8:b0 inet6 addr: fe80::21a:4bff:fe33:f8b0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:29 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1450 (1.4 KiB) TX bytes:936 (936.0 B) loLink 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:14 errors:0 dropped:0 overruns:0 frame:0 TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1078 (1.0 KiB) TX bytes:1078 (1.0 KiB) root@squeeze:~# brctl show bridge name bridge id STP enabled interfaces br0 8000.001a4b33f8b0 no eth0 br0.40948000.001a4b33f8b0 no eth0.4094 root@squeeze:~# cat /proc/net/vlan/config VLAN Dev name| VLAN ID Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD eth0.4094 | 4094 | eth0 root@squeeze:~# Wheezy: unexpected outcome; eth0.4094 isn't up, and also br0.4094 is not actually a bridge (see brctl output) root@wheezy:~# ifconfig br0 Link encap:Ethernet HWaddr 00:1c:c4:5d:53:d6 inet addr:10.205.16.8 Bcast:10.205.23.255 Mask:255.255.248.0 inet6 addr: fe80::21c:c4ff:fe5d:53d6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:375 errors:0 dropped:0 overruns:0 frame:0 TX packets:80 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25089 (24.5 KiB) TX bytes:8678 (8.4 KiB) br0.4094 Link encap:Ethernet HWaddr 00:1c:c4:5d:53:d6 inet6 addr: fe80::21c:c4ff:fe5d:53d6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:578 (578.0 B) eth0 Link encap:Ethernet HWaddr 00:1c:c4:5d:53:d6 UP BROADCAST
