Posts made by Scott Horsley

@Michal-Rok Okay, you are a genius!

That is working, however, still unsure why setting it after connection changes anything.

Even more so, it appears that without setting mode sta it doesn't even appear to attempt to connect with the router.

Would really love to know what the mode flags do to the ralink device!

Using rc.local is of course the key to getting this working after the fact but I feel dirty leaving it as a proper solution.

Thanks to anybody and everybody that put effort in here, I think we have a (albeit, not perfect) working solution.

Can anybody else confirm this works on other MT units out in the wild?

I'm doing this on a 2011UAS-2HnD but I believe it should work on any unit of them.

@Michal-Rok Seems rather inconsistent if that is the case, I originally couldn't connect with anything of course, this configuration I can reproduce directly after a firstboot -y, sync.... which means it's certainly working.

My SSID and Passphrase are really simple words only, ECLIPSE being the SSID (as referenced, and strangely, I blanked out in the SSID box), but the password may as well be abc123 with how simple it is.

I'm dumping my MT config for the information it may or may not share with regards to this. I'm running RouterOS v6.39.2 (stable) at this time.

[scott@ap2] > /interface wireless print where name=wlan-ECLIPSE                     
Flags: X - disabled, R - running 
 0  R name="wlan-ECLIPSE" mtu=1500 l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX arp=enabled interface-type=Atheros AR9300 mode=ap-bridge ssid="ECLIPSE" frequency=channel-6 band=2ghz-b/g/n channel-width=20mhz 
      scan-list=default wireless-protocol=any vlan-mode=no-tag vlan-id=1 wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no bridge-mode=enabled default-authentication=yes default-forwarding=yes 
      default-ap-tx-limit=0 default-client-tx-limit=0 hide-ssid=no security-profile=profile-ECLIPSE compression=no 
[scott@ap2] > /interface wireless security-profiles print where name=profile-ECLIPSE
Flags: * - default 
 0   name="profile-ECLIPSE" mode=dynamic-keys authentication-types=wpa2-psk unicast-ciphers=aes-ccm group-ciphers=aes-ccm wpa-pre-shared-key="xxxxx" wpa2-pre-shared-key="xxxxx" 
     supplicant-identity="MikroTik" eap-methods=passthrough tls-mode=no-certificates tls-certificate=none mschapv2-username="" mschapv2-password="" static-algo-0=none static-key-0="" static-algo-1=none 
     static-key-1="" static-algo-2=none static-key-2="" static-algo-3=none static-key-3="" static-transmit-key=key-0 static-sta-private-algo=none static-sta-private-key="" radius-mac-authentication=no 
     radius-mac-accounting=yes radius-eap-accounting=no interim-update=0s radius-mac-format=XX:XX:XX:XX:XX:XX radius-mac-mode=as-username radius-mac-caching=disabled group-key-update=5m 
     management-protection=disabled management-protection-key="" 

@Michal-Rok thanks for the feedback, sorry it got you no further either.

Yep, I disabled the firewall entirely, even as far as removing the rc startup link and rebooting with no change. iptables -L shows nothing at all at this point (what you'd expect really). I tried forcing the wlan interface into the bridge (br-wlan) also with no change at all. I disabled dnsmasq and forced the resolution to Google (8.8.8.8) with, of course, no change either (which you'd expect as nothing appears to arrive on the router itself).

Was there a reference anywhere to what the "option mode '9'" (or 'sta') does and any other options relating to this area of the config? I searched on anything WRT but didn't show anything about the ralink unit so was rather roadblocked at that point.

One other point that I noted was that I needed to ensure my channel was low in order to work at all, almost like the AU flag wasn't being used. Not a huge deal as a quick scan on the MT suggested 6 was the best channel for me but changing from AU to US and/or back didn't seem to change anything at all.

As far as running with no security, I might try that trick and see if I can get any ideas of what is happening.

I originally tried connecting to my mobiles hotspot to get running and that worked, then modified the config to suite the MT, hoping that the initial config was doing something more when it was first coming online but as mentioned by a few others, that made no difference either.

Frustration to say the least.

Has anybody had any luck with a USB wifi adaptor and an MT on these units?

I love my MT(s, I have a few running in the house) so a decision to swap them isn't going to fly and I'd rather just accept that the Omega isn't for me than contemplate the alternative.

As this seems to still be an ongoing issue and I've had my unit for some crazy amount of time, after testing the latest firmware every month or so I seem to have finally cracked this issue.

No promises that this will work for everybody but it certainly worked for me.

I have my MT set to some pretty vanilla standards

I have static channels configured

But again, all really normal bizwack.

The only change required on my onion in order to connect cleanly was the following

root@Omega-2EB7:/etc/config# cat wireless 

config wifi-device 'ra0'
        option type 'ralink'
#        option mode '9' # This doesn't seem to work on an MT
        option mode 'sta' # This works on an MT
        option channel '6' # This shouldn't be required to be a number and can be left as 'auto'
        option txpower '100'
        option ht '20+40' # Meh, 20, this works but so does 20 or 40 from memory
        option country 'AU' # Whatever your country is
        option disabled '0'

I'm not going to say that this is the magic bullet but it certainly got me up and running.

Caveat I still don't have network access other than ICMP. I think this is a firewall issue on the unit itself but I can't work it out yet. This is just my first step so sharing in case it corrects the problem for anybody else.

Hope that helps somebody

Just as a point of interest, I've upgraded the unit to the latest firmware (1.9) as of yesterday and it still produces the same result.

I've also had no end of complications getting my wireless to work.

Connecting to my mobile (Nexus 6P) works perfectly with a password, but my Mikrotik (CRS125 + 2011) units just don't play ball.
I've tried turning the security on for every protocol and nothing seems to help.

I can access the unit itself on it's own AP address which allows SSH access and then I've changed settings, including setting the country code, setting AES, etc.

I haven't tried allowing purely MAC only with no password yet, will try that when I get home and see how it goes.

Very frustrating indeed.