Bug #5783
closed
IGMP Proxy not working with CARP alias on upstream interface
Added by Anonymous almost 9 years ago.
Updated almost 9 years ago.
Affected Architecture:
All
- Status changed from New to Assigned
- Assignee set to Luiz Souza
- Target version set to 2.3
- Status changed from Assigned to Feedback
- % Done changed from 0 to 100
This should be fixed. Let us know if it works for you. Thanks!
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
- Status changed from Feedback to Confirmed
- % Done changed from 100 to 0
wasn't related to the changes in 2a5960b0. Appears latest igmpproxy has a Linuxism that expects its interfaces to only have a single IP
- Status changed from Confirmed to Feedback
- % Done changed from 0 to 100
exactly, the bug in igmpproxy was fixed and now works fine with CARP and IP alias on upstream interface.
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?
- Status changed from Feedback to Resolved
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by