Batman advanced

Hi all,
I recently started using B.A.T.M.A.N Advanced on 23.05.2. I set up the bat0 batman device and bat interface (batmesh) using bat0 and everything seemed to work fine.

However, suddenly and out of the blue, I am now getting
Error - interface does not exist

> Tue Jan  9 20:53:01 2024 daemon.notice netifd: Interface 'batmesh' is setting up now
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842): Error - interface does not exist:
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": true, "keep": false, "interface": "batmesh" } (Invalid argument)
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842): Usage: ubus [<options>] <command> [arguments...]
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842): Options:
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842):  -s <socket>:            Set the unix domain socket to connect to
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842):  -t <timeout>:           Set the timeout (in seconds) for a command to complete
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842):  -S:                     Use simplified output (for scripts)
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842):  -v:                     More verbose output
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842):  -m <type>:              (for monitor): include a specific message type
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842):                  (can be used more than once)
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842):  -M <r|t>                (for monitor): only capture received or transmitted traffic
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842):
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842):  - list [<path>]                 List objects
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842):  - call <path> <method> [<message>]      Call an object method
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842):  - subscribe <path> [<path>...]  Subscribe to object(s) notifications
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842):  - listen [<path>...]                    Listen for events
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842):  - send <type> [<message>]               Send an event
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842):  - wait_for <object> [<object>...]       Wait for multiple objects to appear on ubus
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842):  - monitor                               Monitor ubus traffic
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6842):
Tue Jan  9 20:53:01 2024 daemon.notice netifd: batmesh (6876): Error - interface does not exist:
Tue Jan  9 20:53:01 2024 daemon.notice netifd: Interface 'batmesh' is now down

What's gone wrong?

Did you tried to restart wifi or the aps itself? :speak_no_evil:

I have. The logread quote above is after doing that.