DNS domain name servers are always requested from the server but must be explicitly "allowed" by set systems name-servers-dhcp

Running Docker on 1.3 rolling works, but there is no integration with the docker bridge interfaces and docker iptables rules obviously.
My goal was to run Traefik and Pihole and it works so far.
https://gist.github.com/Cremator/183c1a4d24e7812f94ec4bd41f7718b3

https://marc.info/?l=dhcp-hackers&m=128755776831463 describes the solution.
Setting ClientName, ClientIp, ClientMac, ClientDomain on release and expire fails, and there's no need for that since they are already known.
Simply removing all "set" commands in the release and expire section fixes this bug and restores the desired behaviour that i.e. the leases are removed from /etc/hosts.

I just saw the patch above for how to fix this and yes, with that line changed to sudo it now works correctly.
Thanks!

I have adjust the logic which now sets the interface MAC address before any other parameter. Using the OSI model this makes sense as the MAC layer is below IP.

PR https://github.com/vyos/vyos-1x/pull/614
Add the ability to use policy local-route

Hi there,

Let the responsible person of T2859 take care of it. I have not been able to see the problem from the information you provided for the time being. If you are familiar with python and linux, you can consider troubleshooting by yourself to try to find the problem. If not, just ask Maintenance personnel reproduce the fault

@c-po I have changed the PR to prohibit WLAN ports from joining VLAN-aware bridge ports

I can now again bridge the WIFI interface to br0, please resolve the outstanding commit message changes and then it feels good to me! Thanks

In T3067#80025, @jack9603301 wrote:

# Bridge port handling of wireless interfaces is done by hostapd.
        if 'wlan' in interface:
            return

Why can't wlan be completed in bridge.py?

Propose to use that format

Contains 2 patch submissions

This patch changes the settings and does not modify the vlan filter settings when VLAN awareness is not set, but the root cause of different problems is that the following code does not set the wireless port to the bridge normally:

Strange, the problem seems to be that the interface has not been added to the bridge. I may submit a patch about VLAN awareness to refuse to operate the vlan filter setting without enabling VLAN awareness, but I am not sure whether it has any Relationship, manual operation is normal:

Whether the VLAN aware bridge is activated?

@jack9603301 Below the desired information:

Jool can handle 2 times as many packets.
https://link.springer.com/article/10.1007/s11235-020-00681-x

Duplicate T2859

Please execute and analyze the following command to return the result, and carry out fault exploration, if possible, please output the result

Sorry, I have forgotten to copy them.
the error does not occur with every query (nor as a supplement)

PR https://github.com/vyos/vyos-1x/pull/612
Add IS-IS routing.

Is there no NAT policy?

I'm curious about how to do ERSPAN?

Why not use ERSPAN?

In the example above you only included the header, could you extend the examples with example information you want to display there?

Resolved as informed by @tuxnet

If you do not change show int, you can output the specific information of vlan id in the command show interfaces bridge vlan

Ungortunately this is a -1 from me.

Possible reason - ipset should be converted to nft list set

This will be resolved / migrated away in T3048.

We have a basic implementation available. Additional changes should be submitted via feature requests.

VyOS 1.2 adds a random link-local address on tunnel interfaces by default.

Now there is a new plan, please see T3071

Now there is a new plan, please see T3071

@runar The latest image already supports VLAN aware bridge, so this task list can be closed