firmware & tools: chamoc tools and chamos module implementation

[CW-75]

Contribution description

This is an implementation of vaina source code, The objective of this PR is design an udp client to connect with an device and send it a NIB_ADD request or a NIB_DEL, this device will response with an ACK if the request was received correctly, if the request was wrong received, the device should response with an NACK.

These Pr contains some structures to gives the elements required to this process, refering an client by an interface.

The interface that could be used are that appears in your System. you could see these executing ip address show command or ifconfig

enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.119  netmask 255.255.255.0  broadcast 192.168.2.255
        inet6 fe80::bef4:bb4a:f786:e805  prefixlen 64  scopeid 0x20<link>
...
enx5a008df2d56b: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.199  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::98eb:d858:51a0:dcc0  prefixlen 64  scopeid 0x20<link>
        ether 5a:00:8d:f2:d5:6b  txqueuelen 1000  (Ethernet)
...
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
...

Testing procedure

There are two cases to test the client connection, first testing locally by the an local host and then connecting with an m4a-24g board.

1 - Case °1 Running with chamoc_server test and the chamoc tool.

follow these steps:

• open two terminals (Terminal A & Terminal B):

# Terminal A
cd test/chamoc_server/
./run.sh

The script will ask about which interface will be used
when you see this output

# Terminal A
Server it's running

means that you are running the chamoc server, this will nerver stop until that received and nib request from a chamoc client.

• start the client code to local host test:
  note: before to start run the client, it's recommended take note of the iface name (see typing ip address show or ifconfig).
  in terminal B go to dist/tools/chamoc folder and ther run the test script.

# Terminal B
cd dist/tools/chamoc
./test.sh

When you are started you need to fill all the params fields that the script will need to execute te client code, e.g:

# Terminal B
Interface: enp2s0
Ipv6 Address: 2001:db8::1
Ipv6 Address prefix (64 - 128): 64

your expected output should see just like this:

# Terminal A
Server it's running
Packet Received:02004020010db8000000000000000000000001

# Terminal B
running nib add request
Request Confirmed

In terminal A it can look the packet received in hexadecimals pais, where:

Packet representation

02	00	40	20010db8000000000000000000000001
type of message	Message sequence number	network prefix of the ipv6 address	Ipv6 address

Packet HEX	Description
02	Refers to the NIB type of message (2) is NIB_ADD, (3) NIB_DEL
00	Refers to Message sequence number
40	It's the network prefix of the ipv6 address (0x40 is 64 in decimal value)
20010db8000000000000000000000001	it's the entered address 2001:db8:1

2 - Case °2 Running with chamos_server in m4a-24g board

follow these steps:

• open two terminals (Terminal A & Terminal B):

# terminal A
cd dist/tools/chamoc
./autoconfigure.sh

note : you could run the autoconfig script placing your owns parameters to the nib message and setup of the host,
./autoconfigure.sh [ipv6 address]
When you execute the script without any input, by default the script will take the ipv6 address 2001:db8::1 by default.

Issues/PRs references

[luisan00]

1.- The tool name is ambiguous
2.- What's the purpose of a command in this tool?

[luisan00]

nice job !! 💯
just documentation and aesthetics by now

[CW-75]

Good, only has a little doc corrections and format corrections 👍

[luisan00]

well done. almost finished!

[luisan00]

well dona!! going ahead!! 👍