Hi, I build an rdk-b image according to the tutorial and everything went fine so far until I checked with the WiFi information. My goal is to fetch data about connected wifi clients, such as their current RSSI value, via the CcspWifiAgent component. 
I flashed the image, booted up for the first time, connected to the standard AP Wifi and configured it via the xfinity webui accordingly. 
Afterwards, I connected to the new user defined WiFi sshed onto the RPI. I noticed there is no data available about connected clients under "Device.WiFi." as shown below.





Also, in the xfinity webui, the connected client (my machine) is shown as offline device. 


and in the Wifi Spectrum Analyzer Part, the Scan never shows any real data. 



I looked into journal log of CcspWifiAgent component and found a lot of errors relating to the interface and seemingly missing binaries. I attached two logs, one of the scan process  wifi_scan_error_log.txt and the other while trying to show the connected devices connected_devices_error_log.txt.
I suspect it's merely a configuration issue in yocto where certain dependencies haven't been set properly in the recipes, but that's just a wild guess.


Hopefully, someone can point me to the causes of this issue and how to solve it.

Thanks


UPDATE ON 03.04.2019 - Inserted "ifconfig" output 

br0       Link encap:Ethernet  HWaddr 1A:D0:39:82:64:AC
          inet addr:192.168.101.3  Bcast:192.168.101.255  Mask:255.255.255.0
          inet6 addr: fe80::18d0:39ff:fe82:64ac/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:3318 (3.2 KiB)

brlan0    Link encap:Ethernet  HWaddr B8:27:EB:5E:D0:BA
          inet addr:10.0.0.1  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: fe80::6009:51ff:fe87:c646/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:20053 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10691 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2284539 (2.1 MiB)  TX bytes:3446312 (3.2 MiB)

erouter0  Link encap:Ethernet  HWaddr B8:27:EB:0B:85:EF
          inet addr:192.168.20.180  Bcast:192.168.20.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:219956 errors:0 dropped:30933 overruns:0 frame:0
          TX packets:202103 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:23687153 (22.5 MiB)  TX bytes:20757039 (19.7 MiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:257576 errors:0 dropped:0 overruns:0 frame:0
          TX packets:257576 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13261698 (12.6 MiB)  TX bytes:13261698 (12.6 MiB)

wlan0     Link encap:Ethernet  HWaddr B8:27:EB:5E:D0:BA
          inet6 addr: fe80::ba27:ebff:fe5e:d0ba/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:20053 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10889 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2284539 (2.1 MiB)  TX bytes:3737669 (3.5 MiB)






  • No labels

4 Comments

  1. Hi  Z-Lyn Matten,

    Could you please paste the output of 'ifconfig' in your RPi ?

    1. Of course. Sorry for the late answer. In the setup, the RPI is only connected via Ethernet to the main gateway router. The clients connected over wifi are getting assigned IP addresses of the 10.0.0.0/24 subnet.

      br0       Link encap:Ethernet  HWaddr 1A:D0:39:82:64:AC
                inet addr:192.168.101.3  Bcast:192.168.101.255  Mask:255.255.255.0
                inet6 addr: fe80::18d0:39ff:fe82:64ac/64 Scope:Link
                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                RX packets:0 errors:0 dropped:0 overruns:0 frame:0
                TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:1000
                RX bytes:0 (0.0 B)  TX bytes:3318 (3.2 KiB)
      
      brlan0    Link encap:Ethernet  HWaddr B8:27:EB:5E:D0:BA
                inet addr:10.0.0.1  Bcast:10.0.0.255  Mask:255.255.255.0
                inet6 addr: fe80::6009:51ff:fe87:c646/64 Scope:Link
                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                RX packets:20053 errors:0 dropped:0 overruns:0 frame:0
                TX packets:10691 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:1000
                RX bytes:2284539 (2.1 MiB)  TX bytes:3446312 (3.2 MiB)
      
      erouter0  Link encap:Ethernet  HWaddr B8:27:EB:0B:85:EF
                inet addr:192.168.20.180  Bcast:192.168.20.255  Mask:255.255.255.0
                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                RX packets:219956 errors:0 dropped:30933 overruns:0 frame:0
                TX packets:202103 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:1000
                RX bytes:23687153 (22.5 MiB)  TX bytes:20757039 (19.7 MiB)
      
      lo        Link encap:Local Loopback
                inet addr:127.0.0.1  Mask:255.0.0.0
                inet6 addr: ::1/128 Scope:Host
                UP LOOPBACK RUNNING  MTU:65536  Metric:1
                RX packets:257576 errors:0 dropped:0 overruns:0 frame:0
                TX packets:257576 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:1000
                RX bytes:13261698 (12.6 MiB)  TX bytes:13261698 (12.6 MiB)
      
      wlan0     Link encap:Ethernet  HWaddr B8:27:EB:5E:D0:BA
                inet6 addr: fe80::ba27:ebff:fe5e:d0ba/64 Scope:Link
                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                RX packets:20053 errors:0 dropped:0 overruns:0 frame:0
                TX packets:10889 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:1000
                RX bytes:2284539 (2.1 MiB)  TX bytes:3737669 (3.5 MiB)





  2. Hello,


    I have encountered same issue.

    Connected devices to RPI shows in Device offline list.

    I am using the code at the Release 2019q1.


    Besides, other issue is running WebUI through WAN.

    As per User guide document, i can access WebUI from LAN side as shown below. 

    From LAN Side:

    http://10.0.0.1

    From WAN Side:

    http://<WAN IP Address of RaspberryPi>:8080

    For e.g

    http://10.213.51.122:8080

    From WAN side i could not able to connect. I have changed IP address to Ethernet address of RPI.

    Any inputs (Like Browser configuration if any) ?

    Thanks


  3. Hi All,

    CcspLmlite component has dependency on CcspEthAgent to sync the connected clients. The issue was observed and created a ticket earlier and since the CcspEthAgent was not opensourced to LLC the ticket was put in frozen  state and recently the CcspEthAgent is opensouced to LLC so re-opened the below ticket to address this issue.

    REFPLTB-93 - Getting issue details... STATUS

    Thanks and Regards

    Srinivas