The template keepalived.conf file has the 'vrrp_strict' option set by default, but als

Commit <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https:/

Template 'keepalived.conf' in the etc folder is somewhat misleading about keepalived HOT 2 CLOSED

gesture1968 commented on June 2, 2024

Template 'keepalived.conf' in the etc folder is somewhat misleading

from keepalived.

Comments (2)

pqarmitage commented on June 2, 2024

Commit a7c4085 adds:

    # Allow packets addressed to the VIPs above to be received
    accept

to the sample configuration, which should help in future.

@gesture1968 Many thanks for reporting this.

from keepalived.

gesture1968 commented on June 2, 2024

Hello pqarmitage,

Thanks for the change. I did test your solution, but I still can't ping the virtual IP address if the 'accept' option is added to the vrrp_instance and the 'vrrp_strict' is set with a priority of 100. It still needs either a priority of 255 or the vrrp_strict disabled...

for good measure, here is my config that does not ping the 192.168.85.85 VIP address :

! Configuration File for keepalived

global_defs {
   notification_email {
     [email protected]
   }
   notification_email_from [email protected]
   smtp_server smtp.mail.com
   smtp_connect_timeout 30
   router_id ROUTERID
   vrrp_skip_check_adv_addr
   vrrp_strict
   vrrp_garp_interval 0
   vrrp_gna_interval 0
}

# enter failed state when the process is down
vrrp_track_script track_script {
    script /etc/script/check_script.sh
    interval 5
    timeout 5
}

vrrp_instance VI_1 {
    state MASTER
    interface eth0
    virtual_router_id 51
    priority 100
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1234
    }
    virtual_ipaddress {
        192.168.85.85/24
    }
    track_script {
        track_script
    }
    accept
    smtp_alert
}

Regards, gesture

from keepalived.

Recommend Projects