Mikrotik wireless connection with ZTE F660 router

Hello,

I’m creating my personal lab where I have

  1. Switch l3
  2. Fortigate 60D
  3. Mikrotik hAP lite
  4. Computer as server NAS (proxmox)

I would like have 3 VLANS (like OFFICE 10.10.10.1/24, DMZ 10.10.20.1/24 and PROD 10.10.30.1) - the VLANS will be create on Fortigate 60D on int1 to int1 on switch l3 (trunk)

Problem exist with connecting to the internet because I don’t have possibility connected main router (ZTE F660) with Mikrotik through LAN cable. I must do it only through wireless.

My main router have address 192.168.1.1

I tried connected wlan1 on mikrotik as station mode with wi-fi ZTE but the connection flapping (although the main router is the next room)

ZTE F660 (192.168.1.1)→ wireless→Mikrotik→Fortigate 60D (where is VLANS,NAT)→Switch l3→ NAS (with vm’s) ,main Computer,Printer

VLAN OFFICE→ Internet and access to DMZ

VLAN DMZ → Only https,http,ping, access to OFFICE and DMZ

VLAN PROD → Separated network (only access to DMZ)

I will be very grateful for any advice :slight_smile:

I can see two different issues:

  1. your wireless connection flapping <- if this is not somehow solved, there is not much point in checking the rest
  2. the "station mode" that is not the correct one if you want multiple devices connected downstream to the hap lite, you can try using "station pseudo-bridge", but still it won't be a "proper" solution[1].

Anyway post your current configuration, instructions here:

[1] short of running an ethernet cable to the router, you could procure a second hap lite, they can often be found used for a few bucks, and with Mikrotik devices on both sides of the wireless link you can use station-bridge mode

1.by flapping we mean this:

As you can see connection to main router (ZTE 192.168.1.1 is ok) but when I’m trying pinging 8.8.8.8 only two packets have been received but rest are timeout or host unreachable2.2026-01-02 16:52:05 by RouterOS 7.20.6

# 2026-01-02 16:52:05 by RouterOS 7.20.6
# software id = 6WAT-D202
#
# model = RB941-2nD
# serial number = removed
/interface bridge
add admin-mac=04:F4:1C:41:65:67 auto-mac=no comment=defconf name=bridge
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa-psk,wpa2-psk comment=\
    defconf disable-pmkid=yes mode=dynamic-keys supplicant-identity=MikroTik
add authentication-types=wpa2-psk mode=dynamic-keys name=zte \
    supplicant-identity=MikroTik
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n disabled=no distance=indoors \
    frequency=2462 security-profile=zte ssid=MIDIKO_18:44:e6:a7:28:bf \
    wireless-protocol=802.11
/ip pool
add name=default-dhcp ranges=192.168.88.10-192.168.88.254
/ip dhcp-server
add address-pool=default-dhcp interface=bridge name=defconf
#error exporting "/system/ntp/key" (timeout)
#interrupted

[1] short of running an ethernet cable to the router, you could procure a second hap lite, they can often be found used for a few bucks, and with Mikrotik devices on both sides of the wireless link you can use station-bridge mode

I'm considering it, but the ZTE F660 is connected directly to the IPS via fiber optic. I don't know how much it will cost to convert it to Ethernet (because the ZTE router is owned by the operator).

Isn't it this device:
https://www.normann-engineering.com/en/products/860/zte-f660/

That ZTEF660 has 4 LAN ports, you connect the second hap lite to one of them and you are ready for a "wireless wire" kind of link.

Your export however is incomplete:

#error exporting "/system/ntp/key" (timeout)
#interrupted

That could be due to something that only happens randomly or some problems in either the firmware or configuration.

Try again, hopefully it was just busy at the moment you tried the /export, the hap lite is a not-so-much-powerful device, and installing 7.20.6 on it is "border-line", making an export when running v7 is usually "stuttering", but it should complete.

The picture you posted tells little about the quality of the wireless link, as a matter of fact, the pinging to 192.168.1.1 seems fine, is the pinging to 8.8.8.8 that is flaky and that could be this (or that) configuration issue.

If I were you I would downgrade it to latest v6 version, but of course this is (highly) debatable.

Form the parts of configuration you posted I cannot understand if the radio is actually set to station (but again in case it should be set to station pseudo-bridge), it looks like an "undefined" mode? (there is no mode set in /interface wireless and no pre-shared keys in /interface wireless security-profile?) :face_with_raised_eyebrow:

Now I understand what you mean – I need to connect to the ZTE with an additional Mikrotik and configure a wireless connection between them. The question is, will this solve the problem? and second hAP lite will be enough (or do I need to invest in a better Mikrotik router)?

Below I sent once again configuration script.


# 2026-01-02 20:26:49 by RouterOS 7.20.6
# software id = 6WAT-D202
#
# model = RB941-2nD
# serial number = HJT0AHET0Y8

/interface bridge
add admin-mac=04:F4:1C:41:65:67 auto-mac=no comment=defconf name=bridge
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa-psk,wpa2-psk comment=\
    defconf disable-pmkid=yes mode=dynamic-keys supplicant-identity=MikroTik
add authentication-types=wpa2-psk mode=dynamic-keys name=zte \
    supplicant-identity=MikroTik
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n disabled=no distance=indoors \
    frequency=2462 security-profile=zte ssid=MIDIKO_18:44:e6:a7:28:bf \
    wireless-protocol=802.11
/ip pool
add name=default-dhcp ranges=192.168.88.10-192.168.88.254
/ip dhcp-server
add address-pool=default-dhcp interface=bridge name=defconf
#error exporting "/routing/id" (timeout)
/interface bridge port
add bridge=bridge comment=defconf interface=ether2
add bridge=bridge comment=defconf interface=ether3
add bridge=bridge comment=defconf interface=pwr-line1
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface detect-internet
set detect-interface-list=all internet-interface-list=all lan-interface-list=\
    all wan-interface-list=all
/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf interface=ether1 list=WAN
/ip address
add address=192.168.88.1/24 comment=defconf interface=bridge network=\
    192.168.88.0
add address=192.168.10.1/24 interface=ether4 network=192.168.10.0
/ip dhcp-client
# Interface not active
add comment=defconf interface=ether1
add default-route-tables=main interface=wlan1
/ip dhcp-server network
add address=192.168.88.0/24 comment=defconf dns-server=192.168.88.1 gateway=\
    192.168.88.1
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=192.168.88.1 comment=defconf name=router.lan type=A
/ip firewall filter
add action=accept chain=input comment=\
    "defconf: accept established,related,untracked" connection-state=\
    established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=\
    invalid
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=input comment=\
    "defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1
add action=drop chain=input comment="defconf: drop all not coming from LAN" \
    in-interface-list=!LAN
add action=accept chain=forward comment="defconf: accept in ipsec policy" \
    ipsec-policy=in,ipsec
add action=accept chain=forward comment="defconf: accept out ipsec policy" \
    ipsec-policy=out,ipsec
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" \
    connection-state=established,related hw-offload=yes
add action=accept chain=forward comment=\
    "defconf: accept established,related, untracked" connection-state=\
    established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" \
    connection-state=invalid
add action=drop chain=forward comment=\
    "defconf: drop all from WAN not DSTNATed" connection-nat-state=!dstnat \
    connection-state=new in-interface-list=WAN
/ip firewall nat
add action=masquerade chain=srcnat comment="defconf: masquerade" \
    ipsec-policy=out,none out-interface-list=WAN
add action=masquerade chain=srcnat log=yes out-interface=wlan1
#error exporting "/ip/ipsec/mode-config" (timeout)
/ip route
add disabled=no distance=1 dst-address=0.0.0.0/0 gateway=192.168.1.4 \
    routing-table=main suppress-hw-offload=no
/ipv6 firewall address-list
add address=::/128 comment="defconf: unspecified address" list=bad_ipv6
add address=::1/128 comment="defconf: lo" list=bad_ipv6
add address=fec0::/10 comment="defconf: site-local" list=bad_ipv6
add address=::ffff:0.0.0.0/96 comment="defconf: ipv4-mapped" list=bad_ipv6
add address=::/96 comment="defconf: ipv4 compat" list=bad_ipv6
add address=100::/64 comment="defconf: discard only " list=bad_ipv6
add address=2001:db8::/32 comment="defconf: documentation" list=bad_ipv6
add address=2001:10::/28 comment="defconf: ORCHID" list=bad_ipv6
add address=3ffe::/16 comment="defconf: 6bone" list=bad_ipv6
/ipv6 firewall filter
add action=accept chain=input comment=\
    "defconf: accept established,related,untracked" connection-state=\
    established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=\
    invalid
add action=accept chain=input comment="defconf: accept ICMPv6" protocol=\
    icmpv6
add action=accept chain=input comment="defconf: accept UDP traceroute" \
    dst-port=33434-33534 protocol=udp
add action=accept chain=input comment=\
    "defconf: accept DHCPv6-Client prefix delegation." dst-port=546 protocol=\
    udp src-address=fe80::/10
add action=accept chain=input comment="defconf: accept IKE" dst-port=500,4500 \
    protocol=udp
add action=accept chain=input comment="defconf: accept ipsec AH" protocol=\
    ipsec-ah
add action=accept chain=input comment="defconf: accept ipsec ESP" protocol=\
    ipsec-esp
add action=accept chain=input comment=\
    "defconf: accept all that matches ipsec policy" ipsec-policy=in,ipsec
add action=drop chain=input comment=\
    "defconf: drop everything else not coming from LAN" in-interface-list=\
    !LAN
add action=fasttrack-connection chain=forward comment="defconf: fasttrack6" \
    connection-state=established,related
add action=accept chain=forward comment=\
    "defconf: accept established,related,untracked" connection-state=\
    established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" \
    connection-state=invalid
add action=drop chain=forward comment=\
    "defconf: drop packets with bad src ipv6" src-address-list=bad_ipv6
add action=drop chain=forward comment=\
    "defconf: drop packets with bad dst ipv6" dst-address-list=bad_ipv6
add action=drop chain=forward comment="defconf: rfc4890 drop hop-limit=1" \
    hop-limit=equal:1 protocol=icmpv6
add action=accept chain=forward comment="defconf: accept ICMPv6" protocol=\
    icmpv6
add action=accept chain=forward comment="defconf: accept HIP" protocol=139
add action=accept chain=forward comment="defconf: accept IKE" dst-port=\
    500,4500 protocol=udp
add action=accept chain=forward comment="defconf: accept ipsec AH" protocol=\
    ipsec-ah
add action=accept chain=forward comment="defconf: accept ipsec ESP" protocol=\
    ipsec-esp
add action=accept chain=forward comment=\
    "defconf: accept all that matches ipsec policy" ipsec-policy=in,ipsec
add action=drop chain=forward comment=\
    "defconf: drop everything else not coming from LAN" in-interface-list=\
    !LAN
/system clock
set time-zone-name=Europe/Warsaw
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN
[spoiler]This text will be blurred[/spoiler]

Please reformat your config.

1 Like

I still don't understand how your wireless connection Is working, but you have a route with gateway 192.168.1.4, if the zte Is the gateway, that should be 192.168.1.1.
But you don't have seemingly any interface with IP address in that range, so that's another mistery, your device seems configured as router, while likely you want a bridge instead.

Post the output of

/ip route print

and

/ip address print

About a "faster" Mikrotik device, you would need two of them, so some money would be needed, a hap lite (or a mAP lite or anyway a "previous generation" one) can usually be found for around or less than 20 € or so.

Here:

I posted a typical configuration for a hap lite setup as station pseudobridge (but for v6 so something will need to be changed) that you might use as an example.

jaclaz you have right, by mistake I set 192.168.1.4 as gateway. I corrected this route:

If I good understand my configuration looks like:

ZTE(192.168.1.1)-(mode:station)->(wlan1 -192.168.1.5)- mikrotik-(ether4-192.168.10.1)->(wan1 - 192.168.10.2) fortigate 60d(int1-VLANS 10,20,30)->(trunk)switch l3->hosts,printers etc.

Currently
Mikrotik pinging 8.8.8.8, 192.168.1.1, 192.168.10.2, 10.10.10.3 (OFFICE)
Firewall pinging 8.8.8.8, 192.168.1.1, 192.168.1.5, 192.168.10.2, 10.10.10.3
Host (10.10.10.3) - pinging 8.8.8.8,192.168.1.5, 192.168.10.1, 10.10.10.1

Thank you for your support jaclaz :slight_smile:

PS:If something else is wrong with my conf please let me know :slight_smile:

Maybe now I see, you are setting the ZTE as 'station" and then you have the hap lite setup as AP (and as router).
Usually the roles are inverted (the AP Is on the side connected to the internet, and the station Is on the side of the clients) but I don't think that this can have any adverse effect.

But the hap lite Is routing the connection.

This implies double NAT and only L3 connectivity, these could be just fine, of course.