Added by Tobias Wigand about 8 years ago. Updated about 8 years ago.
100%
Updated by Jim Thompson about 8 years ago
Updated by Luiz Souza about 8 years ago
This should be fixed. Let us know if it works for you. Thanks!
Updated by Tobias Wigand about 8 years ago
Sorry, did not help. I'm on the latest beta with gitsync as of now.
ifconfig still shows the CARP IPs as aliases of my interfaces, thus IGMP Proxy tries to add both IPs of my WAN interface and fails with something like:
Vif #7 was already upstream. Cannot set VIF #8 as upstream as well.
Running it in debug mode shows this for my WAN interface:
buildIfVc: Interface igb1 Addr: 192.x.x.252, Flags: 0xffff8943, Network: 192.x.x/24 buildIfVc: Interface igb1 Addr: 192.x.x.250, Flags: 0xffff8943, Network: 192.x.x/24
Updated by Chris Buechler about 8 years ago
wasn't related to the changes in 2a5960b0. Appears latest igmpproxy has a Linuxism that expects its interfaces to only have a single IP
Updated by Luiz Souza about 8 years ago
exactly, the bug in igmpproxy was fixed and now works fine with CARP and IP alias on upstream interface.
Updated by Chris Buechler about 8 years ago
This seems to be fine, it no longer errors out with something like
Vif #7 was already upstream. Cannot set VIF #8 as upstream as well.
Tobias: can you confirm?