LAUNCHXL-CC1350: Webdemo application in contiki is not able to connect to local MQTT Server

After some enabling and disabling of IPV4 in PC network setting i could able to see the page in IBM which says like this

en we disable IPV4 and enable IPV6 in PC Network settings we are able to get the webpage [bbbb::100]. But when we enable both IPV4 and IPV6 we are not able to get the webpage after sometime. So i assume that when IPV4 is enabled we are not able to get the IPV6 webpage. So i enabled the IP64 in configuration page.

So that we can access IPV4 IP and we are able to get the webpage. But the link for web and coap is missing.

Please let me know your thoughts on this.

Thanks

Rahul

No.

Please let me know what we need to configure.

Thanks

We have configured the peer router.

But everything seems to be same. I assume after doing this we will be able to access webpage [bbbb::100] without changing network settings to IPV6 only. Is that what you are expecting after doing this step?

Please check the image

We tried that too.

We are ok with getting webpage using IPV4 also but why we are not getting the web page with web and coap enabled in the sensor list.

Please let me if this is the issue due to which we are not able to communicate to the MQTT server?

Thanks

Hi,

Please check the result and let me know your thoughts,

debian@beaglebone:~$ sudo tcpdump -X -v -i eth0 port 1883
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
12:19:59.106751 IP6 (hlim 63, next-header TCP (6) payload length: 20) fd00::xx > fdde:xx.1883: Flags [R.], cksum 0x7e59 (correct), seq 100, ack 0, win 128, length 0
0x0000: 6000 0000 0014 063f fd00 0000 0000 0000 `......?........
0x0010: 0212 4b00 0e00 b501 fdde 7b2d 3976 0000 ..K.......{-9v..
0x0020: 6084 48e0 e9d2 d264 0405 075b 0000 0064 `.H....d...[...d
0x0030: 0000 0000 5014 0080 7e59 0000 ....P...~Y..

Hi,

"I suggest you to check your network settings."

Please let me know in which part we need to correct this.  Is this in PC or BBB? and what needs to be changed exactly?

Please check the following images of the MQTT server running on PC.

MQTT Subscription on port 18883 on all topics,

MQTT publishing to a particular topic, i tried publishing by giving IPV6 address also. In both cases i can see the messages in subscription 

So is there any other method other than local server to test and see MQTT packets coming from Nodes?

Thanks

Rahul

Hi,

We are glad to inform you that we can see some data coming in IBM Server.

Please let me know if this is the expected result in IBM server. As per our understanding in order to send data to our server we just need to change the broker IP. Is that correct?

Thanks

Rahul

Awesome.. Cheers... You are right..

Thanks a lot for your valuable support and time.

Actually we need to allow the connection for mosquitto in  the windows firewall advance security inbound rules.

Now i can see the data coming from the node in my local MQTT server as well.

Thanks for your quick and valuable response.

Thanks

Rahul

No problem.. You have really helped us a lot to reach so far and we are extremely thankful for that..

We will let u know once we have anything from 6lbr/contiki team.

One update is there like after trying many things today we could see some mqtt data in tcpdump for sometime, but seems like only data is coming from nodes and no response is going from BBB even though we are able to connect to the BBB mqtt broker from another pc connected in same network. But mosquitto broker log is not showing anything when nodes trying to connect.

Anyway we will post you the updates as we progress.

Thanks

Rahul

Hi,

Cheers!!!

Even though we didnt receive any response from contiki/6lbr git forums yet, we were trying many configurations and finally we are able to see the data in BBB local mosquitto broker.

Please check the following configurations that worked for us,

6lbr.config

#This file contains a default configuration for BeagleBone platform using
#a Telos SLIP Radio
#The full list of parameters and their meaning can be found in 6lbr.conf.example

MODE=ROUTER
#MODE=SMART-BRIDGE
#MODE=RPL-RELAY
#MODE=FULL-TRANSPARENT-BRIDGE
#MODE=NDP-ROUTER
#MODE=6LR
#MODE=RPL-ROOT

RAW_ETH=0
BRIDGE=1
CREATE_BRIDGE=6LBR
DEV_BRIDGE=br0
DEV_TAP=tap0
DEV_ETH=eth0
ETH_JOIN_BRIDGE=1
#RAW_ETH_FCS=1
RAW_ETH_FCS=0

DEV_RADIO=/dev/ttyACM0 #2.4GHz USB Dongle will enumerate like ACM0
#DEV_RADIO=/dev/ttyUSB1 #SmartRF06EB+CC13xxEM will enumerate like USB1
BAUDRATE=115200

LOG_LEVEL=3

interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
#auto br0
#iface br0 inet dhcp
auto eth0
iface eth0 inet dhcp

# Example to keep MAC address between reboots
#hwaddress ether DE:AD:BE:EF:CA:FE

# The secondary network interface
#auto eth1
#iface eth1 inet dhcp

# WiFi Example
#auto wlan0
#iface wlan0 inet dhcp
# wpa-ssid "essid"
# wpa-psk "password"
# Ethernet/RNDIS gadget (g_ether)
# ... or on host side, usbnet and random hwaddr
# Note on some boards, usb0 is automaticly setup with an init script
iface usb0 inet static
address 192.168.7.2
netmask 255.255.255.0
network 192.168.7.0
gateway 192.168.7.1

Along with this, we did the following

1. we configured peer router as the IPV6 address of br0.
2. Started MQTT broker in br0 IPV6 address.
3. Configured broker ip of Nodes to the IPV6 address of br0

Please note that some of those steps that we did may not be really relevant for its working, we are just posting all our configurations.

Thanks

Rahul

Cheers!!!

We could able to do that by giving the broker ip as bbbb:0:0:0: x : xyz : xyza : xyz instead of giving bbbb : : x : xyz : xyza : xyz

Now we are able to connect to local MQTT broker on BBB with both IPV6 and IPV4 routers connected to BBB.

Thanks
Rahul