Bringup procedure of a real device

Hello everybody, I try to bring up a wireless connection between two identical boards, both equiped with the at86rf233 module. At first everything seems to be good - the source was compiled without failure, the process list shows all the threads needed for a working interface, but when I try to get a contact from one board to the other nothing happens.

Is there anyone who can give some hints about the best way to bring up a wireless connection with RIOT?

Here is what I have done: First I flash the gnrc_networking example on both boards. The command showed exactly the same on both boards:

> ifconfig Iface 7 HWaddr: 30:02 Channel: 26 Page: 0 NID: 0x23             Long HWaddr: 88:77:66:55:44:33:22:12             TX-Power: 0dBm State: IDLE max. Retrans.: 3 CSMA Retries: 4             AUTOACK CSMA MTU:1280 HL:64 6LO RTR IPHC             Source address length: 8             Link type: wireless             inet6 addr: ff02::1/128 scope: local [multicast]             inet6 addr: fe80::8a77:6655:4433:2212/64 scope: local             inet6 addr: ff02::1:ff33:2212/128 scope: local [multicast]

so far so good. Then I altered the ip-addresses on one board to:

> ifconfig Iface 7 HWaddr: 30:02 Channel: 26 Page: 0 NID: 0x23             Long HWaddr: 88:77:66:55:44:33:22:12             TX-Power: 0dBm State: IDLE max. Retrans.: 3 CSMA Retries: 4             AUTOACK CSMA MTU:1280 HL:64 6LO RTR IPHC             Source address length: 8             Link type: wireless             inet6 addr: ff02::1/128 scope: local [multicast]             inet6 addr: fe80::8a77:6655:4433:2214/64 scope: local             inet6 addr: ff02::1:ff33:2214/128 scope: local [multicast]

then I tried to ping from one board to the other:

> ping6 fe80::8a77:6655:4433:2214

result: no output - the shell output stucks and I have to reboot....

A ping to the own address delivers this output, but then the shell stucks again:

> ping6 fe80::8a77:6655:4433:2212 12 bytes from fe80::8a77:6655:4433:2212: id=83 seq=1 hop limit=64 time = 4.892 ms

Is this the normal behaviour of RIOT that the command don't come back to the shell? When the board stucks and I stop it with the debugger it seems the it cycles through the Idle-State.

Can anyone give me some hints what I'm doing wrong? How could it be found out that there is some traffic in the air?

Thanks a lot and best regards, Bernhard