I have been trying to connect an Acer Aspire 5920-3A2G16Mi - with Lubuntu 22.04 installed on it as a OS - to my Mk HAP ac² via wifi (2.4Ghz).
It seems to be working at the very beginning since the laptop sees the MK wifi signal, and asks me to type the WPA2 wifi password in, but after that I keep getting
“lost connection” messages.
I then tried to connect it to another AP (a tp-link device) which in turn is connected to my Mk HAP ac², and the laptop gets wifi connection this time without any issue.
So, does anyone know if there can be any wifi compatibility issue with MK devices and pc/laptop wifi cards running linux OS distros?
I tried with another distro as well, (mx-linux) and got the same problem.
Best to post config of your device, probably a configuration issue.
terminal
/export hide-sensitive file=anynameyouwish
Review file for sensitive remaining info (Serial numbers, public IP, secret keys, …) and hide those.
Then post contents between [__code] quotes.
Why are there address lists (there is no firewall)?
Why are there (so) many security profiles?
Why set 40MHz bandwidth on 2.4GHz radio (you know it will interfere)?
Why didn’t you set wireless-protocol on the 5GHz radio?
In your case I would reset the RB, without configuration and then choose “HomeAP dual” from the Quickset. Get rid of WPA (choose WPA2-AES only) and continue from there.
Tip: never touch Quickset after primary config.
Why are there address lists (there is no firewall)?
Why are there (so) many security profiles?
Why set 40MHz bandwidth on 2.4GHz radio (you know it will interfere)?
Why didn't you set wireless-protocol on the 5GHz radio?
\
I'm going to use VLANs maybe when I buy another MK device, or a VLAN capable switch. Besides, many don't like use VLANs for security reasons (not my case though), and it wouldn't make any sense in my case. It would be overkilled.
?? off topic
?? off topic
Interfere? How? I didn't notice any problem before.
What? Off topic anyway.
In your case I would reset the RB, without configuration and then choose "HomeAP dual" from the Quickset. Get rid of WPA (choose WPA2-AES only) and continue from there.
Tip: never touch Quickset after primary config.
Resetting my RB just to make ONE old device's wifi card (or whatever) work (which even is not mine)? Are you serious? No way! Tons of setup there:
Port forwarding for a few services running on my server,
OpenVPN
WAN recursive failover (which works like charm and I DO need it!)
script to switch to different DNS servers in case the primary one goes occasionaly down
subnet isolation
and a few others I even don't remember at the moment (yes, this might be a problem really )
Come on, dude! I know that my mk device doean't have a state-of-the-art, perfect setup, and it can look a bit messy, but everything does its dirty job.
I'll maybe reset it when I switch to a stable , reliable V7 OS.
Okay, so it turns out you didn’t share your complete config. That explains a lot.
Getting offended by someone making time to give feedback on your config. Well…in the end…it is your problem, isn’t it!?
Ontopic: Yes, there are devices that can’t handle 40MHz on 2.4GHz radios. But well… for “ONE old device’s wifi card (or whatever)”, why even bother starting a topic.
@broderick, ignorando il resto e considerando soltanto la wlan1, e ignorando che rimuovendo “VODAFONE” da una parte hai lasciato “VD” e dall’altra “VOD”:
/interface wireless security-profiles
eap-methods=“” → deve essere passthrough
management-protection=allowed → deve essere disabled, management-protection è supportato solo da prodotti MikroTik
supplicant-identity=“” → deve essere MikroTik
/interface wireless
band=2ghz-onlyn → se solo n, e non anche g (o b) i vecchi dispositivi solo g non si collegano
channel-width=20/40mhz-Ce → i dispositivi solo g si collegano comunque, perché a 20+20 (che non è 40) ci vanno solo gli n
country=france ??? maddai… un po’ d’orgoglio nazionale…
keepalive-frames=disabled → perché???
multicast-buffering=disabled → hai i tuoi motivi…???
wds-default-bridge=bridge & wds-mode=dynamic → hai qualche dispositivo non-microtik che fa da range extender? se “no”, non va bene
I am sick and tired to get unsolicited advice.
You could have as well stayed on point and give feedback only on the problem I was asking for.
BUT, it seems that some people here are too often dying to say other ones that they are the MK badasses, so the first thing they come up with is "you should reset!".
I guess it is hot for everyone …
I’ll throw in my 0.02€
More often then not there are problems being reported here based on limited info the user “thinks” is relevant.
Quite a lot the cause of the problem is not to be found there. It’s elsewhere, in the part not shown.
Hence the almost standard request here to provide full config.
If for whatever reason you do not think this is relevant for solving your problem, it is not correct to blame others for not being able to solve your problem.
A problem not created by the ones trying to help. OK ?
I am by no means an IT professional (just happen to be someone who knows quite a lot from decades of fiddling and experimenting) and certainly not an MK badass (still learning quite a lot myself) but you’d be surprised that in 8 or 9 cases out of 10 pulling the plug on a device solves a lot of problems.
So does clean config reset on a router device which has been wrongly configured (which I am not saying is the case for your problem, we’ll see about that further on).
You came here for assistance with a problem.
Be glad someone is willing to help. We are all doing this in our free time.
I know that something else in our setup can be relevant, but that wouldn’t explain why all other my devices work perfectly as expected both via wifi and ethernet.
I am by no means an IT professional (just happen to be someone who knows quite a lot from decades of fiddling and experimenting) and certainly not an MK badass
…
So, you should understand why your answer can be annerving.
Be glad someone is willing to help. We are all doing this in our free time.
why: used or not, eap default is passthrough (long term bug, fixed on latest v7.4), and supplicant as MikroTik device, is the default
/interface wireless security-profiles
set [find] eap-methods=passthrough supplicant-identity="MikroTik"
You can/must disable wds if you do not have any mikrotik “station-wds” as client.
the default are wds-default-bridge=none and wds-mode=disabled
keepalive-frames=disabled → if disabled, the ap do not keep track of the client if is really connected or not, and can cause problems, better enabled (default)
multicast-buffering=disabled → if disabled do not buffer multicast traffic, and is dropped. If you use some device that use this function, better keep it enabled (default).
If that do not fix, and all other devices work,
supposing you do not have put an access-list rule that deny the registration,
or a fixed dhcp lease that assign wrong ip,
or firewall rule that block the MAC,
or any other setting than can cause the problem on another config parts (I provide exact examples, not generic)
try to make a bootable usb stick with windows 10 / kaspersky recovery / other iso than can boot and use wlan
and check if on another OS the wireless work correclty.
If work, the problem can be only on Lubuntu driver/kernel/settings/etc.
I don't think so, I mean, it is very unlikely. I didn't set any particular rules to block new devices trying to connect to the Wlan1, and as far as I remember, my MK dhcp has never had issues before.
try to make a bootable usb stick with windows 10 / kaspersky recovery / other iso than can boot and use wlan
and check if on another OS the wireless work correclty.
Unfortunately, I can't do any attempts now. The laptop wasn't mine; just a friend of mine passing by who asked me to install lubuntu on his old device.
Windows 7 ran on it before I installed lubuntu, and I didn't notice this problem, BUT I don't remember if it was connected via wifi or ethernet, sorry ..maybe wifi, but I often plug a cable when I need to install a new OS on a device. Anyway, he told me that the laptop works flawlessly via wifi on his home network, it is the most important thing.
Anyway, as I said above already, it was an opportunity to learn new things, and tune up my mk setup.
If work, the problem can be only on Lubuntu driver/kernel/settings/etc.