USB Direct Supported?

[clee604]

Hi there,

I'm currently using a wyze v3 with wz_mini_hacks and evaluating whether I can move over to thingino for my use case. I noticed browsing through the documentation that I can't find any reference to USB Direct or ncm (ie. https://github.com/gtxaspec/wz_mini_hacks/wiki/Configuration-File#usb-direct)

Searching through the code, it does seem like the ncm module is loaded; my main question is whether USB Direct is supported with Thingino? (ie. single cable to supply power and ethernet to the camera from a linux/supported host)

[gtxaspec]

hi @clee604, its supported if you compile your own build and enable :

[gtxaspec]

Some info:

1. Lock the Interface Name Using udev Rules

You can create a persistent network interface name based on the USB port where the device is plugged in. udev rules allow you to define custom names for devices based on their physical attributes (like the USB port).

Steps:

1. Identify the USB Device Details:
   Run the following command to get details about your USB device, including the physical path:

   udevadm info -a -p /sys/class/net/<interface_name> | grep -m 1 "KERNELS=="

   Replace <interface_name> with the current name of your USB-NCM device (e.g., enxdea9d3ef49cb). This will output something like:

   KERNELS=="3-1"
   

   This shows the device is connected to USB bus 3, port 1.

2. Create a udev Rule:
   Create or edit a new udev rule file in /etc/udev/rules.d/. For example:

   sudo nano /etc/udev/rules.d/99-usb-net.rules

   Add a rule to lock the interface name based on the USB bus and port:

   SUBSYSTEM=="net", ACTION=="add", KERNELS=="3-1", ATTR{type}=="1", NAME="usbnet0"

   • KERNELS=="3-1": This is the USB bus and port (from the previous command).
   • ATTR{type}=="1": Ensures it's a network device.
   • NAME="usbnet0": This assigns a persistent interface name usbnet0 for the device connected to this USB port.

3. Reload udev Rules:
   Reload udev rules and reconnect the USB device:

   sudo udevadm control --reload-rules
   sudo udevadm trigger

   After this, the network interface should always appear as usbnet0 (or whatever name you chose) when connected to that specific USB port, regardless of the MAC address.

[clee604]

Issue created here for the usb0 portal issue - #273

Following the instructions above I was able to successfully set the interface name to usbnet0 using the port location. Using a proxmox machine I'm able to set up the usbnet0 interface and bridge it using a linux bridge. The camera then pulls an IP via dhcp from my router on my network.

I am unable to disable wifi completely though, I've confirmed the usb0 bug above.

[gtxaspec]

try
fw_setenv disable_wlan true then reboot

[clee604]

that works, thanks!

[clee604]

this is probably more of a standard linux question but i haven't been able to get 'allow-hotplug' type functionality to work with usbnet0.

Everything works when the host starts from boot; however if the camera reboots while the host is already running, usbnet0 interface is DOWN until I manually use 'ifup usbnet0'

i have this in my /etc/network/interfaces file

allow-hotplug usbnet0
iface usbnet0 inet manual
        up /sbin/ip link set $IFACE master vmbr0

I'm guessing I need to modify something in the udex rules?