I've used ap51-flash-gui.exe in order to flash kamikaze into a
meraki-mini... but after the execution the meraki doesn't load kamikaze:
the boot script is correct (fis load -d linux) but redboot return "can't
execute linux - invalid entry address".
I've uploaded the correct .gz file for kernel .jffs2 for rootfs)
I'm testing batmand 0.2 in two hardware-different nodes:
184.108.40.206/8 is a Fonera running its standard firmware
220.127.116.11/8 is a Fonera running Kamikaze
>From kamikaze(d) node I see:
Received BATMAN packet via NB: 18.104.22.168, IF: ath0 22.214.171.124 (from OG:
126.96.36.199, seqno 926, TTL 50, V 3, UDF 0, IDF 0)
Creating new originator: 188.8.131.52
Forward packet: rebroadcast neighbour packet with direct link and
Forwarding packet (originator 184.108.40.206, seqno 926, TTL 49) on interface ath0
Orginator timeout: originator 220.127.116.11, last_valid 0
but the same node, issuing the command "batmand -c -d 1 -b" tells me "No
batman nodes in range".
I'm afraid of the message "Orginator timeout: originator 18.104.22.168" in the
above lines... is this the problem?
>> I have two Asus wl500gp router, each with atheros(Atheros 5212)
>> wlancards, running kamikaze 7.06; kernel ver.:22.214.171.124. and B.A.T.M.A.N.
>> 0.2 rv451 (compability version 3)
>> one of them has access to the internet.
>> The one who has no internet connection, doesn't set a default route to
>> the one who has. It only sets this routes:
> it looks quite good so far. Blocked TCP is the most obvious reason that the
> tun device does not appear. the client tries to establish a TCP control
> channel (port 1967) to the gateway. If that connection attempt is ignored no
> default route will be set.
thanks for replying so fast. Unfortunately the reason isn't the blocked
tcp-port, I tested it after I shutdown the firewall on each node with
the same result as you can see above. Is there something else I can do?