The Force10 manual states about peer-routing: VLT unicast routing locally routes packets destined for the L3 endpoint of the VLT peer. So if this means that if LSAs for router1 are sent down the link in the port channel connecting to router2, then router2 will respond instead of sending the traffic to router1 - I’m not sure, but this seems plausible as to why it does not work with the peer routing feature. Funny actually that it works with quagga then… Anyway, it seems to be stable now - let me know if you would like the tcpdump anyway. Thanks for your help! Regards Kristoffer On 16/12/2013, at 11.07.50, Kristoffer Egefelt <kristoffer@itoc.dk> wrote:
It seems this is working if I disable the peer-routing feature on the Force10 routers - I’ll test a little more and get back with a tcpdump
Thanks.
On 13/12/2013, at 18.01.10, Ondrej Zajicek <santiago@crfreenet.org> wrote:
On Fri, Dec 13, 2013 at 04:47:17PM +0100, Kristoffer Egefelt wrote:
Hi,
Is this not supported?
This is supported on Linux.
I?m trying to use a bonded interface on linux to connect to two routers, one router on each physical link, each with a /31 subnet. Only one of the routers (Force10 S4810) forms adjacency with the linux host (whichever comes first), the other gets stuck in EXSTART until I shut/no shut the link, then Bird creates adjacency with both routers.
That is even more strange. It would be useful if you could make verbose tcpdump log (tcpdump -i ethX -vv -s 0) together with BIRD OSPF log ('debug all' for OSPF) and send it to me.
-- Elen sila lumenn' omentielvo
Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."