Configure WIFI v.7.13 [SOLVED]

Ryosaeba · Wed Dec 20, 2023 12:34 am

I updated the mikrotik hap ac lite software to v.7.13 and I lost the WIFI configuration, as everything has changed.
I read the guide but I can't understand how to reconfigure...in the network scan, the interface always remains unknown.
Thanks for the help.

DeDMorozzzz · Wed Dec 20, 2023 6:15 am

Hello you need to netinstall it

mkx · Wed Dec 20, 2023 8:41 am

Since 7.13 you need to have two packages installed: routeros (the main package) and wireless (your device doesn't qualify for the new wifi-qcom-ac package). If wireless package is missing, fetch it from extras archive (available on mikrotik download page), drop it on hAP ac lite and reboot. After rebooting check if package is installed. If not, check log to see what it's got to say about it. It is probable that flash storage is not enough to install the extra package. In this case netinstall is the only way. When netinstalling, it's recommended to wipe the config and after that configure device from factory defaults. By keeping configuration it is possible to also keep any inconsistencies in configuration (which might have led to the lack of free flash space in the first place).

Ryosaeba · Wed Dec 20, 2023 9:36 pm

Thanks for the information, in fact I solved it immediately by installing wireless 7.13 from the extra package, the item appeared again and I was able to configure the WIFI again.

Rabinovitch · Fri Jan 19, 2024 8:02 am

I have C53UiG+5HPaxD2HPaxD with wifi-qcom package.
Regardless of configuration method I can't find at even 2.4 GHz wifi network from this router on any client.

At the moment the configuration is like this:

# 2024-01-19 00:49:56 by RouterOS 7.14beta7
# software id = G1Q0-4165
#
# model = C53UiG+5HPaxD2HPaxD
# serial number = H---------5
/interface bridge
add admin-mac=48:A9:8A:80:75:BF auto-mac=no comment=defconf name=bridge
/interface wifi
set [ find default-name=wifi1 ] channel.band=5ghz-ax .skip-dfs-channels=\
    10min-cac .width=20/40/80mhz configuration.mode=ap .ssid=MikroTik-8075C3 \
    security.authentication-types=wpa2-psk,wpa3-psk .ft=yes .ft-over-ds=yes
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface wifi channel
add band=2ghz-n disabled=no name=2ghz width=20/40mhz
/interface wifi datapath
add bridge=bridge disabled=no interface-list=LAN name=datapath1
/interface wifi security
add authentication-types=wpa2-psk disabled=no name=security
/interface wifi
set [ find default-name=wifi2 ] channel=2ghz channel.skip-dfs-channels=\
    10min-cac configuration.chains=0,1 .country=Russia .mode=ap .ssid=\
    MikroTik-8075C3 .tx-chains=0,1 datapath=datapath1 datapath.bridge=bridge \
    .interface-list=LAN disabled=no security=security \
    security.authentication-types=wpa2-psk .encryption="" .ft=yes \
    .ft-over-ds=yes
/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 lease-time=1d10m name=defconf
/ip smb smb-user
set [ find default=yes ] read-only=yes
/interface bridge port
add bridge=bridge comment=defconf interface=ether3
add bridge=bridge comment=defconf interface=ether4
add bridge=bridge comment=defconf interface=ether5
add bridge=bridge comment=defconf interface=wifi1
add bridge=bridge comment=defconf interface=wifi2
add bridge=bridge interface=ether1
/ip firewall connection tracking
set udp-timeout=10s
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf interface=ether2 list=WAN
/ip address
add address=192.168.88.1/24 comment=defconf interface=bridge network=\
    192.168.88.0
/ip dhcp-client
add comment=defconf interface=ether2
/ip dhcp-server network
add address=192.168.88.0/24 comment=defconf dns-server=8.8.8.8,1.1.1.1 \
    gateway=192.168.88.1
/ip dns
set allow-remote-requests=yes servers=8.8.8.8,1.1.1.1
/ip dns static
add address=192.168.88.1 comment=defconf name=router.lan
/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=ether2 src-address=192.168.88.0/24
/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" 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=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/Moscow
/system note
set show-at-login=no
/system package update
set channel=testing
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN

The strange thing is that the router believes that wifi1 is 5GHz radio capable (sorry, I tried twice to insert the link to image, it is attached)
Please help me...

Fri Jan 19, 2024 9:30 am

hAP AX3 is a an AX device.
Starting from that AX line Mikrotik swapped the labels on devices having 2.4 and 5Ghz radio.
Wifi1 = 5GHz
wifi2 = 2.4Ghz.

So the router is actually correct. Wifi 1 IS your 5GHz radio.
You might be better of to start with default config and work from there to make your changes.

PS best to insert your config in between [code] quotes after sanitizing (remove serial, remove WAN IP, ...).
Most of us are not too happy with external links. Me included. I'm not going to look at it unless available directly in a post.

Rabinovitch · Fri Jan 19, 2024 2:19 pm

No problem, I will post the config into my post right now.
Over the past night, I started configuring the router three times, the last time including creating a default configuration. But so far it has not produced a positive result.

Rabinovitch · Tue Jan 23, 2024 9:26 am

Anyone, please?

Tue Jan 23, 2024 9:32 am

Post says "solved", so what is the question?

DeDMorozzzz · Tue Jan 23, 2024 5:10 pm

So now there is no way to do a distant upgrade in ROS7?
I have remotely upgraded LDF5 and it's wireless interface diaspeared (solved by netinstalling ROS6 latest version)
Do 802.11ad also lose 60Ghz interface?

rextended · Tue Jan 23, 2024 5:16 pm

distant upgrade

No matter the productor of the device, a distant update CAN fail, so upgrade CAN go worse...
Always keep the car engine running... you might leave...

Ask yourself a question: Do you really need v7 on those working devices instead of 6.49.12?

Tue Jan 23, 2024 5:20 pm

Adding:
I assume you went to 7.13 or higher.
Release notes for 7.13 clearly indicate for 60GHz device you need to add an additional wireless package. Base package since 7.13 only contains wave2 drivers and that one is not compatible with 60GHz radios.
But if you do not have enough space, this is not possible (and given LDF5 is a 16Mb flash device, chances are high your problem is there).

So you may be effectively better of to stay on ROS6 for that device.

DeDMorozzzz · Tue Jan 23, 2024 6:40 pm

distant upgrade
No matter the productor of the device, a distant update CAN fail, so upgrade CAN go worse...
Always keep the car engine running... you might leave...

Ask yourself a question: Do you really need v7 on those working devices instead of 6.49.12?

Every upgrade may fail lets not produce "empty" posts.
7.13 distant upgrade leads to interface loss, pre-7.13 were OK

rextended · Tue Jan 23, 2024 6:46 pm

lets not produce "empty" posts.

Your is another one, don't be rude: viewtopic.php?t=203686

The question I asked you, which you obviously didn't answer, probably because it was uncomfortable for you, is useful.

DeDMorozzzz · Wed Jan 24, 2024 2:55 am

Your is another one, don't be rude: viewtopic.php?t=203686

The question I asked you, which you obviously didn't answer, probably because it was uncomfortable for you, is useful.

Sorry i din't want to be rude to anyone it's a misunderstanding.
My network core is ROS6 becouse I'm used to it
My less inportant nodes sometimes run ROS7, becouse I want to get used to it. Also some old devices cant be upgraded via internet to the newest ROS6 without netinstalling (It needs some "pre-newest-version" to be installed manualy before that), But upgrading to ROS7 workes fine in distant mode (before 7.13). It never caused me any trouble and distant-upgrade process was always perfect

Wed Jan 24, 2024 7:53 am

Unless the device to be upgraded runs out of space due to the upgrade.

Which can happen more on 16Mb storage devices using ROS7.

Configure WIFI v.7.13 [SOLVED]

Configure WIFI v.7.13 [SOLVED]

Re: Configure WIFI v.7.13

Re: Configure WIFI v.7.13

Re: Configure WIFI v.7.13 [SOLVED]

Re: Configure WIFI v.7.13 [SOLVED]

Re: Configure WIFI v.7.13 [SOLVED]

Re: Configure WIFI v.7.13 [SOLVED]

Re: Configure WIFI v.7.13 [SOLVED]

Re: Configure WIFI v.7.13 [SOLVED]

Re: Configure WIFI v.7.13 [SOLVED]

Re: Configure WIFI v.7.13 [SOLVED]

Re: Configure WIFI v.7.13 [SOLVED]

Re: Configure WIFI v.7.13 [SOLVED]

Re: Configure WIFI v.7.13 [SOLVED]

Re: Configure WIFI v.7.13 [SOLVED]

Re: Configure WIFI v.7.13 [SOLVED]

Who is online