Communication between lan switch ports LAN2 LAN3 LAN4 is inconsistent

[gericho]

Hi! Thank you for your firmware! I just installed it, I found the communication between the switch non-WAN ports is inconsistent, eg. Here you see my ping to a local device (can be any on the 192.168.0.0 class), the current pinging PC is connected on the LAN3, and the home switch on the LAN4. I never had this problem with the previous firmware. As I attach a second cable to the ZTE switch it seems to flood the entire network with something bad and all the devices' connections become unstable. There are no other DHCP servers or other gateway/routers present. Thank you for your help.

EDIT: using the pinging PC on ZTE WIFI instead of the cable, pinging the same local LAN4 connected device (one cable only connected to the home switch) it works flawlessly, with no packet loss.

Reply from 192.168.0.100: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.100: bytes=32 time=2809ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.100: bytes=32 time<1ms TTL=64
Reply from 192.168.0.100: bytes=32 time<1ms TTL=64
Reply from 192.168.0.100: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.100: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.100: bytes=32 time<1ms TTL=64
Reply from 192.168.0.100: bytes=32 time<1ms TTL=64
Reply from 192.168.0.100: bytes=32 time<1ms TTL=64
Reply from 192.168.0.100: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.100: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.100: bytes=32 time<1ms TTL=64
Reply from 192.168.0.100: bytes=32 time<1ms TTL=64
Reply from 192.168.0.100: bytes=32 time<1ms TTL=64

[4IceG]

Hi @gericho , I have published a new compilation. If this image still does not work properly, create a topic on the OpenWrt forum to report the error. My images are not modified in any way, so the errors need to be changed generally.

[gericho]

Unfortunately, I had no time to wait for the latest release so I put the 23.05 and installed almost the same packages as your release and it works flawlessly. I do not recommend doing the same to newbies since needed packages as QMI must be installed manually (SCP/SSH) without a proper 4G connection, at least upload and install via SSH the QMI package and configure the modem manually with vi editor in /etc/config/network. I don't like vi at all so also the package nano (and dependencies) was a must.

config interface 'wan'
    option proto 'qmi'
    option device '/dev/cdc-wdm0'
    option auth 'none'
    option pdptype 'ipv4'
    option apn 'your.apn'
    option dhcp '0'

I advise trying the 4IceG release first, or if you want to work a lot, install the 23.05 with a configured WIFI client connection or a cable on LAN2+ port with available internet access, install the package luci-proto-qmi and configure the modem in the WAN interface using LuCI. At that point, the WAN must be up and downloading and configuring the rest of the packages a "breeze".

I reserve the right to try your release as soon as possible and report back to OpenWRT the problem if it still exists on your latest version. Thank you for your reply and your fine work!

[gericho]

Using the last sysupgrade snapshot just released here with 23.05.2 initramfs openwrt master, "seems" to solve the issue.