root@17-21:~# batmand -v
B.A.T.M.A.N. 0.3-beta rv791 (compatibility version 4) root@17-21:~# batmand -cd4 [ 33051930] Received BATMAN packet via NB: 105.61.17.32, IF: eth1:bat 105.61.17.21 (from OG: 4.0.50.0, via old OG: 31.213.16.210, seqno 4384, tq 17, TTL 61, V 61, UDF 0, IDF 1) [ 33051930] Is an internet gateway (class 105) [ 33051930] Drop packet: incompatible batman version (61)
---
root@17-32:~# batmand -v WARNING: You are using the unstable batman branch. If you are interested in *using* batman get the latest stable release ! B.A.T.M.A.N. 0.3-beta rv824 (compatibility version 4) root@17.32:~# batmand -cd4 [ 7946500] Received BATMAN packet via NB: 105.61.17.21, IF: eth1:bat 105.61.17.32 (from OG: 0.254.113.181, via old OG: 0.4.117.105, seqno 26941, tq 61, TTL 18, V 105, UDF 0, IDF 0)
[ 7946500] Is an internet gateway (class 1) [ 7946510] Drop packet: incompatible batman version (105)
Regards tetzlav
[ 7946500] Is an internet gateway (class 1) [ 7946510] Drop packet: incompatible batman version (105)
In revision 812 the header format was changed due to future compability issues (the version field is now the first field in the header). I'm sorry about the inconvenience - it wont happen too often.
Greetings, Marek
Marek Lindner schrieb:
[ 7946500] Is an internet gateway (class 1) [ 7946510] Drop packet: incompatible batman version (105)
In revision 812 the header format was changed due to future compability issues (the version field is now the first field in the header). I'm sorry about the inconvenience - it wont happen too often.
:-/ just this minute we included batmand-0.3 rv791 in our Leipziger Freifunk-Firmware and now the newer Versions are incompatible with this included version... So wie never get an big connected batman-testbed in Leipzig in near Future, because i think the the users wont update as often as batmand-compat change.
The rv791 routes fine, but gateway make some Problems. So we included this testet version and only request the users that _want_ to use batman-gateway-tunnel tu update their batmand. (updatecheck is includet) -> now our Plans are broken... :-(
Why you dont enlarge the compat# from 4 to 5, or so? Thats confusing, sorry...
Regards tetzlav
The rv791 routes fine, but gateway make some Problems. So we included this testet version and only request the users that _want_ to use batman-gateway-tunnel tu update their batmand. (updatecheck is includet) -> now our Plans are broken... :-(
Sorry about that. We don't do it to explicitly annoy our users but to minimize future problems. But to do that change now than after the final release.
Why you dont enlarge the compat# from 4 to 5, or so? Thats confusing, sorry...
That would not change the problem - here is why: Before rev812 the version (compat) field was the 10th byte in the header. Now it is the first byte. Even if the newer versions increment their version field the older version will look for it at the wrong place.
If we don't have the version field at the first byte all future header changes may "move" the version field around (same as now). That is why we have to do it once and hopefully never again.
Regards, Marek
b.a.t.m.a.n@lists.open-mesh.org
-
Marek Lindner -
tetzlav