hi all
we finally got a lot of debug lines from the gateway node 5.5.56.38 and we
will begin to examine the file. From a quick glance I was truck by the
message
"22:03:49 root: Not processing message originating from 5.5.56.38!"
repeated a few lines further
Well, as said, 5.5.56.38 is the IP address of that node so - excluding that
there are no repeated addresses in the network - it seems that that node
starts to receive olsrd packets sent by itself! And, IMO, this could be the
problem because after these two messages all neighbors of
the node are not symmetric ones and all links go to INFINITE (see the
portion of debug lines just after the ned of this post).
Moreover, from what I can see (...and understand) it seems that the node
processes itself (5.5.56.38) like any other neighbour:
--- 22:19:05.165044 ----------------------------------------------------
GATEWAYS
SPF: append path 5.5.56.38, cost 0.000, via -
--- 22:19:05.164935 -------------------------------------------------
DIJKSTRA
SPF: exploring node 5.5.56.38, cost 0.000
SPF: delete candidate 5.5.56.38, cost 0.000
SPF: insert candidate 5.5.56.38, cost 0.000
Or maybe my thoughts are wrong?
Antonio
--- 22:03:49.239496 ----------------------- TWO-HOP NEIGHBORS
5.67.178.219 0.000 YES YES YES 3
TC: chg edge entry 5.101.255.146 > 5.103.216.152, cost (0.592/0.537) 3.143
TC: chg edge entry 5.101.255.146 > 5.103.1.95, cost (0.678/0.615) 2.394
TC: chg edge entry 5.101.255.146 > 5.101.254.224, cost (0.784/0.631) 2.019
TC: chg edge entry 5.101.255.146 > 5.101.254.120, cost (0.117/0.203)
41.683
Processing TC from 5.101.255.146, seq 0x3aad
TC: chg edge entry 5.101.254.224 > 5.103.216.228, cost (0.757/0.769) 1.719
TIMER: jitter 5% rel_time 288000ms to 280369ms
TC: chg edge entry 5.101.254.224 > 5.149.138.10, cost (0.168/0.419) 14.132
TC: chg edge entry 5.101.254.224 > 5.101.255.146, cost (0.615/0.808) 2.010
TIMER: jitter 5% rel_time 288000ms to 284555ms
TC: chg edge entry 5.101.254.224 > 5.67.177.233, cost (0.757/0.489) 2.695
Processing TC from 5.101.254.224, seq 0x62dc
TC: chg edge entry 5.149.138.10 > 5.101.254.224, cost (0.286/0.199) 17.465
TC: chg edge entry 5.149.138.10 > 5.103.1.136, cost (0.650/0.882) 1.740
TC: chg edge entry 5.149.138.10 > 5.103.216.228, cost (0.635/0.549) 2.866
TC: chg edge entry 5.149.138.10 > 5.67.177.233, cost (0.732/0.808) 1.688
Processing TC from 5.149.138.10, seq 0x8e73
TIMER: jitter 5% rel_time 288000ms to 277541ms
TC: chg edge entry 5.67.177.233 > 5.149.138.10, cost (0.839/0.732) 1.624
TC: chg edge entry 5.67.177.233 > 5.103.1.136, cost (0.310/0.497) 6.480
TC: chg edge entry 5.67.177.233 > 5.103.216.228, cost (0.721/0.784) 1.767
TC: chg edge entry 5.103.1.136 > 5.149.138.10, cost (0.882/0.631) 1.795
Processing TC from 5.67.177.233, seq 0x600e
TIMER: jitter 5% rel_time 288000ms to 273980ms
TC: chg edge entry 5.67.177.233 > 5.101.254.224, cost (0.478/0.678) 3.080
TC: chg edge entry 5.103.1.136 > 5.67.177.233, cost (0.497/0.372) 5.389
TC: chg edge entry 5.103.1.136 > 5.67.179.17, cost (0.619/0.415) 3.882
Received TC from NON SYM neighbor 5.103.1.136
Not processing message originating from 5.5.56.38!
<-------------------------- !!!!
Received TC from NON SYM neighbor 5.103.1.136
Processing TC from 5.103.1.136, seq 0xd695
Received TC from NON SYM neighbor 5.101.255.146
Received TC from NON SYM neighbor 5.101.255.146
Not processing message originating from 5.5.56.38!
<-------------------------- !!!!
Received TC from NON SYM neighbor 5.103.1.136
Processing TC from 5.103.1.136, seq 0xd695
Received TC from NON SYM neighbor 5.101.255.146
Received TC from NON SYM neighbor 5.101.255.146
Received TC from NON SYM neighbor 5.103.216.152
Received TC from NON SYM neighbor 5.103.216.152
TIMER: jitter 5% rel_time 20000ms to 19453ms
Received TC from NON SYM neighbor 5.101.254.224
Received TC from NON SYM neighbor 5.101.254.224
Received TC from NON SYM neighbor 5.101.254.224
Received TC from NON SYM neighbor 5.101.254.224
Received TC from NON SYM neighbor 5.101.254.224
Received TC from NON SYM neighbor 5.103.216.119
reset link timer: 5.103.216.119 = 19128060
5.103.1.95 INFINITE
5.103.216.119 INFINITE
5.101.255.146 INFINITE
5.67.178.219 INFINITE
5.103.1.95 INFINITE
5.67.179.22 INFINITE
5.103.216.152 5.149.138.53 INFINITE
5.103.216.119 5.67.179.22 INFINITE
5.67.179.17 INFINITE
5.101.254.120 INFINITE
5.103.216.152 INFINITE
2014-07-30 19:55 GMT+02:00 Henning Rogge <(spam-protected)>:
> On Wed, Jul 30, 2014 at 7:47 PM, Antonio Anselmi <(spam-protected)>
> wrote:
> >> Are you using prioritization for the Olsr UDP port?
> >
> >
> > that's an interesting point, it could make the difference.
> > Do you know examples about tc implementation that prioritizes UDP
> packets?
>
> I think the Freifunk firmware has it.
>
> Just google for "OLSR UDP prioritization" and you should find a few
> examples.
>
> With some current wifi drivers it might be even possible to set the
> traffic class of OLSR UDP packets so that they get prioritization on
> layer2 (wifi) too. But I am not an expert for using the "tc" command.
>
> Henning Rogge
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20140801/5714a042/attachment.html>