2115

I've adopted official MTK driver to current 6.6 kernel ('filogic-2024-10-15') - you can use it.
Meanwhile @Ansuel is creating patchwork to official kernel with all requested changes and improvements. So looking for future we assume that patchwork will be merged into official kernel. In this case an8855 will be officially supported by kernel and by openwrt automatically.

2116

I understand that I can use what already works.
I can't understand why this is not used for official addition to the core = openWrt. :thinking:

2117

man... all this negative feedback... wtf is wrong lately with opensource o.O

2 Likes
2118

OK!
I really don't understand, maybe not yet... But I'll try.))))

2119

If something works doesn't mean it works good or it will last.
Nobody is stupid enough to reinvent the wheel just for the sake of it. The version from SDK is in a not acceptable state and needs changes.

Such changes might cause some bug that will be fixed with the help of the community.
The new driver will for sure receive more support than the current one in the SDK.

It's this easy.
To make it more understandable it's like saying.
I have this old car from 1990. Engine starts and tire moves. Better not change it.
(and ignore the fact that probably 90% of the parts are not produced anymore and as soon as a single piece starts to fail, you will have to trash the entire car)

2 Likes
2120

I don't want to offend anyone, including people who are smarter than me.
I just try to understand them as best I can.
Thank you for your time, I'll repay you as much as I can)).

1 Like
2121

@dimfish @Ansuel Once again, thank you guys for your hard work.

I did one more test with wan. Maybe it would help to solve this mystery. Set dhcp to wan, run dhcp server and tcpdump. Looks like there is communication and even IP is returned from dhcp server but openwrt does not show any received packets and obtained IP.

Config, no RX on dhcp_wan

dhcp_wan
dhcp_wan1449×538 92.3 KB

Communication router <-> dhcp server

dhcp_tcpdump
dhcp_tcpdump1192×1405 340 KB

1 Like
2122

Guys please try new an8855 build:

2 Likes
2123

i should have found the bug

1 Like
2124

Yep, I've found and fixed typos - see PR

1 Like
2125

mhhh nope it's not that but I will check...

1 Like
2126

but yes those regs are also correct thanks for noticing them!

2 Likes
2127

Ok yes i repro your bug (the broken wan port) and can confirm the bug I found was the culprit :smiley:

Now preparing to send v4 upstream so @dimfish can update the pr.

3 Likes
2128

New v4 build is here

2 Likes
2129

@dimfish @Ansuel Goog job guys :clap:

Dhcp works on each device/interface.
dhcp_wan_081124

Do you need anything to be checked?

4 Likes
2130

Nice! Thanx for testing

2 Likes
2131

It would be great to test vlans (on 23.05 there were problems)

1 Like
2132
  1. Add Winbond support.
  2. Add Foresee support.
  3. Add AN8855 support
  4. Add support - soft brick fix code after 7 reboots.

1,3 can be considered solved, 2, 4 remain.

2133

Not sure if this is a good vlan configuration but it works on @dimfish relase 15-10-2024, unfortunately it does not work for 08-11-2024.

EDIT:
tcpdump shows

tcpdump: unsupported DSA tag: mtk

VLAN config

config device
	option type '8021q'
	option ifname 'lan2'
	option vid '20'
	option name 'lan2.20'

config device
	option type '8021q'
	option ifname 'lan3'
	option vid '30'
	option name 'lan3.30'

config device
	option type '8021q'
	option ifname 'lan4'
	option vid '40'
	option name 'lan4.40'

config interface 'vlan20'
	option proto 'static'
	option device 'lan2.20'
	option ipaddr '192.168.20.2'
	option netmask '255.255.255.0'

config interface 'vlan30'
	option proto 'static'
	option device 'lan3.30'
	option ipaddr '192.168.30.3'
	option netmask '255.255.255.0'

config interface 'vlan40'
	option proto 'static'
	option device 'lan4.40'
	option ipaddr '192.168.40.4'
	option netmask '255.255.255.0'

Version 08-11-2024

vln40
vln401056×154 50.7 KB

Version 15-10-2024 (web connected via vlan40)

vlan_40_151024
vlan_40_151024564×526 49.9 KB

2134

Could u try creating vlans using the bridge vlan filtering option? My devices are running in prod i cant test it.

Example config:

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'lan2'
        list ports 'lan3'
        list ports 'lan4'

config interface 'lan'
        option device 'br-lan.99'
        option proto 'static'
        option ipaddr '192.168.2.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config bridge-vlan
        option device 'br-lan'
        option vlan '3'
        list ports 'lan2:t'

config bridge-vlan
        option device 'br-lan'
        option vlan '4'
        list ports 'lan2:t'

config bridge-vlan
        option device 'br-lan'
        option vlan '99'
        list ports 'lan2:t'
        list ports 'lan3:u*'
        list ports 'lan4:u*'

config interface 'iot'
        option proto 'static'
        option device 'br-lan.3'
        option ipaddr '192.168.3.1'
        option netmask '255.255.255.0'

config interface 'guest'
        option proto 'static'
        option device 'br-lan.4'
        option ipaddr '192.168.4.1'
        option netmask '255.255.255.0'