OS: Ubuntu 24.04.1 LTS and macOS Sonoma 14.5.
Hardware:
product: mediaTek Wireless_Device
driver: mt7921u
wireless: IEEE 802.11
Apple M2
Purpose: Simple data transfer between linux and mac via awdl0 interface.
Problem:
When I start owl with the command “sudo owl -i wlx90de808874cd -c 6”, the terminal will display the add peer information, and then run my own c++ code in linux and mac respectively, i.e., the linux side registers for the service and starts it (avahi), and the mac side discovers the service, and parses and sends the data (dns_sd), but the problem is that it's hard for my mac to discover the service, maybe occasionally it will discover the service and then successfully transfer the data to linux.
when I set the control domain to us, and use the command “sudo owl -i wlx90de808874cd -c 149” to start owl, the terminal shows unhandled frame(-1), but the mac can immediately discover the service. service and parses it, though at best it doesn't finish sending data. The same experiment runs perfectly fine for me in both macs, of course macs don't need owl to emulate the awld0 interface as they come with it, please let me know how to solve my problem, I would like the mac side to discover the service faster and for owl to work stably as well as transferring the data successfully.
OS: Ubuntu 24.04.1 LTS and macOS Sonoma 14.5.
Hardware:
product: mediaTek Wireless_Device
driver: mt7921u
wireless: IEEE 802.11
Apple M2
Purpose: Simple data transfer between linux and mac via awdl0 interface.
Problem:
When I start owl with the command “sudo owl -i wlx90de808874cd -c 6”, the terminal will display the add peer information, and then run my own c++ code in linux and mac respectively, i.e., the linux side registers for the service and starts it (avahi), and the mac side discovers the service, and parses and sends the data (dns_sd), but the problem is that it's hard for my mac to discover the service, maybe occasionally it will discover the service and then successfully transfer the data to linux.
when I set the control domain to us, and use the command “sudo owl -i wlx90de808874cd -c 149” to start owl, the terminal shows unhandled frame(-1), but the mac can immediately discover the service. service and parses it, though at best it doesn't finish sending data. The same experiment runs perfectly fine for me in both macs, of course macs don't need owl to emulate the awld0 interface as they come with it, please let me know how to solve my problem, I would like the mac side to discover the service faster and for owl to work stably as well as transferring the data successfully.