I just purchased two (non-LTE) Audience routers to resolve a problem getting Internet around my home.
I’ve been setting up one of them in order to figure out how to use them as I want (and upgraded to 7., but have ended up locked out.
I set up a password already, and have logged in and out several times (mostly via ssh), so I know the password is (or was) good.
I turned the unit back on yesterday to continue learning about it, and I cannot ssh into it any more.
Right now the Audience is only connected on ETH1 to my laptop, and with WinBox 4.0beta44 (for Linux) I can see it’s MAC address as a “Neighbor” but any attempt to login to it fails with “ERR Could not connect. MacConnection syn timeout”.
When I switch my laptop from ETH1 to ETH2 a short while later another MAC pops up, one more than the previous one (no surprise), but I get the same error trying to connect.
I have tried doing a hard reset several times, but I still cannot get in. I’m holding the reset button in while applying power until the LED on the front starts flashing green then let go of the reset button. The LED goes through some on/off cycles but eventually ends up solid blue again, but I cannot get into it.
From my experience with wireless devices in v7, default firewall only allow to connect from wireless interfaces. It was the case at least on wAP R, mAP lite. Since Audience is Wi-Fi, maybe the upgrade from v6 to v7 triggered default-configuration. Have you tried connecting from wireless ? Have you disabled it ?
I have not tried with an Audience but have done straight upgrades from v6 to 7.20.6 without a problem. On these non-AX devices, my sequence is upgrade to the latest v6, then straight to current v7, then upgrade firmware to match. I speculate that you should netinstall v6 then try again.
Something changed. Did you add a switch between, for example? Barring cosmic rays from the universe, it cannot be the case that the same system in the same absolute context allows login one day but not the next.
Edit: EmanK posted while I was writing. It is true that mAP Lite firewalls ethernet and not wireless by default, but that is the same in v6.
When performing netinstall, it's best to go directly with desired version ... because upgrade involves configuration conversion (which is quite heavy when going from v6 to v7) and it tends to leave v6 config stored (in case user decides to downgrade to v6 again).
The only exception to this rule is if routerboot firmware is ancient, routerboots versions below 6.44 or something around that might not be able to boot v7 kernel. In this case it's necessary to install one of most recent ROS v6 versions and perform upgrade of routerboot firmware. After that either go through upgrade to v7 (again with remnants of v6 config lurking on filesystem) or perform another netinstall to desired ROS version.
I think I went straight from the v6 it came with to the latest v7.
I'm not seeing any WiFi SSIDs from the device, neither the values that I changed them to nor the default “MikroTik” (or whatever it was).
I disabled capsman that the two regular WiFi interfaces were set to use by default. I don't have a capsman server set up and don't see the point of another layer of complexity for two APs. After doing that I never saw the two main SSIDs in the air.
The last substantial thing I recall doing before I lost it was to use the WebFig to select “AP” mode (from memory, I'm away from my notes right now), as that seems to fit my desired functionality.
I will try a netinstall. Does the factory reset procedure just not work?
Any chance there's a serial console port buried inside this thing so I can see what's going on?
Winbox 4.x is still experimental, if it works it works, but soemtimes it doesn't.
Webfig (in version 7.2x.y) has been reported as having sometimes issues.
In ANY case Quickset (particularly from Webfig, but not only) is re-known to create issues, it should NEVER be run (better) or if you really-really want to run it, ONLY run it ONCE and ONLY after a reset to default configuration, as running it on an already partially custom configured router is a perfect recipe for disaster.
Also, by default, ETH1 on the Audience is in the WAN list, so no neighbor advertising and no traffic permitted to the input. If you are using Linux, you can try with mactelnet-client and see if it works on eth2.
Well, I have regained access to my Audience via ssh, and the web interface is alive as well.
Was prompted to set up a password, as per the usual first-login experience.
But the LED on the front of the Audience is off (after some boot-time activity), and I have no wifi interfaces (/interface/wifi/print produces nothing).
So I’ve lost all of the factory Audience-specific configuration stuff?
Check /system/default-configuration/print, that should have the mesh setup.
If it does, you can just re-apply the defconf via: /system/reset-configuration no-default=no keep-users=yes.
Depending on exactly what you did with netinstall it may not restore the audience specific configuration. But that should still be default-configuration, which be applied when doing a reset-configuration.
But you likely should upgrade to the wifi-qcom-ac which has way better performance. And if you install wifi-qcom-ac with netinstall... it does not support default "meshing" scheme with that. But you'd can roll-your-own mesh & you still have the 2 x 5Ghz radios to use for it.
With all due respect, it seems to me you are making It more difficult than needed.
You have a second, identical device.
Power it on, DO NOT fiddle with It.
Connect to It make an export of the configuration and post It, instructions here:
That configuration can be loaded on the "misconfigured" Audience with only some little changes (the MAC address(es) will likely need to be changed, maybe something else).
This command only installs base ROS package ... but omits wifi drivers. So either install wifi-qcom-ac package via ssh/winbox ... or repeat netinstall but add wifi-qcom-ac package to the lsit of packages.
Each package adds default config ... so wifi (mesh or not) default config won't be there until wifi driver package gets installed.
Either way, perform reset configuration (and don't add any of possible checks, like "no default configuration" to reset config to factory default (which is not empty). Then proceed as if your Audience was new from factory (set admin password, etc.).
Agree with @mkx, once you get the device accessible (via netinstall, including the wifi-qcom-ac package), you should start by doing the /system/reset-configuration keep-users=yes which will apply the default configuration, which gets a good firewall as base to work with. And after the /system/reset-configuration complete, I'd just use QuickSet to set some initial Wi-Fi SSID and password, just to make sure everything works.
See with just netinstall, you'll be left with an empty configuration. While this may sound good to learn by building config... you'll learn more by understanding the default and adapting it IMO, in particular the firewall is deceptively complex and default firewall is an excellent base to start working with.
Now since you have two Audience, and want to "mesh" them... If you explain a bit how you want them "meshed" it be helpful. Or if you want VLAN or need VPNs, etc... Also, re-post the configuration of both after you get access again, since even though the default not all defaults are same.
Alright, looks like I have two paths here, and I cannot do both.
Export the configuration for “untouched” Audience 2 (that came with 6.49.11), hand-edit it to replace MAC addresses with those of Audience 1, then netinstall 6.49.13 (I don’t see 6.49.11 available to download) and import the hand-edited configuration file to get Audience 1 back to out-of-the-box state
Netinstall 7.20.7 and add the wifi-qcom-ac package, but the exported config file from Audience 2 with RouterOS 6.49.11 probably should not be used. So I won’t have the Audience-specific configuration stuff to make the front LED function and enable wlan3
