<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3132" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>hi all!</DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>I have the following situation:</DIV>
<DIV> </DIV>
<DIV>1 -------- 2</DIV>
<DIV>¦
¦</DIV>
<DIV>¦
¦</DIV>
<DIV>3----------4</DIV>
<DIV>¦
¦</DIV>
<DIV>¦
¦</DIV>
<DIV>5----------6</DIV>
<DIV> </DIV>
<DIV>where 1 ... 6 are nodes and every direct neighbor is specified as a dundi
peer (in *). When I start a dundi request, every queried node is mentioned in
the dpdiscover. For example 1 sends a discover to 2 and 3, so 2 sees in the EID
or EID_DIRECT field that a discover has also been sent to 3. So much for that.
Is this field also filled with the neighbour peers even if they are
unreachable/offline?</DIV>
<DIV> </DIV>
<DIV>
<DIV>1 ---x---- 2</DIV>
<DIV>¦
¦</DIV>
<DIV>¦
¦</DIV>
<DIV>3----x-----4</DIV>
<DIV>¦
¦</DIV>
<DIV>¦
¦</DIV>
<DIV>5----------6</DIV></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>My problem: When links break (e.g. 1-2 and 3-4) I have the problem
that 6 doesn't forward the query (received from 5) to 4, because 4 is mentioned
in the EID or EID_DIRECT field even though it is not possible that this peer
could have been reached.</DIV>
<DIV> </DIV>
<DIV>Is this a problem of the protocol or can I fix this by setting a special
option in *? Thanks for helping.</DIV>
<DIV> </DIV>
<DIV>Best regards</DIV>
<DIV> </DIV>
<DIV>Andre</DIV></BODY></HTML>