Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Tue, Jan 18, 2005 at 12:30:48AM +0000, Simon Edwards wrote: > Hello, > I'm using DRBD 0.7.6 in a configuration where each of the two hosts have > eth0/eth1 on the same subnet. For example: > > server1 server2 > eth0: 192.168.0.60 eth0:192.168.0.70 > eth1: 192.168.0.61 eth1:192.168.0.71 > > Now when I establish a DRBD device using the "eth1" addressses (as > confirmed with the "show" output): > > # drbdsetup /dev/drbd0 show > Lower device: 58:00 (/dev/vg01/lv01) > Meta device: 58:01 (/dev/vg01/lv01_meta) > Meta index: 0 > Disk options: > Local address: 192.168.0.61:9901 > Remote address: 192.168.0.71:9901 > Wire protocol: C > Net options: > timeout = 6.0 sec (default) > connect-int = 10 sec (default) > ping-int = 10 sec (default) > max-epoch-size = 2048 (default) > max-buffers = 2048 (default) > sndbuf-size = 131070 (default) > ko-count = 0 (default) > Syncer options: > rate = 5000 KB/sec > group = 0 (default) > al-extents = 127 (default) > > > The IP addresses in the above output look correct - however the device > starts getting used the "eth0" addresses appear to take the traffic. The > "netstat" output confirms this; > > # netstat -an|grep 9901 > tcp 0 0 192.168.0.61:9901 192.168.0.70:33174 > ESTABLISHED > tcp 0 0 192.168.0.60:33093 192.168.0.71:9901 > ESTABLISHED Try specifying the interfaces to use to the linux kernel: 192.168.0.61: route add -host 192.168.0.71 dev eth1 192.168.0.71: route add -host 192.168.0.61 dev eth1 Regards, Luciano Rocha