[Olsr-users] OLSR2D and DLEP_ROUTER plugin interplay:

[Henning Rogge]

On Thu, Dec 10, 2015 at 12:23 PM, s-mtafel <(spam-protected)> wrote:
> Quite. I attached the session wire trace and the dlep_router_log. In the
> trace is a 148 bytes tcp_packet. It has 2 in it ups. Very prominent in the
> trace.
> Log has no warn or err: so I guess dlep_router accepts everything. Querying
> the layer2 db shows the destinations, which unterpins the latter.

When I look what messages the DLEP router receives I see this:

grep Process\ signal dlep_router_log
12:11:37.413 DEBUG(dlep_router)
src-plugins/generic/dlep/dlep_session.c 421: Process signal 2 (length
23) from [fe80::200:ff:feaa:1]:2001%eth0 (27 bytes)
12:11:37.414 DEBUG(dlep_router)
src-plugins/generic/dlep/dlep_session.c 421: Process signal 4 (length
66) from [fe80::200:ff:feaa:1]:2001%eth0 (70 bytes)
12:11:39.411 DEBUG(dlep_router)
src-plugins/generic/dlep/dlep_session.c 421: Process signal 13 (length
70) from [fe80::200:ff:feaa:1]:2001%eth0 (148 bytes)
12:11:39.412 DEBUG(dlep_router)
src-plugins/generic/dlep/dlep_session.c 421: Process signal 13 (length
70) from [fe80::200:ff:feaa:1]:2001%eth0 (74 bytes)
12:11:41.722 DEBUG(dlep_router)
src-plugins/generic/dlep/dlep_session.c 421: Process signal 14 (length
0) from [fe80::200:ff:feaa:1]:2001%eth0 (4 bytes)
12:11:46.122 DEBUG(dlep_router)
src-plugins/generic/dlep/dlep_session.c 421: Process signal 14 (length
0) from [fe80::200:ff:feaa:1]:2001%eth0 (4 bytes)
12:11:50.521 DEBUG(dlep_router)
src-plugins/generic/dlep/dlep_session.c 421: Process signal 14 (length
0) from [fe80::200:ff:feaa:1]:2001%eth0 (4 bytes)

So it gets a DLEP_PEER_OFFER (yeah!) followed by a
DLEP_PEER_INITIALIZATION_ACK (even better)...

and then followed by two DLEP_DESTINATION_UPDATE (WTF?) and three
DLEP_HEARTBEAT (okay).

I see no incoming DLEP_DESTINATION_UP (message type 9).

Henning Rogge