I've got everything figured out except for this:
:local wirelesslist [scan $interface1 freeze-frame-interval=0:0:02];
Thank you
:local wirelesslist [scan $interface1 freeze-frame-interval=0:0:02];
:global interface1 "wlan1";
:global wirelesslist1 "";
/interface
wireless
:global wirelesslist1 [scan $interface1 duration=5];
:log info "sending mail"
/tool
e-mail
send server="mail.something.com:25" user="user" password="somepwd" from="sender" to="recipient" subject="list" body="body with wireless lists";
:foreach myVar in=[scan wlan1 duration=3] do={;
:log info "loop";
:};
:global myVar [scan wlan1 duration=2];
:put $myVar;
; Filename: MikroTik_Wlan_Scan.ttl
; Tera Term Script (use newer version 4.6x)
; Author: Bob Burley - April 19, 2011
; Initialize Variables
deviceUsernamePrompt='Login:'
devicePasswordPrompt='Password:'
deviceUsername="admin"
devicePassword="xxxxxxxx"
commandPrompt='] >'
deviceIPaddress="1.1.1.1"
host=deviceIPaddress
strconcat host ':23 /nossh /T=1'
outputFilename='ScanList.txt'
; Regular Expression for matching - could still use some fine tuning
; The Band '2.4ghz-b' is hard-coded in this string and needs tweaking to allow different bands
regexStr='^\w{1,5}\s{1,5}\h{2}:\h{2}:\h{2}:\h{2}:\h{2}:\h{2}\s.{1,12}\s2\.4ghz-b\s{3}\d{4}\s-\d{2}\s-\d{2,3}\s\d{2}'
; Connect to device
connect host
wait deviceUsernamePrompt
sendln deviceUsername
wait devicePasswordPrompt
sendln devicePassword
wait CommandPrompt
; Delete previous file if present and you are not using append mode
filesearch outputFilename
if result filedelete outputFilename
; Open Output File
; Last parameter: 0 = Overwrite - 1 = Append
fileopen outputFile 'ScanList.txt' 0
; Write header lines to file
; This is manually written because these lines appear multiple times during the scan
filewriteln outputFile 'Flags: A - active, B - bss, P - privacy, R - routeros-network, N - nstreme'
filewriteln outputFile ' ADDRESS SSID BAND FREQ SIG NF SNR RADIO-NAME'
; the command prompt appears multiple times during the scan,
; so 'end' detection is done with this 3 second timeout
timeout=3
; Start the WLAN Scan and run for 5 seconds
sendln '/interface wireless scan 0 duration=5'
; flush the command just entered from the buffer
flushrecv
; detect output lines that match the Regular Expression
:loop1
waitregex regexStr
outputLine=inputstr
if result filewrite outputFile outputLine
; detect timeout
if result=0 goto exit1
goto loop1
:exit1
fileclose outputFile
sendln '/quit'
; The output file will contain duplicate entries
; Additional scripting is required to process the output file
/interface wireless scan 0 duration=5 outputfile=something
/interface wireless scanonce 0 duration 5
What use is the background scan function?Have you noticed the background scan function?
1) Not true. Just tested on such station (actually station-bridge mode): station scanned while there was uninterrupted traffic flowing both ways and the winbox was connected over the scanning wlan.
2) Not true. Really funny idea to have a client without working scan. How could it connect to ap without it?
3) Does not see airmax. Like ubnt does not see nv2, because the protocols ar proprietary. Not sure how superchannel works on ac, so I cannot say.
Generally, why you think that this topic is about ac?
1). Ok, But then please explain this; it just doesn't work. On ANY of our MT units. So its software/hardware wide issue.
2). Sorry, you are right. ac does support scan. But not spectral scan. And as is shown in no. 4 and 5 the scan in itself is not a very useful feature for professional netops. You need a spectral scan.
3). A spectral scan should see all signals. Because all signals can create noise. In fact we don't care about the technology; babyphone, bluetooth, airmax, Wimax, tdma or whatever. Noise is noise and if you want a good working channel you'd better find one with little noise.
And why do you think ubnt can't see NV2? As well as I can see airmax they can see NV2......
Why do I think this topic is about ac?
Well, for one I am one of the several that started discussion on the scan in-availability in several treads in the forum. Some in this tread even revere to me.
And nowhere is stated in this tread 'ac' is not included in this topic.
Off course this should be about ac. This is the latest product line so why should we talk about shortcomings in a product line where same short comings are even more prominent in the latest product line?
(Its like BMW had a car series that had regular broken windshield (front windows) and now their newest model are just supplied with the steelplate in place. Problem solved! You now only have to drive blind! Just as the new ac product line is sort of 'blind' in a ever more crowded spectrum.)
In stead of rejecting some of my points you'd better acknowledge and try to find a solution for your users....
For the interested reader, we have a bypass to solve the issue;
- Just fit your obsolete single stream 'a/b/g/n' radio or outdated OmniTik at the AP for spectral scan purposes. All it need is extra cable and a power supply and you can make as much spectral scan as you'd wish for as long as you want.
It doesn't help on the client side though...... but I'll think that is what you have to live with for a long time to come if you are a Mikrotik fan like me.....
Can you try again with 6.35.4? I did the test with this version using wireless-rep package while you are using 6.35.2, as shown on your picture...
This topic is from year 2010, so it was not about ac at all for sure. You have just brought it here. Nothing against you, you are right, the ac should handle spectral scan and narrow bands, but this topic was not about it. There are other topics already discussing it, so no need to have it here again...
If I would follow all posts in this forum not to miss anything I would'n make no more sense since I wouldn't have any more time to run a network......Congratulations to your re-invented ability to read. It is very useful...
Never mind, I have sometimes the same problem - overlooking obvious things.
Enjoy the background scan!
Oeps, your right. Seldom read the manual anymore. Habit from the past I guess when the manual was about century behind developments.... Sorry.It is clearly written in the manual too:
http://wiki.mikrotik.com/wiki/Manual:In ... eless#Scan