Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
asgard:~# ping -I 192.168.10.5 192.168.10.6 PING 192.168.10.6 (192.168.10.6) from 192.168.10.5 : 56(84) bytes of data. 64 bytes from 192.168.10.6: icmp_seq=1 ttl=64 time=0.201 ms 64 bytes from 192.168.10.6: icmp_seq=2 ttl=64 time=0.146 ms 64 bytes from 192.168.10.6: icmp_seq=3 ttl=64 time=0.142 ms 64 bytes from 192.168.10.6: icmp_seq=4 ttl=64 time=0.163 ms 64 bytes from 192.168.10.6: icmp_seq=5 ttl=64 time=0.145 ms 64 bytes from 192.168.10.6: icmp_seq=6 ttl=64 time=0.169 ms 64 bytes from 192.168.10.6: icmp_seq=7 ttl=64 time=0.147 ms --- 192.168.10.6 ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 5998ms rtt min/avg/max/mdev = 0.142/0.159/0.201/0.019 ms asgard:~# It works very well, heartbeat2 and MySQL5 replication have no problems with connection. Brian Candler pisze: > On Fri, Jun 13, 2008 at 10:59:50AM +0200, Michał Szpadzik wrote: > >> In my post there were two configuration - one not working with bonded >> interconnect interfaces, and one working with drbd configured on >> physical interfaces :) >> > > Have you tried this? > > ping -I 192.168.10.5 192.168.10.6 > > If you can't ping between the machines on this bonded network, then that > would point to this being not anything to do with drbd. > >