Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Fri, Jun 13, 2008 at 02:26:14PM +0200, Michał Szpadzik wrote: > 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 OK. A few more suggestions then: (1) netstat -natp # on both machines Before connecting, I'd expect to see listening ports: tcp 0 0 192.168.10.5:7788 0.0.0.0:* LISTEN After drbdadm connect from the far side, I'd expect to see something like tcp 0 0 192.168.10.5:7788 192.168.10.6:54321 ESTABLISHED (2) telnet 192.168.15.6 7788 (assuming the other side says LISTEN). Does drbd accept a connection? (3) tcpdump -i bond0 -nn -s0 -v When you drbdadm connect, do you see TCP SYNs for the ports which drbd is configured to use? (4) Do you have selinux enforcing? Do you have iptables rules? If so, try disabling them both temporarily. Regards, Brian.