[Bug 614389] New: iputils arping not working
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c0 Summary: iputils arping not working Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: i586 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: marco@nucleus.it QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.55 Safari/533.4 Afert the upgrade to iputils-ss021109-305.1.i586.rpm arping is not working properly. Before : the command arping -I eth0 192.168.0.88 send the arp request to broadcast 21:00:38.264597 00:0c:29:e5:30:1e > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.0.88 .... After: the command arping -I eth0 192.168.0.88 21:17:33.919294 00:0c:29:e5:30:1e > ff:0c:ff:e5:00:1e, ethertype ARP (0x0806), length 42: Request who-has 192.168.0.88 .... why arping send the broadcast to ff:0c:ff:e5:00:1e ????? Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c yang xiaoyu <xyyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |ms@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c2 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #2 from Marius Tomaschewski <mt@novell.com> 2010-06-18 08:11:59 UTC --- (In reply to comment #0)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.55 Safari/533.4
Afert the upgrade to iputils-ss021109-305.1.i586.rpm arping is not working properly.
Before : the command arping -I eth0 192.168.0.88 send the arp request to broadcast 21:00:38.264597 00:0c:29:e5:30:1e > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 192.168.0.88 ....
After: the command arping -I eth0 192.168.0.88 21:17:33.919294 00:0c:29:e5:30:1e > ff:0c:ff:e5:00:1e, ethertype ARP (0x0806), length 42: Request who-has 192.168.0.88 ....
why arping send the broadcast to ff:0c:ff:e5:00:1e ?????
Because it received a reply. This is IMO completely normal behavior. See also "man arping": -b Send only MAC level broadcasts. Normally arping starts from sending broadcast, and switch to unicast after reply received. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c4 --- Comment #4 from mine mine <marco@nucleus.it> 2010-06-18 08:34:56 UTC ---
Because it received a reply. This is IMO completely normal behavior. See also "man arping":
-b Send only MAC level broadcasts. Normally arping starts from sending broadcast, and switch to unicast after reply received.
Not true arping -I ethlan -b 192.168.1.95 10:32:04.588517 00:0d:60:eb:c4:5e > ff:0d:ff:eb:00:5e, ethertype ARP (0x0806), length 42: Request who-has 192.168.1.95 (ff:0d:ff:eb:00:5e) tell 192.168.1.254 Before upgrading iputils arping did always the corret thing even if it received a reply. Try downgrading it . Thanks for the support -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c5 mine mine <marco@nucleus.it> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |marco@nucleus.it Resolution|WORKSFORME | Severity|Normal |Major --- Comment #5 from mine mine <marco@nucleus.it> 2010-06-18 08:39:55 UTC --- I don think it is correct because the behavior changed. Is correct to send an arp request to unicast ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c6 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |610839 --- Comment #6 from Marius Tomaschewski <mt@novell.com> 2010-07-12 19:27:36 UTC --- A unicast ARP request is usually sent to already known - e.g. cached - address. But you're right -- it seems that the Infiniband fix for bnc #610839 breaks the broadcasts completely. Without the patch it sends one broadcast + unicasts and receives replies: ### without -b: # arping -I br0 -c 3 172.16.1.5 ARPING 172.16.1.5 from 172.16.1.1 br0 Unicast reply from 172.16.1.5 [00:24:E8:CD:32:33] 0.686ms Unicast reply from 172.16.1.5 [00:24:E8:CD:32:33] 0.709ms Unicast reply from 172.16.1.5 [00:24:E8:CD:32:33] 0.688ms Sent 3 probes (1 broadcast(s)) Received 3 response(s) # (tcpdump -lenfvi eth0 'ether proto \arp') 00:26:b9:8e:f8:66 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 172.16.1.5 (ff:ff:ff:ff:ff:ff) tell 172.16.1.1 00:24:e8:cd:32:33 > 00:26:b9:8e:f8:66, ethertype ARP (0x0806), length 60: arp reply 172.16.1.5 is-at 00:24:e8:cd:32:33 00:26:b9:8e:f8:66 > 00:24:e8:cd:32:33, ethertype ARP (0x0806), length 42: arp who-has 172.16.1.5 (00:24:e8:cd:32:33) tell 172.16.1.1 00:24:e8:cd:32:33 > 00:26:b9:8e:f8:66, ethertype ARP (0x0806), length 60: arp reply 172.16.1.5 is-at 00:24:e8:cd:32:33 00:26:b9:8e:f8:66 > 00:24:e8:cd:32:33, ethertype ARP (0x0806), length 42: arp who-has 172.16.1.5 (00:24:e8:cd:32:33) tell 172.16.1.1 00:24:e8:cd:32:33 > 00:26:b9:8e:f8:66, ethertype ARP (0x0806), length 60: arp reply 172.16.1.5 is-at 00:24:e8:cd:32:33 #### with -b # arping -I br0 -c 3 -b 172.16.1.5 ARPING 172.16.1.5 from 172.16.1.1 br0 Unicast reply from 172.16.1.5 [00:24:E8:CD:32:33] 0.749ms Unicast reply from 172.16.1.5 [00:24:E8:CD:32:33] 0.814ms Unicast reply from 172.16.1.5 [00:24:E8:CD:32:33] 0.724ms Sent 3 probes (3 broadcast(s)) Received 3 response(s) # (tcpdump -lenfvi eth0 'ether proto \arp') 00:26:b9:8e:f8:66 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 172.16.1.5 (ff:ff:ff:ff:ff:ff) tell 172.16.1.1 00:24:e8:cd:32:33 > 00:26:b9:8e:f8:66, ethertype ARP (0x0806), length 60: arp reply 172.16.1.5 is-at 00:24:e8:cd:32:33 00:26:b9:8e:f8:66 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 172.16.1.5 (ff:ff:ff:ff:ff:ff) tell 172.16.1.1 00:24:e8:cd:32:33 > 00:26:b9:8e:f8:66, ethertype ARP (0x0806), length 60: arp reply 172.16.1.5 is-at 00:24:e8:cd:32:33 00:26:b9:8e:f8:66 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 172.16.1.5 (ff:ff:ff:ff:ff:ff) tell 172.16.1.1 00:24:e8:cd:32:33 > 00:26:b9:8e:f8:66, ethertype ARP (0x0806), length 60: arp reply 172.16.1.5 is-at 00:24:e8:cd:32:33 When the patch applied, it sends to ff:26:ff:8e:00:66 regardless of -b and does not receives any reply: # arping -I br0 -c 3 172.16.1.5 ARPING 172.16.1.5 from 172.16.1.1 br0 Sent 3 probes (3 broadcast(s)) Received 0 response(s) # (tcpdump -lenfvi eth0 'ether proto \arp') 00:26:b9:8e:f8:66 > ff:26:ff:8e:00:66, ethertype ARP (0x0806), length 42: arp who-has 172.16.1.5 (ff:26:ff:8e:00:66) tell 172.16.1.1 00:26:b9:8e:f8:66 > ff:26:ff:8e:00:66, ethertype ARP (0x0806), length 42: arp who-has 172.16.1.5 (ff:26:ff:8e:00:66) tell 172.16.1.1 00:26:b9:8e:f8:66 > ff:26:ff:8e:00:66, ethertype ARP (0x0806), length 42: arp who-has 172.16.1.5 (ff:26:ff:8e:00:66) tell 172.16.1.1 00:26:b9:8e:f8:66 > ff:26:ff:8e:00:66, ethertype ARP (0x0806), length 42: arp who-has 172.16.1.5 (ff:26:ff:8e:00:66) tell 172.16.1.1 # arping -I br0 -c 3 -b 172.16.1.5 ARPING 172.16.1.5 from 172.16.1.1 br0 Sent 3 probes (3 broadcast(s)) Received 0 response(s) 00:26:b9:8e:f8:66 > ff:26:ff:8e:00:66, ethertype ARP (0x0806), length 42: arp who-has 172.16.1.5 (ff:26:ff:8e:00:66) tell 172.16.1.1 00:26:b9:8e:f8:66 > ff:26:ff:8e:00:66, ethertype ARP (0x0806), length 42: arp who-has 172.16.1.5 (ff:26:ff:8e:00:66) tell 172.16.1.1 00:26:b9:8e:f8:66 > ff:26:ff:8e:00:66, ethertype ARP (0x0806), length 42: arp who-has 172.16.1.5 (ff:26:ff:8e:00:66) tell 172.16.1.1 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c8 --- Comment #8 from Marcus Schaefer <ms@novell.com> 2010-07-13 12:11:29 UTC --- I tried to reproduce this but can't find a difference in the behavior of arping with and without the infiniband patch. I compiled arping for 11.3 with and without the patch on shannon.suse.de and tried ---without infiniband patch--- 1) cd /abuild/buildsystem.shannon.ms/usr/src/packages/BUILD/iputils/ ./arping -I eth0 -c 3 -b 212.114.146.242 ---with infiniband patch--- 2) /sbin/arping -I eth0 -c 3 -b 212.114.146.242 ARPING 172.16.1.5 from 10.10.0.79 eth0 Sent 3 probes (3 broadcast(s)) Received 0 response(s) and on a address where I would expect a response 1) cd /abuild/buildsystem.shannon.ms/usr/src/packages/BUILD/iputils/ ./arping -I eth0 -c 3 -b 10.10.2.43 2) /sbin/arping -I eth0 -c 3 -b 10.10.2.43 ARPING 10.10.2.43 from 10.10.0.79 eth0 Unicast reply from 10.10.2.43 [00:E0:81:79:8E:B4] 0.731ms Unicast reply from 10.10.2.43 [00:E0:81:79:8E:B4] 0.721ms Unicast reply from 10.10.2.43 [00:E0:81:79:8E:B4] 0.761ms Sent 3 probes (3 broadcast(s)) Received 3 response(s) confused ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c9 --- Comment #9 from Marius Tomaschewski <mt@novell.com> 2010-07-13 15:07:14 UTC --- The set_device_broadcast call breaks it -- when I change it as follows it starts to work again (with and without bridge): Index: iputils-ss021109-arping-infiniband.diff =================================================================== --- iputils-ss021109-arping-infiniband.diff (revision 6c6112bc113d4f5f78e52928237f7136) +++ iputils-ss021109-arping-infiniband.diff (working copy) @@ -165,7 +165,7 @@ he = me; - memset(he.sll_addr, -1, he.sll_halen); + -+#if 1 ++#if 0 + set_device_broadcast(device, ((struct sockaddr_ll *)&he)->sll_addr, + ((struct sockaddr_ll *)&he)->sll_halen); +#else -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c11 --- Comment #11 from Leonardo Chiquitto <lchiquitto@novell.com> 2010-07-13 15:36:13 UTC --- Hi Marius and Marcus. I didn't test this patch because I *thought* it was the same as the one in bug #581830, comment #36 but apparently it's not. IIRC, I tested the patch from bug #581830 on Infiniband and regular Ethernet interfaces and it worked fine. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c12 --- Comment #12 from Marius Tomaschewski <mt@novell.com> 2010-07-13 16:09:09 UTC --- When I fix the loop as follows, it works fine for me: -+ for (p = ba, ch = 0; p < ba + balen; p++, ch += 3) -+ *p++ = strtoul(brdcast->value + ch * 3, NULL, 16); ++ for (p = ba, ch = 0; p < ba + balen; ch += 3) ++ *p++ = (uint8_t)strtoul(brdcast->value + ch, NULL, 16); Fixed package is in home:mtomaschewski:branches:network:utilities/iputils and submit request 42881 to network:utilities/iputils. Marcus, Marco, Leonardo, can you retest again please? Does it work for you? http://download.opensuse.org/repositories/home:/mtomaschewski:/branches:/net... (In reply to comment #11)
Hi Marius and Marcus. I didn't test this patch because I *thought* it was the same as the one in bug #581830, comment #36 but apparently it's not. IIRC, I tested the patch from bug #581830 on Infiniband and regular Ethernet interfaces and it worked fine.
Until now I not even knew, that there is one variant more flying around :-) OK, the difference is that this patch makes use of sockaddr_storage and the sysfslib, the patch from bug #581830 implements the sysfs reading "manually". -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c14 --- Comment #14 from mine mine <marco@nucleus.it> 2010-07-14 07:33:39 UTC --- Ok , arping is working fine . Thanks for the patch -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c16 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mt@novell.com |ms@novell.com --- Comment #16 from Marius Tomaschewski <mt@novell.com> 2010-07-14 09:10:37 UTC --- OK, it seems to be fixed. Back to you Marcus. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c Marcus Schaefer <ms@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|610839 | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c17 Marcus Schaefer <ms@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #17 from Marcus Schaefer <ms@novell.com> 2010-07-14 12:14:20 UTC --- - added your patch - upstream maintainer has changed. new maintainer is YOSHIFUJI Hideaki. Along with this change the versioning of the package also changed. Current version is: s20100418 from 18-Apr-2010 - many patches upstream now, reduced patch set ===> created request id 42903 => openSUSE:Factory -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c18 Swamp Workflow Management <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:released:sle11-sp1:34 | |500 --- Comment #18 from Swamp Workflow Management <swamp@suse.com> 2010-07-20 17:09:23 UTC --- Update released for: iputils, iputils-debuginfo, iputils-debugsource Products: SLE-DEBUGINFO 11-SP1 (i386, ia64, ppc64, s390x, x86_64) SLE-DESKTOP 11-SP1 (i386, x86_64) SLE-SERVER 11-SP1 (i386, ia64, ppc64, s390x, x86_64) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c19 --- Comment #19 from mine mine <marco@nucleus.it> 2010-07-22 09:24:13 UTC --- And for opensuse 11.1 , 11.2 and 11.3 ? (In reply to comment #18)
Update released for: iputils, iputils-debuginfo, iputils-debugsource Products: SLE-DEBUGINFO 11-SP1 (i386, ia64, ppc64, s390x, x86_64) SLE-DESKTOP 11-SP1 (i386, x86_64) SLE-SERVER 11-SP1 (i386, ia64, ppc64, s390x, x86_64)
-- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c20 Leonardo Chiquitto <lchiquitto@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #20 from Leonardo Chiquitto <lchiquitto@novell.com> 2010-07-22 11:29:22 UTC --- Reopening to handle maintenance updates for openSUSE. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c21 Leonardo Chiquitto <lchiquitto@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |maintenance@opensuse.org --- Comment #21 from Leonardo Chiquitto <lchiquitto@novell.com> 2010-07-22 11:30:13 UTC --- Maintenance Team, please, can we release this fix (already released for SLE 11-SP1) for openSUSE 11.1/11.2/11.3 too? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c22 Swamp Workflow Management <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11-sp1:34 |maint:released:sle11-sp1:34 |500 |500 maint:running:34707:low --- Comment #22 from Swamp Workflow Management <swamp@suse.com> 2010-07-22 15:27:37 UTC --- The SWAMPID for this issue is 34707. This issue was rated as low. Please submit fixed packages as soon as possible. Also create a patchinfo file using this link: https://swamp.suse.de/webswamp/wf/34707 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c23 Christian Dengler <cdengler@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED CC| |cdengler@novell.com InfoProvider|maintenance@opensuse.org | --- Comment #23 from Christian Dengler <cdengler@novell.com> 2010-07-22 15:36:58 UTC --- For 11.3 ok. For the rest I think it is not necessary. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c24 --- Comment #24 from mine mine <marco@nucleus.it> 2010-07-22 15:48:35 UTC --- Please fix for all cause this tool is not working as expected (In reply to comment #23)
For 11.3 ok. For the rest I think it is not necessary.
-- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c25 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |cdengler@novell.com --- Comment #25 from Marius Tomaschewski <mt@novell.com> 2010-07-22 15:58:10 UTC --- (In reply to comment #23)
For 11.3 ok. For the rest I think it is not necessary.
Christian, please reconsider to provide the updates. IMO we should provide it everywhere, where the last update broke it. Note that arping is used in some scripts, as /sbin/dhclient-script, monitoring or in HA failover that may trigger wrong actions because of broken arping. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c26 --- Comment #26 from Leonardo Chiquitto <lchiquitto@novell.com> 2010-07-22 17:32:50 UTC --- I think there's a bit of confusion here, let's try to clarify: - We never released updates for iputils on openSUSE 11.0, 11.1 and 11.2. - openSUSE 11.3 shipped with the broken iputils-ss021109-arping-infiniband.diff patch, so we must do the update to fix it. Regarding the original bug report (comment #0):
Afert the upgrade to iputils-ss021109-305.1.i586.rpm arping is not working properly.
The package iputils-ss021109-305.1 was not shipped in any product, so I believe the reporter is using the devel repository network:/utilities (which is now already fixed). Since Factory will soon get the fix through the Devel project, I will submit the update for 11.3. I believe this is everything we need. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c27 --- Comment #27 from Leonardo Chiquitto <lchiquitto@novell.com> 2010-07-22 17:36:58 UTC --- Patchinfo filled and package submitted against openSUSE:11.3:Update:Test (request id 43771). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c28 Christian Dengler <cdengler@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|cdengler@novell.com | --- Comment #28 from Christian Dengler <cdengler@novell.com> 2010-07-26 10:41:02 UTC --- Thanks Leonardo. the old version should not be affected. But feel free to test it. If the old one is also affected we can do an update there. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c Swamp Workflow Management <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11-sp1:34 |maint:released:sle11-sp1:34 |500 maint:running:34707:low |500 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=614389 http://bugzilla.novell.com/show_bug.cgi?id=614389#c29 Leonardo Chiquitto <lchiquitto@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Component|Other |Other Resolution| |FIXED Product|openSUSE 11.0 |openSUSE 11.3 OS/Version|openSUSE 11.0 |openSUSE 11.3 --- Comment #29 from Leonardo Chiquitto <lchiquitto@novell.com> 2010-08-05 14:57:52 UTC --- Update was released for openSUSE 11.3. Adjusting product and closing as RESOLVED/FIXED. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com