Fantastic! - Thanks again for reading and patching!
Later on will check if LANs 2-3 are in the correct order also what i should of checked.
There is also another issue for default Switch on the FB 750 If i do
swconfig dev switch0 show
VLAN 1:
vid: 1
ports: 0t 1t 2t 3t 4t
VLAN 2:
vid: 2
ports: 0t 5
Since is a DSL router and dos not have a WAN port on ports 5, Should this be corrected as just VLAN 1
VLAN 1:
vid: 1
ports: 0t 1t 2t 3t 4t
Hello!
MT7621's Hardware Flow Offloading combined with the VLAN filtering feature works on 19.07 (very low CPU usage) but it does not on 21.02 (huge CPU usage).
I'm afraid it won't work for you with the 21.02 release, you'll need to wait for the next one, based on kernel 5.10 (or newer):
[12:06] <nbd> right. that's not supported in the 5.4 code
[12:06] <nbd> only in the 5.10 kernel
Did you mean 7530? If so, I don't know where does that port 5 come from.
If you look at 02_network, you'll see:
avm,fritzbox-7530)
ucidef_add_switch "switch0" \
"0u@eth0" "1:lan" "2:lan" "3:lan" "4:lan"
;;
(there isn't anything like 5:wan).
FB 7530 sorry @rmilecki
Hmmm... That's very strange why swconfig shows VLANs 1 and 2 at default via SSH however VLAN 1 shows in Network > Switch under Luci.just how 02_network looks like!
Now another issue i found is that deleting VLANs swconfig seems to think i have this setup.
root@FB750:~# swconfig dev switch0 show
VLAN 1:
vid: 1
ports: 0t 1t 2t 3t 4t
VLAN 2:
vid: 2
ports: 0t 5
VLAN 42:
vid: 42
ports: 0t 2 3 4
VLAN 92:
vid: 92
ports: 0t 1
however only setup i have is 42 and 92
VLAN 42 - LAN
VLAN 92 - WAN via port 4 but afther the patch i will be port 1)
On the Wiki, Someone mentioned that with this SoC, VLAN IDs 1 and 2 are treated specially by the hardware driver, Hints the 42 and 92.
/etc/config/network
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '42'
option vid '42'
option description 'LAN'
option ports '0t 2 3 4'
config switch_vlan
option device 'switch0'
option vlan '92'
option ports '0t 1'
option vid '92'
option description 'WAN'
Hmm- what setting? LAN -> DHCP -> General?
I just set 5m for my LAN, joined my iPhone, and status page shows it counting down:
0h 3m 44s
I'm running not rc2, but OpenWrt SNAPSHOT r16380-3a6b187e03 / LuCI Master git-21.088.74150-ba4e214 so master is OK.
Can anyone else confirm?
Ouch. 
Will a point release jump to >= 5.10?
OpenWrt 21.02.0-rc2 r16122-c2139eef27
Tested on 3 different routers:
Each time at least twice on 19.07.7, then 21.02.0-rc2
Case 1: lease time 12h
Result 1:
Case 2: only change: lease time = 10h:
Result 2: It starts to loose leases on each client once the actual lease time is over.
I forced a ipconfig/renew6 on hosts 'station10' and 'GL503VD' to illustrate that, the leases disappeared from the list (and of course the hosts lost Stateful/reserved addresses):
station10 and GL503VD are not there anymore:
if I reset the value to 12h the hosts are able again to get the leases:
Sorry, I don't understand this sentence
If you mean whether or not during the 21.02 cycle we will ever update the kernel to >= 5.10 the answer is no. Such kernel updates are usually only done on master way before branching off a stable.
Before you save the 10h change, what does LuCI say above when you click on unsaved changes?
Only one row? Or does something else slip in?
Try also via command line (SSH):
uci set dhcp.lan.leasetime='5m'
uci commit dhcp
See if it has the same effect.
Are you sure those are DHCP assigned leases? And not SLAAC?
How is the IPv6 Settings Tab set, esp for
DHCPv6-Mode
DHCPv6-Service
NDP-Proxy
I will test what you just asked me in one minute
but before, I just want to tell that it also breaks IPV6-PD to downstream routers, the downstream router is a Fritz!box4040 running 19.07.7 r11306-c4a6851c72:
Were I an owner of 7621 - I'd skip 21.02 based on this.... perhaps just stick with master.
Via SSh:
on the downstream router Before the commands :
After => no change at all, on any host neither on the downstream router, I still have 12h leases after a /renew6 and yes I'm sure I am static:
But if I restart the LAN interface then I loose the leases (on the hosts and PD on the downstream router)
My config:
config dnsmasq
option domainneeded '1'
option localise_queries '1'
option rebind_protection '1'
option rebind_localhost '1'
option local '/xxx.local/'
option domain 'xxx.local'
option expandhosts '1'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
option resolvfile '/tmp/resolv.conf.auto'
option localservice '1'
list server '192.168.0.254'
list server '1.1.1.1'
option logqueries '1'
option confdir '/tmp/dnsmasq.d'
config dhcp 'lan'
option interface 'lan'
option ra 'server'
option dhcpv6 'server'
option ra_management '1'
option start '120'
option limit '50'
option leasetime '5m'
config dhcp 'wan'
option interface 'wan'
option ignore '1'
config odhcpd 'odhcpd'
option maindhcp '0'
option leasefile '/tmp/hosts/odhcpd'
option leasetrigger '/usr/sbin/odhcpd-update'
option loglevel '4'
A question, Isn't this parameter option leasetime supposed to be used only by DHCPv4 (dnsmasq) ???
Do you see anything in kernel log when those devices try for a DHCPv6?
Cannot say authoritatively. Probably should affect only that.
Anyway, I observe the same thing: my DHCPv6 clients seem to disappear from LuCI DHCPv6 status if lease-time is not 12h...
Does it help to set
ra_useleasetime 1 also?
I tried it, and my devices at least come back with 12h leases, even if leasetime is set to 9h or 50m.
Wireshark shows identical DHCPv6 Confirm/Reply for 12h and 50m with ra_useleasetime 1 and with ra_useleasetime 0 on my macbook.
Thx for you tests, still with your snapshost build ?
I will test that tomorrow, 2h20 A.M here.
For me leases disappears from Luci also, but worst, clients loose their fixed IP (just have to wait for the lease expiration ... or do a renew or a WAN6 interface restart on downstream routers)
Sorry, no. Same behaviour for me:
Note: 19.07.7 for downstream router, will try with my another spare running 21.02.0-rc2
vevere
ipheth works on today's snapshot
kernel - 5.4.124
libusbmuxd - 2.0.2-1
usbmuxd - 1.1.1-1
