23 Feb
2014
23 Feb
'14
1:24 a.m.
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 ?
23 Feb
23 Feb
1:13 p.m.
Using bmx6 1d022e3f0ae0a2954c90b18fdfbcc178d7437605 the problem is not
present, so it seems some regression was introduced in newer version...
25 Feb
25 Feb
5:21 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/23/2014 02:13 PM, Gioacchino Mazzurco wrote:
Using bmx6 1d022e3f0ae0a2954c90b18fdfbcc178d7437605
the problem is
not present, so it seems some regression was introduced in newer
version...
Can you name a revision that shows the problem (ideally one close to
1d022e3)?
/axel
_______________________________________________ Dev
mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTDChoAAoJECcbc9JNAq8psdsIAKHGUYNUB3qXKVMOv77eyJ/J
E4PgGdyVVoH3KpzLKrxZKQoGsXB5WohdyjB5humu3LJUA0aG4RuQLglQwwERbXPh
pY3hkpnzJqsopRbGRqC1l7dBOy9idWO5xshU1egZb2D/11eyUBS/nAS392stCFfr
X7T9N92xBMT2nW8OMNaHw41jtiqxziNrbmGBKyydwP9CF570wEQyLDVsH+rd3WY4
SEygefirbX83/lpbB8FBZcfI8QEHTiyrZZeoUCX4NnXo3kCsiDZJ1qDpuUcVG0yP
937cJpJ8H/bBdjT8XLn1BhcgrznXCIjTCq8OKi4qa5M+7BtfCHK9W54T0IpPuTQ=
=8rVt
-----END PGP SIGNATURE-----
11:22 a.m.
It was the last one (in day 20140221). If you need it maybe I can turn on some router that
have this unworking revision and take a look to big hex number.
----- Mensaje original -----
De: "Axel Neumann" <neumann(a)cgws.de>
Para: dev(a)lists.libre-mesh.org
Enviados: Martes, 25 de Febrero 2014 6:21:44
Asunto: Re: [lime-dev] bmx6 debugging
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/23/2014 02:13 PM, Gioacchino Mazzurco wrote:
Using bmx6
1d022e3f0ae0a2954c90b18fdfbcc178d7437605 the problem is
not present, so it seems some regression was introduced in newer
version...
Can you name a revision that shows the problem (ideally one close to
1d022e3)?
/axel
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTDChoAAoJECcbc9JNAq8psdsIAKHGUYNUB3qXKVMOv77eyJ/J
E4PgGdyVVoH3KpzLKrxZKQoGsXB5WohdyjB5humu3LJUA0aG4RuQLglQwwERbXPh
pY3hkpnzJqsopRbGRqC1l7dBOy9idWO5xshU1egZb2D/11eyUBS/nAS392stCFfr
X7T9N92xBMT2nW8OMNaHw41jtiqxziNrbmGBKyydwP9CF570wEQyLDVsH+rd3WY4
SEygefirbX83/lpbB8FBZcfI8QEHTiyrZZeoUCX4NnXo3kCsiDZJ1qDpuUcVG0yP
937cJpJ8H/bBdjT8XLn1BhcgrznXCIjTCq8OKi4qa5M+7BtfCHK9W54T0IpPuTQ=
=8rVt
-----END PGP SIGNATURE-----
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
27 Feb
27 Feb
5:08 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/25/2014 12:22 PM, al wrote:
It was the last one (in day 20140221). If you need it
maybe I can
turn on some router that have this unworking revision and take a
look to big hex number.
yes please.
And can you also confirm that this non-working router has the same
kernel version running as the working router and which these are?
I still have the feeling that something in kernel changed.
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
Did you try to reach ipv4 or ipv6 internet?
/axel
----- Mensaje original -----
De: "Axel Neumann"
<neumann(a)cgws.de> Para:
dev(a)lists.libre-mesh.org Enviados: Martes, 25 de Febrero 2014
6:21:44 Asunto: Re: [lime-dev] bmx6 debugging
On 02/23/2014 02:13 PM, Gioacchino Mazzurco wrote:
>> Using bmx6
1d022e3f0ae0a2954c90b18fdfbcc178d7437605 the
>> problem is not present, so it seems some regression was
>> introduced in newer version...
Can you name a revision that shows the problem (ideally one close
to 1d022e3)?
/axel
>>
_______________________________________________ Dev mailing
>> list Dev(a)lists.libre-mesh.org
>> https://lists.libre-mesh.org/mailman/listinfo/dev
>>
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTD3DnAAoJECcbc9JNAq8plVMH/ihoeB8E/5OZgvQ1/coz32wJ
L0yEctgUkZz4vr3ieAy8QEW0+YhUqA567ibEFcWf7GCxV8UZmIErbMuqtZvKmcyY
m9NEJYqURJ416gAWRFmTTq4L0hIyPfOsJevzJyyBbAPA73Gbb2Lz01Ikm+1BZHsn
0h1y7gW+YlKfIk8o9uVN/3djIghjDsRuekTUW05YYHPhvBO5wrwaQ08HS2cz2dCv
rH04LPc77AbnjEl+GubkAZBn8V3Kck5lFwBGnHxorK39HGRKSqByplPJ2wrCPD/r
yUuAd5ckwJAvGP3DXb2w6ye02zLpwOe/gNy9BSoYnwW5jO0pDeUd2VaouOUsL2c=
=v5BG
-----END PGP SIGNATURE-----
28 Feb
28 Feb
6:12 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've just tested with two qmp nodes both running latest
qmp testing branch with the bmx6 master commit:
60e1cd8ab8a8ec6259f8cae4748f0cdd63b2c5f2 (current bmx6 master tip).
And there ipv4 and ipv6 tunnels work fine (also ipv4 internet).
These ones are running kernel 3.3.8
But doing some tests with my home server (running 3.8.0-36) I indeed
notice some strange problems with ipv4 tunnels. But then with both
bmx6 versions. The 1d022e and the latest 60e1cd8 !
And here the problem is on the GW side where now it seems inpossible
to use different ipip6 tunnel for incoming and outgoing packets!!!??
Being able to reproduce the problem you face would help a lot.
Maybe via access to your problematic nodes or a sysupgrade binary for
TPlinks TL-WR703N and the config you applied for GW and GW client.
/axel
On 02/27/2014 06:12 PM, Gioacchino Mazzurco wrote:
On Thursday 27 February 2014 18:08:00 Axel Neumann
wrote:
And can you also confirm that this non-working
router has the
same kernel version running as the working router and which these
are?
Yes they have
Did you try to reach ipv4 or ipv6 internet?
ipv4
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTENGNAAoJECcbc9JNAq8pyboIAK5I/WUOSJXaDzraZLp7GDh8
zOmeEXSUOiZJ3qae2hZdYbUnyTs1up4kR9JpyGpfabzJtQ2ANxT1G3D/K6f3K43J
NrQYdR2NZrrnZ6qGcKODyGv+Q5t2rE0kBkUzjUVLKpCywnXw7wIafmDuENHxiQKD
DOlw8UdkMXUFu5vkISL7EphhinSQqPLEQTk8Z5ZlaQib+4Inps2ZvZ7MUx8psvAM
+c+ieuwTvFhfC7SPiaXTaUKDf0oVemXQIggTlaWkwhlTBwi9nSXF2VPEzuDYTHj5
NlbxHDfM/n0PaDrUxngLqKn4speuBxrkQ6cwmjXQzNhmh3Q8X3Warxni/o50gnw=
=MvyN
-----END PGP SIGNATURE-----
1 Mar
1 Mar
3:01 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
On 02/28/2014 07:12 PM, Axel Neumann wrote:
I've just tested with two qmp nodes both running latest qmp testing
branch with the bmx6 master commit:
60e1cd8ab8a8ec6259f8cae4748f0cdd63b2c5f2 (current bmx6 master
tip). And there ipv4 and ipv6 tunnels work fine (also ipv4
internet). These ones are running kernel 3.3.8
But doing some tests with my home server (running 3.8.0-36) I
indeed notice some strange problems with ipv4 tunnels. But then
with both bmx6 versions. The 1d022e and the latest 60e1cd8 ! And
here the problem is on the GW side where now it seems inpossible to
use different ipip6 tunnel for incoming and outgoing packets!!!??
I figured out my problem: some sysctl settings were not configured
correctly! Maybe your problem is the same.
quick fix (on GW and client):
for f in $(find /proc/sys/net/ipv4/conf/*/rp_filter); do echo 0 > $f; done
this bmx6 one should also solve it (setting rp_filter = 2 by default):
2179ce5cd8e8413cdc2c815aa11944640a7c104d
/axel
Being able to reproduce the problem you face would help a lot.
Maybe via access to your problematic nodes or a sysupgrade binary
for TPlinks TL-WR703N and the config you applied for GW and GW
client.
/axel
On 02/27/2014 06:12 PM, Gioacchino Mazzurco wrote:
On Thursday 27 February 2014 18:08:00 Axel
Neumann wrote:
> And can you also confirm that this non-working router has the
> same kernel version running as the working router and which
> these are?
Yes they have
> Did you try to reach ipv4 or ipv6 internet?
ipv4
_______________________________________________ Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTEfZBAAoJECcbc9JNAq8pBrUH/iTd0O/U6DLxvnuSvjStLbyU
U6jXiZsnVXby8K00Ul+8uMeki1HW5KS5L87y7wu7lDBDByErEdnInAumA4zut8m/
cQ+UvsAO1mk1Adi3ZIbhBPhcIE85JKMjd1GxnEN06Vyo7gvNVGXUFa6WIt+yhOq6
aYxMJ/4nGdGo5WV0/A0NP8+UggqEd6PCA+X+/KqTJQ0OfltmSwypg+Md24a4o9vy
Cz+U33TFM9Jj6iFYG4Nfhbj8hEojQRokkpwZs733yQBwqqd+LegkXy7IYKNdYnJ3
Orjk/dvo9zQCubG8f9kVWt+kYGDfpSitGqRLR7UIdjHvMUaaCoArlURjHdpfxi8=
=FunO
-----END PGP SIGNATURE-----
23 Feb
23 Feb
2:34 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
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.
best
/axel
_______________________________________________ Dev
mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTCgcAAAoJECcbc9JNAq8pLYYH/RdnO47S3W+x7We0G7LwAnzM
gvVeUILHW7ZKhmpo6Paqir28+HMloQd54pX8hyidz7vSwIJFBRHaClNYh29t0BTb
Ske/GSVZlTe4u8fdxccoV4ZgBdMsmA7wMPS3JNB581aeerROUoQAhCRofU7p6dVd
9LjjlrrNgJrU6mrsQ7mqKweQHZo4eJ1NtIFTnTqhVtZWX2/Jycuka7U/3eXOGQzE
O3iHaMDMU61e8tLgBfvcuKnUlXh93xWwMkLUBItvVjHrm7hz4oMTCN17g7mTgHf7
d20pLsgyRDgGjc1wvplIjyob3b5RGwsjQKMJnLJE9eBvwEcfwqd2gs9y8gSKE5g=
=Rqwz
-----END PGP SIGNATURE-----
3708
days inactive
3714
days old
8 comments
3 participants
participants (3)
-
al -
Axel Neumann -
Gioacchino Mazzurco