Hi,
the size is increased by few bytes only. The 64k is between tcpdump mini 4.9.3
and 4.99.1.
The output contains two new values. Adblock must be update too to generate
reports:
diff --git a/net/adblock/files/adblock.sh b/net/adblock/files/adblock.sh
index 0c6efc648..0e1b5154a 100755
---
On 8.09.2022 10:54, Thibaut wrote:
Hi,
Le 8 sept. 2022 à 08:49, Arınç ÜNAL a écrit :
On 8.09.2022 00:12, Jo-Philipp Wich wrote:
[...]
Anyhow, so while I agree that:
Interfaces section should be called Networks.
Devices section should be called Interfaces.
... it will directly contradict
From: Baptiste Jonglez
ULA IPv6 prefixes (Unique Local Addresses, RFC 4193) are not routable on
the Internet. As such, they have very limited use, and enabling them by
default causes more problems than it solves:
- if an OpenWrt device already has external IPv6 connectivity with
globally
Hi,
> [...]
> Meanwhile I wonder if a few specific cases wouldn't need to be better
> addressed. For instance ppp or wwan create extra « Interfaces » (in current
> Luci lingo), some having the related protocol - PPPoE/NCM, some having
> protocol « Virtual Dynamic Interface » (for ipv4/ipv6) -
On 8.09.2022 00:12, Jo-Philipp Wich wrote:
Hi,
I wrote this mostly because the LuCI interface itself makes a distinction
between the "Devices" tab and the "Interfaces" tab. But maybe this isn't the
best way to describe what goes there.
I agree that there are inconsistencies in LuCI. The only
Commit dc9cc0d3e2a1 ("realtek: add QoS and rate control") replaced a
16 bit reserved field in the RTL83xx packet header with the initial
cpu_tag word, shifting the real cpu_tag fields by one. Adjusting for
this new shift was partially forgotten in the new RX tag decoders.
This caused the switch
> Baptiste Jonglez writes:
> - there have been various bug reports [1, 2, 3] in 19.07 and 21.02
> where ULA addresses basically break global IPv6 connectivity. These
> bugs have not been solved in several years, indicating a probable lack
> of interest for ULA from the
One of the first things I do when I bring up a new OpenWrt box is to
disable ULA to the LAN as it has not usage in most scenarios I think.
I basically use the IPv6 connectivity to receive a global prefix
delegated from my ISP, install it on the LAN and bring global
connectivity to devices
> Baptiste Jonglez writes:
> ULA IPv6 prefixes (Unique Local Addresses, RFC 4193) are not routable
> on the Internet. As such, they have very limited use, and enabling
> them by default causes more problems than it solves:
> - if an OpenWrt device already has external IPv6
On 8.09.2022 02:54, Florian Fainelli wrote:
On 9/7/2022 3:00 PM, Sebastian Moeller wrote:
Hi Jo,
I was under the impression* that bridge-vlan filtering is something
that can be relegated to the switch hardware, while creating a bridge
between VLAN interfaces happens in software. Is that
On Thu, 2022-09-08 at 22:23 +0200, Bjørn Mork wrote:
> Sander Vanheule writes:
>
> > > Based-on-fix-by: Jan Hoffmann
> >
> > checkpatch.pl complains about this tag:
> > WARNING: Non-standard signature: Based-on-fix-by:
>
> Yes, I noticed and didn't care ;-)
Just as I thought ;)
>
> > Mind
Hey Luiz,
On 8.09.2022 06:28, Luiz Angelo Daros de Luca wrote:
- Bridge device "br-vlan10" containing "lan1.10 lan2.10 lan3.10"
- VLAN filtering disabled
Bridging virtual 802.1q interfaces might fail in some scenarios, like
when you use vlan1 or mix tagged with untagged traffic
Sander Vanheule writes:
>> Based-on-fix-by: Jan Hoffmann
>
> checkpatch.pl complains about this tag:
> WARNING: Non-standard signature: Based-on-fix-by:
Yes, I noticed and didn't care ;-)
> Mind if I change it to Suggested-by?
No problem.
Bjørn
On Thu, 2022-09-08 at 19:35 +0200, Bjørn Mork wrote:
> Commit dc9cc0d3e2a1 ("realtek: add QoS and rate control") replaced a
> 16 bit reserved field in the RTL83xx packet header with the initial
> cpu_tag word, shifting the real cpu_tag fields by one. Adjusting for
> this new shift was partially
Hi Bjørn,
On Thu, 2022-09-08 at 19:35 +0200, Bjørn Mork wrote:
> Commit dc9cc0d3e2a1 ("realtek: add QoS and rate control") replaced a
> 16 bit reserved field in the RTL83xx packet header with the initial
> cpu_tag word, shifting the real cpu_tag fields by one. Adjusting for
> this new shift was
Signed-off-by: LiXiong Liu
---
.../patches/100-bridge-vlan-support-untagged.patch | 58 ++
1 file changed, 58 insertions(+)
create mode 100644
package/network/config/netifd/patches/100-bridge-vlan-support-untagged.patch
diff --git
### swconfig & DSA VLAN Configuration Comparison
Doesn't just support Tunnk on lan5,
also need access to 192.168.1.1
so must setting untagged at br-lan
#switch-vlan
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
17 matches
Mail list logo
