Hi Jesus,
To my best knowledge, access-points are usually transparent from direct
end clients. They do not change hardware address of clients going to AP
or any machines behind it.
In my experience, hardware access points doing just AP transparent
bridge are not problematic. Directly connected de
On Sat, May 15, 2021 at 12:38:16PM +0100, Jesus M Diaz wrote:
> Hello,
Hi,
> I have a 'TP-Link One-Mesh' system at home formed by the main router and
> three satellite access-points. It works really well making a good coverage
> over the house with smooth change from one AP to the other, but it
Hi Jesus and dnsmasq-discuss,
> ... the AP change the client mac-address with a combination of the three
> last duplas from the own AP mac-addr and the last three ones from the
client itself
I'd be very interested to know which IETF/RFC this behaviour is specified in
before I embark on using mesh
Hello,
I am trying to set different ranges in my dnsmasq configuration, to be used
based on tags. I have a series of dhcp-host entries, matching by
mac-address, and setting host-name and tag in most cases, and static lease
in others:
dhcp-host=set:iot,a1:b1:c1:d1:e1:f1,hostname1
> ...
> dhcp-host
Hello,
I have a 'TP-Link One-Mesh' system at home formed by the main router and
three satellite access-points. It works really well making a good coverage
over the house with smooth change from one AP to the other, but it has a
caveat: for DHCP requests, the AP change the client mac-address with a
