Setup I'm trying to create would consist of lets say 5 devices, all connected to each other over wireless. At any point, you would be able to connect to any of those APs and ping any device in that network. Each AP would have their own DHCP server aswell.
To make it more interesting, have it all dynamic, ie any of those devices might drop off or a new one might be added.
A, E - clients.
B, C, D - APs and clients
WLAN1 - AP interface
WLAN0 - client interface
A(WLAN0) --- B(WLAN0,WLAN1) --- C(WLAN0,WLAN1) --- D(WLAN0,WLAN1) --- E(WLAN0)
Any recommondations what would be proper way to have them connected.
Wifi driver is rtl8723ds, bridging interfaces doesn't seem to be working.
Having a different subnet for each AP (device starts as client, scans network, chooses a subnet not in use before bring its AP up) - this seemed promising but, routing is turning into a nightmare..
Update: To add more details and clarify a few things.
Only have wireless interfaces available. WLAN1, WLAN0
An external device should be able to connect to an AP (or somehow over wifi), to see all devices in that network and send UDP packets to any of those devices.
Did play around with babeld ad-hoc/mesh protocol, but... Ran into quite a few issues though, had WLAN0 for babeld and WLAN1 for AP, so that an external device(eg smartphone) can talk to mesh. I was using hostapd for AP configuration.
Issues came when AP was brought up - couldn't see any devices any more, ie the mesh was gone. Even needed to restart babeld on some random devices.
Never managed to get DHCP to work for mesh nodes. Maybe because devices will be brought up in random order and the whole network will be brought up/down quite often. No static nodes..
Did run some random tests, strange instabilites.. eg: left mesh running for the night and in the morning devices couldn't see each other anymore.
Update2: More details what is the end goal here.
Been stressing with this for some time now and think I've left out a few too many key details trying to explain the purpose of all this. Maybe there is a better approach.
Collection of small embedded devices, relatively close range, all connected to each other.
Only connection option is WiFi.
Some other WiFi enabled device(eg smartphone) must be able to connect to one device to send custom UDP data/identifying packets to all devices. Most logical solution seemed something like a button is pressed on one of those devices, which brings up an AP.
Nothing will be static, number of devices will change.
Babeld kinda put me off the mesh idea, but maybe batman is more promising.
There isn't many more alternatives, is there..?
Connecting APs, clients, APs... and all that routing. More I look into it, worse it gets.
batman with rtl8723ds driver - haven't been able to get module working. Keep getting Segmentation Fault, when trying to load the module.
Running into dead end once again..