Beta Asuswrt-Merlin 3006.102.7 Beta is now available

[mistermoonlight1]

Deeper analysis (main dhcp lan bug with guess wifi and trunk lan port)...

I have also found than once i disable the guess network at the end of post #99 (which repair the main dhcp problem), then reenable it, and assigned a trunk again to the 2.5gbps lan port (same i did in post #99 the 1st time), main dhcp is now working!!!

When main dhcp is working with the guess wifi active, i can see in the syslog something like attached "working-dnsmasq.txt" (oups, it seems i cannot attache txt file!). We can see that there is no more than 2 successive readings of the etc-host file by dnsmasq instance.

And when the main dhcp is broken, we can see something like "buggy-dnsmasq.txt" (i was not enable to attached it), with many successive reading (7 successive readings!) of etc-host file reading (dnsmasq crashed?), the number of successive reading is not fix, and can be greater than what i have seen.

About the nvram buggy left entry...

I made a comparaison between a dump of nvram when main dhcp is working with guess wifi enable and trunk configured on lan port and when it is not with the same trunk configuration on 2.5gbps (eth5 port) (it should be the same, but it is not).

a)buggy situation (with trunk enable):
lan_ifnames=eth1 eth2 eth3 eth4 eth5 eth6 eth7
vlan_trunk_rl=
vlan_trunklist=
br0_ifname=br0
br0_ifnames=
br1_ifname=br52
br1_ifnames=wl0.1 eth1.52 eth2.52 eth3.52 eth4.52 eth5.52 eth6.52 eth7.52

b)working situation (with trunk enable):
lan_ifnames=eth1 eth2 eth3 eth4 eth6 eth7
vlan_trunk_rl=<5>52
vlan_trunklist=<xx:xx:xx:xx:xx:xx>L5#all
br0_ifname=br0
br0_ifnames=
br1_ifname=br52
br1_ifnames=wl0.1 eth1.52 eth2.52 eth3.52 eth4.52 eth5.52 eth6.52 eth7.52

As we can see between a) and b), both configuration when doing "brctl show" shows exactly the same bridges definitions for br0 and br52, but the trunk definitions were not made correctly in the buggy a) version and the lan_ifnames neither.

I have also compare the nvram definitions once i am in situation a) and just disable the guess wifi definition, which also repairs the main dhcp problem.

c)working situation (after disable the trunk definition and also disable the guess wifi definition, which also repair main dhcp):
lan_ifnames=eth1 eth2 eth3 eth4 eth5 eth6 eth7
vlan_trunk_rl=
vlan_trunklist=
br0_ifname=br0
br0_ifnames=eth1 eth2 eth3 eth4 eth5
br1_ifname=br52
br1_ifnames=wl0.1 eth1.52 eth2.52 eth3.52 eth4.52 eth5.52 eth6.52 eth7.52

so if we compare a) and c), we can see we have a normal br0 definition without any trunking definitions...

 

[JarleH]

How does the GT-BE19000AI work with Merlin, when it comes to all the extra AI features (like Docker etc)? Does Merlin just run the standard Asus GUI/features untouched?

 

[bennor]

2- I configured in the vlan section the 2.5gbps port to be a trunk port with allow all tagging option. Bang. No more main dhcp will work from that point!

The switching 2.5GB port to VLAN is something I don't think you mentioned in your initial post #97 (unless I missed it). For more context, how is your Dual WAN (see WAN > Dual WAN) configured? Is Enable Dual WAN set to off and is 1GB WAN selected as Primary WAN?
For more context, is there a device connected to the 2.5GB port? If so what is that device?
And to confirm, is the window machine with DHCP server mentioned in your prior post connected to the 1GB WAN port
.

 

[mistermoonlight1]

The switching 2.5GB port to VLAN is something I don't think you mentioned in your initial post #97 (unless I missed it). For more context, how is your Dual WAN (see WAN > Dual WAN) configured? Is Enable Dual WAN set to off and is 1GB WAN selected as Primary WAN?
For more context, is there a device connected to the 2.5GB port? If so what is that device?
And to confirm, is the window machine with DHCP server mentioned in your prior post connected to the 1GB WAN port
.

No dual wan, and wan is 1gb port. Actually, there is no device connected to the 2.5gbps lan port. Yes the window dhcp server is connected to the router wan 1gb port port to simulate wan server (but i can remove it and it changes nothing at all).

I have also discovered something more: i don't have to remove the trunk port definition and disable the wifi guess to repare the problem, but after creating the lan trunk on 2.5gbps, i just have to disable the wifi guess and reenable it and it repairs everything. It is like the trunk lan port definition is made in wrong order (should be done before the guess wifi? i did not tried it yet)...

 

[mistermoonlight1]

Conclusion about main ethernet dhcp bug and customized guess wifi / vlan 2.5gbps trunk port creation (102.7_beta1, was there also in 102.6)

I put it here in summary because this problem made me lost several hours of testing, in case it could help someone else...

wan port on router is 1gbps (no dual wan), there is a dhcp client on router eth1 (which would get into problem)

Situation that does not work:

a) create a customized wifi 2.4g guess network with dhcp and no sharing of subnet with main lan (no ap isolation neither)
-create the wifi guess 1st
-create the vlan trunk port on the 2.5gbps lan eth5 (with all tag setting) next

main ethernet dhcp is broken on eth1 lan port after this (window dhcp client eth1 gets a dhcp timeout error)

rebooting or power off the router won't solve this issue has it appears nvram was not configured correctly (as i have shown in previous post)

workaround: disable the wifi guess that was created before creating the vlan trunk and reenable it (it repair the nvram entries at least). Main dhcp ethernet starts to work again on eth1.

Situation that does work:

b) create a customized wifi 2.4g guess network with dhcp and no sharing of subnet with main lan (no ap isolation neither)
-create the vlan trunk port on the 2.5gbps lan eth5 (with all tag setting) 1st
-create the wifi guess next

main ethernet dhcp on eth1 is working correctly from this sequence

N.B. when testing sequence a) or b), i made it from the same backup config restoration in both case (as the problems seem to deal with nvram entries creation)

So it looks like a bug, and order of doing things is very important but maybe i just didn't catch the correct instructions on how to do it...