which path do you use for connecting Raspberry pi zero w?

[lida2003]

which path do you use for connecting Raspberry pi zero w?

• serial(uart0)
• usb net
• wifi 2.4 net
• ip4 tunnel for ssh

Note: I noticed in previous topics about ip4 tunnel, but i don't know how to use.

[svpcom]

For GS I use RPI3 with ethernet for connection to laptop.
PI zero 2w is only suitable for air side or for standalone (without laptop) GS

[lida2003]

For GS I use RPI3 with ethernet for connection to laptop.

Yes. I saw the eth0

PI zero 2w is only suitable for air side or for standalone (without laptop) GS

@svpcom how do u connect this pi, serial/usb/wifi2.4/ip4 tunnel? Or there is an eth hw module for eth0?

[svpcom]

use serial console or wfb-ng tunnel when connection is established

[voluandev]

For GS I use RPI3 with ethernet for connection to laptop. PI zero 2w is only suitable for air side or for standalone (without laptop) GS

i have this dea, can you please tell me with wfb-ng can do like that?
In GS i use pi zero 2W, and connect with PC (run QGroundcontrol) via wifi (use chip wifi of raspberry). that mean setting up raspberry as a wifi hostpot using the wifi chip on the raspberry board, then use pc connect to this wifi.

[lida2003]

RPI3 with Release 23.01(image), plugin "taobao wifi card, 8812AU chip, usb powered"

The device is detected and registed with proper driver (rtl88xxau_wfb), but i DID NOT see wlan0?

pi@raspberrypi:~ $ dmesg |tail
[   33.110939] cam-dummy-reg: disabling
[ 1178.586140] usb 1-1.1.2: new high-speed USB device number 5 using dwc_otg
[ 1178.716725] usb 1-1.1.2: config 1 interface 0 altsetting 0 endpoint 0x85 has an invalid bInterval 0, changing to 7
[ 1178.717318] usb 1-1.1.2: New USB device found, idVendor=0bda, idProduct=881a, bcdDevice= 0.00
[ 1178.717345] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1178.717366] usb 1-1.1.2: Product: 802.11n NIC
[ 1178.717383] usb 1-1.1.2: Manufacturer: Realtek
[ 1178.717400] usb 1-1.1.2: SerialNumber: 123456
[ 1178.916641] 88XXau_wfb: loading out-of-tree module taints kernel.
[ 1179.158582] usbcore: registered new interface driver rtl88xxau_wfb
pi@raspberrypi:~ $ lsmod |grep wfb
88XXau_wfb           1921024  0
cfg80211              765952  1 88XXau_wfb
pi@raspberrypi:~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.68.232  netmask 255.255.255.0  broadcast 192.168.68.255
        ether b8:27:eb:f3:69:a6  txqueuelen 1000  (Ethernet)
        RX packets 1968  bytes 196965 (192.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1788  bytes 188263 (183.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 8  bytes 770 (770.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8  bytes 770 (770.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[lida2003]

Oh iwconfig shows the wifi interface, why Managed mode???

pi@raspberrypi:~ $ iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=18 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off

pi@raspberrypi:~ $ ethtool -i wlan0
driver: rtl88xxau_wfb
version: 5.15.76-v7+
firmware-version:
expansion-rom-version:
bus-info: 1-1.3:1.0
supports-statistics: no
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

[lida2003]

OK I got default pi wlan0 work.

pi@raspberrypi:~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.68.232  netmask 255.255.255.0  broadcast 192.168.68.255
        ether b8:27:eb:f3:69:a6  txqueuelen 1000  (Ethernet)
        RX packets 145  bytes 17634 (17.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 27  bytes 3221 (3.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 8  bytes 770 (770.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8  bytes 770 (770.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.68.231  netmask 255.255.255.0  broadcast 192.168.68.255
        ether b8:27:eb:a6:3c:f3  txqueuelen 1000  (Ethernet)
        RX packets 36  bytes 4279 (4.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 116  bytes 17501 (17.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[svpcom]

Builtin wifi card is blacklisted in /etc/modprobe.d/wfb.conf to avoid confuse with 8812au card

[lida2003]

Builtin wifi card is blacklisted in /etc/modprobe.d/wfb.conf to avoid confuse with 8812au card

OK, i got ur point. udev might do the job. BUT I haven't tested yet.

1. How do you force a wifi interface to be a certain wlanX?
2. write udev rules for changing network interface name

[lida2003]

@svpcom udev do the job pretty good!

wfb-ng 锁定WiFi接口