How to Set STA mode

[horasjey]

Hallo ,
i have 2 ap and set mode ptp,
My 2 access points are connected to sta mode

~ # iw dev ath1 link
Connected to 00:01:23:20:15:f8 (on ath1)
        SSID: 123
        BSS Load:
                 * qbssload_ie_valid: 0
        freq: 5200
        RX: 63068 bytes (1254 packets)
        TX: 113927 bytes (355 packets)
        signal: -4 dBm
        rx bitrate: 600.0 MBit/s
        tx bitrate: 4270.4 MBit/s

        bss flags:      CTS-protection short-slot-time
        dtim period:    1
        beacon int:     100
~ #

but why my sta can't get ip dhcp from master mode,
in master mode there is a log like this

Wed May 29 05:24:39 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 00:01:23:20:14:b0
Wed May 29 05:24:39 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.1.194 00:01:23:20:14:b0
Wed May 29 05:24:42 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 00:01:23:20:14:b0
Wed May 29 05:24:42 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.1.194 00:01:23:20:14:b0
Wed May 29 05:24:45 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 00:01:23:20:14:b0
Wed May 29 05:24:45 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.1.194 00:01:23:20:14:b0
Wed May 29 05:24:48 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 00:01:23:20:14:b0
Wed May 29 05:24:48 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.1.194 00:01:23:20:14:b0
Wed May 29 05:24:51 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 00:01:23:20:14:b0
Wed May 29 05:24:51 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.1.194 00:01:23:20:14:b0
Wed May 29 05:24:54 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 00:01:23:20:14:b0
Wed May 29 05:24:54 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.1.194 00:01:23:20:14:b0
Wed May 29 05:24:58 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 00:01:23:20:14:b0
Wed May 29 05:24:58 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.1.194 00:01:23:20:14:b0
Wed May 29 05:25:04 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 00:01:23:20:14:b0
Wed May 29 05:25:04 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.1.194 00:01:23:20:14:b0
Wed May 29 05:25:04 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 00:01:23:20:14:b0
Wed May 29 05:25:04 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.1.194 00:01:23:20:14:b0
Wed May 29 05:25:07 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 00:01:23:20:14:b0
Wed May 29 05:25:07 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.1.194 00:01:23:20:14:b0

I've tried creating a static IP on the BR-LAN interface on Sta and Master, but I still can't ping communication between devices (1 network).

I have also tested the MLD0 interface for static on the Sta and AP side, but the results are the same, they can't ping each other.

I have turned off the firewall on both sides of the AP, but it doesn't show results,

Please, has anyone experienced this, and what is the solution so that I can use point to point (PTP) mode?

NB :but if I join the AP using a secure phone connection, I get an IP and can ping each other between the cellphone and the AP

[slh]

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

[horasjey]

hello @slh ,
thank's for your answare,
i wil try for it