| Summary: | Can not ping a bonding interface using ping6 with balance-rr mode | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Liang Zheng <lzheng> |
| Component: | kernel | Assignee: | Ivan Vecera <ivecera> |
| Status: | CLOSED DUPLICATE | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2 | CC: | arozansk, kzhang |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-02 04:31:22 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Is it a regression? (In reply to comment #2) > Is it a regression? No. Liang, is it really be2net specific? IPv4 ping works? (In reply to comment #4) > Liang, is it really be2net specific? IPv4 ping works? Yes,It's be2net specific, no issue via ipv4 ping. Could be possible to use bonding setup with balance-rr mode and with one be2net and one non-be2net device? (In reply to comment #6) > Could be possible to use bonding setup with balance-rr mode and with one be2net > and one non-be2net device? okļ¼but our lab controller is broken for 2 weeks,I cannot provision my systems to rhel6.If the systems are available,I will give the test feedback asap. Thanks. Thanks Liang. ixgbe --
|--bond0 <------> eth4
be2net -- fe01::2/64 fe01::3/24
No issue,no IPv6 duplicate address.Every thing work fine.
Tested both on kernel-2.6.32-202 & 211
The patch for Bug 709280 can fix this issue. Tested on kernel-2.6.32-214.el6 *** This bug has been marked as a duplicate of bug 709280 *** |
Description of problem: When I tested ipv6 on bonding,I config bonding with mode=0 (balance-round-robin), I can not use ping6 on that bonding interface. I used two be2net NICs in bond0. Version-Release number of selected component (if applicable): 2.6.32-202.el6.x86_64 How reproducible: always Steps to Reproduce: 1.modprode bonding mode=0 miimon=100 2.ifconfig bond0 up 3.ifenslave bond0 eth6 eth7 4.ip a a fe01::2/64 dev bond0 5.ping6 fe01::3 or netperf -6 -H fe01::3 Actual results: Can not ping successfully. [root@hp-dl580g7-01 ~]# ping6 fe01::1 PING fe01::1(fe01::1) 56 data bytes From ::1 icmp_seq=2 Destination unreachable: Address unreachable From ::1 icmp_seq=3 Destination unreachable: Address unreachable From ::1 icmp_seq=4 Destination unreachable: Address unreachable Expected results: Additional info: [root@hp-dl580g7-01 ~]# ip -6 route fe01::/64 dev bond0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 [root@hp-dl580g7-01 ~]# ip -6 a s 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 23: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 inet6 fe01::2/64 scope global tentative dadfailed valid_lft forever preferred_lft forever [root@hp-dl580g7-01 ~]# dmesg | tail -n 20 ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready ixgbe 0000:11:00.1: eth5: NIC Link is Up 10 Gbps, Flow Control: RX/TX bond0: link status definitely up for interface eth5, 10000 Mbps full duplex. bond0: no IPv6 routers present bonding: bond0: released all slaves Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009) bonding: MII link monitoring set to 100 ms ADDRCONF(NETDEV_UP): bond0: link is not ready 8021q: adding VLAN 0 to HW filter on device bond0 eth6: Link up 8021q: adding VLAN 0 to HW filter on device eth6 New slave device eth6 does not support netpoll Disabling netpoll support for bond0 bonding: bond0: enslaving eth6 as an active interface with an up link. eth7: Link up 8021q: adding VLAN 0 to HW filter on device eth7 bonding: bond0: enslaving eth7 as an active interface with an up link. ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready bond0: IPv6 duplicate address fe80::200:c9ff:feb1:eade detected! bond0: IPv6 duplicate address fe01::2 detected!