@bushw ok this is what i saw in my setup running as an ap (I used netplan and NetworkManager - but I do not use its AP (wifi hotspot) features ) > sudo iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination ^ empty sudo nft list ruleset ^ empty

Forum moderatores are there to provide guidance in discussion and take action if things get out of control. Having a wide varity of knowledge in various areas is desireable but not mandatory. As for myself I did not know about that either.

i didn't found any axp chip in my device, but only a controller, it's very small and that's all i found. Is it ok to dump the boot.img from the android (i have usb to usb cable)

To be honest, I'm shocked that I need to provide evidence. I assumed this was common knowledge — at the very least among the forum moderators — and that we'd be discussing how it's even possible for the recommended package to behave this way. How to reproduce it? Just implement "mode: ap" in netplan config and check your iptables chains.

We appreciate idea, but we have to look at the health of the whole ecosystem. Our build framework deals with many boards and non-standard low-level components (e.g., U-Boot), and right now it builds reliably only on Ubuntu Jammy. Even Noble isn’t fully compatible yet; adding Debian (unofficially, to some degree, it already works for many years) at this stage would likely cause regressions. As Ubuntu is more present in embedded world, making Debian recommended would costs a lot more from budget we don't have while bringing nothing in return. Exactly. There are many issues in FOSS and there is little we can do. We didn't develop any of those tools - we provide them. Networking stack is an important part, it has its own diversity and this should be in users domain. I think our logic for providing images is a good compromise - we provide Debian and Ubuntu images, we provide them once with systemd-networkd (minimal) and the rest with NetworkManager. Now to keep some consistency and make it simple for non experts, using NetPlan as a central config point also makes sense - for most of use cases and most of users. Those who needs special handling of net stack, its easy to replace them with something else.