Debian 12.x (Major Changes).... NCM only, iwd for wifi..

General Discussion
1

So with todays’ 12.x snapshot uploads: Debian 12.x (Bookworm) - Monthly Snapshot - 2023-10-07 and ARM64 - Debian 12.x (Bookworm) - Monthly Snapshots - 2023-10-07 - #2

We have 2 big changes in the stack…

RNDIS

RNDIS is now disabled by default, you will not see two usbX interfaces, only usb0, which uses NCM… This means, Linux, Mac, and Windows (11) are all driverless, and use 192.168.7.2.

If your on Windows 10, 8.x, 7, Vista, XP etc, sorry no out of the box NCM driver. If someone figures out how to build a windows driver that works on those, let us know, then we can add it by default… But in Linux, Greg has stated, RNDIS is going to be ripped out…

For those that need it all cost, till it’s finally ripped out completly, just open:
/etc/default/bb-boot and disable: USB_RNDIS_DISABLED=yes → #USB_RNDIS_DISABLED=yes

WiFi

It turns out, wpa_supplicant and wpa_cli was to complex for some users, so we moved to iwd…

debian@BeagleBone:~$ iwctl device list
                                    Devices                                    
--------------------------------------------------------------------------------
  Name                  Address               Powered     Adapter     Mode      
--------------------------------------------------------------------------------
  wlan0                 80:30:dc:f8:30:22     on          phy0        station     

debian@BeagleBone:~$ iwctl station wlan0 scan
debian@BeagleBone:~$ iwctl station wlan0 get-networks
                               Available networks                              
--------------------------------------------------------------------------------
      Network name                      Security            Signal
--------------------------------------------------------------------------------
      Avenger                           psk                 ****    
      BeagleBone                        psk                 ****    

debian@BeagleBone:~$ iwctl --passphrase "BeagleBone" station wlan0 connect "BeagleBone"
debian@BeagleBone:~$ iwctl station wlan0 show
                                 Station: wlan0                                
--------------------------------------------------------------------------------
  Settable  Property              Value                                          
--------------------------------------------------------------------------------
            Scanning              no                                               
            State                 connected                                        
            Connected network     BeagleBone                                     
            IPv4 address          192.168.3.32                                     
            ConnectedBss          ba:fb:e4:f4:7a:ad                                
            Frequency             2412                                             
            Security              WPA2-Personal                                    
            RSSI                  -78 dBm                                          
            AverageRSSI           -79 dBm                                          
            TxBitrate             1000 Kbit/s                                      
            RxBitrate             1000 Kbit/s 
debian@BeagleBone:~$ iwctl station wlan0 get-networks
                               Available networks                              
--------------------------------------------------------------------------------
      Network name                      Security            Signal
--------------------------------------------------------------------------------
  >   BeagleBone                      psk                 ****    
      Avenger                           psk                 ****

Regards,

4 Likes
2

argh…

Seth

P.S. I guess it is okay now. It shows the actual IP of the beaglebone used which is neat.

3

On Windows 10, the drivers for NCM are located here, but must be manually assigned to the device:
C:\Windows\System32\DriverStore\FileRepository\usbncm.inf_amd64_9957a38c3d2283ed

1 Like
4

What could be the reason if iwd does not reconnect after reboot on Beaglebone green wireless?

Bookworm IoT image 2023-12-07

journalctl -f -u iwd
Dec 10 20:17:04 vector3 iwd[627]: HT RX MCS indexes:
Dec 10 20:17:04 vector3 iwd[627]: 0-7
Dec 10 20:17:04 vector3 iwd[627]: Ciphers: CCMP-128 TKIP
Dec 10 20:17:04 vector3 iwd[627]: Supported iftypes: station ap p2p-client p2p-go p2p-device
Dec 10 20:17:05 vector3 iwd[627]: Received error during CMD_TRIGGER_SCAN: Invalid argument (22)