Dawn isn't working/doesnt roam devices | BEACON REQUEST failed

Pablo1732 · January 10, 2024, 3:46pm

Hello,
I've been trying to get dawn up and running for a month now. I have already read through several forum posts, the OpenWRT Wiki and the Install.md/Configure.md on GitHub. However, Dawn has not worked properly once so far, the devices decide for themselves when they are roaming not dawn. I've even reset my router and APs and set everything up again.
I am using OpenWRT 23.05.2.

The error "BEACON REQUEST failed" always appears in the console for each of my devices.

(Here is a short excerpt of the log)

Wed Jan 10 16:04:21 2024 daemon.warn dawn: Client / BSSID = ZZ:ZZ:ZZ:ZZ:ZZ:ZZ / YY:YY:YY:YY:YY:YY: BEACON REQUEST failed
Wed Jan 10 16:04:21 2024 daemon.warn dawn: Client / BSSID = ZZ:ZZ:ZZ:ZZ:ZZ:ZZ / YY:YY:YY:YY:YY:YY: BEACON REQUEST failed
Wed Jan 10 16:04:21 2024 daemon.warn dawn: Client / BSSID = XX:XX:XX:XX:XX:XX / YY:YY:YY:YY:YY:YY: BEACON REQUEST failed
Wed Jan 10 16:04:34 2024 daemon.warn dawn: Client / BSSID = ZZ:ZZ:ZZ:ZZ:ZZ:ZZ / YY:YY:YY:YY:YY:YY: BEACON REQUEST failed
Wed Jan 10 16:04:34 2024 daemon.warn dawn: Client / BSSID = ZZ:ZZ:ZZ:ZZ:ZZ:ZZ / YY:YY:YY:YY:YY:YY: BEACON REQUEST failed
Wed Jan 10 16:04:34 2024 daemon.warn dawn: Client / BSSID = XX:XX:XX:XX:XX:XX / YY:YY:YY:YY:YY:YY: BEACON REQUEST failed
Wed Jan 10 16:04:41 2024 daemon.warn dawn: Client / BSSID = ZZ:ZZ:ZZ:ZZ:ZZ:ZZ / YY:YY:YY:YY:YY:YY: BEACON REQUEST failed
Wed Jan 10 16:04:41 2024 daemon.warn dawn: Client / BSSID = XX:XX:XX:XX:XX:XX / YY:YY:YY:YY:YY:YY: BEACON REQUEST failed

I don't know if the "BEACON REQUEST failed" error is really the problem with Dawn not working for me, but that is the only error shown in the log.

My dawn config is pretty much default but I have played around with it a lot and also reset it to default several times, but everything did not work.

(Examples of which pages I have used)

github.com

berlin-open-wireless-lab/DAWN/blob/master/CONFIGURE.md

# Configuring DAWN

## Making Configuration Changes
Edit settings under

    /etc/config/dawn

After changes, restart daemon

    /etc/init.d/dawn restart

## Resetting DAWN's Configuration
The configuration for several key sections (see per section notes below)
can be shared with other DAWN
instances via ubus. This can be used to "reset" the configuration file to
remove any items that are no longer used.  To do this:

    # Backup current config
    cd /etc/config
    mv dawn dawn.old

This file has been truncated. show original

github.com

berlin-open-wireless-lab/DAWN/blob/master/INSTALL.md

# DAWN Installation
This guide should allow you to get DAWN running, and check its basic
behaviour.

## Setting up Routers
DAWN will typically run in a network where one AP is providing core
networking services like DHCP and internet gateway, while other APs are
being used to extend wifi network range.  For example, the "main" AP near
the telecoms provider entry point, and one or more other AP on the other
side of the house, in the garden, etc.  Or several AP distributed about an
office building.

The term "dumb AP" is typically used for the extending APs, meaning that
they don't directly provide those DHCP type services.  If adding APs for
the first time as a part of the plan to make DAWN work then it's important
to have them configured correctly, and you can find a good guide to that
[here](https://gist.github.com/braian87b/bba9da3a7ac23c35b7f1eecafecdd47d).

Once those basics are in place DAWN is installed on each of the APs
("main" and "dumb") so that a full view of the network can be gathered.

This file has been truncated. show original