[lime-dev] bmx6 debugging

Axel Neumann neumann at cgws.de
Sun Feb 23 14:34:48 UTC 2014

Hash: SHA1

On 02/23/2014 02:24 AM, Gioacchino Mazzurco wrote:
> Hi!
> On one node we are announcing a tunIn for internet and anotherone
> that have a corresponding tunOut is tring to reach internet, but
> there is some problem, packets never reach the other nodes and
> sniffing on interfaces never goes out from the originating node,
> and on dmesg i have found some of this messages
> [ 8829.860000] ip6_tunnel: bmxOut_9f4872: Path to destination
> invalid or inactive!
> That seems related ecause appears only on the node that is trying
> to go out, is it a well known problem or it is necessary a deeper
> debug ?

At least it's unknown to me. The message comes from ip6_tunnel kernel
module and (as far as I understand) is triggered when the kernel
catches a packet that is to be routed via the tunnel. Can you confirm
this? I mean does it appear when bmx6 creates the tunnel or when you
send a packet that should go via this tunnel. To test this start bmx6
on the originating node (I understand this is the tunnel client having
the bmxOut device) with parameter tunOutTimeout=0 (disabling the
automatic reactive tunnel setup). Also interesting would be which
kernel version you are running and if this happens with a specific
openWrt. Maybe the kernel developers have introduced some new validity
checks (that have not been there before) and that now detect packets
or routes as infeasible according to some RFC rules.


> _______________________________________________ Dev mailing list 
> Dev at lists.libre-mesh.org 
> https://lists.libre-mesh.org/mailman/listinfo/dev

Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/


More information about the lime-dev mailing list