sometimes we scan from winbox…
BUT, sometimes we have to scan from console…
this is the result of a console scan:
[lewis@UOM] interface wireless> scan bb-hadji
ADDRESS SSI BAND FREQ BSS PRI SIGNAL-S... ROU NST FAS RA RO
00:09:5B:96:F2:05 2.4ghz-g 2312 yes no -68 no
00:30:4F:35:FE:68 twm 2.4ghz-g 2357 yes no -78 no
36:0D:79:32:2F:15 wor 2.4ghz-b 2412 no no -88 no
00:02:6F:20:82:E4 tes 2.4ghz-b 2412 yes yes -89 no
00:40:96:34:E4:3B twm 2.4ghz-b 2432 yes no -73 no
00:12:17:DF:16:A3 twm 2.4ghz-b 2437 yes no -87 no
00:0F:66:12:0A:C5 hel 2.4ghz-g 2452 yes no -61 no
00:90:4B:A0:09:72 wir 2.4ghz-b 2457 yes yes -71 no
00:40:96:26:32:6C 2.4ghz-b 2472 yes no -50 no
00:C0:49:D9:02:27 cdp 2.4ghz-b 2472 yes no -68 no
00:0F:3D:DF:CC:6A def 2.4ghz-g 2467 yes no -77 no
00:40:96:46:8C:11 Gri 2.4ghz-b 2417 yes no -91 no
00:12:01:96:D0:20 2.4ghz-g 2462 yes no -76 no
48:59:DD:19:2E:94 wth 2.4ghz-b 2472 no no -80 no
00:02:6F:01:B8:3D twm 2.4ghz-b 2462 yes no -88 no
00:40:96:38:03:6F twm 2.4ghz-b 2447 yes no -88 no
as you all see, the ssid is almost invisible…
so, i suggest in a newer version, to add a switch (i.e. brief)
and the result should be like this:
ADDRESS SSID BAND FREQ BSS PRIVACY SIGNAL-STRENGTH
00:09:5B:96:F2:05 g 2312 y n -69
00:30:4F:35:FE:68 twmn::hadji2salonic g 2357 y n -78
00:02:6F:20:82:E4 testing_telecom_2 b 2412 y y -89
00:40:96:34:E4:3B twmn::uom b 2432 y n -73
00:12:17:DF:16:A3 twmn::BlackPeeT_2_C&S b 2437 y n -90
00:0F:66:12:0A:C5 helmug::macgiorgosgr g 2452 y n -62
00:90:4B:A0:09:72 wireless_egnatia b 2457 y y -71
00:12:01:96:D0:20 g 2462 y n -84
00:C0:49:D9:02:27 cdpas2hadji b 2472 y n -67
00:40:96:26:32:6C b 2472 y n -49
00:40:96:38:03:6F twmn::h2ocooled b 2447 y n -88
36:0D:79:32:2F:15 work b 2412 n n -90
00:0F:3D:DF:CC:6A default g 2467 y n -75
and of course there should be an option to write the scan to a file…
i dont know if this is possible with this “do=” parameter
Flags: A - active, B - bss, P - privacy, R - routeros-network, N - nstreme
ADDRESS SSID BAND FREQ SIG RADIO-NAME
AB R 00:0C:42:05:06:41 ARTS 2.4ghz-g 2494 -47 000C42050641
[admin@MA_GW] interface wireless>
I’ve always had this same problem too…In every version ever used (since the 2.7 days) you can only see the first 3 characters of the ssid while scanning. Eugene, perhaps you can enlighten us on how to display these differently?
Well, I see no way to display these differently (of course differently from my view)
Apparently, you need to upgrade to the latest 2.9 version.
Once again console output with the command (v2.9rc2):
[admin@MA_GW] interface wireless> scan wlan1
Flags: A - active, B - bss, P - privacy, R - routeros-network, N - nstreme
ADDRESS SSID BAND FREQ SIG RADIO-NAME
AB R 00:0C:42:05:06:41 ARTS 2.4ghz-g 2494 -45 000C42050641
Flags: A - active, B - bss, P - privacy, R - routeros-network, N - nstreme
ADDRESS SSID BAND FREQ SIG RADIO-NAME
AB R 00:0C:42:05:06:41 ARTS 2.4ghz-g 2494 -44 000C42050641
[admin@MA_GW] interface wireless>
As much as I like 2.9, we have to wait until it is finished and stable before we can use it on production systems. I believe we are using the only supported version, 2.8.
What do you consider stable? Does it “become” stable once the two “rc” letters are removed from the name??? I consider the 2.9 platform to be very stable, and I feel it has been for the last several release candidates. What I mean by stability is: Does it have any memory leaks(etc.) that get worse over time? Does it have any bugs that can cause the platform to crash after a certain amount of time or activity? Does it act inconsistently or unreliably? The answers to these questions has been “no”, for me, since about rc4. Sure there are still some bugs that may or may not affect any given person depending on which features they are using, but even the lateset versions of 2.8.x will have some bugs(that’s why there needs to be the “.x” after the “2.8.”), there is just no way to always get every single one…
We have been running 8 wireless high sites as Access Concentrators using version 2.9rcX for the last few months with no recurring problems at all, other that a few small consistent bugs that were quickly corrected by Mikrotik upon request, and these were easily identified and already known to us before deployment through testing. Again, I should stress that the operating system has been predictable for a good while now, so that you can correctly ascertain it’s usability for your application by testing. 2.9 is not far from being a full release now, and the only reason it is probably not already out of “rc” stage is because MT is still correcting the last few small bugs that only affect a small number of installations. At this stage, chances are small that any changes made to 2.9 before it’s removed from “rc” status would make any difference to most of us…
In my opinion, unless one of the small remaining bugs would specifically effect your configuration(look for complaints in the RouterOS Beta forum), I would suggest testing 2.9 for yourself to see if it will already work perfectly for you. Like I said, most of the serious problems, especially those having to do with stability, have been corrected long ago…
Hitek
P.S. Also, I know that 2.9rcX is not officially supported because it is still a release candidate, but don’t let that fool you. MT still gives top priority to any of even the smallest problems with the release candidates, as they are almost done working the last few bugs out, and wish to correct them as quickly as possible. I have had my requests for 2.9rcX support answered and corrected just as quickly as version 2.8.x, if not even faster. I would actually expect support for 2.9 to be a little faster now than it would be for 2.8, as 2.9 spends the majority of it’s time in the thoughts of the developers now, so it is always fresh in their minds. Were they to be posed a problem to be corrected for version 2.8.x, they would seemingly have to “switch gears” back to the old 2.8 mentality, it being so internally different from 2.9…
I wasn’t going to reply to this, but after playing with rc7 a little more the last few days and reflecting on the last several weeks of posts in the beta forum, I feel much more comfortable with 2.8 for the time being.
What do I consider stable? Being able to walk away from a device and know that it will be up 6 months later. Since I still can’t do this with 2.8 as a hotspot router, there’s just no way I’d blindly switch everything over just yet. It’s unfortunate that most attention has been put into 2.9 for this very reason.
Don’t get me wrong, we eagerly await the final version of 2.9, or whichever subversion works best for what we do. But, it’s still in RC for a reason and I can’t put it in place before it has been proven to handle it’s job reliably, and that proof just takes time.
rc7 seems very stable to me and has improved my network. The only problem I have seen with rc7 is with prism cards.
When I installed rc7 on a node with 2 prism card servering 40 customers, it only brought up about 20, the other 20 were yelling at me on the phone.
after ripping my hair for a few hours, I went back to 2.8.28 and viola all the customers came back on. I didnt have time to get the answer from the forum. I was going to try again next week and try to squeak out a support file before all the clients kill me.
I consider the 2.9 platform to be very stable, and I feel it has been for the last several release candidates. What I mean by stability is: Does it have any memory leaks(etc.) that get worse over time? Does it have any bugs that can cause the platform to crash after a certain amount of time or activity? Does it act inconsistently or unreliably? The answers to these questions has been “no”, for me, since about rc4. Sure there are still some bugs that may or may not affect any given person depending on which features they are using, but even the lateset versions of 2.8.x will have some bugs(that’s why there needs to be the “.x” after the “2.8.”), there is just no way to always get every single one…