-----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-----