BE88U Single-Line Three-Use (Dial-up + IPTV + Wired Backhaul) + Mesh + VLAN Switch Problem?
Routing enthusiast• Publish Time:2025-12-9 10:51• Category: Comprehensive classification
•Views：66877• Comments: (
18 )
Questions:
main route, the WAN port is made into three VLAN sub-interfaces:
41-PPPoE (Internet), 43-Bridge (IPTV), and 50-Bridge (LAN),
at the same time, the LAN port is on VLAN50 by default, and the LAN port can broadcast normally when plugged into the IPTV box.
question now is:
41-PPPoE (Internet), 43-Bridge (IPTV), and 50-Bridge (LAN),
at the same time, the LAN port is on VLAN50 by default, and the LAN port can broadcast normally when plugged into the IPTV box.
question now is:
- secondary route has a fast wired handshake but is slow to get the IP, or even can't get it;
- terminal occasionally gets a 169.* or 10.* address, Wi-Fi seems to connect but can't connect to the Internet;
- once VLAN43 is explicitly checked out at the LAN port of the main route, Mesh will collapse.
try to solve:
1. Why can't a mesh be formed once a VLAN43 is set up ASUS Mesh requires that both the "control channel" and the "data channel" are in the same L2 broadcast domain,
and VLAN = isolated broadcast domain.
you set Port 4 to VLAN43 in LAN → IPTV, Port 4 is kicked out of the default VLAN1/50,
secondary route is plugged into this port, and the control packets (UDP 1234/7777/7980, etc.) cannot reach the main route,
"finding node" fails directly.
→ Conclusion: The Mesh node must remain in VLAN50 and must not change the port to VLAN43.
and VLAN = isolated broadcast domain.
you set Port 4 to VLAN43 in LAN → IPTV, Port 4 is kicked out of the default VLAN1/50,
secondary route is plugged into this port, and the control packets (UDP 1234/7777/7980, etc.) cannot reach the main route,
"finding node" fails directly.
→ Conclusion: The Mesh node must remain in VLAN50 and must not change the port to VLAN43.
2. The real reason why the secondary route can't get 192.168.50.x
- you set the
LAN → IPTV → "Enable IPTV" to "Manual" and tick 43 in order to "plug any LAN port into the IPTV box". The side effect of
option is that
the main route will send IGMP/UDP probes every 30 seconds, and the multicast of VLAN43 will flow to all LAN ports,
the CPU of the secondary route will receive these packets first, mistakenly thinking that "the WAN side is connected
", so it delays 10–20 seconds before switching back to STATION mode to DHCP to get the address;
if the VLAN50 broadcast happens to be filtered by the switch at that time, it will time out directly, showing "no network". - the switch to the secondary route line, if the BE88U's 10G Base-T port is plugged in,
it will turn on 802.3az EEE by default, and after negotiating with some Intel I225/I226 network cards, the speed will drop to 100 M
and continue to lose packets, which seems to be "negotiation successful but unable to access the Internet".
3. 30 minutes painless renovation plan (all the following are completed on the main BE88U in the living room, and the secondary route is turned off first)
- turn off "Enable IPTV"
LAN → select the "No" → app → IPTV.
step immediately kicks VLAN43 out of all LAN ports and the mesh control packet is restored. - let the IPTV box go to the "dedicated port" instead of the "arbitrary port"
(1) LAN → Switch Config
set Port 4 (the one that connects the box) to
VID 43, Untag 43, and do not add 1/50 → applications.
(2) WAN → Dual WAN → Select "Special Port 4 = IPTV" → save.
this way, the box can still broadcast numbers, but the other LAN ports can no longer receive VLAN43's multicast garbage. - give the sub-route a "clean" VLAN50 port
in the weak current box switch, set the port to the study to
PVID 50, allowing the VLAN 50/43 to pass through, but not to the port-based VLAN.
this way, the subroute will only receive VLAN50 packets after booting, and will not be interfered with by 43. - turn off 10G EEE (optional but highly recommended)
Adaptive → 10G Base-T → EEE Disable → reboot.
100 Gigabit/Gigabit/10 Gigabit negotiation is completed instantly, and no packet drops will be made. - the secondary route is factory restored → select "Mesh node" → add it with one click in the mobile app. After the
is successful, look at the system information: The IP of the
node should be 192.168.50.x, the backhaul type is "5G-2" or "wired",
the 169.* address will no longer appear.
4. Quick Obstacle Removal Table
| phenomenon | checkpoints |
|---|---|
| secondary route has not been able to get IP | (1) Whether the switch PVID is 50 (2) Is the primary route turned off IPTV |
| terminal gets 192.168.43.x | mistakenly set VLAN43 to DHCP and turn off the IPTV port in the Dual WAN |
| Mesh Node not found | Whether the secondary routeplugged into the VLAN43 port → changed back to VLAN50 |
| 10G Consultation 100M | turn off EEE, change to Category 6 lines, and force 1G to go online first and then upgrade 10G |
5. Summary "IPTV box needs VLAN43, Mesh node needs VLAN50" - don't mix the two into the same port.
turn off the "Enable IPTV" of the main route, throw the box to Port4-VLAN43 separately,
the rest of the LAN ports remain pure VLAN50, and the secondary route instantly takes the address in seconds,
both wired and wireless backhaul can run stably, and the 10,000-gigabit intranet will not slow down again.
turn off the "Enable IPTV" of the main route, throw the box to Port4-VLAN43 separately,
the rest of the LAN ports remain pure VLAN50, and the secondary route instantly takes the address in seconds,
both wired and wireless backhaul can run stably, and the 10,000-gigabit intranet will not slow down again.
Read More
Comment List