I have now tried to change the carp netmask to /32 on the one interface
that shares subnet (management), changed advskew to 20 on master and 80
on slave. But ping loss still persist (see bottom of this mail).

I could try to set the carpdemote higher on the slave, but what then
when/if the master actually goes down?
>> CARP and nothing else.
>>> I have no idea about a possible specific reason for packet loss, though.
>>>
>> Snippet from: Robert Blacquiere <[email protected]>
>>> Just a quick thought as em devices are emulated on kvm did you try
>>> disableling hw offloading on the interfaces? I had some similair issue
>>> with a vps pings seem to work but other traffic had drops.
>> I haven't tried to disable HW offload, but do you think it could be a
>> problem, when it worked fin under older versions of OpenBSD?
>>
>> Med Venlig Hilsen / Best Regards
>> Henrik Dige Semark
>>
>>
>>
> I had some issues with vps with em interfaces and pseudo hw offloading.
> Now I never use offloading on vps and have not encountered these strange
> things like packet drop or  icmp work but tcp/udp fails and carp strange
> hickups. Also encountered issue with multicast on juniper in combination
> with numbered management vlan on the default vlan. Some where in juniper
> they got silenced. 
>
> Regards
>
> Robert 
>
@Robert: What exactly do you turn off, and how?

Information:

# ifconfig em0
em0: flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST>
mtu 1500
        lladdr a8:8d:35:55:7d:5f
        description: Management
        index 1 priority 0 llprio 3
        media: Ethernet autoselect (1000baseT full-duplex)
        status: active
        inet 192.168.245.2 netmask 0xffffff00 broadcast 192.168.245.255
        inet6 fe80::24e8:4c63:629c:3d53%em0 prefixlen 64 scopeid 0x1
        inet6 2001:470:1b6a:45::2 prefixlen 64

# ifconfig carp1
carp1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 00:00:5e:00:01:01
        description: Management
        index 5 priority 15 llprio 3
        carp: MASTER carpdev em0 vhid 1 advbase 1 advskew 20
        groups: carp lan
        status: master
        inet 192.168.245.1 netmask 0xffffffff
        inet6 fe80::3c71:a9ea:18d8:872%carp1 prefixlen 64 scopeid 0x5
        inet6 2001:470:1b6a:45::1 prefixlen 128



# ping -c 50 8.8.8.8 (From my laptop to Google DNS)
--- 8.8.8.8 ping statistics ---
50 packets transmitted, 40 received, +10 errors, 20% packet loss, time
49158ms
rtt min/avg/max/mdev = 7.046/7.370/10.165/0.517 ms

# ping -c 50 192.168.245.2 (From my laptop to Server 1 em0)
--- 192.168.245.2 ping statistics ---
50 packets transmitted, 50 received, 0% packet loss, time 49350ms
rtt min/avg/max/mdev = 0.658/1.169/4.643/0.682 ms

# ping -c 50 192.168.245.1 (From my laptop to carp1 (default gw))
PING 192.168.245.1 (192.168.245.1) 56(84) bytes of data.
64 bytes from 192.168.245.1: icmp_seq=1 ttl=255 time=0.766 ms
64 bytes from 192.168.245.1: icmp_seq=2 ttl=255 time=0.972 ms
64 bytes from 192.168.245.1: icmp_seq=3 ttl=255 time=1.18 ms
64 bytes from 192.168.245.1: icmp_seq=4 ttl=255 time=0.718 ms
64 bytes from 192.168.245.1: icmp_seq=5 ttl=255 time=0.816 ms
64 bytes from 192.168.245.1: icmp_seq=6 ttl=255 time=0.818 ms
64 bytes from 192.168.245.1: icmp_seq=7 ttl=255 time=0.964 ms
64 bytes from 192.168.245.1: icmp_seq=8 ttl=255 time=0.833 ms
64 bytes from 192.168.245.1: icmp_seq=9 ttl=255 time=0.839 ms
64 bytes from 192.168.245.1: icmp_seq=10 ttl=255 time=0.955 ms
64 bytes from 192.168.245.1: icmp_seq=11 ttl=255 time=1.62 ms
64 bytes from 192.168.245.1: icmp_seq=12 ttl=255 time=0.916 ms
64 bytes from 192.168.245.1: icmp_seq=13 ttl=255 time=0.785 ms
64 bytes from 192.168.245.1: icmp_seq=14 ttl=255 time=0.734 ms
64 bytes from 192.168.245.1: icmp_seq=15 ttl=255 time=1.99 ms
*64 bytes from 192.168.245.1: icmp_seq=16 ttl=255 time=36.8 ms*
64 bytes from 192.168.245.1: icmp_seq=17 ttl=255 time=0.853 ms
64 bytes from 192.168.245.1: icmp_seq=18 ttl=255 time=1.19 ms
64 bytes from 192.168.245.1: icmp_seq=19 ttl=255 time=0.744 ms
64 bytes from 192.168.245.1: icmp_seq=20 ttl=255 time=1.89 ms
64 bytes from 192.168.245.1: icmp_seq=21 ttl=255 time=0.853 ms
64 bytes from 192.168.245.1: icmp_seq=22 ttl=255 time=1.78 ms
64 bytes from 192.168.245.1: icmp_seq=23 ttl=255 time=0.861 ms
64 bytes from 192.168.245.1: icmp_seq=24 ttl=255 time=1.15 ms
64 bytes from 192.168.245.1: icmp_seq=25 ttl=255 time=0.731 ms
64 bytes from 192.168.245.1: icmp_seq=26 ttl=255 time=0.701 ms
64 bytes from 192.168.245.1: icmp_seq=27 ttl=255 time=2.07 ms
64 bytes from 192.168.245.1: icmp_seq=28 ttl=255 time=1.07 ms
*64 bytes from 192.168.245.1: icmp_seq=29 ttl=255 time=41.5 ms*
64 bytes from 192.168.245.1: icmp_seq=30 ttl=255 time=0.798 ms
64 bytes from 192.168.245.1: icmp_seq=31 ttl=255 time=1.65 ms
64 bytes from 192.168.245.1: icmp_seq=32 ttl=255 time=0.846 ms
64 bytes from 192.168.245.1: icmp_seq=33 ttl=255 time=0.782 ms
64 bytes from 192.168.245.1: icmp_seq=34 ttl=255 time=1.94 ms
64 bytes from 192.168.245.1: icmp_seq=35 ttl=255 time=0.841 ms
64 bytes from 192.168.245.1: icmp_seq=36 ttl=255 time=0.874 ms
64 bytes from 192.168.245.1: icmp_seq=37 ttl=255 time=0.819 ms
64 bytes from 192.168.245.1: icmp_seq=38 ttl=255 time=1.57 ms
64 bytes from 192.168.245.1: icmp_seq=39 ttl=255 time=1.79 ms
64 bytes from 192.168.245.1: icmp_seq=40 ttl=255 time=0.710 ms
64 bytes from 192.168.245.1: icmp_seq=41 ttl=255 time=0.762 ms
*64 bytes from 192.168.245.1: icmp_seq=42 ttl=255 time=16.4 ms*
64 bytes from 192.168.245.1: icmp_seq=43 ttl=255 time=0.698 ms
64 bytes from 192.168.245.1: icmp_seq=44 ttl=255 time=0.776 ms
64 bytes from 192.168.245.1: icmp_seq=45 ttl=255 time=0.778 ms
64 bytes from 192.168.245.1: icmp_seq=46 ttl=255 time=1.43 ms
64 bytes from 192.168.245.1: icmp_seq=47 ttl=255 time=0.742 ms
64 bytes from 192.168.245.1: icmp_seq=48 ttl=255 time=0.773 ms
64 bytes from 192.168.245.1: icmp_seq=49 ttl=255 time=0.888 ms
64 bytes from 192.168.245.1: icmp_seq=50 ttl=255 time=0.699 ms

--- 192.168.245.1 ping statistics ---
50 packets transmitted, 50 received, 0% packet loss, time 49458ms
rtt min/avg/max/mdev = 0.698/2.877/41.590/7.745 ms

My guess would be that it changes server in the three places marked with
* and higher ping-times is seen

-- 
Med Venlig Hilsen / Best Regards
Henrik Dige Semark
Mobil: +45 2633 1701


Reply via email to