[ Trevor Burt ]
> Package: ucarp
> 
> Version: 1.5.2-1+nmu1
> 
> After upgrading from 2.6.32-48squeeze4 to Debian Wheezy 3.2.0-4-amd64. I
> noticed that ucarp no longer works on a vlan interface.
> 
> After checking the vip-up script, I found it runs /sbin/ifup $1:ucarp
> 
> After trying to run this script manually:-
> 
> ifup wan-2.3076:ucarp
> 
> I found it returns the following error:-
> 
> RTNETLINK answers: Numerical result out of range
> Failed to bring up wan-2.3076:ucarp.
> 
> It looks like an issue with ifup, so I downgraded from ifupdown 0.7.8 to
> ifupdown_0.6.10_amd64.deb and ucarp started to work, although I broke other
> packages in the downgrade.
> 
> I then noticed that the example file in Debian for ucarp now uses the
> interface :254 instead of :ucarp.
> 
> So I adjusted my /etc/network/interfaces file and change all :ucarp entries
> to :254, making the same changes to the vip-up and vip-down replacing
> :ucarp with :254.
> 
> So vip-up now contains /sbin/ifup $1:254 instead of /sbin/ifup S1:ucarp.
> 
> I am able to manually bring up the ucarp interface for example:-
> 
> ifup wan-2.3076:254 but the ucarp interface will it not load automatically.
> 
> How do I debug this issue further?

I'm not able to reproduce this here, though I do not have any vlan
interfaces.  Can you provide information on reproducing your setup?

Also, the example vip-up/vip-down scripts use /sbin/ip to bring the
interface up/down.  I'd be interested to see how that works; Can you give
that a shot and report back here?

> Can anyone confirm if ucarp supports IPv6?

No, ucarp does not support IPv6, this is a known issue[1].  The interface
mentioned above isn't IPv6, is it?
 
> Is there an alternative to ucarp? I have tried email Eric Evans a few times
> to report this bug with no response.
>
> Is this package being maintained?

Yes.


[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529383

-- 
Eric Evans
[email protected]


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to