Community discussions

MikroTik App
 
andzinslv
just joined
Topic Author
Posts: 2
Joined: Sat Mar 11, 2023 2:06 pm

Device cannot connect specifically to Mikrotik APs

Sat Mar 11, 2023 2:20 pm

Hi,

ordered Up2stream Mini V3 device and cannot connect to Mikrotik AP.
Interestingly I can connect to any other vendor APs, but tried 2 different places and setups using Mikrotik and it did not work.

This guy seems to have the same issue, but no one solved it: https://forum.arylic.com/t/unable-to-co ... ini/2752/9
Could it be caused by the device's MAC address?

What test could I run to narrow down the issue?

Thanks!
 
mfrommel
newbie
Posts: 25
Joined: Wed Dec 23, 2020 2:21 pm
Location: Munic, Germany

Re: Device cannot connect specifically to Mikrotik APs

Sun Mar 12, 2023 11:46 am

Please read this!
viewtopic.php?p=908118

You may start with "Step2"
 
andzinslv
just joined
Topic Author
Posts: 2
Joined: Sat Mar 11, 2023 2:06 pm

Re: Device cannot connect specifically to Mikrotik APs

Mon Mar 13, 2023 9:38 pm

Thanks for point to right direction!

Here is some additional information.

I want to connect device - up2stream mini V3 - to my home network.

Tried to do the initial setup of the device, but cannot connect to the network sometimes getting network timeout and sometimes DHCP error message.
I have tried to connect this exact device to three different networks.
It did connect successfully to one of them that was not based on Mirkotik devices.
But in both cases (my home network and lab network where Mikrotiks are used with different config) it did not connect, failing with the same massages.

My network consists of 2 Mikrotik devices.
Configurations are listed below.

HexPoe:
# mar/13/2023 21:21:23 by RouterOS 6.43.12
# software id = A1EQ-AR83
#
# model = 960PGS
# serial number = xxxxxx
/interface bridge
add admin-mac=B8:69:F4:B3:A7:33 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 ] supplicant-identity=MikroTik
/ip hotspot profile
set [ find default=yes ] html-directory=flash/hotspot
/ip pool
add name=dhcp ranges=192.168.88.2-192.168.88.254
/ip dhcp-server
add address-pool=dhcp disabled=no interface=bridge name=defconf
/caps-man manager interface
set [ find default=yes ] forbid=yes
add disabled=no interface=bridge
add disabled=no interface=ether1
/interface bridge port
add bridge=bridge comment=defconf interface=ether2
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=sfp1
/ip neighbor discovery-settings
set discover-interface-list=LAN
/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
/ip dhcp-client
add comment=defconf dhcp-options=hostname,clientid disabled=no interface=\
    ether1
/ip dhcp-server lease
add address=192.168.88.2 client-id=1:6c:3b:6b:87:82:d6 mac-address=\
    6C:3B:6B:87:82:D6 server=defconf use-src-mac=yes
add address=192.168.88.15 client-id=1:b8:27:eb:42:dc:19 mac-address=\
    B8:27:EB:42:DC:19 server=defconf use-src-mac=yes
/ip dhcp-server network
add address=192.168.88.0/24 comment=defconf dns-server=8.8.8.8 gateway=\
    192.168.88.1
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=192.168.88.1 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=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
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=accept chain=srcnat ipsec-policy=out,none out-interface=ether1
/system clock
set time-zone-name=Europe/Riga
/system identity
set name=MikroTik-HexPoE
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN

wAP:
# mar/13/2023 21:27:08 by RouterOS 6.49.7
# software id = YKCP-2YN2
#
# model = RouterBOARD wAP G-5HacT2HnD
# serial number = xxxxx
/interface bridge
add name=bridge1
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
add authentication-types=wpa2-psk mode=dynamic-keys name=JenoteniSecured \
    supplicant-identity=""
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-onlyn country=latvia disabled=no \
    frequency=2437 mode=ap-bridge name=wlan-2G security-profile=\
    JenoteniSecured ssid=Jenoteni-2G
set [ find default-name=wlan2 ] band=5ghz-onlyac channel-width=\
    20/40/80mhz-Ceee country=latvia disabled=no frequency=5260 mode=ap-bridge \
    name=wlan-5G security-profile=JenoteniSecured ssid=xxxxx
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=wlan-2G
add bridge=bridge1 interface=wlan-5G
add bridge=bridge1 disabled=yes interface=all
/ip neighbor discovery-settings
set discover-interface-list=!dynamic
/ip dhcp-client
add disabled=no interface=bridge1
/system clock
set time-zone-name=Europe/Riga
/system leds
set 0 disabled=yes
set 1 disabled=yes
set 2 disabled=yes
 
User avatar
chechito
Forum Guru
Forum Guru
Posts: 2990
Joined: Sun Aug 24, 2014 3:14 am
Location: Bogota Colombia
Contact:

Re: Device cannot connect specifically to Mikrotik APs

Mon Mar 13, 2023 11:08 pm

i think will be useful to enable more extensive logging on wireless topic
/system logging
add topics=wireless
in that way you can collect info at the moment your client device try to associate with the AP and the possible reason of failing to do so
 
R1CH
Forum Guru
Forum Guru
Posts: 1099
Joined: Sun Oct 01, 2006 11:44 pm

Re: Device cannot connect specifically to Mikrotik APs

Tue Mar 14, 2023 3:14 am

Try setting more compatible protocols instead of only n / ac. Cheap IOT chipsets sometimes don't even support 802.11n.
 
User avatar
Ca6ko
Member
Member
Posts: 499
Joined: Wed May 04, 2022 10:59 pm
Location: Kharkiv, Ukraine

Re: Device cannot connect specifically to Mikrotik APs  [SOLVED]

Tue Mar 14, 2023 8:31 am

Configure the wifi mode on Mikrotik as your device supports, the specification says b/g/n, so set it to 2 GHz - B/G/N

Who is online

Users browsing this forum: lmeira, petardo and 34 guests