Problem with carp and "inet alias"

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Problem with carp and "inet alias"

Christiano Liberato
This post has NOT been accepted by the mailing list yet.
Hi,

I have the following scenario in a client:

fw1: 200.200.200.168
fw2: 200.200.200.172

carp0 (for twho fw)
inet 200.200.200.162 255.255.255.240 200.200.200.175 vhid 1 advskew 0 carpdev em0 pass senha
inet alias 200.200.200.163 255.255.255.255
inet alias 200.200.200.164 255.255.255.255
inet alias 200.200.200.165 255.255.255.255
inet alias 200.200.200.166 255.255.255.255
inet alias 200.200.200.167 255.255.255.255

After restart the fw, I can not access the router (gateway). I think it has problems default route in between.

Searching the internet, I found the post http://openbsd.7691.n7.nabble.com/Carp-with-aliases-route-problem-td84179.html, Todd T. Fries-2, saying that in /etc/netstart interface carp rises after the physical and do not know if it is necessary to change this sequence.

Anyone have an environment with carp and alias working to give an opinion?

Thanks.