starred/ZTE-MF286D
1
0
Fork 0
mirror of https://github.com/4IceG/ZTE-MF286D.git synced 2026-04-27 03:35:51 +03:00
Code Issues 7 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #10] Communication between lan switch ports LAN2 LAN3 LAN4 is inconsistent #8

New issue
Open
opened 2026-03-13 14:13:49 +03:00 by kerem · 3 comments
kerem commented 2026-03-13 14:13:49 +03:00
Owner
Copy link

Originally created by @gericho on GitHub (Jan 13, 2024).
Original GitHub issue: https://github.com/4IceG/ZTE-MF286D/issues/10

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
Originally created by @gericho on GitHub (Jan 13, 2024). Original GitHub issue: https://github.com/4IceG/ZTE-MF286D/issues/10 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 ```
kerem commented 2026-03-13 14:13:55 +03:00
Author
Owner
Copy link

@4IceG commented on GitHub (Jan 14, 2024):

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.

<!-- gh-comment-id:1890955128 --> @4IceG commented on GitHub (Jan 14, 2024): 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.
kerem commented 2026-03-13 14:14:00 +03:00
Author
Owner
Copy link

@gericho commented on GitHub (Jan 14, 2024):

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!

<!-- gh-comment-id:1891007864 --> @gericho commented on GitHub (Jan 14, 2024): Unfortunately, I had no time to wait for the latest release so I put the [23.05](https://openwrt.org/toh/zte/mf286d) 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!
kerem commented 2026-03-13 14:14:05 +03:00
Author
Owner
Copy link

@gericho commented on GitHub (Jan 21, 2024):

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

<!-- gh-comment-id:1902614739 --> @gericho commented on GitHub (Jan 21, 2024): Using the last sysupgrade snapshot just released here with 23.05.2 initramfs openwrt master, "seems" to solve the issue.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
r27842-3407269ba5
r31617-677c5c3b0d
r26815-b4069fad02
r23741-497012ab4e
r25826-5713032fd4
r24396-09b7e1955c
r23479-f24c9b9d86
r24564-78d259e7d2-V2
r24786-38bec08e87
r24806-735efbfb7c
r24878-09bc806229
r25115-7181eb9f81
r24099-e66eed033f
r24564-78d259e7d2
r23175-446178dc36
r22702-cf8d861978
r22711-4fa9ec125a
r22637-70000ab509
r22547-21d02e598a
r22128-9837f81bae
r22257-166ab6f90e
r22325-00b40ef00d
r21861-5dee596501
r21569-9b6dd57a33
r21703-4965cbd259
r21584-b2bfea481e
r21335-e410833bdd
r21523-4609228432
r21112-eb456aedfe
r21118-f4849c0ab7
r21087-288b36c2ea
r20877-7d6032f310
r20893-ffd29a55c3
r21020-e629ced778
r20799-e937663025
r20675-9338c09ecb
r20374-a434795809
r20374-a434795809-2
r20462-be555b9dd8
r20351-60738feded
r20337-a66f843971
r20297-5238a87c20
r20265-e6e4f97999
r20260-1bfe42beb4
r19575-506432a783_20220727
r20230-7df6795d4c
r19575-506432a783_20220725
r19575-506432a783
r20146-bc43ad88ed
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ZTE-MF286D#8
No description provided.