Page 1 of 2

v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Jan 29, 2016 5:54 pm
by sergejs
v6.35rc has a new wireless package, that has the same features as wireless-cm2 package and will contain many new interesting features.
Few of the added functions are listed in the changelog below, more to come!

Documentation for the new wireless package is in progress. Please test new wireless-rep package before adding it to the production networks. Thank you very much for your feedback in the advance!

Package is available on download page with 'All packages' file.

What's new in 6.35rc1 (2016-Jan-29 13:59):

*) route - do not show duplicate gateway on connected route;
*) wireless - added new package "wireless-rep";
*) wireless-rep - initial support for station roaming for station mode in 802.11 protocol;
*) wireless-rep - added support for wireless repeater mode for 802.11 protocol;
*) wireless-rep - added support for wireless background scan for 802.11protocol;
*) wireless-rep - added support for saving wireless scan results to file;
*) wireless-rep - added support for wireless scan rounds setting;
*) wireless-rep - added WPS client support;
*) wireless-rep - added STEP feature for the scan-list;


how to configure wireless-repeater on _one_ wirless interface.
it is done by command,
setup-repeater command,
/interface wireless setup-repeater

there are parameters:
address -- MAC address of AP to setup repeater for (optional)
ssid -- SSID of AP to setup repeater for (optional)
passphrase -- key to use for AP - if this is specified, command will
just scan for AP and create security profile based on info in beacon and
with this passphrase. If this IS NOT specified, command will do WPS to
find out passphrase.

Re: v6.35rc is released, new wireless package!

Posted: Fri Jan 29, 2016 5:57 pm
by bommi
Will this wireless-rep package also provide CAPsMAN support?

Re: v6.35rc is released, new wireless package!

Posted: Fri Jan 29, 2016 6:11 pm
by sergejs
Yes, wireless-rep is the like cm2, but it has additional features (CAPsMAN will work with the package).

Re: v6.35rc is released, new wireless package!

Posted: Fri Jan 29, 2016 7:08 pm
by plisken
I hope we soon get to see the user manual.
If all this is going to work is a great asset.
Congratulations to Mikrotik

Re: v6.35rc is released, new wireless package!

Posted: Fri Jan 29, 2016 8:11 pm
by taduikis
Do you plan to merge all those new changes into ordinary wirelessXX.npk (without -cm2, -fp, -rep) package sometime in the future? It's kinda difficult to do a mass upgrade when package name changes every year or so..

Posted: Fri Jan 29, 2016 9:45 pm
by jarda
Do we need repeater function? It will be probably easier to configure than wds, maybe it will bring compatibility with other vendor's APs, but do we really need it?

Re: v6.35rc is released, new wireless package!

Posted: Fri Jan 29, 2016 9:49 pm
by deanMKD1
@jarda Client/Ap was most featured option last year. Keep it up Mikrotik.

Posted: Fri Jan 29, 2016 10:01 pm
by jarda
I am not against. Just asking... There were times I thought this would be very useful feature, but as the time went forward and I learned more and more, today I don't think it is necessary. Wds is perfectly working and I am not missing the other vendor's compatibility. So why? It's bad idea to use one radio repeater anyway because it is not possible to align antennas against Ap and clients ideally at the same time. But ok, mikrotik thinks it will rise sales on consumer market, so that is it. I can forsee the topics here that the repeater is not as expected by consumers... Will never be.

Re: v6.35rc is released, new wireless package!

Posted: Fri Jan 29, 2016 11:48 pm
by czolo
How to run repeater mode?
Background scan, rounds, scan to file - all that feature works OK.
I see no options for station roaming. Is it "automagical" and it's default enabled when I'm using new package, or I'm missing smthng?

Re:

Posted: Sat Jan 30, 2016 12:25 am
by taduikis
ok, mikrotik thinks it will rise sales on consumer market, so that is it.
I know what would not as much rise but prevent from falling: improvement of current and future WiFi software or hardware. It becomes uncompetitive with todays user demand and trends :( and there's already a list of inventions made. Because currently 4g lte provides numbers which majority of users only care of, and they even justify unresponsiveness, high lag and other related problems.. We desperately need to increase sector capacity, since currently I don't get more than 30M total with 20-30 clients connected. And whats worse, I can't even experiment and seek for best config, they feel shortages of service and immediately start looking who to kill. And I'm not joking, even at 4-5 AM there's no total freedom for that recently.

I understand that with overcrowded 5GHz there's no chance to get what you could with multi-band licensed freq and insane tx powers, but based on what 11n/ac competitors offer, it's certainly not impossible to at least double the mentioned figure, which would be a life saver. For a while.

I might be naive, but I really hope something new and revolutionary might appear with these new wireless-smth packages every time they are introduced. Heck, I'd at least take changelog entries like "improved nv2 performance" :)

v6.35rc is released, new wireless package!

Posted: Sat Jan 30, 2016 1:09 am
by darkprocess
Set the fist wlan as an ap bridge and the second as pseudobridge. First we be the ap and the second the client
If i do the contrary i am unable to connect to the ap

Re: v6.35rc is released, new wireless package!

Posted: Sat Jan 30, 2016 1:31 am
by angboontiong
when the user manual available ???

Re: Re:

Posted: Sat Jan 30, 2016 3:25 am
by gius64
ok, mikrotik thinks it will rise sales on consumer market, so that is it.
I know what would not as much rise but prevent from falling: improvement of current and future WiFi software or hardware. It becomes uncompetitive with todays user demand and trends :( and there's already a list of inventions made. Because currently 4g lte provides numbers which majority of users only care of, and they even justify unresponsiveness, high lag and other related problems.. We desperately need to increase sector capacity, since currently I don't get more than 30M total with 20-30 clients connected. And whats worse, I can't even experiment and seek for best config, they feel shortages of service and immediately start looking who to kill. And I'm not joking, even at 4-5 AM there's no total freedom for that recently.

I understand that with overcrowded 5GHz there's no chance to get what you could with multi-band licensed freq and insane tx powers, but based on what 11n/ac competitors offer, it's certainly not impossible to at least double the mentioned figure, which would be a life saver. For a while.

I might be naive, but I really hope something new and revolutionary might appear with these new wireless-smth packages every time they are introduced. Heck, I'd at least take changelog entries like "improved nv2 performance" :)
I'm with you :D I really hope MikroTik will introduce something new on wireless for point to multipoint!

Re: v6.35rc is released, new wireless package!

Posted: Sat Jan 30, 2016 9:50 am
by rzirzi
Is there any improvement for Ticket # 2015121766000465] - for problem with ROS 6.xx and Nstreme+Polling radio disconnections?

Re: v6.35rc is released, new wireless package!

Posted: Sat Jan 30, 2016 12:18 pm
by asaleh75
How to configure wireless repeater mode

Re: v6.35rc is released, new wireless package!

Posted: Sat Jan 30, 2016 12:23 pm
by npero
*) wireless-rep - added support for wireless background scan;
I see opportunity to make auto frequency mode to work in background active scanning for noise and some algorithm to choice best channel or to make report in background it will be nice to see both options.
Now auto just scan when disable enable interface.

Re: v6.35rc is released, new wireless package!

Posted: Sat Jan 30, 2016 2:59 pm
by czolo
With new package TCP throughput is really impresive. There is a problem with nv2 connection. Client's can't connect, when protocol is set to nv2, only nstreme and 802.11 works. With nstreme, there is a problem with dynamic framin policy.

I really starting to like what you are doing.Don't stop, and make it better :)

Re: v6.35rc is released, new wireless package!

Posted: Sat Jan 30, 2016 3:25 pm
by efaden
What exactly is the "station roaming for station mode" ??? Is this the start of seamless roaming?

Re: v6.35rc is released, new wireless package!

Posted: Sat Jan 30, 2016 3:43 pm
by efaden
Also... if I just upgrade my routers to 6.35rc1 will they automatically get rep package or will I need to add it?

-Eric

Re: v6.35rc is released, new wireless package!

Posted: Sat Jan 30, 2016 3:47 pm
by asaleh75
Also... if I just upgrade my routers to 6.35rc1 will they automatically get rep package or will I need to add it?

-Eric

Eric,
You have to add rep package.

Re: v6.35rc is released, new wireless package!

Posted: Sat Jan 30, 2016 4:28 pm
by plisken
Also... if I just upgrade my routers to 6.35rc1 will they automatically get rep package or will I need to add it?

-Eric
Download the package here http://www.mikrotik.com/download/share/ ... ep_all.zip

Re: v6.35rc is released, new wireless package!

Posted: Sat Jan 30, 2016 5:04 pm
by andriys
What exactly is the "station roaming for station mode" ???
Roaming in WiFi network is a function of client, not AP (AP can assist, but that's the client who always makes the roaming decision). Mikrotik in station mode (i.e. wireless client, not an access point) used to be a very poor roamer. I guess now the situation is going to be better.
Is this the start of seamless roaming?
It is not, I guess.

andreacoppini sent a couple of great posts on the topic of roaming in WiFi networks. Here's the links: first, second.

Re: v6.35rc is released, new wireless package!

Posted: Sat Jan 30, 2016 9:04 pm
by gius64
With new package TCP throughput is really impresive. There is a problem with nv2 connection. Client's can't connect, when protocol is set to nv2, only nstreme and 802.11 works. With nstreme, there is a problem with dynamic framin policy.

I really starting to like what you are doing.Don't stop, and make it better :)
Do you have some numbers? TCP throughput before and after? :D

Re: v6.35rc is released, new wireless package!

Posted: Sat Jan 30, 2016 9:06 pm
by gius64
Yes, wireless-rep is the like cm2, but it has additional features (CAPsMAN will work with the package).
Does it have improvements on point to multipoint with nv2?

Re: v6.35rc is released, new wireless package!

Posted: Sat Jan 30, 2016 11:53 pm
by czolo
NV2 is not working.TCP 40% better than before

Re: v6.35rc is released, new wireless package!

Posted: Sun Jan 31, 2016 3:56 am
by gius64
NV2 is not working.TCP 40% better than before
40% better in 802.11? :shock: Did you test AC?

I tested 802.11ac in a room on SXT 5 ac, 0dBm tx power to don't have too high signal, about 30 meters distance, max 314Mbps iperf TCP between two powerful computers on 80MHz channel :(

Re: v6.35rc is released, new wireless package!

Posted: Sun Jan 31, 2016 2:50 pm
by nkourtzis
NV2 is not working.TCP 40% better than before
40% better in 802.11? :shock: Did you test AC?

I tested 802.11ac in a room on SXT 5 ac, 0dBm tx power to don't have too high signal, about 30 meters distance, max 314Mbps iperf TCP between two powerful computers on 80MHz channel :(

By which measure is this too little? 802.11n would give you 200 Mbps max, under ideal link conditions.

Re: v6.35rc is released, new wireless package!

Posted: Sun Jan 31, 2016 3:09 pm
by Cha0s
I believe the 40% gius64 refers to is the improvement on TCP on the Bandwidth Test tool. Not on NV2.

I can confirm that I see huge improvements on TCP tests.

Running the test on 127.0.0.1 on an quad core atom before 6.34 I would get ~570Mbit.
With 6.34 I now get 3.4Gbit.

Re: v6.35rc is released, new wireless package!

Posted: Sun Jan 31, 2016 6:51 pm
by Zorro
apparently its had updated/new wi-fi drivers aside enteriely new code, based on it.
perhaps ROS7 release with new kernel/toolchain - isn't so far(just guessing ;)
With 6.34 I now get 3.4Gbit.
with "6.35rc1" you mean ?
p.s.
anyone see other improvements ? :)
did NV2 works with older packages?

Re: v6.35rc is released, new wireless package!

Posted: Sun Jan 31, 2016 6:54 pm
by Cha0s
The changes to the Bandwidth Test tool were made on 6.34, so 6.35rc also includes them.
What's new in 6.34 (2016-Jan-29 10:25):
...
*) btest - significantly increased TCP bandwidth test performance;

Re: v6.35rc is released, new wireless package!

Posted: Sun Jan 31, 2016 8:22 pm
by Zorro
ok, good to know, tnx.

Re:

Posted: Sun Jan 31, 2016 9:10 pm
by yottabit
Do we need repeater function? It will be probably easier to configure than wds, maybe it will bring compatibility with other vendor's APs, but do we really need it?
I think this is intended to address what is commonly called WISP mode in other vendors' equipment, where the single radio can operate in AP and Station mode simultaneously. The #1 use case is where one wishes to create a private, firewalled Wi-Fi network with the "WAN" interface being Station Wi-Fi mode to another Wi-Fi network (rather than Ethernet), and without using two radios or connecting two Routerboards back-to-back. This is very help in a hotel environment where one wishes to use, e.g., Chromecast on the in-room TV.

Presently I do just that, using an RB951U and a hAP lite configured back-to-back. The RB951U with its 1W radio connects in Station mode to the hotel, and bridges that connection through Ethernet cable link to the hAP lite which is configured in traditional NAT mode from that Ethernet port, broadcasting a low-powered (50 mW) in-room Wi-Fi network for my own devices and Chromecast. This allows only a single device (computer, phone, or tablet) to get through the Captive Portal for all devices (including Chromecast that isn't capable of navigating through a Captive Portal), and then also having broadcasts available on the Wi-Fi network to make things easier like device-to-device transfers and casting to the Chromecast.

Re: v6.35rc is released, new wireless package!

Posted: Sun Jan 31, 2016 10:19 pm
by czolo
apparently its had updated/new wi-fi drivers aside enteriely new code, based on it.
did NV2 works with older packages?
Yes - you can always enable old cm2, and than nv2 is working.
Througput is really better, than with old wireless package. Even with 802.11 it's better, and especialy in one session TCP test.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 2:48 am
by buckthis
hAP lite: issues with wireless-rep
LOG Message: broken package wireless-rep-6.35rc1-smips.npk
Board Name: hAP lite
Version 6.35rc1 (testing)
Architecture Name: smips
CPU MIPS 24Kc V7.4

I have two hAP lite devices and both produced the same message.

---
no issue with wireless-rep running on a 2011UiAS-2HnD and cAP 2n devices

---
I just noticed the "Routerboard" tab produces no result (empty)
Routerboard
Model
Serial Number
Current Firmware
Upgrade Firmware

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 3:13 am
by chechito
wireless-fp is on way to fading out??

i means cm2 or rep pckages will replace the fp package??

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 3:38 am
by taduikis
-fp doesn't mean Fast Path, if I remember correctly, it's more like Feature pack?

BTW, this wireless-rep package doesn't seem to work in nv2 mode (AP - 912UAG ROS v6.35rc1, CPEs - SXT Lite5/5HPnD v6.19-6.28,6.35rc1). Changing to nstreme - clients reconnect ok, changing to -cm2 - clients reconnect ok. Also I haven't been able to use background scan with scanner, it says something about "function not supported in this state (6)", no matter what device or operation mode. Any info on this?

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 5:05 am
by gius64
-fp doesn't mean Fast Path, if I remember correctly, it's more like Feature pack?

BTW, this wireless-rep package doesn't seem to work in nv2 mode (AP - 912UAG ROS v6.35rc1, CPEs - SXT Lite5/5HPnD v6.19-6.28,6.35rc1). Changing to nstreme - clients reconnect ok, changing to -cm2 - clients reconnect ok. Also I haven't been able to use background scan with scanner, it says something about "function not supported in this state (6)", no matter what device or operation mode. Any info on this?
When you press "Scan" it starts a scan which interrupts the wireless link. You have to stop it and then start a background scan when the link is running, otherwise you'll get that error.

I don't know why, it would be clever to have a Scan button which defaults to background scan, and if you choose to you can interrupt the link and have a more detailed scan...

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 8:33 am
by strods
wireless-fp - wireless package with fast path support and CapsMan1
wireless-cm2 - wireless package with same features as wireless-fp + CapsMan2
wireless-rep - wireless package with same features as wireless-cm2 + additional new features.

We can not simply replace packages because, for example, CapsMan1 is not compatible with CapsMan2.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 9:24 am
by sergejs
wireless repeater configuration can be done by,
setup-repeater command,
/interface wireless setup-repeater

there are parameters:
address -- MAC address of AP to setup repeater for (optional)
ssid -- SSID of AP to setup repeater for (optional)
passphrase -- key to use for AP - if this is specified, command will
just scan for AP and create security profile based on info in beacon and
with this passphrase. If this IS NOT specified, command will do WPS to
find out passphrase.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 10:05 am
by uldis
hAP lite: issues with wireless-rep
LOG Message: broken package wireless-rep-6.35rc1-smips.npk
Board Name: hAP lite
Version 6.35rc1 (testing)
Architecture Name: smips
CPU MIPS 24Kc V7.4

I have two hAP lite devices and both produced the same message.
On hAP lite there is not enough space for this package when you try to install it together with bundle package. You can fist upgrade to v6.35rc1 using bundle package and then install the wireless-rep package if you want to test the rep package feature.
This is a temp solution till we include the -rep package in the bundle package by replacing the old -cm2 package.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 10:37 am
by normis
The repeater mode allows you to make a client and an AP both on the same physical interface. You don't need two interfaces. That is the best about this new feature. It seems some of the above posters missed that.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 11:11 am
by gius64
wireless-fp - wireless package with fast path support and CapsMan1
wireless-cm2 - wireless package with same features as wireless-fp + CapsMan2
wireless-rep - wireless package with same features as wireless-cm2 + additional new features.

We can not simply replace packages because, for example, CapsMan1 is not compatible with CapsMan2.
It would be great to have a list of improvements on different wireless packages. On the forum you always write that wireless-cm2 has improvements while wireless-fp is "legacy", but what are these improvements?
It would be good to know what are your plans about replacing wireless packages to schedule massive upgrades on users!

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 11:18 am
by docmarius
On the DHCP Server/Leases Tab in Winbox, there is no way to get the dynamic leases on top.

And just a reminder - a missing bus field on USB Power reset in Winbox on multi bus systems like the RB922...

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 11:55 am
by andriys
We can not simply replace packages because, for example, CapsMan1 is not compatible with CapsMan2.
It's clear "wireless-fp" is somewhat incompatible with "wireless-cm2". However both of them provide superset of features included in plain old "wireless" (and thus may be considered backwards-compatible with "wireless"). As I understand, "wireless-rep" can also be considered backwards-compatible with "wireless-cm2", but just is not stable enough yet to just replace the latter.

Can you please consider renaming "wireless-cm2" to "wireless"- this way you will ease a lot of pain while upgrading, while still stay compatible with the previous releases. You can do the same with "wireless-rep" later when it stabilizes, provided you do not invent CAPsMANv3 or similar thing that breaks compatibility.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 12:45 pm
by strods
We are considering many ways how we should proceed with these packages.

This is first rc release where we give our wireless-rep package. It will take a while for this package to be considered as stable.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 12:54 pm
by honzam
wireless-rep package.
Name of package wireless-rep is "repeater" ?

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 1:03 pm
by taduikis
Well, I think that "wireless.npk" package should somehow be "default" package that is the latest stable. That way you don't really have to know the sequence and keep tracking what is what. Of course there's issues with compatibility, but you can always have any other package if you need something special or historic?

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 1:08 pm
by normis
wireless-rep means repeater, yes. it also has a new wireless driver and many other new features, so It can't be placed as default yet.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 1:15 pm
by taduikis
Sure it can't. As I mentioned above, I had a problem where 6.35rc1 AP with -rep package in NV2 didn't work.
wireless-rep means repeater, yes. it also has a new wireless driver and many other new features, so It can't be placed as default yet.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 1:21 pm
by czolo
Is there any chance for working sniffer or snooper similiar to scan? Background sniffing will be very useful.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 2:39 pm
by honzam
How to run background scan? Example?

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 2:47 pm
by ivicask
The repeater mode allows you to make a client and an AP both on the same physical interface. You don't need two interfaces. That is the best about this new feature. It seems some of the above posters missed that.
Can you give some more details how to exactly setup this, i tried entering just /interface wireless setup-repeater and got "no such item (4)".

I have 2.4ghz Metal 2SHPn, its currently set in WISP mode(AP BRIDGE).But i have nearby WIFI network to which i would want to connect at the same time.

I upgraded to new package and its enabled in packages list.

Any help how to run this scenario?

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 2:51 pm
by pukkita
I wonder if its intended to provide spectral scan/history support in the future for the AC chipsets within this new package?

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 2:54 pm
by czolo
hotspot - fixed login by mac-cookie when roaming among hotspot servers

How it works? Can I distribute MAC-cookie to another router?

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 3:32 pm
by strods
New wireless-rep package now can be found under extra packages at our download site (choose release candidate 6.35rcX):
http://www.mikrotik.com/download

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 3:57 pm
by soulflyhigh
-fp doesn't mean Fast Path, if I remember correctly, it's more like Feature pack?

BTW, this wireless-rep package doesn't seem to work in nv2 mode (AP - 912UAG ROS v6.35rc1, CPEs - SXT Lite5/5HPnD v6.19-6.28,6.35rc1). Changing to nstreme - clients reconnect ok, changing to -cm2 - clients reconnect ok. Also I haven't been able to use background scan with scanner, it says something about "function not supported in this state (6)", no matter what device or operation mode. Any info on this?
When you press "Scan" it starts a scan which interrupts the wireless link. You have to stop it and then start a background scan when the link is running, otherwise you'll get that error.

I don't know why, it would be clever to have a Scan button which defaults to background scan, and if you choose to you can interrupt the link and have a more detailed scan...

I have the same problem, background scan doesn't work even from terminal ...
/interface wireless> scan 0 background=yes 
failure: background scan not supported in this state
It doesn't work from winbox 3.1 with this method
When you press "Scan" it starts a scan which interrupts the wireless link. You have to stop it and then start a background scan when the link is running, otherwise you'll get that error.
- I'm getting the same error "Couldn't start-background scan not supported in this state(6)"

Also, Nv2 doesnt work with this rep package, period.
Mikrotik guys, any comment regarding those issues?

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 3:57 pm
by abis
How to run background scan? Example?
background-scan.PNG
A nice feature :D

v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 4:04 pm
by jarda
Not tried it yet. But can we join two APs in repeater mode to be mutually AP and client on both ways together each to the other? Just curious of it...

Like we have multiple virtual AP, will we see also multiclient repeater mode one day?

(don't take it seriously too much, just playing with the ideas)

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 4:09 pm
by strods
Version 6.35rc2 has been released.

Changes since 6.35rc1:
*) chr - fixed high rate limitation;
*) ippool6 - fix potential crash;
*) routing - fixed rare kernel failure on different dynamic routing configurations;
*) wireless-rep - fix nv2 protocol.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 4:26 pm
by lelmus
Wow! This new wireless-rep is fantastic! All my UDP packets are consistent, I have not lost a single packet! Amazing work guys!

Re: Re:

Posted: Mon Feb 01, 2016 4:28 pm
by WirelessRudy
ok, mikrotik thinks it will rise sales on consumer market, so that is it.
I know what would not as much rise but prevent from falling: improvement of current and future WiFi software or hardware. It becomes uncompetitive with todays user demand and trends :( and there's already a list of inventions made. Because currently 4g lte provides numbers which majority of users only care of, and they even justify unresponsiveness, high lag and other related problems.. We desperately need to increase sector capacity, since currently I don't get more than 30M total with 20-30 clients connected. And whats worse, I can't even experiment and seek for best config, they feel shortages of service and immediately start looking who to kill. And I'm not joking, even at 4-5 AM there's no total freedom for that recently.

I understand that with overcrowded 5GHz there's no chance to get what you could with multi-band licensed freq and insane tx powers, but based on what 11n/ac competitors offer, it's certainly not impossible to at least double the mentioned figure, which would be a life saver. For a while.

I might be naive, but I really hope something new and revolutionary might appear with these new wireless-smth packages every time they are introduced. Heck, I'd at least take changelog entries like "improved nv2 performance" :)
I'm with you :D I really hope MikroTik will introduce something new on wireless for point to multipoint!
And here's another one...

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 4:46 pm
by soulflyhigh
Version 6.35rc2 has been released.

Changes since 6.35rc1:
*) chr - fixed high rate limitation;
*) ippool6 - fix potential crash;
*) routing - fixed rare kernel failure on different dynamic routing configurations;
*) wireless-rep - fix nv2 protocol.
- nv2 protocol seems to work now (clients can connect now at AP with nv2 - mipsbe rep 6.35rc2)

- background scan doesn't work yet (tested on QRT-5), the same "state(6)" message appears... can anyone confirm that this feature works at all and show us some working example of it?

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 4:52 pm
by ivicask
Version 6.35rc2 has been released.

Changes since 6.35rc1:
*) chr - fixed high rate limitation;
*) ippool6 - fix potential crash;
*) routing - fixed rare kernel failure on different dynamic routing configurations;
*) wireless-rep - fix nv2 protocol.
- nv2 protocol seems to work now (clients can connect now at AP with nv2 - mipsbe rep 6.35rc2)

- background scan doesn't work yet (tested on QRT-5), the same "state(6)" message appears... can anyone confirm that this feature works at all and show us some working example of it?
Background scan worked since first version for me, simple tick background scan option, my clients didint lost connection, and my AP showed other WIFI networks in range, if thats whats not working for you.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 5:23 pm
by soulflyhigh
@ ivicask
Yes, that doesn't work for me on two different AP...
1st step - open wlan and click "Scan..." button (i've tried it on QRT-5 and RB433AH with UB5 wlan card)
2nd step - "regular" scan runs automatically and all clients loose connection to AP
3rd step - I stop scan by clicking on "Stop" button and tick "background scan" option
4th step - Then I click on "Scan" button in "Scanner" window and I'm always getting that "Couldn't start-background scan not supported in this state(6)" error message no matter what I do.... any ideas?

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 6:27 pm
by ivicask
@ ivicask
Yes, that doesn't work for me on two different AP...
1st step - open wlan and click "Scan..." button (i've tried it on QRT-5 and RB433AH with UB5 wlan card)
2nd step - "regular" scan runs automatically and all clients loose connection to AP
3rd step - I stop scan by clicking on "Stop" button and tick "background scan" option
4th step - Then I click on "Scan" button in "Scanner" window and I'm always getting that "Couldn't start-background scan not supported in this state(6)" error message no matter what I do.... any ideas?
Works on 2SHPN, in what mode is your routers now?Mine is AP Bridge, maybe doesnt work in some other modes, or just doesnt work on this models you have in general.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 8:16 pm
by soulflyhigh
@ivicask
It is in AP bridge mode... I tried with setting it as station, with nv2 and nstreme, tried to connect to them from different winbox/ PC... the same thing happens.
Don't think I've any 2SHPN in my network to test it (99% equipment in our network does work on 5GHz band, the rest are old R52s with sector 2.4GHz antennas).

Does anybody else have this problem with background scan?

Just for basics check - I installed latest RouterOS 6.35rc2 (download & install through winbox),
then manually downloaded wlan rep package for mipsbe from mikrotik site to my pc, uploaded it to those two routers, rebooted them again and then tried new features - I did things like that a million times before.
Background scan just won't work.
Bizarre.

This is how it looks with station mode :
scr1.PNG

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 9:00 pm
by ivicask
@ivicask
It is in AP bridge mode... I tried with setting it as station, with nv2 and nstreme, tried to connect to them from different winbox/ PC... the same thing happens.
Don't think I've any 2SHPN in my network to test it (99% equipment in our network does work on 5GHz band, the rest are old R52s with sector 2.4GHz antennas).

Does anybody else have this problem with background scan?

Just for basics check - I installed latest RouterOS 6.35rc2 (download & install through winbox),
then manually downloaded wlan rep package for mipsbe from mikrotik site to my pc, uploaded it to those two routers, rebooted them again and then tried new features - I did things like that a million times before.
Background scan just won't work.
Bizarre.

This is how it looks with station mode :
scr1.PNG
Yea, seams you did all good, btw i just tested this on all models we have in our company and for me its working on this models.

RB911G-5HPnD
RB2011UiAS-2HnD
RBcAP2n
2SHPn

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 9:25 pm
by yottabit
wireless-rep means repeater, yes. it also has a new wireless driver and many other new features, so It can't be placed as default yet.
I would propose a new wireless package for testing should just be called something such as "wireless-test", and stable wireless packages should be called, e.g., "wirelessV1" (wireless), "wirelessV2" (wireless-fp), "wirelessV3" (wireless-cm2), and eventually "wirelessV4" (stable version of today's wireless-rep or wireless-test).

This makes it clear the upgrade path for additional functionality, and makes it clear there are backward-incompatible changes with each "V" version increment of the package.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 9:28 pm
by yottabit
The repeater mode allows you to make a client and an AP both on the same physical interface. You don't need two interfaces. That is the best about this new feature. It seems some of the above posters missed that.
Hi Normis,

What is required to have this work? Should only Virtual interfaces be used? Or main/physical interface set to Station mode and add Virtual AP to that?

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 10:05 pm
by ivicask
The repeater mode allows you to make a client and an AP both on the same physical interface. You don't need two interfaces. That is the best about this new feature. It seems some of the above posters missed that.
Hi Normis,

What is required to have this work? Should only Virtual interfaces be used? Or main/physical interface set to Station mode and add Virtual AP to that?
I tried that and it didint work, virtual interfaces can be set to station, but they cant scan for networks..

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 10:08 pm
by uldis
background scan and repeater function can only work when wireless interface is running 802.11 wireless protocol.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 10:10 pm
by yottabit
I tried that and it didint work, virtual interfaces can be set to station, but they cant scan for networks..
Did you try my second thought? Setting the main physical interface to Station and then adding a Virtual AP on top?

I gave away my test RBs recently so I don't have any extras I can use to test this. I've been waiting for the hAP ac to finally be available to buy a couple to use for test devices.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 01, 2016 10:18 pm
by ivicask
background scan and repeater function can only work when wireless interface is running 802.11 wireless protocol.
I was running 802.11, background scan works for me, but im unable to connect to another WIFI AP while its set to AP mode, or dont know how to..

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 12:33 am
by honzam
background scan can only work when wireless interface is running 802.11 wireless protocol.
Very nice feature! Works well. :) No disconnect clients during sken.
Will be supported in future with NV2 protocol?

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 12:42 am
by PeterDoBrasil
wireless repeater configuration can be done by,
setup-repeater command,
/interface wireless setup-repeater

there are parameters:
address -- MAC address of AP to setup repeater for (optional)
ssid -- SSID of AP to setup repeater for (optional)
passphrase -- key to use for AP - if this is specified, command will
just scan for AP and create security profile based on info in beacon and
with this passphrase. If this IS NOT specified, command will do WPS to
find out passphrase.


New terminal says
[admin@MikroTik] > /interface wireless setup-repeater address="4C:5E:0C:C4:41:BF" ssid="5g.net 1";
no such item (4)

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 9:58 am
by djdrastic
It's great to see MTK tackling some new wireless features.
Wireless often felt neglected in the MTK stable.
Any chance we'll see any NV2 AC improvements going forward ?

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 10:11 am
by soulflyhigh
background scan and repeater function can only work when wireless interface is running 802.11 wireless protocol.
*) wireless-rep - initial support for station roaming for station mode in 802.11 protocol;
*) wireless-rep - added support for wireless repeater mode for 802.11 protocol;
*) wireless-rep - added support for wireless background scan;

Thanks for clarification, please correct this in the changelog.
Are there any plans for adding background scan feature for nstreme/nv2 ?

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 10:45 am
by taduikis
You could have said that in the begining :( I've spent an hour or so and thought I was doing something wrong. I haven't got a single AP running in plain 802.11, only in SOHO routers.. So no new function for me :( anyway nice to see something being done.

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 2:00 pm
by WirelessRudy
Is the default authenticate option gone? Is client now always to connect to units mentioned in the 'Connect List'?
Def-auth missing.PNG
Can someone also explain when, and what, the Multicast Helper options do and the two new tickboxes might bring me for use....?

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 2:23 pm
by andriys
Can someone also explain when, and what, the Multicast Helper options do and the two new tickboxes might bring me for use....?
Multicast helper option is described here.

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 3:56 pm
by PeterDoBrasil
Is this config the right way?
first interface wireless - ap-bridge
second inteface wireless (virtual) - station pseudobridge
what is the right setup from wds in station pseudobridge? disabled? or static with wds default bridge set to bridge?
For now I think this Setup is much estable as the old WDS configuration? :lol:
Iám using 912UAG-2HPnD Basebox with two Antenas Omni 15 dbi !
My Question is why the AP Interface do not show traffic = the station Interface?

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 4:51 pm
by uldis
PeterDoBrasil, the configuration is ok. there is no need to WDS as this virtual wireless station interface works without WDS.

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 5:03 pm
by PeterDoBrasil
My Hotspot Stops to work correctly! Is this an Address translation prolem because the new pseudobridge setup?


# feb/ 2/2016 11:59:12 by RouterOS 6.34
# software id = KPNX-1FGN
#
11:28:15 system,info router rebooted
11:28:23 script,error Google Down
11:28:23 script,error 5g.net 1 Down
11:28:23 script,error 5g.net 2 Down
11:28:25 hotspot,debug Hotspot: bypassed host 08:2E:5F:75:6C:56/10.63.192.255 added, ip 10.63.192.255
11:28:25 hotspot,debug Hotspot: bypassed host 4C:5E:0C:CA:05:46/10.63.192.3 added, ip 10.63.192.3
11:28:25 hotspot,debug Hotspot: bypassed host 4C:5E:0C:C4:53:F7/10.63.192.4 added, ip 10.63.192.4
11:28:25 hotspot,debug Hotspot: bypassed host 5C:C9:D3:0D:D1:AD/10.63.192.254 added, ip 10.63.192.254
11:28:25 hotspot,debug Hotspot: bypassed host 4C:5E:0C:C4:41:BE/10.63.192.2 added, ip 10.63.192.2
11:28:25 hotspot,debug Hotspot: bypassed host 4C:5E:0C:C4:4D:F9/10.63.192.5 added, ip 10.63.192.5
11:28:26 interface,info eth1 link up (speed 100M, full duplex)
11:28:26 interface,info eth2 link up (speed 1G, full duplex)
11:28:26 interface,info eth9 link up (speed 100M, full duplex)
11:28:26 dhcp,info dhcp-client on eth1 got IP address 192.168.33.2
11:28:27 interface,info eth7 link up
11:28:28 dhcp,info switch2 deassigned 172.16.0.2 from 3C:E5:B4:0D:0D:27
11:28:28 dhcp,info switch2 assigned 172.16.0.2 to 3C:E5:B4:0D:0D:27
11:28:29 hotspot,debug Hotspot: bypassed host 10.63.192.255 moved to bridge port <eth2> from <<none>>
11:28:30 wireless,info 94:51:03:D3:B6:B8@wlan: connected
11:28:58 dhcp,info Hotspot assigned 10.63.192.253 to 94:51:03:D3:B6:B8
11:28:58 hotspot,debug Hotspot: new host detected 94:51:03:D3:B6:B8/10.63.192.253 by UDP :26098 -> 10.63.192.1:53
11:28:58 hotspot,debug Hotspot: static host 94:51:03:D3:B6:B8/10.63.192.253 added, ip 10.63.192.253
11:28:59 system,info,account user ersitizastes logged in from 10.63.192.255 via winbox
11:29:00 script,warning Google Up
11:29:29 system,info device changed by ersitizastes
11:29:31 interface,info eth10 link up (speed 100M, full duplex)
11:29:53 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by UDP :53828 -> 10.63.192.1:53
11:29:53 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:29:57 hotspot,debug Hotspot: bypassed host 10.63.192.3 moved to bridge port <eth10> from <<none>>
11:29:57 hotspot,debug Hotspot: new host detected 34:FC:EF:CF:50:24/10.63.193.76 by UDP :11266 -> 10.63.192.1:53
11:29:57 hotspot,debug Hotspot: dynamic host 34:FC:EF:CF:50:24/10.63.193.76 added, ip 10.63.193.76
11:29:59 hotspot,debug Hotspot: bypassed host 10.63.192.2 moved to bridge port <eth10> from <<none>>
11:30:00 system,info hotspot user profile 00 changed by ersitizastes
11:30:00 system,info,account user ersitizastes logged out from 10.63.192.255 via winbox
11:30:25 script,warning 5g.net 1 Up
11:30:35 dhcp,info Hotspot assigned 10.63.193.75 to 60:72:0D:39:1F:9A
11:30:41 dhcp,info Hotspot assigned 10.63.193.74 to F8:95:C7:CF:4F:AF
11:30:44 hotspot,debug Hotspot: new host detected F8:95:C7:CF:4F:AF/10.63.193.74 by UDP :18710 -> 10.63.192.1:53
11:30:44 hotspot,debug Hotspot: dhcp host F8:95:C7:CF:4F:AF/10.63.193.74 added, ip 10.63.193.74
11:30:47 wireless,info 94:51:03:D3:B6:B8@wlan: disconnected, extensive data loss
11:30:58 hotspot,debug Hotspot: static host 10.63.192.253 removed: login timeout
11:31:00 script,warning 5g.net 2 Up
11:31:01 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by UDP :14001 -> 10.63.192.1:53
11:31:01 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:31:44 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by UDP :18764 -> 10.63.192.1:53
11:31:44 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.46, ip 10.63.193.46: max addresses per mac is reached
11:31:48 dhcp,info Hotspot assigned 10.63.193.46 to F8:A9:D0:5E:6A:9F
11:31:54 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:31:57 hotspot,debug Hotspot: dynamic host 10.63.193.76 removed: login timeout
11:31:59 hotspot,debug Hotspot: new host detected 34:FC:EF:CF:50:24/10.63.193.76 by UDP :41705 -> 10.63.192.1:53
11:31:59 hotspot,debug Hotspot: dynamic host 34:FC:EF:CF:50:24/10.63.193.76 added, ip 10.63.193.76
11:32:01 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:32:04 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:32:06 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:32:07 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:32:08 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:32:10 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:32:10 wireless,info 94:51:03:D3:B6:B8@wlan: connected
11:32:12 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by UDP :41167 -> 10.63.192.1:53
11:32:12 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:32:13 hotspot,debug Hotspot: new host detected 94:51:03:D3:B6:B8/10.63.192.253 by TCP :34668 -> 74.125.141.188:5228
11:32:13 hotspot,debug Hotspot: static host 94:51:03:D3:B6:B8/10.63.192.253 added, ip 10.63.192.253
11:32:14 dhcp,info Hotspot assigned 10.63.193.45 to 14:32:D1:1C:E1:6E
11:32:15 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.45 by UDP :40340 -> 10.63.192.1:53
11:32:15 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.45, ip 10.63.193.43: max addresses per mac is reached
11:32:24 dhcp,info Hotspot assigned 10.63.193.42 to 3C:18:9F:33:05:31
11:32:44 hotspot,debug Hotspot: dhcp host 10.63.193.74 removed: login timeout
11:32:45 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by UDP :54175 -> 10.63.192.1:53
11:32:45 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.46, ip 10.63.193.43: max addresses per mac is reached
11:32:49 dhcp,info Hotspot deassigned 10.63.193.46 from F8:A9:D0:5E:6A:9F
11:33:06 dhcp,info Hotspot assigned 10.63.193.40 to 44:91:DB:51:5E:EB
11:33:06 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.42 by UDP :60411 -> 10.63.192.1:53
11:33:06 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.42, ip 10.63.193.43: max addresses per mac is reached
11:33:11 dhcp,info Hotspot assigned 10.63.193.41 to 30:19:66:27:D9:9F
11:33:12 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :63309 -> 10.63.192.1:53
11:33:12 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.41, ip 10.63.193.43: max addresses per mac is reached
11:33:13 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by UDP :34466 -> 10.63.192.1:53
11:33:13 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:33:37 dhcp,info Hotspot assigned 10.63.193.39 to 88:9B:39:D0:AB:19
11:33:38 hotspot,debug Hotspot: new host detected 88:9B:39:D0:AB:19/10.63.193.39 by UDP :19652 -> 10.63.192.1:53
11:33:38 hotspot,debug Hotspot: dhcp host 88:9B:39:D0:AB:19/10.63.193.39 added, ip 10.63.193.39
11:33:59 hotspot,debug Hotspot: dynamic host 10.63.193.76 removed: login timeout
11:34:12 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :13730 -> 10.63.192.1:53
11:34:12 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.41, ip 10.63.193.43: max addresses per mac is reached
11:34:13 hotspot,debug Hotspot: static host 10.63.192.253 removed: login timeout
11:34:17 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by TCP :43245 -> 108.168.176.243:80
11:34:17 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:34:54 dhcp,info Hotspot assigned 10.63.193.50 to 18:22:7E:2A:5A:5E
11:35:08 dhcp,info Hotspot deassigned 10.63.193.50 from 18:22:7E:2A:5A:5E
11:35:13 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :51145 -> 10.63.192.1:53
11:35:13 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.41, ip 10.63.193.43: max addresses per mac is reached
11:35:15 dhcp,info Hotspot assigned 10.63.193.60 to 00:9F:08:01:5A:11
11:35:31 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by UDP :59871 -> 10.63.192.1:53
11:35:31 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:35:31 hotspot,debug Hotspot: new host detected 34:FC:EF:CF:50:24/100.64.13.255 by TCP :60463 -> 216.58.222.106:443
11:35:31 hotspot,debug Hotspot: dynamic host 34:FC:EF:CF:50:24/100.64.13.255 added, ip 10.63.193.76
11:35:32 hotspot,debug Hotspot: new host detected 34:FC:EF:CF:50:24/10.63.193.76 by UDP :31887 -> 10.63.192.1:53
11:35:32 hotspot,debug Hotspot: failed to add dynamic host 34:FC:EF:CF:50:24/10.63.193.76, ip 10.63.193.76: to-address is already used
11:35:35 hotspot,debug Hotspot: new host detected 94:51:03:D3:B6:B8/10.63.192.253 by TCP :45967 -> 74.125.141.188:5228
11:35:35 hotspot,debug Hotspot: static host 94:51:03:D3:B6:B8/10.63.192.253 added, ip 10.63.192.253
11:35:38 hotspot,debug Hotspot: dhcp host 10.63.193.39 removed: login timeout
11:36:16 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :33412 -> 10.63.192.1:53
11:36:16 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.41, ip 10.63.193.43: max addresses per mac is reached
11:36:33 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by TCP :41661 -> 158.85.58.15:5222
11:36:33 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:36:33 hotspot,debug Hotspot: new host detected 34:FC:EF:CF:50:24/10.63.193.76 by UDP :21894 -> 10.63.192.1:53
11:36:33 hotspot,debug Hotspot: failed to add dynamic host 34:FC:EF:CF:50:24/10.63.193.76, ip 10.63.193.76: to-address is already used
11:36:54 dhcp,info Hotspot assigned 10.63.193.38 to 00:F4:6F:F6:0A:DF
11:36:56 hotspot,debug Hotspot: new host detected 00:F4:6F:F6:0A:DF/10.63.193.38 by UDP :36811 -> 10.63.192.1:53
11:36:56 hotspot,debug Hotspot: dhcp host 00:F4:6F:F6:0A:DF/10.63.193.38 added, ip 10.63.193.38
11:37:21 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :34072 -> 10.63.192.1:53
11:37:21 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.41, ip 10.63.193.43: max addresses per mac is reached
11:37:31 hotspot,debug Hotspot: dynamic host 10.63.193.76 removed: login timeout
11:37:33 hotspot,debug Hotspot: new host detected 34:FC:EF:CF:50:24/10.63.193.76 by UDP :1169 -> 10.63.192.1:53
11:37:33 hotspot,debug Hotspot: dynamic host 34:FC:EF:CF:50:24/10.63.193.76 added, ip 10.63.193.76
11:37:34 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by TCP :50139 -> 174.36.210.48:80
11:37:34 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:37:35 hotspot,debug Hotspot: static host 10.63.192.253 removed: login timeout
11:37:53 dhcp,info Hotspot assigned 10.63.193.46 to F8:A9:D0:5E:6A:9F
11:37:54 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by UDP :1405 -> 10.63.192.1:53
11:37:54 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.46, ip 10.63.193.43: max addresses per mac is reached
11:38:21 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :12764 -> 10.63.192.1:53
11:38:21 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.41, ip 10.63.193.43: max addresses per mac is reached
11:38:40 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by TCP :58368 -> 173.192.222.176:5222
11:38:40 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:38:54 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by UDP :43736 -> 10.63.192.1:53
11:38:54 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.46, ip 10.63.193.43: max addresses per mac is reached
11:38:56 hotspot,debug Hotspot: dhcp host 10.63.193.38 removed: login timeout
11:39:22 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :59533 -> 10.63.192.1:53
11:39:22 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.41, ip 10.63.193.43: max addresses per mac is reached
11:39:31 wireless,info 94:51:03:D3:B6:B8@wlan: disconnected, extensive data loss
11:39:33 hotspot,debug Hotspot: dynamic host 10.63.193.76 removed: login timeout
11:39:40 hotspot,debug Hotspot: new host detected 34:FC:EF:CF:50:24/10.63.193.76 by UDP :4063 -> 10.63.192.1:53
11:39:40 hotspot,debug Hotspot: dynamic host 34:FC:EF:CF:50:24/10.63.193.76 added, ip 10.63.193.76
11:39:41 dhcp,info Hotspot assigned 10.63.193.37 to 34:FC:EF:CF:50:24
11:39:45 hotspot,debug Hotspot: new host detected 34:FC:EF:CF:50:24/10.63.193.37 by UDP :9080 -> 10.63.192.1:53
11:39:45 hotspot,debug Hotspot: dynamic host 10.63.193.76 removed: limiting addresses per mac
11:39:45 hotspot,debug Hotspot: dhcp host 34:FC:EF:CF:50:24/10.63.193.37 added, ip 10.63.193.37
11:39:56 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by UDP :48853 -> 10.63.192.1:53
11:39:56 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.46, ip 10.63.193.43: max addresses per mac is reached
11:40:26 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :28569 -> 10.63.192.1:53
11:40:26 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.41, ip 10.63.193.43: max addresses per mac is reached
11:40:35 dhcp,info Hotspot assigned 10.63.193.36 to 9C:D3:5B:51:B7:AE
11:40:36 hotspot,debug Hotspot: new host detected 9C:D3:5B:51:B7:AE/10.63.193.36 by UDP :39596 -> 10.63.192.1:53
11:40:36 hotspot,debug Hotspot: dhcp host 9C:D3:5B:51:B7:AE/10.63.193.36 added, ip 10.63.193.36
11:40:51 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by UDP :49592 -> 10.63.192.1:53
11:40:51 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:41:01 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by UDP :38436 -> 10.63.192.1:53
11:41:01 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.46, ip 10.63.193.43: max addresses per mac is reached
11:41:10 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:41:28 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :30119 -> 10.63.192.1:53
11:41:28 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.41, ip 10.63.193.43: max addresses per mac is reached
11:41:45 hotspot,debug Hotspot: dhcp host 10.63.193.37 removed: login timeout
11:41:45 hotspot,debug Hotspot: new host detected 34:FC:EF:CF:50:24/10.63.193.37 by UDP :36887 -> 10.63.192.1:53
11:41:45 hotspot,debug Hotspot: dhcp host 34:FC:EF:CF:50:24/10.63.193.37 added, ip 10.63.193.37
11:42:04 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by UDP :31373 -> 10.63.192.1:53
11:42:04 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:42:10 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:42:21 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:42:21 wireless,info 94:51:03:D3:B6:B8@wlan: connected
11:42:26 hotspot,debug Hotspot: new host detected 94:51:03:D3:B6:B8/10.63.192.253 by UDP :34378 -> 10.63.192.1:53
11:42:26 hotspot,debug Hotspot: static host 94:51:03:D3:B6:B8/10.63.192.253 added, ip 10.63.192.253
11:42:26 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by UDP :6429 -> 10.63.192.1:53
11:42:26 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.46, ip 10.63.193.43: max addresses per mac is reached
11:42:36 hotspot,debug Hotspot: dhcp host 10.63.193.36 removed: login timeout
11:43:04 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :63921 -> 10.63.192.1:53
11:43:04 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.41, ip 10.63.193.43: max addresses per mac is reached
11:43:07 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by UDP :56948 -> 10.63.192.1:53
11:43:07 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:43:45 hotspot,debug Hotspot: dhcp host 10.63.193.37 removed: login timeout
11:43:46 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by UDP :3360 -> 10.63.192.1:53
11:43:46 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.46, ip 10.63.193.43: max addresses per mac is reached
11:43:57 hotspot,debug Hotspot: new host detected 34:FC:EF:CF:50:24/10.63.193.37 by UDP :59609 -> 10.63.192.1:53
11:43:57 hotspot,debug Hotspot: dhcp host 34:FC:EF:CF:50:24/10.63.193.37 added, ip 10.63.193.37
11:44:05 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :27895 -> 10.63.192.1:53
11:44:05 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.41, ip 10.63.193.43: max addresses per mac is reached
11:44:08 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by UDP :65040 -> 10.63.192.1:53
11:44:08 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:44:26 hotspot,debug Hotspot: static host 10.63.192.253 removed: login timeout
11:44:31 hotspot,debug Hotspot: new host detected 94:51:03:D3:B6:B8/10.63.192.253 by UDP :65422 -> 10.63.192.1:53
11:44:31 hotspot,debug Hotspot: static host 94:51:03:D3:B6:B8/10.63.192.253 added, ip 10.63.192.253
11:44:38 dhcp,info Hotspot assigned 10.63.193.34 to B8:5A:73:A8:5B:84
11:44:41 hotspot,debug Hotspot: new host detected B8:5A:73:A8:5B:84/10.63.193.34 by UDP :51462 -> 10.63.192.1:53
11:44:41 hotspot,debug Hotspot: dhcp host B8:5A:73:A8:5B:84/10.63.193.34 added, ip 10.63.193.34
11:44:48 wireless,info 94:51:03:D3:B6:B8@wlan: disconnected, extensive data loss
11:44:50 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:44:51 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:44:55 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:45:00 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:45:01 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by UDP :64102 -> 10.63.192.1:53
11:45:01 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.46, ip 10.63.193.43: max addresses per mac is reached
11:45:05 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:45:07 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :27505 -> 10.63.192.1:53
11:45:07 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.41, ip 10.63.193.43: max addresses per mac is reached
11:45:10 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:45:10 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by UDP :44628 -> 10.63.192.1:53
11:45:10 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:45:11 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:45:12 wireless,info wlan: data from unknown device 94:51:03:D3:B6:B8, sent deauth
11:45:57 hotspot,debug Hotspot: dhcp host 10.63.193.37 removed: login timeout
11:45:59 hotspot,debug Hotspot: new host detected 34:FC:EF:CF:50:24/10.63.193.37 by TCP :55573 -> 216.58.202.42:443
11:45:59 hotspot,debug Hotspot: dhcp host 34:FC:EF:CF:50:24/10.63.193.37 added, ip 10.63.193.37
11:46:08 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :26897 -> 10.63.192.1:53
11:46:08 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.41, ip 10.63.193.43: max addresses per mac is reached
11:46:13 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by UDP :26195 -> 10.63.192.1:53
11:46:13 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:46:20 hotspot,debug Hotspot: new host detected F8:95:C7:CF:4F:AF/10.63.193.74 by UDP :50490 -> 10.63.192.1:53
11:46:20 hotspot,debug Hotspot: dhcp host F8:95:C7:CF:4F:AF/10.63.193.74 added, ip 10.63.193.74
11:46:22 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by UDP :25845 -> 10.63.192.1:53
11:46:22 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.46, ip 10.63.193.43: max addresses per mac is reached
11:46:31 hotspot,debug Hotspot: static host 10.63.192.253 removed: login timeout
11:46:41 hotspot,debug Hotspot: dhcp host 10.63.193.34 removed: login timeout
11:46:53 system,info,account user ersitizastes logged in from 10.63.192.255 via winbox
11:47:08 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :13439 -> 10.63.192.1:53
11:47:08 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.41, ip 10.63.193.43: max addresses per mac is reached
11:47:16 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by TCP :40428 -> 158.85.58.105:5222
11:47:16 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:47:23 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by TCP :52470 -> 158.85.58.11:5222
11:47:23 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.46, ip 10.63.193.43: max addresses per mac is reached
11:47:26 dhcp,info Hotspot assigned 10.63.193.172 to F4:F1:E1:1E:3A:2C
11:47:33 hotspot,debug Hotspot: new host detected F4:F1:E1:1E:3A:2C/10.63.193.172 by UDP :37541 -> 10.63.192.1:53
11:47:33 hotspot,debug Hotspot: dhcp host F4:F1:E1:1E:3A:2C/10.63.193.172 added, ip 10.63.193.172
11:47:59 hotspot,debug Hotspot: dhcp host 10.63.193.37 removed: login timeout
11:48:10 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :19285 -> 10.63.192.1:53
11:48:10 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.41, ip 10.63.193.43: max addresses per mac is reached
11:48:17 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by TCP :55889 -> 173.192.222.169:80
11:48:17 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:48:20 hotspot,debug Hotspot: dhcp host 10.63.193.74 removed: login timeout
11:48:24 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by UDP :65450 -> 10.63.192.1:53
11:48:24 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.46, ip 10.63.193.43: max addresses per mac is reached
11:49:04 hotspot,debug Hotspot: new host detected 34:FC:EF:CF:50:24/10.63.193.37 by UDP :32891 -> 10.63.192.1:53
11:49:04 hotspot,debug Hotspot: dhcp host 34:FC:EF:CF:50:24/10.63.193.37 added, ip 10.63.193.37
11:49:10 hotspot,debug Hotspot: new host detected F8:95:C7:CF:4F:AF/10.63.193.74 by UDP :31988 -> 8.8.8.8:53
11:49:10 hotspot,debug Hotspot: dhcp host F8:95:C7:CF:4F:AF/10.63.193.74 added, ip 10.63.193.74
11:49:19 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by TCP :51064 -> 173.193.230.112:5222
11:49:19 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.106, ip 10.63.193.106: max addresses per mac is reached
11:49:20 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :30275 -> 10.63.192.1:53
11:49:20 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.41, ip 10.63.193.43: max addresses per mac is reached
11:49:27 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by TCP :54487 -> 158.85.58.47:80
11:49:27 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.46, ip 10.63.193.43: max addresses per mac is reached
11:49:33 hotspot,debug Hotspot: dhcp host 10.63.193.172 removed: login timeout
11:49:49 hotspot,debug Hotspot: new host detected F4:F1:E1:1E:3A:2C/10.63.193.172 by TCP :40155 -> 216.58.222.14:80
11:49:49 hotspot,debug Hotspot: dhcp host F4:F1:E1:1E:3A:2C/10.63.193.172 added, ip 10.63.193.172
11:50:21 system,info hotspot server Hotspot changed by ersitizastes
11:50:23 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by UDP :46256 -> 10.63.192.1:53
11:50:23 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.106 added, ip 10.63.193.106
11:50:58 dhcp,info Hotspot assigned 10.63.193.50 to 18:22:7E:2A:5A:5E
11:50:58 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.50 by UDP :41457 -> 10.63.192.1:53
11:50:58 hotspot,debug Hotspot: dynamic host 10.63.193.106 removed: limiting addresses per mac
11:50:58 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.50 added, ip 10.63.193.43
11:51:04 hotspot,debug Hotspot: dhcp host 10.63.193.37 removed: login timeout
11:51:04 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by UDP :54443 -> 10.63.192.1:53
11:51:04 hotspot,debug Hotspot: dynamic host 10.63.193.43 removed: limiting addresses per mac
11:51:04 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.106 added, ip 10.63.193.106
11:51:04 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by UDP :16757 -> 10.63.192.1:53
11:51:04 hotspot,debug Hotspot: dynamic host 10.63.193.106 removed: limiting addresses per mac
11:51:04 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.46 added, ip 10.63.193.43
11:51:04 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.50 by UDP :18646 -> 10.63.192.1:53
11:51:04 hotspot,debug Hotspot: dynamic host 10.63.193.43 removed: limiting addresses per mac
11:51:04 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.50 added, ip 10.63.193.30
11:51:05 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by UDP :57375 -> 10.63.192.1:53
11:51:05 hotspot,debug Hotspot: dynamic host 10.63.193.30 removed: limiting addresses per mac
11:51:05 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.46 added, ip 10.63.193.43
11:51:05 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.50 by TCP :42518 -> 192.12.31.106:5228
11:51:05 hotspot,debug Hotspot: dynamic host 10.63.193.43 removed: limiting addresses per mac
11:51:05 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.50 added, ip 10.63.193.30
11:51:06 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by UDP :48778 -> 10.63.192.1:53
11:51:06 hotspot,debug Hotspot: dynamic host 10.63.193.30 removed: limiting addresses per mac
11:51:06 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.46 added, ip 10.63.193.29
11:51:06 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.50 by UDP :12765 -> 10.63.192.1:53
11:51:06 hotspot,debug Hotspot: dynamic host 10.63.193.29 removed: limiting addresses per mac
11:51:06 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.50 added, ip 10.63.193.30
11:51:06 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.46 by UDP :46609 -> 10.63.192.1:53
11:51:06 hotspot,debug Hotspot: dynamic host 10.63.193.30 removed: limiting addresses per mac
11:51:06 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.46 added, ip 10.63.193.29
11:51:07 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.50 by UDP :17912 -> 10.63.192.1:53
11:51:07 hotspot,debug Hotspot: dynamic host 10.63.193.29 removed: limiting addresses per mac
11:51:07 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.50 added, ip 10.63.193.28
11:51:09 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by UDP :54443 -> 10.63.192.1:53
11:51:09 hotspot,debug Hotspot: dynamic host 10.63.193.28 removed: limiting addresses per mac
11:51:09 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.106 added, ip 10.63.193.106
11:51:09 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.50 by UDP :18646 -> 10.63.192.1:53
11:51:09 hotspot,debug Hotspot: dynamic host 10.63.193.106 removed: limiting addresses per mac
11:51:09 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.50 added, ip 10.63.193.28
11:51:10 hotspot,debug Hotspot: dhcp host 10.63.193.74 removed: login timeout
11:51:23 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by TCP :59268 -> 174.36.251.211:80
11:51:23 hotspot,debug Hotspot: dynamic host 10.63.193.28 removed: limiting addresses per mac
11:51:23 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.106 added, ip 10.63.193.106
11:51:23 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.50 by UDP :25091 -> 10.63.192.1:53
11:51:23 hotspot,debug Hotspot: dynamic host 10.63.193.106 removed: limiting addresses per mac
11:51:23 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.50 added, ip 10.63.193.28
11:51:28 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :3064 -> 10.63.192.1:53
11:51:28 hotspot,debug Hotspot: dynamic host 10.63.193.28 removed: limiting addresses per mac
11:51:28 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.41 added, ip 10.63.193.27
11:51:30 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.50 by UDP :34255 -> 10.63.192.1:53
11:51:30 hotspot,debug Hotspot: dynamic host 10.63.193.27 removed: limiting addresses per mac
11:51:30 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.50 added, ip 10.63.193.28
11:51:31 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.106 by TCP :59268 -> 174.36.251.211:80
11:51:31 hotspot,debug Hotspot: dynamic host 10.63.193.28 removed: limiting addresses per mac
11:51:31 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.106 added, ip 10.63.193.106
11:51:31 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.50 by TCP :59365 -> 54.215.19.103:80
11:51:31 hotspot,debug Hotspot: dynamic host 10.63.193.106 removed: limiting addresses per mac
11:51:31 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.50 added, ip 10.63.193.27
11:51:33 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.41 by UDP :3064 -> 10.63.192.1:53
11:51:33 hotspot,debug Hotspot: dynamic host 10.63.193.27 removed: limiting addresses per mac
11:51:33 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.41 added, ip 10.63.193.26
11:51:33 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.50 by UDP :8999 -> 10.63.192.1:53
11:51:33 hotspot,debug Hotspot: dynamic host 10.63.193.26 removed: limiting addresses per mac
11:51:33 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.50 added, ip 10.63.193.27
11:51:35 hotspot,debug Hotspot: bypassed host 10.63.192.255 removed: server stopped
11:51:35 hotspot,debug Hotspot: bypassed host 10.63.192.3 removed: server stopped
11:51:35 hotspot,debug Hotspot: bypassed host 10.63.192.4 removed: server stopped
11:51:35 hotspot,debug Hotspot: bypassed host 10.63.192.254 removed: server stopped
11:51:35 hotspot,debug Hotspot: bypassed host 10.63.192.2 removed: server stopped
11:51:35 hotspot,debug Hotspot: bypassed host 10.63.192.5 removed: server stopped
11:51:35 hotspot,debug Hotspot: dhcp host 10.63.193.172 removed: server stopped
11:51:35 hotspot,debug Hotspot: dynamic host 10.63.193.27 removed: server stopped
11:51:35 system,info hotspot server Hotspot changed by ersitizastes
11:52:25 dhcp,info Hotspot assigned 10.63.193.25 to 58:A2:B5:DA:FD:96
11:53:40 dhcp,info Hotspot assigned 10.63.193.97 to 18:89:5B:3B:83:67
11:53:59 dhcp,info Hotspot deassigned 10.63.192.253 from 94:51:03:D3:B6:B8
11:54:03 dhcp,info Hotspot assigned 10.63.193.31 to 18:89:5B:0C:17:72
11:54:05 system,info simple queue added by ersitizastes
11:54:29 dhcp,info Hotspot assigned 10.63.193.84 to 9C:65:B0:E0:B1:45
11:54:32 dhcp,info Hotspot deassigned 10.63.193.25 from 58:A2:B5:DA:FD:96
11:54:32 dhcp,info Hotspot assigned 10.63.193.25 to 58:A2:B5:DA:FD:96
11:54:42 dhcp,info Hotspot assigned 10.63.193.51 to 60:D7:AE:C8:92:CC
11:55:10 dhcp,info Hotspot assigned 10.63.193.35 to EC:88:92:40:CC:8B
11:55:17 system,info simple queue changed by ersitizastes
11:56:29 system,info DHCP server dhcp1 changed by ersitizastes
11:58:10 dhcp,info dhcp1 deassigned 10.63.193.37 from 34:FC:EF:CF:50:24
11:58:29 system,info hotspot server Hotspot changed by ersitizastes
11:58:38 system,info,account user ersitizastes logged in from 10.63.192.255 via telnet


I've found this dynamic Nat rule after remove the hotspot, from where comes this rule?

[ersitizastes@5g.net 0] > /ip firewall nat print detail
Flags: X - disabled, I - invalid, D - dynamic
0 chain=srcnat action=masquerade out-interface=eth1 log=no log-prefix=""

1 D ;;; upnp 10.63.192.255: Teredo
chain=dstnat action=dst-nat to-addresses=10.63.192.255 to-ports=61355 protocol=udp dst-address=192.168.33.2 in
dst-port=61355 log=no log-prefix=""
[ersitizastes@5g.net 0] >

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 5:08 pm
by WirelessRudy
Is the default authenticate option gone? Is client now always to connect to units mentioned in the 'Connect List'?
Def-auth missing.PNG
Maybe the question is missed... There is no 'default authenticate' option tickbox anymore......

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 5:36 pm
by abis
Is the default authenticate option gone? Is client now always to connect to units mentioned in the 'Connect List'?
Maybe the question is missed... There is no 'default authenticate' option tickbox anymore......
For me is still there...
Untitled.png

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 5:43 pm
by Cha0s
Is the default authenticate option gone? Is client now always to connect to units mentioned in the 'Connect List'?
Def-auth missing.PNG
Maybe the question is missed... There is no 'default authenticate' option tickbox anymore......
I can confirm that too.

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 5:45 pm
by Cha0s
Is the default authenticate option gone? Is client now always to connect to units mentioned in the 'Connect List'?
Maybe the question is missed... There is no 'default authenticate' option tickbox anymore......
For me is still there...
Untitled.png
The option is missing when using the interface in Station mode. In AP mode it is available as shown in your screenshot

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 5:50 pm
by honzam

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 6:06 pm
by Thalid
been havent troubble connecting whit client since 6.34rc43 server is vmware

Client trows something whit 10061 no connection but i cant read the rest

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 02, 2016 6:47 pm
by uldis
PeterDoBrasil, please look at this wiki page which explains more about the station modes in the RouterOS.
If your AP is RouterOS based then try to switch from station-pseudobridge to station-bridge.
http://wiki.mikrotik.com/wiki/Manual:Wi ... tion_Modes

Re: v6.35rc is released, new wireless package!

Posted: Wed Feb 03, 2016 3:19 am
by PeterDoBrasil
The new configuration causes big trouble on my Hotspot Network! The Hotspot host shows many diferent IP addresses for only one Mac Address, the Mac is from my outside AP, Translation doesn't work!!!!!

/ip hotspot host print
Flags: S - static, H - DHCP, D - dynamic, A - authorized, P - bypassed
# MAC-ADDRESS ADDRESS TO-ADDRESS SERVER IDLE-TIMEOUT
0 SP ;;; 5g.net 1
4C:5E:0C:C4:41:BE 10.63.192.2 10.63.192.2 Hotspot
1 SP ;;; 5g.net 3
4C:5E:0C:C4:53:F8 10.63.192.4 10.63.192.4 Hotspot
2 SP ;;; HP Ether
08:2E:5F:75:6C:56 10.63.192.255 10.63.192.255 Hotspot
3 SP ;;; 5g.net 4
4C:5E:0C:C4:4D:FA 10.63.192.5 10.63.192.5 Hotspot
4 SP ;;; 5g.net 2
4C:5E:0C:CA:05:46 10.63.192.3 10.63.192.3 Hotspot
5 HA 64:6C:B2:51:9E:0D 10.63.194.67 10.63.194.67 Hotspot
6 HA 00:F4:6F:F6:0A:DF 10.63.194.84 10.63.194.84 Hotspot
7 D 4C:5E:0C:CA:05:46 10.63.193.28 10.63.193.150 Hotspot
8 D 4C:5E:0C:CA:05:46 10.63.194.18 10.63.194.86 Hotspot
9 D 4C:5E:0C:CA:05:46 10.63.193.59 10.63.194.29 Hotspot
10 H 74:BA:DB:04:26:13 10.63.194.28 10.63.194.28 Hotspot
11 H F4:F1:E1:F4:62:F6 10.63.193.3 10.63.193.3 Hotspot
12 H 84:11:9E:C3:1F:FE 10.63.194.87 10.63.194.87 Hotspot
13 HA 0C:B3:19:E9:AE:30 10.63.194.85 10.63.194.85 Hotspot
14 H 10:D3:8A:17:AB:26 10.63.194.88 10.63.194.88 Hotspot
15 H 38:2D:D1:A5:04:39 10.63.193.23 10.63.193.23 Hotspot


# 4C:5E:0C:CA:05:46 is the Mac Address from my AP; pseudobridge #

/log print

# feb/ 2/2016 22:17:40 by RouterOS 6.33
# software id = KPNX-1FGN
#
feb/02 19:00:31 system,error,critical router was rebooted without proper shutdown
feb/02 19:00:37 interface,info ether1 link up (speed 100M, full duplex)
feb/02 19:00:37 interface,info ether2 link up (speed 1G, full duplex)
feb/02 19:00:37 interface,info ether9 link up (speed 100M, full duplex)
feb/02 19:00:39 dhcp,info 172.16 deassigned 172.16.0.2 from 3C:E5:B4:0D:0D:27
feb/02 19:00:40 dhcp,info dhcp-client on ether1 got IP address 192.168.33.2
feb/02 19:00:40 interface,info ether10 link up (speed 100M, full duplex)
feb/02 19:00:42 dhcp,info 172.16 assigned 172.16.0.2 to 3C:E5:B4:0D:0D:27
feb/02 19:30:47 wireless,info 60:D7:AE:C8:92:CC@wlan: connected
feb/02 19:30:59 dhcp,info Hotspot assigned 10.63.193.5 to 74:BA:DB:04:26:13
feb/02 19:31:00 dhcp,info Hotspot deassigned 10.63.193.16 from 9C:D3:5B:51:B7:AE
feb/02 19:31:03 dhcp,info Hotspot deassigned 10.63.193.23 from 38:2D:D1:A5:04:39
feb/02 19:31:03 dhcp,info Hotspot assigned 10.63.193.23 to 38:2D:D1:A5:04:39
feb/02 19:31:04 dhcp,info Hotspot assigned 10.63.193.16 to 9C:D3:5B:51:B7:AE
feb/02 19:31:04 system,info,account user ersitizastes logged in from 10.63.192.255 via winbox
feb/02 19:31:35 dhcp,info Hotspot deassigned 10.63.193.21 from 20:55:31:66:20:D8
feb/02 19:31:40 dhcp,info Hotspot assigned 10.63.193.21 to 20:55:31:66:20:D8
feb/02 19:32:09 system,info,account user ersitizastes logged out from 10.63.192.255 via winbox
feb/02 19:32:10 wireless,info 50:55:27:A0:E9:AF@wlan: connected
feb/02 19:32:11 dhcp,info Hotspot deassigned 10.63.193.133 from 50:55:27:A0:E9:AF
feb/02 19:32:11 dhcp,info Hotspot assigned 10.63.193.133 to 50:55:27:A0:E9:AF
feb/02 19:32:54 system,info,account user ersitizastes logged in from 10.63.192.255 via winbox
feb/02 19:32:55 dhcp,info Hotspot deassigned 10.63.193.13 from 18:22:7E:2A:5A:5E
feb/02 19:33:00 dhcp,info Hotspot assigned 10.63.193.13 to 18:22:7E:2A:5A:5E
feb/02 19:33:08 dhcp,info Hotspot deassigned 10.63.193.21 from 20:55:31:66:20:D8
feb/02 19:33:08 dhcp,info Hotspot assigned 10.63.193.21 to 20:55:31:66:20:D8
feb/02 19:34:23 system,info hotspot server profile default changed by ersitizastes
feb/02 19:34:33 system,info hotspot user profile 00 changed by ersitizastes
feb/02 19:35:09 dhcp,info Hotspot assigned 10.63.193.40 to B4:EF:39:7D:B2:50
feb/02 19:35:12 system,info hotspot user profile 00 changed by ersitizastes
feb/02 19:35:13 system,info hotspot user profile 00 changed by ersitizastes
feb/02 19:35:15 dhcp,info Hotspot assigned 10.63.193.1 to 10:D3:8A:04:9B:58
feb/02 19:35:16 dhcp,info Hotspot assigned 10.63.193.2 to F4:F1:E1:1E:3A:2C
feb/02 19:35:30 dhcp,info Hotspot deassigned 10.63.193.22 from 34:BE:00:95:74:65
feb/02 19:35:43 system,info hotspot user profile 00 changed by ersitizastes
feb/02 19:35:44 system,info hotspot user profile 00 changed by ersitizastes
feb/02 19:35:53 system,info hotspot user profile 00 changed by ersitizastes
feb/02 19:36:03 system,info hotspot user profile 00 changed by ersitizastes
feb/02 19:36:04 system,info hotspot user profile 00 changed by ersitizastes
feb/02 19:36:06 dhcp,info Hotspot assigned 10.63.193.0 to F8:95:C7:B4:25:3A
feb/02 19:36:08 dhcp,info Hotspot deassigned 10.63.193.6 from 64:89:9A:27:FA:67
feb/02 19:36:23 system,info hotspot user profile 00 changed by ersitizastes
feb/02 19:36:51 system,info hotspot server profile default changed by ersitizastes
feb/02 19:37:53 dhcp,info Hotspot deassigned 10.63.193.15 from 34:FC:EF:FF:AD:06
feb/02 19:38:24 system,info hotspot user profile 00 changed by ersitizastes
feb/02 19:38:25 system,info hotspot user profile 00 changed by ersitizastes
feb/02 19:38:26 system,info hotspot user profile 00 changed by ersitizastes
feb/02 19:38:28 system,info hotspot user profile 00 changed by ersitizastes
feb/02 19:38:40 dhcp,info Hotspot deassigned 10.63.193.18 from A8:9F:BA:02:A5:84
feb/02 19:38:51 system,info hotspot user profile 00 changed by ersitizastes
feb/02 19:39:05 dhcp,info Hotspot deassigned 10.63.193.12 from 34:FC:EF:D2:AB:CD
feb/02 19:39:44 dhcp,info Hotspot deassigned 10.63.193.19 from 00:F4:6F:FC:E4:47
feb/02 19:40:07 dhcp,info Hotspot assigned 10.63.193.7 to E8:B4:C8:28:76:16
feb/02 19:40:26 system,info new script added by ersitizastes
feb/02 19:40:31 system,info changed script settings by ersitizastes
feb/02 19:40:59 dhcp,info Hotspot deassigned 10.63.193.5 from 74:BA:DB:04:26:13
feb/02 19:41:21 system,info hotspot user profile 00 changed by ersitizastes
feb/02 19:42:43 dhcp,info Hotspot deassigned 10.63.193.9 from 3C:18:9F:33:05:31
feb/02 19:42:43 dhcp,info Hotspot assigned 10.63.193.9 to 3C:18:9F:33:05:31
feb/02 19:43:10 dhcp,info Hotspot assigned 10.63.193.5 to 74:BA:DB:04:26:13
feb/02 19:44:07 system,info hotspot server Hotspot added by ersitizastes
feb/02 19:44:08 system,info filter rule added
feb/02 19:44:08 system,info nat rule added
feb/02 19:45:09 dhcp,info Hotspot deassigned 10.63.193.40 from B4:EF:39:7D:B2:50
feb/02 19:45:10 wireless,info 94:51:03:D3:B6:B8@wlan: connected
feb/02 19:45:10 dhcp,info Hotspot assigned 10.63.192.253 to 94:51:03:D3:B6:B8
feb/02 19:45:16 dhcp,info Hotspot deassigned 10.63.193.2 from F4:F1:E1:1E:3A:2C
feb/02 19:45:24 dhcp,info Hotspot assigned 10.63.193.24 to 80:65:6D:4F:75:69
feb/02 19:45:30 dhcp,info Hotspot deassigned 10.63.193.13 from 18:22:7E:2A:5A:5E
feb/02 19:45:30 dhcp,info Hotspot assigned 10.63.193.13 to 18:22:7E:2A:5A:5E
feb/02 19:45:39 hotspot,info,debug T-94:51:03:D3:B6:B8 (10.63.192.253): trying to log in by trial
feb/02 19:45:39 hotspot,account,info,debug T-94:51:03:D3:B6:B8 (10.63.192.253): logged in
feb/02 19:46:21 hotspot,info,debug T-50:55:27:A0:E9:AF (10.63.193.133): trying to log in by trial
feb/02 19:46:21 hotspot,account,info,debug T-50:55:27:A0:E9:AF (10.63.193.133): logged in
feb/02 19:46:27 hotspot,info,debug T-50:55:27:A0:E9:AF (10.63.193.133): logged out: user request
feb/02 19:46:31 hotspot,info,debug T-50:55:27:A0:E9:AF (10.63.193.133): trying to log in by trial
feb/02 19:46:31 hotspot,account,info,debug T-50:55:27:A0:E9:AF (10.63.193.133): logged in
feb/02 19:46:34 hotspot,info,debug T-50:55:27:A0:E9:AF (10.63.193.133): logged out: user request
feb/02 19:46:38 dhcp,info Hotspot assigned 10.63.193.28 to F4:0E:22:7E:AB:C8
feb/02 19:46:47 dhcp,info Hotspot assigned 10.63.193.11 to C4:9A:02:39:61:13
feb/02 19:47:41 dhcp,info Hotspot deassigned 10.63.193.0 from F8:95:C7:B4:25:3A
feb/02 19:47:50 dhcp,info Hotspot assigned 10.63.193.32 to 10:3B:59:CF:FE:A8
feb/02 19:49:08 system,info hotspot user profile 00 changed by ersitizastes
feb/02 19:49:34 wireless,info 34:FC:EF:D2:AB:CD@wlan: connected
feb/02 19:49:35 dhcp,info Hotspot assigned 10.63.193.12 to 34:FC:EF:D2:AB:CD
feb/02 19:49:35 dhcp,info Hotspot deassigned 10.63.193.133 from 50:55:27:A0:E9:AF
feb/02 19:49:35 dhcp,info Hotspot assigned 10.63.193.133 to 50:55:27:A0:E9:AF
feb/02 19:49:36 dhcp,info Hotspot deassigned 10.63.193.21 from 20:55:31:66:20:D8
feb/02 19:49:36 wireless,info 50:55:27:A0:E9:AF@wlan: disconnected, extensive data loss
feb/02 19:50:07 dhcp,info Hotspot deassigned 10.63.193.7 from E8:B4:C8:28:76:16
feb/02 19:50:20 system,info log action changed by ersitizastes
feb/02 19:50:32 dhcp,info Hotspot deassigned 10.63.193.11 from C4:9A:02:39:61:13
feb/02 19:50:33 dhcp,info Hotspot assigned 10.63.193.11 to C4:9A:02:39:61:13
feb/02 19:50:37 system,info log rule added by ersitizastes
feb/02 19:51:07 system,info hotspot server Hotspot changed by ersitizastes
feb/02 19:51:18 system,info hotspot server Hotspot changed by ersitizastes
feb/02 19:52:41 dhcp,info Hotspot assigned 10.63.193.21 to 20:55:31:66:20:D8
feb/02 19:52:43 dhcp,info Hotspot deassigned 10.63.193.9 from 3C:18:9F:33:05:31
feb/02 19:52:47 dhcp,info Hotspot deassigned 10.63.193.10 from 14:A3:64:94:50:C8
feb/02 19:53:01 dhcp,info Hotspot deassigned 10.63.193.13 from 18:22:7E:2A:5A:5E
feb/02 19:53:01 dhcp,info Hotspot assigned 10.63.193.13 to 18:22:7E:2A:5A:5E
feb/02 19:53:11 dhcp,info Hotspot deassigned 10.63.193.5 from 74:BA:DB:04:26:13
feb/02 19:53:19 system,info DHCP server dhcp1 changed by ersitizastes
feb/02 19:53:26 dhcp,info dhcp1 assigned 10.63.193.37 to 14:1A:A3:68:7E:60
feb/02 19:54:48 dhcp,info dhcp1 assigned 10.63.193.75 to B4:EF:39:83:05:9C
feb/02 19:55:02 dhcp,info dhcp1 assigned 10.63.193.90 to C4:3A:BE:D2:D1:20
feb/02 19:55:25 dhcp,info dhcp1 deassigned 10.63.193.24 from 80:65:6D:4F:75:69
feb/02 19:55:56 system,info,account user ersitizastes logged out from 10.63.192.255 via winbox
feb/02 19:56:38 dhcp,info dhcp1 deassigned 10.63.193.28 from F4:0E:22:7E:AB:C8
feb/02 19:56:40 system,info,account user ersitizastes logged in from 10.63.192.255 via winbox
feb/02 19:57:45 dhcp,info dhcp1 assigned 10.63.193.24 to 80:65:6D:4F:75:69
feb/02 19:57:50 system,info hotspot ip binding rule changed by ersitizastes
feb/02 19:57:51 dhcp,info dhcp1 deassigned 10.63.193.32 from 10:3B:59:CF:FE:A8
feb/02 19:58:01 system,info hotspot ip binding rule changed by ersitizastes
feb/02 19:58:11 system,info hotspot ip binding rule changed by ersitizastes
feb/02 19:58:22 system,info hotspot ip binding rule changed by ersitizastes
feb/02 19:58:36 system,info hotspot ip binding rule changed by ersitizastes
feb/02 19:58:44 system,info hotspot ip binding rule changed by ersitizastes
feb/02 19:59:02 dhcp,info dhcp1 assigned 10.63.194.14 to 84:38:38:D9:00:A4
feb/02 19:59:27 system,info,account user ersitizastes logged out from 10.63.192.255 via winbox
feb/02 19:59:45 wireless,info 34:FC:EF:D2:AB:CD@wlan: disconnected, extensive data loss
feb/02 20:00:28 dhcp,info dhcp1 deassigned 10.63.193.1 from 10:D3:8A:04:9B:58
feb/02 20:00:33 dhcp,info dhcp1 deassigned 10.63.193.11 from C4:9A:02:39:61:13
feb/02 20:00:49 dhcp,info dhcp1 deassigned 10.63.193.13 from 18:22:7E:2A:5A:5E
feb/02 20:01:01 dhcp,info dhcp1 assigned 10.63.193.13 to 18:22:7E:2A:5A:5E
feb/02 20:01:32 dhcp,info dhcp1 assigned 10.63.194.15 to B8:5A:73:A8:5B:84
feb/02 20:01:36 system,info,account user ersitizastes logged in from 10.63.192.255 via winbox
feb/02 20:02:39 dhcp,info dhcp1 assigned 10.63.194.16 to E4:90:7E:50:12:B3
feb/02 20:02:40 wireless,info 94:51:03:D3:B6:B8@wlan: disconnected, received disassoc: sending station leaving (8)
feb/02 20:02:41 dhcp,info dhcp1 deassigned 10.63.193.21 from 20:55:31:66:20:D8
feb/02 20:02:45 system,info hotspot user profile 00 changed by ersitizastes
feb/02 20:04:15 hotspot,info,debug T-94:51:03:D3:B6:B8 (10.63.192.253): logged out: keepalive timeout
feb/02 20:04:48 dhcp,info dhcp1 deassigned 10.63.193.75 from B4:EF:39:83:05:9C
feb/02 20:05:02 dhcp,info dhcp1 deassigned 10.63.193.90 from C4:3A:BE:D2:D1:20
feb/02 20:05:25 system,info new script added by ersitizastes
feb/02 20:05:30 system,info changed script settings by ersitizastes
feb/02 20:05:30 dhcp,info dhcp1 assigned 10.63.194.17 to 84:38:38:FE:EE:9A
feb/02 20:06:10 system,info DHCP server setting changed by ersitizastes
feb/02 20:06:58 system,info hotspot ip binding rule changed by ersitizastes
feb/02 20:07:08 system,info,account user ersitizastes logged out from 10.63.192.255 via winbox
feb/02 20:07:11 interface,info ether2 link down
feb/02 20:07:19 wireless,info 5C:C9:D3:0D:D1:AD@wlan: connected
feb/02 20:07:19 dhcp,info dhcp1 assigned 10.63.192.254 to 5C:C9:D3:0D:D1:AD
feb/02 20:07:27 wireless,info 5C:C9:D3:0D:D1:AD@wlan: disconnected, received disassoc: sending station leaving (8)
feb/02 20:07:39 wireless,info 5C:C9:D3:0D:D1:AD@wlan: connected
feb/02 20:07:46 hotspot,info,debug T-5C:C9:D3:0D:D1:AD (10.63.192.254): trying to log in by trial
feb/02 20:07:46 hotspot,account,info,debug T-5C:C9:D3:0D:D1:AD (10.63.192.254): logged in
feb/02 20:08:45 interface,info ether2 link up (speed 1G, full duplex)
feb/02 20:08:51 wireless,info 5C:C9:D3:0D:D1:AD@wlan: disconnected, received disassoc: sending station leaving (8)
feb/02 20:08:59 system,info,account user ersitizastes logged in from 10.63.192.255 via winbox
feb/02 20:09:02 dhcp,info dhcp1 deassigned 10.63.194.14 from 84:38:38:D9:00:A4
feb/02 20:09:14 dhcp,info dhcp1 deassigned 10.63.193.12 from 34:FC:EF:D2:AB:CD
feb/02 20:09:16 dhcp,info dhcp1 assigned 10.63.194.19 to 14:32:D1:1C:E1:6E
feb/02 20:10:12 dhcp,info dhcp1 deassigned 10.63.192.253 from 94:51:03:D3:B6:B8
feb/02 20:10:47 wireless,info 60:D7:AE:C8:92:CC@wlan: disconnected, disabling
feb/02 20:10:47 system,info device changed by ersitizastes
feb/02 20:10:48 wireless,info wlan: data from unknown device 60:D7:AE:C8:92:CC, sent deauth
feb/02 20:10:50 dhcp,info dhcp1 assigned 10.63.194.20 to 40:0E:85:84:C5:85
feb/02 20:10:50 dhcp,info dhcp1 deassigned 10.63.193.16 from 9C:D3:5B:51:B7:AE
feb/02 20:10:51 hotspot,info,debug T-5C:C9:D3:0D:D1:AD (10.63.192.254): logged out: keepalive timeout
feb/02 20:11:25 system,info,account user ersitizastes logged out from 10.63.192.255 via winbox
feb/02 20:11:32 dhcp,info dhcp1 deassigned 10.63.194.15 from B8:5A:73:A8:5B:84
feb/02 20:12:00 dhcp,info dhcp1 assigned 10.63.193.16 to 9C:D3:5B:51:B7:AE
feb/02 20:12:02 dhcp,info dhcp1 assigned 10.63.194.18 to 34:FC:EF:FF:AD:06
feb/02 20:12:53 system,info,account user ersitizastes logged in from 10.63.192.255 via winbox
feb/02 20:13:31 dhcp,info dhcp1 assigned 10.63.194.23 to F8:95:C7:AE:1B:4F
feb/02 20:14:23 dhcp,info dhcp1 deassigned 10.63.193.51 from 60:D7:AE:C8:92:CC
feb/02 20:14:45 system,info hotspot user profile 10 added by ersitizastes
feb/02 20:14:54 dhcp,info dhcp1 deassigned 10.63.194.20 from 40:0E:85:84:C5:85
feb/02 20:15:01 system,info hotspot user profile 00 changed by ersitizastes
feb/02 20:15:36 system,info hotspot user profile 10 changed by ersitizastes
feb/02 20:15:46 system,info hotspot user profile 10 changed by ersitizastes
feb/02 20:16:42 system,info hotspot user profile 10 changed by ersitizastes
feb/02 20:17:02 dhcp,info dhcp1 assigned 10.63.193.28 to F4:0E:22:7E:AB:C8
feb/02 20:17:05 system,info hotspot user profile 30 added by ersitizastes
feb/02 20:17:05 dhcp,info dhcp1 assigned 10.63.193.90 to C4:3A:BE:D2:D1:20
feb/02 20:17:23 dhcp,info dhcp1 deassigned 10.63.194.23 from F8:95:C7:AE:1B:4F
feb/02 20:17:26 dhcp,info dhcp1 assigned 10.63.194.23 to F8:95:C7:AE:1B:4F
feb/02 20:17:39 dhcp,info dhcp1 deassigned 10.63.192.254 from 5C:C9:D3:0D:D1:AD
feb/02 20:18:11 system,info hotspot user profile 30 changed by ersitizastes
feb/02 20:18:26 system,info hotspot user profile 60 added by ersitizastes
feb/02 20:18:58 system,info hotspot user profile 60 changed by ersitizastes
feb/02 20:19:16 dhcp,info dhcp1 deassigned 10.63.194.19 from 14:32:D1:1C:E1:6E
feb/02 20:19:16 system,info hotspot user profile 100 added by ersitizastes
feb/02 20:19:27 system,info hotspot user profile 100 changed by ersitizastes
feb/02 20:19:28 dhcp,info dhcp1 assigned 10.63.194.25 to F8:95:C7:AF:20:92
feb/02 20:19:41 dhcp,info dhcp1 assigned 10.63.194.26 to C4:9A:02:9E:19:A1
feb/02 20:19:51 system,info hotspot user profile 100 changed by ersitizastes
feb/02 20:20:06 system,info hotspot user profile 30 changed by ersitizastes
feb/02 20:20:20 system,info hotspot user profile 60 changed by ersitizastes
feb/02 20:20:25 dhcp,info dhcp1 deassigned 10.63.194.17 from 84:38:38:FE:EE:9A
feb/02 20:23:09 system,info mangle rule added by ersitizastes
feb/02 20:24:02 system,info mangle rule added by ersitizastes
feb/02 20:25:27 system,info wireless access-list entry added by ersitizastes
feb/02 20:25:28 wireless,info 94:51:03:D3:B6:B8@wlan: connected
feb/02 20:25:32 dhcp,info dhcp1 assigned 10.63.192.253 to 94:51:03:D3:B6:B8
feb/02 20:25:33 hotspot,info,debug T-94:51:03:D3:B6:B8 (10.63.192.253): trying to log in by mac-cookie
feb/02 20:25:33 hotspot,account,info,debug T-94:51:03:D3:B6:B8 (10.63.192.253): logged in
feb/02 20:25:34 wireless,info 94:51:03:D3:B6:B8@wlan: disconnected, access-list changed
feb/02 20:25:34 system,info wireless access-list entry changed by ersitizastes
feb/02 20:25:34 wireless,info 94:51:03:D3:B6:B8@wlan: connected
feb/02 20:25:45 dhcp,info dhcp1 deassigned 10.63.193.13 from 18:22:7E:2A:5A:5E
feb/02 20:25:58 dhcp,info dhcp1 assigned 10.63.194.27 to 44:80:EB:CC:B2:5B
feb/02 20:26:01 system,info wireless access-list entry added by ersitizastes
feb/02 20:26:09 system,info wireless access-list entry changed by ersitizastes
feb/02 20:27:02 dhcp,info dhcp1 deassigned 10.63.193.28 from F4:0E:22:7E:AB:C8
feb/02 20:27:05 dhcp,info dhcp1 deassigned 10.63.193.90 from C4:3A:BE:D2:D1:20
feb/02 20:27:10 dhcp,info dhcp1 assigned 10.63.194.28 to 74:BA:DB:04:26:13
feb/02 20:27:12 system,info mangle rule removed by ersitizastes
feb/02 20:27:12 system,info mangle rule removed by ersitizastes
feb/02 20:27:26 dhcp,info dhcp1 deassigned 10.63.194.23 from F8:95:C7:AE:1B:4F
feb/02 20:28:10 dhcp,info dhcp1 assigned 10.63.194.29 to F8:95:C7:B0:02:08
feb/02 20:28:47 dhcp,info dhcp1 assigned 10.63.194.22 to AC:9E:17:0F:63:0D
feb/02 20:28:55 system,info hotspot walled-garden rule added by ersitizastes
feb/02 20:28:56 system,info hotspot walled-garden rule added
feb/02 20:29:02 dhcp,info dhcp1 deassigned 10.63.193.16 from 9C:D3:5B:51:B7:AE
feb/02 20:29:02 dhcp,info dhcp1 assigned 10.63.193.16 to 9C:D3:5B:51:B7:AE
feb/02 20:29:08 system,info hotspot walled-garden rule changed by ersitizastes
feb/02 20:29:12 dhcp,info dhcp1 assigned 10.63.194.30 to 58:3F:54:9F:DA:69
feb/02 20:29:28 dhcp,info dhcp1 deassigned 10.63.194.25 from F8:95:C7:AF:20:92
feb/02 20:30:59 dhcp,info dhcp1 assigned 10.63.193.51 to 60:D7:AE:C8:92:CC
feb/02 20:31:39 dhcp,info dhcp1 deassigned 10.63.194.18 from 34:FC:EF:FF:AD:06
feb/02 20:31:39 system,info DHCP server dhcp1 changed by ersitizastes
feb/02 20:32:05 dhcp,info dhcp1 deassigned 10.63.193.23 from 38:2D:D1:A5:04:39
feb/02 20:32:07 dhcp,info dhcp1 deassigned 10.63.194.16 from E4:90:7E:50:12:B3
feb/02 20:33:08 dhcp,info dhcp1 assigned 10.63.193.23 to 38:2D:D1:A5:04:39
feb/02 20:33:15 system,info,account user ersitizastes logged out from 10.63.192.255 via winbox
feb/02 20:33:59 dhcp,info dhcp1 assigned 10.63.193.21 to 20:55:31:66:20:D8
feb/02 20:34:01 dhcp,info dhcp1 assigned 10.63.194.18 to 34:FC:EF:FF:AD:06
feb/02 20:35:35 dhcp,info dhcp1 deassigned 10.63.194.26 from C4:9A:02:9E:19:A1
feb/02 20:36:45 dhcp,info dhcp1 deassigned 10.63.193.24 from 80:65:6D:4F:75:69
feb/02 20:36:57 hotspot,info,debug T-94:51:03:D3:B6:B8 (10.63.192.253): logged out: session timeout
feb/02 20:37:00 system,info,account user ersitizastes logged in from 10.63.192.255 via winbox
feb/02 20:38:11 dhcp,info dhcp1 deassigned 10.63.194.29 from F8:95:C7:B0:02:08
feb/02 20:38:33 dhcp,info dhcp1 deassigned 10.63.193.133 from 50:55:27:A0:E9:AF
feb/02 20:38:47 dhcp,info dhcp1 deassigned 10.63.194.22 from AC:9E:17:0F:63:0D
feb/02 20:39:12 dhcp,info dhcp1 deassigned 10.63.194.30 from 58:3F:54:9F:DA:69
feb/02 20:40:13 dhcp,info dhcp1 assigned 10.63.194.33 to EC:88:92:40:CC:8B
feb/02 20:41:37 system,info new script scheduled by ersitizastes
feb/02 20:41:41 dhcp,info dhcp1 deassigned 10.63.193.51 from 60:D7:AE:C8:92:CC
feb/02 20:42:13 system,info changed scheduled script settings by ersitizastes
feb/02 20:42:17 system,info changed scheduled script settings by ersitizastes
feb/02 20:42:29 dhcp,info dhcp1 deassigned 10.63.194.28 from 74:BA:DB:04:26:13
feb/02 20:42:33 dhcp,info dhcp1 assigned 10.63.194.28 to 74:BA:DB:04:26:13
feb/02 20:42:37 system,info changed scheduled script settings by ersitizastes
feb/02 20:43:14 system,info new script scheduled by ersitizastes
feb/02 20:43:17 system,info changed scheduled script settings by ersitizastes
feb/02 20:43:26 wireless,info 94:51:03:D3:B6:B8@wlan: disconnected, received disassoc: sending station leaving (8)
feb/02 20:43:28 system,info changed scheduled script settings by ersitizastes
feb/02 20:43:35 dhcp,info dhcp1 assigned 10.63.194.34 to 20:55:31:74:FC:48
feb/02 20:43:48 dhcp,info dhcp1 assigned 10.63.194.35 to F4:F1:E1:1E:3A:2C
feb/02 20:43:50 dhcp,info dhcp1 deassigned 10.63.194.28 from 74:BA:DB:04:26:13
feb/02 20:44:00 dhcp,info dhcp1 assigned 10.63.194.28 to 74:BA:DB:04:26:13
feb/02 20:44:27 system,info new script added by ersitizastes
feb/02 20:44:28 system,info hotspot user profile 00 changed by ersitizastes
feb/02 20:44:35 system,info changed script settings by ersitizastes
feb/02 20:45:24 system,info new script added by ersitizastes
feb/02 20:45:27 system,info changed script settings by ersitizastes
feb/02 20:46:18 system,info new script scheduled by ersitizastes
feb/02 20:46:23 system,info changed scheduled script settings by ersitizastes
feb/02 20:46:38 system,info changed scheduled script settings by ersitizastes
feb/02 20:46:49 dhcp,info dhcp1 assigned 10.63.193.13 to 18:22:7E:2A:5A:5E
feb/02 20:46:51 system,info changed scheduled script settings by ersitizastes
feb/02 20:46:54 dhcp,info dhcp1 assigned 10.63.194.22 to AC:9E:17:0F:63:0D
feb/02 20:47:11 system,info new script scheduled by ersitizastes
feb/02 20:47:15 dhcp,info dhcp1 assigned 10.63.194.36 to 50:B7:C3:CC:5C:A8
feb/02 20:47:17 system,info changed scheduled script settings by ersitizastes
feb/02 20:47:29 system,info changed scheduled script settings by ersitizastes
feb/02 20:48:04 hotspot,info,debug T-50:B7:C3:CC:5C:A8 (10.63.194.36): trying to log in by trial
feb/02 20:48:04 hotspot,account,info,debug T-50:B7:C3:CC:5C:A8 (10.63.194.36): logged in
feb/02 20:48:20 dhcp,info dhcp1 assigned 10.63.194.26 to C4:9A:02:9E:19:A1
feb/02 20:48:41 system,info new script scheduled by ersitizastes
feb/02 20:48:49 system,info changed scheduled script settings by ersitizastes
feb/02 20:49:15 dhcp,info dhcp1 deassigned 10.63.194.28 from 74:BA:DB:04:26:13
feb/02 20:49:26 dhcp,info dhcp1 assigned 10.63.194.28 to 74:BA:DB:04:26:13
feb/02 20:49:58 dhcp,info dhcp1 assigned 10.63.194.38 to 64:89:9A:27:FA:67
feb/02 20:50:00 dhcp,info dhcp1 assigned 10.63.194.39 to 58:A2:B5:DA:FD:96
feb/02 20:50:22 dhcp,info dhcp1 assigned 10.63.193.31 to 18:89:5B:0C:17:72
feb/02 20:50:33 hotspot,info,debug T-18:89:5B:0C:17:72 (10.63.193.31): trying to log in by trial
feb/02 20:50:33 hotspot,account,info,debug T-18:89:5B:0C:17:72 (10.63.193.31): logged in
feb/02 20:50:33 dhcp,info dhcp1 deassigned 10.63.192.253 from 94:51:03:D3:B6:B8
feb/02 20:51:41 dhcp,info dhcp1 assigned 10.63.193.133 to 50:55:27:A0:E9:AF
feb/02 20:53:03 system,info new script scheduled by ersitizastes
feb/02 20:53:11 system,info changed scheduled script settings by ersitizastes
feb/02 20:54:51 dhcp,info dhcp1 assigned 10.63.194.40 to 34:FC:EF:D1:29:25
feb/02 20:55:20 dhcp,info dhcp1 deassigned 10.63.194.28 from 74:BA:DB:04:26:13
feb/02 20:55:20 dhcp,info dhcp1 assigned 10.63.194.28 to 74:BA:DB:04:26:13
feb/02 20:55:26 system,info,account user ersitizastes logged in from 10.63.192.255 via telnet
feb/02 20:55:40 system,info,account user ersitizastes logged out from 10.63.192.255 via telnet
feb/02 20:55:43 system,info new script scheduled by ersitizastes
feb/02 20:55:52 system,info changed scheduled script settings by ersitizastes
feb/02 20:57:01 system,info new script scheduled by ersitizastes
feb/02 20:57:24 system,info changed scheduled script settings by ersitizastes
feb/02 20:57:25 system,info changed scheduled script settings by ersitizastes
feb/02 20:57:33 system,info changed scheduled script settings by ersitizastes
feb/02 20:58:01 dhcp,info dhcp1 deassigned 10.63.194.38 from 64:89:9A:27:FA:67
feb/02 20:58:01 dhcp,info dhcp1 assigned 10.63.194.38 to 64:89:9A:27:FA:67
feb/02 20:58:06 dhcp,info dhcp1 assigned 10.63.194.41 to 34:FC:EF:D3:AD:1D
feb/02 20:58:10 dhcp,info dhcp1 assigned 10.63.194.42 to 34:FC:EF:CF:50:24
feb/02 20:58:30 hotspot,info,debug T-64:89:9A:27:FA:67 (10.63.194.38): trying to log in by trial
feb/02 20:58:30 hotspot,account,info,debug T-64:89:9A:27:FA:67 (10.63.194.38): logged in
feb/02 20:59:18 system,info hotspot user profile 110 added by ersitizastes
feb/02 20:59:32 dhcp,info dhcp1 assigned 10.63.193.51 to 60:D7:AE:C8:92:CC
feb/02 21:00:00 system,info hotspot user profile 10 changed by ersitizastes
feb/02 21:00:03 interface,info ether10 link down
feb/02 21:00:05 dhcp,info 172.16 deassigned 172.16.0.2 from 3C:E5:B4:0D:0D:27
feb/02 21:00:05 interface,info ether10 link up (speed 100M, full duplex)
feb/02 21:00:08 dhcp,info 172.16 assigned 172.16.0.2 to 3C:E5:B4:0D:0D:27
feb/02 21:00:17 system,info hotspot user profile 30 changed by ersitizastes
feb/02 21:00:24 system,info hotspot user profile 60 changed by ersitizastes
feb/02 21:00:26 hotspot,info,debug T-60:D7:AE:C8:92:CC (10.63.193.51): trying to log in by trial
feb/02 21:00:26 hotspot,account,info,debug T-60:D7:AE:C8:92:CC (10.63.193.51): logged in
feb/02 21:00:31 system,info hotspot user profile 100 changed by ersitizastes
feb/02 21:00:37 system,info hotspot user profile 110 changed by ersitizastes
feb/02 21:01:53 dhcp,info dhcp1 deassigned 10.63.193.13 from 18:22:7E:2A:5A:5E
feb/02 21:01:53 dhcp,info dhcp1 assigned 10.63.193.13 to 18:22:7E:2A:5A:5E
feb/02 21:02:39 system,info new script added by ersitizastes
feb/02 21:02:45 system,info changed script settings by ersitizastes
feb/02 21:02:49 dhcp,info dhcp1 deassigned 10.63.193.51 from 60:D7:AE:C8:92:CC
feb/02 21:02:49 dhcp,info dhcp1 assigned 10.63.193.51 to 60:D7:AE:C8:92:CC
feb/02 21:02:49 hotspot,info,debug T-50:B7:C3:CC:5C:A8 (10.63.194.36): logged out: keepalive timeout
feb/02 21:03:13 dhcp,info dhcp1 deassigned 10.63.193.16 from 9C:D3:5B:51:B7:AE
feb/02 21:03:13 dhcp,info dhcp1 assigned 10.63.193.16 to 9C:D3:5B:51:B7:AE
feb/02 21:03:54 system,info changed email settings by ersitizastes
feb/02 21:04:23 dhcp,info dhcp1 deassigned 10.63.193.51 from 60:D7:AE:C8:92:CC
feb/02 21:04:23 dhcp,info dhcp1 assigned 10.63.193.51 to 60:D7:AE:C8:92:CC
feb/02 21:04:31 system,info changed email settings by ersitizastes
feb/02 21:04:33 dhcp,info dhcp1 assigned 10.63.194.44 to B8:5A:73:B1:50:E0
feb/02 21:04:59 system,info Interface Traffic Graphing Config added by ersitizastes
feb/02 21:05:16 system,info Interface Traffic Graphing Config added by ersitizastes
feb/02 21:05:33 system,info Interface Traffic Graphing Config added by ersitizastes
feb/02 21:06:03 system,info Interface Traffic Graphing Config added by ersitizastes
feb/02 21:06:32 dhcp,info dhcp1 assigned 10.63.193.59 to F8:A9:D0:5A:F4:85
feb/02 21:06:45 hotspot,info,debug T-60:D7:AE:C8:92:CC (10.63.193.51): logged out: keepalive timeout
feb/02 21:07:19 dhcp,info dhcp1 deassigned 10.63.194.26 from C4:9A:02:9E:19:A1
feb/02 21:08:06 dhcp,info dhcp1 deassigned 10.63.194.33 from EC:88:92:40:CC:8B
feb/02 21:08:09 dhcp,info dhcp1 assigned 10.63.194.33 to EC:88:92:40:CC:8B
feb/02 21:08:23 dhcp,info dhcp1 assigned 10.63.193.90 to C4:3A:BE:D2:D1:20
feb/02 21:08:29 system,info monitoring new host by ersitizastes
feb/02 21:08:29 script,warning Google Up
feb/02 21:08:37 system,info netwatch host modified by ersitizastes
feb/02 21:08:37 script,warning Google Up
feb/02 21:08:45 dhcp,info dhcp1 deassigned 10.63.193.51 from 60:D7:AE:C8:92:CC
feb/02 21:10:00 system,info monitoring new host by ersitizastes
feb/02 21:10:00 script,warning 5g.net 1 Up
feb/02 21:10:14 system,info netwatch host modified by ersitizastes
feb/02 21:10:14 script,warning 5g.net 1 Up
feb/02 21:10:34 dhcp,info dhcp1 deassigned 10.63.193.133 from 50:55:27:A0:E9:AF
feb/02 21:10:41 dhcp,info dhcp1 assigned 10.63.193.133 to 50:55:27:A0:E9:AF
feb/02 21:10:49 system,info monitoring new host by ersitizastes
feb/02 21:10:49 script,warning 5g.net 2 Up
feb/02 21:10:58 system,info monitoring new host by ersitizastes
feb/02 21:10:58 script,warning 5g.net 2 Up
feb/02 21:11:04 system,info monitored host removed by ersitizastes
feb/02 21:11:17 system,info netwatch host modified by ersitizastes
feb/02 21:11:17 script,warning 5g.net 2 Up
feb/02 21:11:19 dhcp,info dhcp1 assigned 10.63.193.3 to F4:F1:E1:F4:62:F6
feb/02 21:11:48 hotspot,info,debug T-F4:F1:E1:F4:62:F6 (10.63.193.3): trying to log in by trial
feb/02 21:11:48 hotspot,account,info,debug T-F4:F1:E1:F4:62:F6 (10.63.193.3): logged in
feb/02 21:12:01 hotspot,info,debug T-50:55:27:A0:E9:AF (10.63.193.133): trying to log in by trial
feb/02 21:12:01 hotspot,account,info,debug T-50:55:27:A0:E9:AF (10.63.193.133): logged in
feb/02 21:12:48 hotspot,info,debug T-50:55:27:A0:E9:AF (10.63.193.133): logged out: user request
feb/02 21:13:49 wireless,info wlan: data from unknown device 50:55:27:A0:E9:AF, sent deauth
feb/02 21:14:00 hotspot,info,debug T-50:55:27:A0:E9:AF (10.63.193.133): trying to log in by trial
feb/02 21:14:00 hotspot,account,info,debug T-50:55:27:A0:E9:AF (10.63.193.133): logged in
feb/02 21:14:14 dhcp,info dhcp1 deassigned 10.63.193.23 from 38:2D:D1:A5:04:39
feb/02 21:14:14 dhcp,info dhcp1 assigned 10.63.193.23 to 38:2D:D1:A5:04:39
feb/02 21:15:39 system,info log rule added by ersitizastes
feb/02 21:16:03 script,error 5g.net 2 Down
feb/02 21:16:10 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.133 by ICMP type<3> code<3> to 10.63.192.1
feb/02 21:16:10 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.133, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:16:15 hotspot,debug Hotspot: dhcp host 10.63.193.23 removed: login timeout
feb/02 21:16:15 hotspot,debug Hotspot: dhcp host 10.63.194.27 removed: login timeout
feb/02 21:16:16 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by TCP :59687 -> 61.145.124.57:80
feb/02 21:16:16 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
feb/02 21:16:20 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.22 by TCP :37124 -> 192.12.31.106:5228
feb/02 21:16:20 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.22, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:16:50 hotspot,debug Hotspot: new host detected 44:80:EB:CC:B2:5B/10.63.194.27 by UDP :33966 -> 10.63.192.1:53
feb/02 21:16:50 hotspot,debug Hotspot: dhcp host 44:80:EB:CC:B2:5B/10.63.194.27 added, ip 10.63.194.27
feb/02 21:16:52 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by UDP :32977 -> 10.63.192.1:53
feb/02 21:16:52 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:17:05 dhcp,info dhcp1 deassigned 10.63.193.133 from 50:55:27:A0:E9:AF
feb/02 21:17:05 hotspot,debug Hotspot: dhcp host 10.63.193.133 changed type to dynamic (remove after 5s)
feb/02 21:17:05 dhcp,info dhcp1 assigned 10.63.193.133 to 50:55:27:A0:E9:AF
feb/02 21:17:05 hotspot,debug Hotspot: dynamic host 10.63.193.133 changed type to dhcp (got back lease)
feb/02 21:17:31 dhcp,info dhcp1 assigned 10.63.194.48 to 00:F4:6F:C9:DD:01
feb/02 21:17:34 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by UDP :54106 -> 10.63.192.1:53
feb/02 21:17:34 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:17:37 hotspot,debug Hotspot: dhcp host 10.63.194.28 removed: login timeout
feb/02 21:17:39 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by TCP :43148 -> 108.168.174.17:80
feb/02 21:17:39 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.18, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:17:43 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.22 by TCP :47127 -> 192.12.31.91:5228
feb/02 21:17:43 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.22, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:17:52 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.133 by ICMP type<3> code<3> to 10.63.192.1
feb/02 21:17:52 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.133, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:18:00 hotspot,debug Hotspot: new host detected 74:BA:DB:04:26:13/10.63.194.28 by TCP :53388 -> 173.194.213.188:5228
feb/02 21:18:00 hotspot,debug Hotspot: dhcp host 74:BA:DB:04:26:13/10.63.194.28 added, ip 10.63.194.28
feb/02 21:18:00 script,warning 5g.net 2 Up
feb/02 21:18:16 hotspot,debug Hotspot: dhcp host 10.63.193.23 removed: login timeout
feb/02 21:18:16 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by TCP :56745 -> 183.61.112.29:80
feb/02 21:18:16 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
feb/02 21:18:18 system,info,account user ersitizastes logged in from 10.63.192.255 via telnet
feb/02 21:18:23 hotspot,debug Hotspot: new host detected C4:9A:02:61:DA:A3/10.63.193.2 by UDP :35264 -> 10.63.192.1:53
feb/02 21:18:23 hotspot,debug Hotspot: dynamic host C4:9A:02:61:DA:A3/10.63.193.2 added, ip 10.63.193.2
feb/02 21:18:23 hotspot,debug Hotspot: new host detected C4:9A:02:61:DA:A3/100.103.129.231 by TCP :43795 -> 10.63.192.1:7
feb/02 21:18:23 hotspot,debug Hotspot: dynamic host 10.63.193.2 removed: limiting addresses per mac
feb/02 21:18:23 hotspot,debug Hotspot: dynamic host C4:9A:02:61:DA:A3/100.103.129.231 added, ip 10.63.194.49
feb/02 21:18:30 system,info,account user ersitizastes logged out from 10.63.192.255 via telnet
feb/02 21:18:35 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by UDP :37658 -> 10.63.192.1:53
feb/02 21:18:35 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:18:37 hotspot,debug Hotspot: new host detected C4:9A:02:61:DA:A3/10.63.193.2 by UDP :42002 -> 10.63.192.1:53
feb/02 21:18:37 hotspot,debug Hotspot: dynamic host 10.63.194.49 removed: limiting addresses per mac
feb/02 21:18:37 hotspot,debug Hotspot: dynamic host C4:9A:02:61:DA:A3/10.63.193.2 added, ip 10.63.193.2
feb/02 21:18:43 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by TCP :43148 -> 108.168.174.17:80
feb/02 21:18:43 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.18, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:18:50 hotspot,debug Hotspot: dhcp host 10.63.194.27 removed: login timeout
feb/02 21:19:06 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.22 by TCP :52602 -> 192.12.31.84:5223
feb/02 21:19:06 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.22, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:19:06 dhcp,info dhcp1 deassigned 10.63.194.34 from 20:55:31:74:FC:48
feb/02 21:19:12 dhcp,info dhcp1 assigned 10.63.194.34 to 20:55:31:74:FC:48
feb/02 21:19:13 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.34 by UDP :18322 -> 10.63.192.1:53
feb/02 21:19:13 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.34, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:19:19 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by TCP :41108 -> 108.168.176.250:5222
feb/02 21:19:19 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:19:30 hotspot,debug Hotspot: new host detected F4:F1:E1:1E:3A:2C/10.63.194.35 by UDP :47791 -> 10.63.192.1:53
feb/02 21:19:30 hotspot,debug Hotspot: dhcp host F4:F1:E1:1E:3A:2C/10.63.194.35 added, ip 10.63.194.35
feb/02 21:19:36 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by TCP :35911 -> 54.213.65.93:80
feb/02 21:19:36 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:19:45 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :41033 -> 10.63.192.1:53
feb/02 21:19:45 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.18, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:20:00 hotspot,debug Hotspot: dhcp host 10.63.194.28 removed: login timeout
feb/02 21:20:01 hotspot,debug Hotspot: new host detected 74:BA:DB:04:26:13/10.63.194.28 by TCP :54244 -> 208.71.186.86:80
feb/02 21:20:01 hotspot,debug Hotspot: dhcp host 74:BA:DB:04:26:13/10.63.194.28 added, ip 10.63.194.28
feb/02 21:20:14 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.34 by UDP :20634 -> 10.63.192.1:53
feb/02 21:20:14 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.34, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:20:16 hotspot,debug Hotspot: dhcp host 10.63.193.23 removed: login timeout
feb/02 21:20:20 hotspot,debug Hotspot: new host detected 44:80:EB:CC:B2:5B/10.63.194.27 by TCP :53762 -> 174.37.231.87:80
feb/02 21:20:20 hotspot,debug Hotspot: dhcp host 44:80:EB:CC:B2:5B/10.63.194.27 added, ip 10.63.194.27
feb/02 21:20:21 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by TCP :41108 -> 108.168.176.250:5222
feb/02 21:20:21 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:20:29 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.22 by UDP :36712 -> 10.63.192.1:53
feb/02 21:20:29 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.22, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:20:32 dhcp,info dhcp1 deassigned 10.63.194.33 from EC:88:92:40:CC:8B
feb/02 21:20:33 hotspot,info,debug T-18:89:5B:0C:17:72 (10.63.193.31): logged out: session timeout
feb/02 21:20:33 hotspot,debug T-18:89:5B:0C:17:72 (10.63.193.31): removing queue
feb/02 21:20:33 hotspot,debug T-18:89:5B:0C:17:72 (10.63.193.31): removing address-list
feb/02 21:20:33 hotspot,debug T-18:89:5B:0C:17:72 (10.63.193.31): removing ip->user binding
feb/02 21:20:36 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by UDP :11754 -> 10.63.192.1:53
feb/02 21:20:36 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:20:37 hotspot,debug Hotspot: dynamic host 10.63.193.2 removed: login timeout
feb/02 21:20:38 dhcp,info dhcp1 assigned 10.63.194.33 to EC:88:92:40:CC:8B
feb/02 21:20:40 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :23367 -> 10.63.192.1:53
feb/02 21:20:40 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:20:46 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :12245 -> 10.63.192.1:53
feb/02 21:20:46 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.18, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:20:51 system,info dhcp lease changed by ersitizastes
feb/02 21:21:03 script,error Google Down
feb/02 21:21:30 hotspot,debug Hotspot: dhcp host 10.63.194.35 removed: login timeout
feb/02 21:21:31 hotspot,debug Hotspot: new host detected F4:F1:E1:1E:3A:2C/10.63.194.35 by TCP :50303 -> 149.154.175.50:443
feb/02 21:21:31 hotspot,debug Hotspot: dhcp host F4:F1:E1:1E:3A:2C/10.63.194.35 added, ip 10.63.194.35
feb/02 21:21:34 dhcp,info dhcp1 assigned 10.63.193.44 to 6C:2F:2C:1C:E4:DC
feb/02 21:21:37 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by UDP :64886 -> 10.63.192.1:53
feb/02 21:21:37 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:21:41 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by UDP :11473 -> 10.63.192.1:53
feb/02 21:21:41 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:21:42 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :3099 -> 10.63.192.1:53
feb/02 21:21:42 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:21:43 hotspot,debug Hotspot: new host detected 6C:2F:2C:1C:E4:DC/10.63.193.44 by UDP :63814 -> 10.63.192.1:53
feb/02 21:21:43 hotspot,debug Hotspot: dhcp host 6C:2F:2C:1C:E4:DC/10.63.193.44 added, ip 10.63.193.44
feb/02 21:21:45 system,info dhcp lease changed by ersitizastes
feb/02 21:21:52 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.22 by TCP :45978 -> 192.12.31.89:5228
feb/02 21:21:52 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.22, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:22:01 hotspot,debug Hotspot: dhcp host 10.63.194.28 removed: login timeout
feb/02 21:22:05 hotspot,debug Hotspot: new host detected 74:BA:DB:04:26:13/10.63.194.28 by UDP :57453 -> 8.8.8.8:53
feb/02 21:22:05 hotspot,debug Hotspot: dhcp host 74:BA:DB:04:26:13/10.63.194.28 added, ip 10.63.194.28
feb/02 21:22:20 hotspot,debug Hotspot: dhcp host 10.63.194.27 removed: login timeout
feb/02 21:22:27 hotspot,debug Hotspot: new host detected 44:80:EB:CC:B2:5B/10.63.194.27 by TCP :41242 -> 31.13.73.1:443
feb/02 21:22:27 hotspot,debug Hotspot: dhcp host 44:80:EB:CC:B2:5B/10.63.194.27 added, ip 10.63.194.27
feb/02 21:22:33 hotspot,debug Hotspot: dhcp host 10.63.193.31 removed: login timeout
feb/02 21:22:33 hotspot,debug Hotspot: new host detected 18:89:5B:0C:17:72/10.63.193.31 by TCP :58124 -> 31.13.73.36:443
feb/02 21:22:33 hotspot,debug Hotspot: dhcp host 18:89:5B:0C:17:72/10.63.193.31 added, ip 10.63.193.31
feb/02 21:22:44 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :2015 -> 10.63.192.1:53
feb/02 21:22:44 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.18, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:22:44 dhcp,info dhcp1 deassigned 10.63.193.31 from 18:89:5B:0C:17:72
feb/02 21:22:44 hotspot,debug Hotspot: dhcp host 10.63.193.31 changed type to dynamic (remove after 5s)
feb/02 21:22:49 hotspot,debug Hotspot: dynamic host 10.63.193.31 removed: lost dhcp lease
feb/02 21:22:53 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by UDP :55424 -> 10.63.192.1:53
feb/02 21:22:53 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:22:57 dhcp,info dhcp1 assigned 10.63.193.31 to 18:89:5B:0C:17:72
feb/02 21:23:00 hotspot,debug Hotspot: new host detected 18:89:5B:0C:17:72/10.63.193.31 by UDP :49123 -> 10.63.192.1:53
feb/02 21:23:00 hotspot,debug Hotspot: dhcp host 18:89:5B:0C:17:72/10.63.193.31 added, ip 10.63.193.31
feb/02 21:23:14 system,info hotspot server profile default changed by ersitizastes
feb/02 21:23:16 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.22 by UDP :15323 -> 10.63.192.1:53
feb/02 21:23:16 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.22, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:23:19 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :49185 -> 10.63.192.1:53
feb/02 21:23:19 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:23:31 hotspot,debug Hotspot: dhcp host 10.63.194.35 removed: login timeout
feb/02 21:23:42 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by UDP :14050 -> 10.63.192.1:53
feb/02 21:23:42 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:23:43 hotspot,debug Hotspot: dhcp host 10.63.193.44 removed: login timeout
feb/02 21:23:47 dhcp,info dhcp1 assigned 10.63.194.51 to 00:A0:E1:01:58:32
feb/02 21:23:50 system,info hotspot user profile 00 changed by ersitizastes
feb/02 21:23:52 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.51 by UDP :8850 -> 10.63.192.1:53
feb/02 21:23:52 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.51, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:24:05 hotspot,debug Hotspot: dhcp host 10.63.194.28 removed: login timeout
feb/02 21:24:12 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by UDP :8945 -> 10.63.192.1:53
feb/02 21:24:12 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:24:16 hotspot,debug Hotspot: new host detected 74:BA:DB:04:26:13/10.63.194.28 by UDP :37477 -> 10.63.192.1:53
feb/02 21:24:16 hotspot,debug Hotspot: dhcp host 74:BA:DB:04:26:13/10.63.194.28 added, ip 10.63.194.28
feb/02 21:24:19 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :48834 -> 10.63.192.1:53
feb/02 21:24:19 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:24:23 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.22 by TCP :57336 -> 31.13.73.1:443
feb/02 21:24:23 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.22, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:24:27 hotspot,debug Hotspot: dhcp host 10.63.194.27 removed: login timeout
feb/02 21:24:37 hotspot,debug Hotspot: new host detected F4:F1:E1:1E:3A:2C/10.63.194.35 by UDP :64599 -> 10.63.192.1:53
feb/02 21:24:37 hotspot,debug Hotspot: dhcp host F4:F1:E1:1E:3A:2C/10.63.194.35 added, ip 10.63.194.35
feb/02 21:24:40 dhcp,info dhcp1 deassigned 10.63.193.44 from 6C:2F:2C:1C:E4:DC
feb/02 21:24:40 dhcp,info dhcp1 assigned 10.63.193.44 to 6C:2F:2C:1C:E4:DC
feb/02 21:24:40 hotspot,debug Hotspot: new host detected 6C:2F:2C:1C:E4:DC/10.63.193.44 by UDP :36723 -> 10.63.192.1:53
feb/02 21:24:40 hotspot,debug Hotspot: dhcp host 6C:2F:2C:1C:E4:DC/10.63.193.44 added, ip 10.63.193.44
feb/02 21:24:43 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by UDP :34973 -> 10.63.192.1:53
feb/02 21:24:43 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:24:52 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.51 by TCP :33546 -> 66.220.158.2:443
feb/02 21:24:52 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.51, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:25:00 hotspot,debug Hotspot: dhcp host 10.63.193.31 removed: login timeout
feb/02 21:25:01 hotspot,debug Hotspot: new host detected 18:89:5B:0C:17:72/10.63.193.31 by UDP :14671 -> 10.63.192.1:53
feb/02 21:25:01 hotspot,debug Hotspot: dhcp host 18:89:5B:0C:17:72/10.63.193.31 added, ip 10.63.193.31
feb/02 21:25:03 dhcp,info dhcp1 assigned 10.63.194.52 to C4:9A:02:61:DA:A3
feb/02 21:25:04 hotspot,debug Hotspot: new host detected C4:9A:02:61:DA:A3/10.63.194.52 by UDP :62202 -> 10.63.192.1:53
feb/02 21:25:04 hotspot,debug Hotspot: dhcp host C4:9A:02:61:DA:A3/10.63.194.52 added, ip 10.63.194.52
feb/02 21:25:13 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by UDP :15235 -> 10.63.192.1:53
feb/02 21:25:13 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:25:13 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by TCP :47108 -> 158.85.58.26:5222
feb/02 21:25:13 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.18, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:25:21 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :2784 -> 10.63.192.1:53
feb/02 21:25:21 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:25:43 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by TCP :51267 -> 158.85.58.43:443
feb/02 21:25:43 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:25:53 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.51 by UDP :58804 -> 8.8.8.8:53
feb/02 21:25:53 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.51, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:26:03 script,warning Google Up
feb/02 21:26:03 script,error 5g.net 2 Down
feb/02 21:26:16 hotspot,debug Hotspot: new host detected 44:80:EB:CC:B2:5B/10.63.194.27 by UDP :32650 -> 10.63.192.1:53
feb/02 21:26:16 hotspot,debug Hotspot: dhcp host 44:80:EB:CC:B2:5B/10.63.194.27 added, ip 10.63.194.27
feb/02 21:26:16 hotspot,debug Hotspot: dhcp host 10.63.194.28 removed: login timeout
feb/02 21:26:23 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by UDP :39656 -> 10.63.192.1:53
feb/02 21:26:23 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:26:37 hotspot,debug Hotspot: dhcp host 10.63.194.35 removed: login timeout
feb/02 21:26:40 hotspot,debug Hotspot: dhcp host 10.63.193.44 removed: login timeout
feb/02 21:26:43 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by UDP :63725 -> 10.63.192.1:53
feb/02 21:26:43 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:26:44 system,info,account user ersitizastes logged out from 10.63.192.255 via winbox
feb/02 21:26:55 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.51 by UDP :51570 -> 8.8.8.8:53
feb/02 21:26:55 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.51, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:26:58 hotspot,debug Hotspot: new host detected F4:F1:E1:1E:3A:2C/10.63.194.35 by TCP :50350 -> 149.154.175.50:443
feb/02 21:26:58 hotspot,debug Hotspot: dhcp host F4:F1:E1:1E:3A:2C/10.63.194.35 added, ip 10.63.194.35
feb/02 21:27:00 hotspot,debug Hotspot: new host detected 74:BA:DB:04:26:13/10.63.194.28 by TCP :48676 -> 208.71.186.86:80
feb/02 21:27:00 hotspot,debug Hotspot: dhcp host 74:BA:DB:04:26:13/10.63.194.28 added, ip 10.63.194.28
feb/02 21:27:00 script,warning 5g.net 2 Up
feb/02 21:27:01 hotspot,debug Hotspot: dhcp host 10.63.193.31 removed: login timeout
feb/02 21:27:01 hotspot,debug Hotspot: new host detected 18:89:5B:0C:17:72/10.63.193.31 by UDP :50824 -> 10.63.192.1:53
feb/02 21:27:01 hotspot,debug Hotspot: dhcp host 18:89:5B:0C:17:72/10.63.193.31 added, ip 10.63.193.31
feb/02 21:27:04 hotspot,debug Hotspot: dhcp host 10.63.194.52 removed: login timeout
feb/02 21:27:04 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.133 by ICMP type<3> code<3> to 10.63.192.1
feb/02 21:27:04 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.133, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:27:10 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :13020 -> 10.63.192.1:53
feb/02 21:27:10 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.18, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:27:20 dhcp,info dhcp1 deassigned 10.63.194.33 from EC:88:92:40:CC:8B
feb/02 21:27:26 dhcp,info dhcp1 assigned 10.63.194.33 to EC:88:92:40:CC:8B
feb/02 21:27:27 dhcp,info dhcp1 deassigned 10.63.193.13 from 18:22:7E:2A:5A:5E
feb/02 21:27:27 dhcp,info dhcp1 assigned 10.63.193.13 to 18:22:7E:2A:5A:5E
feb/02 21:27:28 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by UDP :16732 -> 10.63.192.1:53
feb/02 21:27:28 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.13, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:27:30 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :30498 -> 10.63.192.1:53
feb/02 21:27:30 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:27:40 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by TCP :49083 -> 108.168.177.6:5222
feb/02 21:27:40 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:27:44 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by UDP :58319 -> 10.63.192.1:53
feb/02 21:27:44 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:27:52 dhcp,info dhcp1 deassigned 10.63.193.44 from 6C:2F:2C:1C:E4:DC
feb/02 21:27:52 dhcp,info dhcp1 assigned 10.63.193.44 to 6C:2F:2C:1C:E4:DC
feb/02 21:27:52 hotspot,debug Hotspot: new host detected 6C:2F:2C:1C:E4:DC/10.63.193.44 by UDP :24305 -> 10.63.192.1:53
feb/02 21:27:52 hotspot,debug Hotspot: dhcp host 6C:2F:2C:1C:E4:DC/10.63.193.44 added, ip 10.63.193.44
feb/02 21:27:56 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.51 by UDP :22797 -> 8.8.8.8:53
feb/02 21:27:56 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.51, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:28:04 hotspot,info,debug T-F4:F1:E1:F4:62:F6 (10.63.193.3): logged out: keepalive timeout
feb/02 21:28:04 hotspot,debug T-F4:F1:E1:F4:62:F6 (10.63.193.3): removing queue
feb/02 21:28:04 hotspot,debug T-F4:F1:E1:F4:62:F6 (10.63.193.3): removing address-list
feb/02 21:28:04 hotspot,debug T-F4:F1:E1:F4:62:F6 (10.63.193.3): removing ip->user binding
feb/02 21:28:04 hotspot,debug Hotspot: dhcp host 10.63.193.3 removed: keepalive timeout
feb/02 21:28:05 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.133 by TCP :35547 -> 169.55.69.138:443
feb/02 21:28:05 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.133, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:28:13 hotspot,info,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): trying to log in by trial
feb/02 21:28:13 hotspot,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): using profile <00>
feb/02 21:28:13 hotspot,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): adding ip->user binding
feb/02 21:28:13 hotspot,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): adding address-list rule <00>
feb/02 21:28:13 hotspot,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): adding queue <256k/256k 0/0 0/0 0/0 8 64k/64k>
feb/02 21:28:13 hotspot,account,info,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): logged in
feb/02 21:28:16 hotspot,debug Hotspot: dhcp host 10.63.194.27 removed: login timeout
feb/02 21:28:17 hotspot,debug Hotspot: new host detected 44:80:EB:CC:B2:5B/10.63.194.27 by TCP :40128 -> 216.58.222.14:443
feb/02 21:28:17 hotspot,debug Hotspot: dhcp host 44:80:EB:CC:B2:5B/10.63.194.27 added, ip 10.63.194.27
feb/02 21:28:20 hotspot,debug Hotspot: new host detected C4:9A:02:61:DA:A3/10.63.194.52 by UDP :18748 -> 10.63.192.1:53
feb/02 21:28:20 hotspot,debug Hotspot: dhcp host C4:9A:02:61:DA:A3/10.63.194.52 added, ip 10.63.194.52
feb/02 21:28:28 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by UDP :46179 -> 10.63.192.1:53
feb/02 21:28:28 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.13, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:28:30 hotspot,info,debug T-64:89:9A:27:FA:67 (10.63.194.38): logged out: session timeout
feb/02 21:28:30 hotspot,debug T-64:89:9A:27:FA:67 (10.63.194.38): removing queue
feb/02 21:28:30 hotspot,debug T-64:89:9A:27:FA:67 (10.63.194.38): removing address-list
feb/02 21:28:30 hotspot,debug T-64:89:9A:27:FA:67 (10.63.194.38): removing ip->user binding
feb/02 21:28:31 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :2267 -> 10.63.192.1:53
feb/02 21:28:31 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:28:40 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by TCP :57475 -> 169.54.55.203:5222
feb/02 21:28:40 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:28:44 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by UDP :8756 -> 10.63.192.1:53
feb/02 21:28:44 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:28:57 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.51 by UDP :40344 -> 10.63.192.1:53
feb/02 21:28:57 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.51, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:28:58 hotspot,debug Hotspot: dhcp host 10.63.194.35 removed: login timeout
feb/02 21:28:59 dhcp,info dhcp1 deassigned 10.63.194.28 from 74:BA:DB:04:26:13
feb/02 21:28:59 hotspot,debug Hotspot: dhcp host 10.63.194.28 changed type to dynamic (remove after 5s)
feb/02 21:28:59 dhcp,info dhcp1 assigned 10.63.194.28 to 74:BA:DB:04:26:13
feb/02 21:28:59 hotspot,debug Hotspot: dynamic host 10.63.194.28 changed type to dhcp (got back lease)
feb/02 21:29:00 hotspot,debug Hotspot: dhcp host 10.63.194.28 removed: login timeout
feb/02 21:29:01 hotspot,debug Hotspot: dhcp host 10.63.193.31 removed: login timeout
feb/02 21:29:03 hotspot,info,debug T-50:55:27:A0:E9:AF (10.63.193.133): logged out: keepalive timeout
feb/02 21:29:03 hotspot,debug T-50:55:27:A0:E9:AF (10.63.193.133): removing queue
feb/02 21:29:03 hotspot,debug T-50:55:27:A0:E9:AF (10.63.193.133): removing address-list
feb/02 21:29:03 hotspot,debug T-50:55:27:A0:E9:AF (10.63.193.133): removing ip->user binding
feb/02 21:29:03 hotspot,debug Hotspot: dhcp host 10.63.193.133 removed: keepalive timeout
feb/02 21:29:05 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.133 by UDP :7870 -> 10.63.192.1:53
feb/02 21:29:05 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.133, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:29:07 hotspot,debug Hotspot: new host detected F4:F1:E1:1E:3A:2C/10.63.194.35 by UDP :54056 -> 8.8.4.4:53
feb/02 21:29:07 hotspot,debug Hotspot: dhcp host F4:F1:E1:1E:3A:2C/10.63.194.35 added, ip 10.63.194.35
feb/02 21:29:08 hotspot,debug Hotspot: new host detected 74:BA:DB:04:26:13/10.63.194.28 by UDP :27061 -> 8.8.8.8:53
feb/02 21:29:08 hotspot,debug Hotspot: dhcp host 74:BA:DB:04:26:13/10.63.194.28 added, ip 10.63.194.28
feb/02 21:29:30 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by UDP :46450 -> 10.63.192.1:53
feb/02 21:29:30 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.13, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:29:32 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :9922 -> 10.63.192.1:53
feb/02 21:29:32 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:29:44 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by TCP :39391 -> 31.13.73.1:443
feb/02 21:29:44 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:29:59 dhcp,info dhcp1 deassigned 10.63.194.52 from C4:9A:02:61:DA:A3
feb/02 21:29:59 hotspot,debug Hotspot: dhcp host 10.63.194.52 changed type to dynamic (remove after 5s)
feb/02 21:29:59 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.51 by UDP :19621 -> 10.63.192.1:53
feb/02 21:29:59 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.51, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:29:59 dhcp,info dhcp1 assigned 10.63.194.52 to C4:9A:02:61:DA:A3
feb/02 21:29:59 hotspot,debug Hotspot: dynamic host 10.63.194.52 changed type to dhcp (got back lease)
feb/02 21:30:03 script,error Google Down
feb/02 21:30:04 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by UDP :17300 -> 10.63.192.1:53
feb/02 21:30:04 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:30:13 hotspot,debug Hotspot: new host detected C4:9A:02:61:DA:A3/179.200.153.41 by ICMP type<3> code<3> to 189.40.198.80
feb/02 21:30:13 hotspot,debug Hotspot: dhcp host 10.63.194.52 removed: limiting addresses per mac
feb/02 21:30:13 hotspot,debug Hotspot: dynamic host C4:9A:02:61:DA:A3/179.200.153.41 added, ip 10.63.193.2
feb/02 21:30:13 hotspot,debug Hotspot: new host detected C4:9A:02:61:DA:A3/10.63.194.52 by TCP :48560 -> 216.58.222.14:80
feb/02 21:30:13 hotspot,debug Hotspot: dynamic host 10.63.193.2 removed: limiting addresses per mac
feb/02 21:30:13 hotspot,debug Hotspot: dhcp host C4:9A:02:61:DA:A3/10.63.194.52 added, ip 10.63.194.52
feb/02 21:30:13 hotspot,debug Hotspot: new host detected C4:9A:02:61:DA:A3/179.200.153.41 by ICMP type<3> code<3> to 189.40.198.81
feb/02 21:30:13 hotspot,debug Hotspot: dhcp host 10.63.194.52 removed: limiting addresses per mac
feb/02 21:30:13 hotspot,debug Hotspot: dynamic host C4:9A:02:61:DA:A3/179.200.153.41 added, ip 10.63.193.2
feb/02 21:30:14 hotspot,debug Hotspot: new host detected C4:9A:02:61:DA:A3/10.63.194.52 by TCP :48560 -> 216.58.222.14:80
feb/02 21:30:14 hotspot,debug Hotspot: dynamic host 10.63.193.2 removed: limiting addresses per mac
feb/02 21:30:14 hotspot,debug Hotspot: dhcp host C4:9A:02:61:DA:A3/10.63.194.52 added, ip 10.63.194.52
feb/02 21:30:17 hotspot,debug Hotspot: dhcp host 10.63.194.27 removed: login timeout
feb/02 21:30:24 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.133 by UDP :15384 -> 10.63.192.1:53
feb/02 21:30:24 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.133, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:30:25 hotspot,debug Hotspot: new host detected 18:89:5B:0C:17:72/10.63.193.31 by UDP :12239 -> 10.63.192.1:53
feb/02 21:30:25 hotspot,debug Hotspot: dhcp host 18:89:5B:0C:17:72/10.63.193.31 added, ip 10.63.193.31
feb/02 21:30:30 hotspot,debug Hotspot: dhcp host 10.63.194.38 removed: login timeout
feb/02 21:30:31 hotspot,debug Hotspot: new host detected 64:89:9A:27:FA:67/10.63.194.38 by TCP :54530 -> 169.45.87.176:443
feb/02 21:30:31 hotspot,debug Hotspot: dhcp host 64:89:9A:27:FA:67/10.63.194.38 added, ip 10.63.194.38
feb/02 21:30:32 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :17482 -> 10.63.192.1:53
feb/02 21:30:32 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:30:43 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by UDP :54439 -> 10.63.192.1:53
feb/02 21:30:43 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.13, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:30:53 dhcp,info dhcp1 assigned 10.63.194.17 to 84:38:38:FE:EE:9A
feb/02 21:30:54 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.17 by UDP :55538 -> 10.63.192.1:53
feb/02 21:30:54 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.17, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:31:01 script,warning Google Up
feb/02 21:31:02 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by UDP :12164 -> 10.63.192.1:53
feb/02 21:31:02 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.51 by TCP :37284 -> 66.220.158.19:443
feb/02 21:31:02 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:31:02 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.51, ip 10.63.194.55: max addresses per mac is reached
feb/02 21:31:05 dhcp,info dhcp1 deassigned 10.63.194.27 from 44:80:EB:CC:B2:5B
feb/02 21:31:07 hotspot,debug Hotspot: dhcp host 10.63.194.35 removed: login timeout
feb/02 21:31:08 hotspot,debug Hotspot: dhcp host 10.63.194.28 removed: login timeout
feb/02 21:31:22 wireless,info wlan: data from unknown device 60:D7:AE:C8:92:CC, sent deauth
feb/02 21:31:25 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.133 by UDP :16105 -> 10.63.192.1:53
feb/02 21:31:25 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.133, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:31:35 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :36139 -> 10.63.192.1:53
feb/02 21:31:35 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:31:41 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by TCP :34044 -> 108.168.174.16:443
feb/02 21:31:41 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.18, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:31:46 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by UDP :29936 -> 10.63.192.1:53
feb/02 21:31:46 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.13, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:31:52 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by TCP :45614 -> 158.85.5.200:443
feb/02 21:31:52 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:31:59 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by UDP :38430 -> 10.63.192.1:53
feb/02 21:31:59 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
feb/02 21:32:03 script,error Google Down
feb/02 21:32:04 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by UDP :63741 -> 10.63.192.1:53
feb/02 21:32:04 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:32:14 hotspot,debug Hotspot: dhcp host 10.63.194.52 removed: login timeout
feb/02 21:32:25 hotspot,debug Hotspot: dhcp host 10.63.193.31 removed: login timeout
feb/02 21:32:25 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.133 by TCP :53085 -> 169.55.235.180:443
feb/02 21:32:25 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.133, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:32:25 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.17 by UDP :48532 -> 10.63.192.1:53
feb/02 21:32:25 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.17, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:32:31 hotspot,debug Hotspot: dhcp host 10.63.194.38 removed: login timeout
feb/02 21:32:31 hotspot,debug Hotspot: new host detected 64:89:9A:27:FA:67/10.63.194.38 by TCP :45820 -> 169.53.250.171:443
feb/02 21:32:31 hotspot,debug Hotspot: dhcp host 64:89:9A:27:FA:67/10.63.194.38 added, ip 10.63.194.38
feb/02 21:32:35 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by TCP :45430 -> 50.22.225.79:80
feb/02 21:32:35 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:32:42 hotspot,debug Hotspot: new host detected 18:89:5B:0C:17:72/10.63.193.31 by UDP :47665 -> 10.63.192.1:53
feb/02 21:32:42 hotspot,debug Hotspot: dhcp host 18:89:5B:0C:17:72/10.63.193.31 added, ip 10.63.193.31
feb/02 21:32:43 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :17525 -> 10.63.192.1:53
feb/02 21:32:43 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.18, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:32:46 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by TCP :34498 -> 158.85.58.59:80
feb/02 21:32:46 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.13, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:33:02 dhcp,info dhcp1 assigned 10.63.193.51 to 60:D7:AE:C8:92:CC
feb/02 21:33:05 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by UDP :18097 -> 10.63.192.1:53
feb/02 21:33:05 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:33:05 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by TCP :40453 -> 108.168.174.25:80
feb/02 21:33:05 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:33:06 hotspot,debug Hotspot: new host detected 60:D7:AE:C8:92:CC/10.63.193.51 by UDP :54348 -> 10.63.192.1:53
feb/02 21:33:06 hotspot,info,debug T-60:D7:AE:C8:92:CC (10.63.193.51): trying to log in by mac-cookie
feb/02 21:33:06 hotspot,debug T-60:D7:AE:C8:92:CC (10.63.193.51): using profile <00>
feb/02 21:33:06 hotspot,debug T-60:D7:AE:C8:92:CC (10.63.193.51): adding ip->user binding
feb/02 21:33:06 hotspot,debug Hotspot: dhcp host 60:D7:AE:C8:92:CC/10.63.193.51 added, ip 10.63.193.51
feb/02 21:33:06 hotspot,debug T-60:D7:AE:C8:92:CC (10.63.193.51): adding address-list rule <00>
feb/02 21:33:06 hotspot,debug T-60:D7:AE:C8:92:CC (10.63.193.51): adding queue <256k/256k 0/0 0/0 0/0 8 64k/64k>
feb/02 21:33:06 hotspot,account,info,debug T-60:D7:AE:C8:92:CC (10.63.193.51): logged in
feb/02 21:33:08 hotspot,debug Hotspot: new host detected 74:BA:DB:04:26:13/10.63.194.28 by UDP :47811 -> 10.63.192.1:53
feb/02 21:33:08 hotspot,debug Hotspot: dhcp host 74:BA:DB:04:26:13/10.63.194.28 added, ip 10.63.194.28
feb/02 21:33:08 hotspot,debug Hotspot: new host detected F4:F1:E1:F4:62:F6/10.63.193.3 by UDP :20871 -> 10.63.192.1:53
feb/02 21:33:08 hotspot,info,debug T-F4:F1:E1:F4:62:F6 (10.63.193.3): trying to log in by mac-cookie
feb/02 21:33:08 hotspot,debug T-F4:F1:E1:F4:62:F6 (10.63.193.3): using profile <00>
feb/02 21:33:08 hotspot,debug T-F4:F1:E1:F4:62:F6 (10.63.193.3): adding ip->user binding
feb/02 21:33:08 hotspot,debug Hotspot: dhcp host F4:F1:E1:F4:62:F6/10.63.193.3 added, ip 10.63.193.3
feb/02 21:33:08 hotspot,debug T-F4:F1:E1:F4:62:F6 (10.63.193.3): adding address-list rule <00>
feb/02 21:33:08 hotspot,debug T-F4:F1:E1:F4:62:F6 (10.63.193.3): adding queue <256k/256k 0/0 0/0 0/0 8 64k/64k>
feb/02 21:33:08 hotspot,account,info,debug T-F4:F1:E1:F4:62:F6 (10.63.193.3): logged in
feb/02 21:33:10 dhcp,info dhcp1 assigned 10.63.194.56 to C4:43:8F:5F:3A:33
feb/02 21:33:26 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.133 by UDP :65164 -> 10.63.192.1:53
feb/02 21:33:26 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.133, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:33:31 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.17 by UDP :41718 -> 10.63.192.1:53
feb/02 21:33:31 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.17, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:33:36 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :59424 -> 10.63.192.1:53
feb/02 21:33:36 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:33:48 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by UDP :62956 -> 10.63.192.1:53
feb/02 21:33:48 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.13, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:33:59 dhcp,info dhcp1 deassigned 10.63.193.21 from 20:55:31:66:20:D8
feb/02 21:33:59 hotspot,debug Hotspot: dhcp host 10.63.193.23 removed: login timeout
feb/02 21:34:01 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :22917 -> 10.63.192.1:53
feb/02 21:34:01 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.18, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:34:05 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by UDP :23141 -> 10.63.192.1:53
feb/02 21:34:05 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:34:06 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by TCP :38175 -> 158.85.58.39:443
feb/02 21:34:06 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:34:17 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by TCP :49901 -> 218.213.248.137:80
feb/02 21:34:17 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
feb/02 21:34:31 hotspot,debug Hotspot: dhcp host 10.63.194.38 removed: login timeout
feb/02 21:34:37 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by TCP :53718 -> 174.37.217.93:80
feb/02 21:34:37 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:34:40 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.133 by TCP :32965 -> 174.37.231.91:5222
feb/02 21:34:40 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.133, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:34:42 hotspot,debug Hotspot: dhcp host 10.63.193.31 removed: login timeout
feb/02 21:34:43 hotspot,debug Hotspot: new host detected 18:89:5B:0C:17:72/10.63.193.31 by UDP :7945 -> 10.63.192.1:53
feb/02 21:34:43 hotspot,debug Hotspot: dhcp host 18:89:5B:0C:17:72/10.63.193.31 added, ip 10.63.193.31
feb/02 21:34:49 dhcp,info dhcp1 assigned 10.63.193.41 to 88:C9:D0:DE:85:AB
feb/02 21:34:52 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by UDP :61245 -> 10.63.192.1:53
feb/02 21:34:52 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.13, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:34:53 hotspot,debug Hotspot: new host detected 88:C9:D0:DE:85:AB/10.63.193.41 by UDP :17913 -> 192.168.2.2:53
feb/02 21:34:53 hotspot,debug Hotspot: dhcp host 88:C9:D0:DE:85:AB/10.63.193.41 added, ip 10.63.193.41
feb/02 21:34:54 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.17 by UDP :33033 -> 10.63.192.1:53
feb/02 21:34:54 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.17, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:35:06 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by TCP :39789 -> 66.220.158.68:443
feb/02 21:35:06 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:35:06 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :13609 -> 10.63.192.1:53
feb/02 21:35:06 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.18, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:35:08 hotspot,debug Hotspot: dhcp host 10.63.194.28 removed: login timeout
feb/02 21:35:10 hotspot,debug Hotspot: new host detected 74:BA:DB:04:26:13/10.63.194.28 by TCP :53331 -> 216.58.202.14:443
feb/02 21:35:10 hotspot,debug Hotspot: dhcp host 74:BA:DB:04:26:13/10.63.194.28 added, ip 10.63.194.28
feb/02 21:35:18 hotspot,debug Hotspot: new host detected C4:9A:02:61:DA:A3/10.63.194.52 by UDP :35916 -> 10.63.192.1:53
feb/02 21:35:18 hotspot,debug Hotspot: dhcp host C4:9A:02:61:DA:A3/10.63.194.52 added, ip 10.63.194.52
feb/02 21:35:19 hotspot,debug Hotspot: new host detected C4:9A:02:61:DA:A3/100.73.26.60 by TCP :47569 -> 10.63.192.1:7
feb/02 21:35:19 hotspot,debug Hotspot: dhcp host 10.63.194.52 removed: limiting addresses per mac
feb/02 21:35:19 hotspot,debug Hotspot: dynamic host C4:9A:02:61:DA:A3/100.73.26.60 added, ip 10.63.193.2
feb/02 21:35:19 hotspot,debug Hotspot: new host detected C4:9A:02:61:DA:A3/10.63.194.52 by TCP :54969 -> 216.58.202.46:80
feb/02 21:35:19 hotspot,debug Hotspot: dynamic host 10.63.193.2 removed: limiting addresses per mac
feb/02 21:35:19 hotspot,debug Hotspot: dhcp host C4:9A:02:61:DA:A3/10.63.194.52 added, ip 10.63.194.52
feb/02 21:35:26 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by TCP :43916 -> 158.85.58.44:5222
feb/02 21:35:26 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:35:29 hotspot,info,debug T-60:D7:AE:C8:92:CC (10.63.193.51): logged out: keepalive timeout
feb/02 21:35:29 hotspot,debug T-60:D7:AE:C8:92:CC (10.63.193.51): removing queue
feb/02 21:35:29 hotspot,debug T-60:D7:AE:C8:92:CC (10.63.193.51): removing address-list
feb/02 21:35:29 hotspot,debug T-60:D7:AE:C8:92:CC (10.63.193.51): removing ip->user binding
feb/02 21:35:29 hotspot,debug Hotspot: dhcp host 10.63.193.51 removed: keepalive timeout
feb/02 21:35:53 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by UDP :37456 -> 10.63.192.1:53
feb/02 21:35:53 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.13, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:36:02 script,warning Google Up
feb/02 21:36:07 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.17 by UDP :45858 -> 10.63.192.1:53
feb/02 21:36:07 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.17, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:36:15 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.48 by UDP :57187 -> 10.63.192.1:53
feb/02 21:36:15 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.48, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:36:17 hotspot,debug Hotspot: dhcp host 10.63.193.23 removed: login timeout
feb/02 21:36:17 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by TCP :33910 -> 10.63.192.1:80
feb/02 21:36:17 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
feb/02 21:36:25 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :6955 -> 10.63.192.1:53
feb/02 21:36:25 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:36:27 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by UDP :28604 -> 10.63.192.1:53
feb/02 21:36:27 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:36:28 hotspot,debug Hotspot: new host detected 50:55:27:A0:E9:AF/10.63.193.133 by ICMP type<3> code<3> to 10.63.192.1
feb/02 21:36:28 hotspot,info,debug T-50:55:27:A0:E9:AF (10.63.193.133): trying to log in by mac-cookie
feb/02 21:36:28 hotspot,debug T-50:55:27:A0:E9:AF (10.63.193.133): using profile <00>
feb/02 21:36:28 hotspot,debug T-50:55:27:A0:E9:AF (10.63.193.133): adding ip->user binding
feb/02 21:36:28 hotspot,debug Hotspot: dhcp host 50:55:27:A0:E9:AF/10.63.193.133 added, ip 10.63.193.133
feb/02 21:36:28 hotspot,debug T-50:55:27:A0:E9:AF (10.63.193.133): adding address-list rule <00>
feb/02 21:36:28 hotspot,debug T-50:55:27:A0:E9:AF (10.63.193.133): adding queue <256k/256k 0/0 0/0 0/0 8 64k/64k>
feb/02 21:36:28 hotspot,account,info,debug T-50:55:27:A0:E9:AF (10.63.193.133): logged in
feb/02 21:36:31 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :58847 -> 10.63.192.1:53
feb/02 21:36:31 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.18, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:36:43 hotspot,debug Hotspot: dhcp host 10.63.193.31 removed: login timeout
feb/02 21:36:53 hotspot,debug Hotspot: dhcp host 10.63.193.41 removed: login timeout
feb/02 21:36:53 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by TCP :38014 -> 50.22.225.77:5222
feb/02 21:36:53 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.13, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:37:00 dhcp,info dhcp1 assigned 10.63.193.28 to F4:0E:22:7E:AB:C8
feb/02 21:37:10 hotspot,debug Hotspot: dhcp host 10.63.194.28 removed: login timeout
feb/02 21:37:13 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.28 by UDP :37782 -> 10.63.192.1:53
feb/02 21:37:13 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.28, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:37:19 hotspot,debug Hotspot: dhcp host 10.63.194.52 removed: login timeout
feb/02 21:37:20 system,info,account user ersitizastes logged in from 10.63.192.255 via winbox
feb/02 21:37:21 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.17 by UDP :34246 -> 10.63.192.1:53
feb/02 21:37:21 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.17, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:37:28 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :3533 -> 10.63.192.1:53
feb/02 21:37:28 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:37:30 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by UDP :53855 -> 10.63.192.1:53
feb/02 21:37:30 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:37:38 hotspot,debug Hotspot: new host detected 74:BA:DB:04:26:13/10.63.194.28 by UDP :23402 -> 8.8.8.8:53
feb/02 21:37:38 hotspot,debug Hotspot: dhcp host 74:BA:DB:04:26:13/10.63.194.28 added, ip 10.63.194.28
feb/02 21:37:54 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by UDP :41620 -> 10.63.192.1:53
feb/02 21:37:54 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.13, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:38:14 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :6316 -> 10.63.192.1:53
feb/02 21:38:14 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.18, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:38:17 hotspot,debug Hotspot: dhcp host 10.63.193.23 removed: login timeout
feb/02 21:38:31 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by UDP :53357 -> 8.8.4.4:53
feb/02 21:38:31 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:38:34 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.17 by UDP :39743 -> 10.63.192.1:53
feb/02 21:38:34 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.17, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:38:36 dhcp,info dhcp1 assigned 10.63.194.58 to C4:9A:02:5D:A1:DC
feb/02 21:38:37 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.58 by UDP :58815 -> 10.63.192.1:53
feb/02 21:38:37 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.58, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:38:38 dhcp,info dhcp1 deassigned 10.63.194.58 from C4:9A:02:5D:A1:DC
feb/02 21:38:39 dhcp,info dhcp1 assigned 10.63.194.58 to C4:9A:02:5D:A1:DC
feb/02 21:38:46 hotspot,info,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): logged out: keepalive timeout
feb/02 21:38:46 hotspot,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): removing queue
feb/02 21:38:46 hotspot,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): removing address-list
feb/02 21:38:46 hotspot,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): removing ip->user binding
feb/02 21:38:46 hotspot,debug Hotspot: dhcp host 10.63.193.44 removed: keepalive timeout
feb/02 21:38:54 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :2919 -> 10.63.192.1:53
feb/02 21:38:54 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:38:56 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by UDP :32141 -> 10.63.192.1:53
feb/02 21:38:56 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.13, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:39:07 dhcp,info dhcp1 assigned 10.63.194.54 to 84:11:9E:C2:02:FE
feb/02 21:39:08 hotspot,debug Hotspot: new host detected 84:11:9E:C2:02:FE/10.63.194.54 by UDP :42279 -> 10.63.192.1:53
feb/02 21:39:08 hotspot,debug Hotspot: dhcp host 84:11:9E:C2:02:FE/10.63.194.54 added, ip 10.63.194.54
feb/02 21:39:15 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.28 by UDP :47014 -> 10.63.192.1:53
feb/02 21:39:15 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.28, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:39:38 hotspot,debug Hotspot: dhcp host 10.63.194.28 removed: login timeout
feb/02 21:39:42 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by UDP :24711 -> 10.63.192.1:53
feb/02 21:39:42 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.59, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:39:48 hotspot,debug Hotspot: new host detected 74:BA:DB:04:26:13/10.63.194.28 by TCP :40020 -> 184.173.161.173:80
feb/02 21:39:48 hotspot,debug Hotspot: dhcp host 74:BA:DB:04:26:13/10.63.194.28 added, ip 10.63.194.28
feb/02 21:39:59 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :17659 -> 10.63.192.1:53
feb/02 21:39:59 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.18, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:40:00 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by UDP :52251 -> 10.63.192.1:53
feb/02 21:40:00 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.13, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:40:00 dhcp,info dhcp1 deassigned 10.63.194.58 from C4:9A:02:5D:A1:DC
feb/02 21:40:01 hotspot,debug Hotspot: new host detected C4:9A:02:61:DA:A3/10.63.194.52 by UDP :9347 -> 10.63.192.1:53
feb/02 21:40:01 hotspot,debug Hotspot: dhcp host C4:9A:02:61:DA:A3/10.63.194.52 added, ip 10.63.194.52
feb/02 21:40:21 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.28 by UDP :41586 -> 10.63.192.1:53
feb/02 21:40:21 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.28, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:40:21 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by TCP :55497 -> 158.85.58.22:80
feb/02 21:40:21 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:40:30 dhcp,info dhcp1 deassigned 10.63.194.52 from C4:9A:02:61:DA:A3
feb/02 21:40:30 hotspot,debug Hotspot: dhcp host 10.63.194.52 changed type to dynamic (remove after 5s)
feb/02 21:40:35 hotspot,debug Hotspot: dynamic host 10.63.194.52 removed: lost dhcp lease
feb/02 21:41:01 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by UDP :31608 -> 10.63.192.1:53
feb/02 21:41:01 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.13, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:41:05 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :22134 -> 10.63.192.1:53
feb/02 21:41:05 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.18, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:41:08 hotspot,debug Hotspot: new host detected 6C:2F:2C:1C:E4:DC/10.63.193.44 by UDP :37362 -> 10.63.192.1:53
feb/02 21:41:08 hotspot,info,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): trying to log in by mac-cookie
feb/02 21:41:08 hotspot,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): using profile <00>
feb/02 21:41:08 hotspot,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): adding ip->user binding
feb/02 21:41:08 hotspot,debug Hotspot: dhcp host 6C:2F:2C:1C:E4:DC/10.63.193.44 added, ip 10.63.193.44
feb/02 21:41:08 hotspot,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): adding address-list rule <00>
feb/02 21:41:08 hotspot,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): adding queue <256k/256k 0/0 0/0 0/0 8 64k/64k>
feb/02 21:41:08 hotspot,account,info,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): logged in
feb/02 21:41:08 hotspot,debug Hotspot: dhcp host 10.63.194.54 removed: login timeout
feb/02 21:41:13 dhcp,info dhcp1 deassigned 10.63.193.23 from 38:2D:D1:A5:04:39
feb/02 21:41:14 dhcp,info dhcp1 assigned 10.63.194.52 to C4:9A:02:61:DA:A3
feb/02 21:41:15 hotspot,debug Hotspot: new host detected C4:9A:02:61:DA:A3/10.63.194.52 by UDP :28868 -> 10.63.192.1:53
feb/02 21:41:15 hotspot,debug Hotspot: dhcp host C4:9A:02:61:DA:A3/10.63.194.52 added, ip 10.63.194.52
feb/02 21:41:16 dhcp,info dhcp1 assigned 10.63.193.23 to 38:2D:D1:A5:04:39
feb/02 21:41:17 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by UDP :37813 -> 10.63.192.1:53
feb/02 21:41:17 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
feb/02 21:41:26 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.28 by UDP :44392 -> 10.63.192.1:53
feb/02 21:41:26 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.193.28, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:41:27 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :35275 -> 10.63.192.1:53
feb/02 21:41:27 hotspot,debug Hotspot: failed to add dynamic host 4C:5E:0C:CA:05:46/10.63.194.33, ip 10.63.193.150: max addresses per mac is reached
feb/02 21:41:48 hotspot,debug Hotspot: dhcp host 10.63.194.28 removed: login timeout
feb/02 21:41:48 system,info log rule removed by ersitizastes
feb/02 21:42:41 hotspot,info,debug T-60:D7:AE:C8:92:CC (10.63.193.51): trying to log in by mac-cookie
feb/02 21:42:41 hotspot,account,info,debug T-60:D7:AE:C8:92:CC (10.63.193.51): logged in
feb/02 21:42:47 dhcp,info dhcp1 deassigned 10.63.193.44 from 6C:2F:2C:1C:E4:DC
feb/02 21:42:47 dhcp,info dhcp1 assigned 10.63.194.61 to 14:32:D1:1C:E1:24
feb/02 21:42:52 hotspot,info,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): logged out: lost dhcp lease
feb/02 21:43:49 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:44:03 system,info hotspot server Hotspot changed by ersitizastes
feb/02 21:45:24 dhcp,info dhcp1 deassigned 10.63.194.28 from 74:BA:DB:04:26:13
feb/02 21:45:24 dhcp,info dhcp1 assigned 10.63.194.28 to 74:BA:DB:04:26:13
feb/02 21:45:35 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:45:35 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:45:35 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:45:35 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:45:35 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:45:35 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:45:35 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:46:51 hotspot,info,debug T-F4:F1:E1:F4:62:F6 (10.63.193.3): logged out: session timeout
feb/02 21:47:05 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:47:05 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:47:05 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:47:05 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:47:05 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:47:11 hotspot,info,debug T-60:D7:AE:C8:92:CC (10.63.193.51): logged out: keepalive timeout
feb/02 21:47:14 dhcp,info dhcp1 deassigned 10.63.194.42 from 34:FC:EF:CF:50:24
feb/02 21:47:15 dhcp,info dhcp1 deassigned 10.63.194.36 from 50:B7:C3:CC:5C:A8
feb/02 21:47:24 dhcp,info dhcp1 assigned 10.63.194.42 to 34:FC:EF:CF:50:24
feb/02 21:47:52 system,info hotspot server Hotspot changed by ersitizastes
feb/02 21:49:11 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:50:00 dhcp,info dhcp1 deassigned 10.63.194.39 from 58:A2:B5:DA:FD:96
feb/02 21:50:38 hotspot,info,debug T-50:55:27:A0:E9:AF (10.63.193.133): logged out: session timeout
feb/02 21:50:38 hotspot,info,debug T-60:D7:AE:C8:92:CC (10.63.193.51): trying to log in by mac-cookie
feb/02 21:50:38 hotspot,account,info,debug T-60:D7:AE:C8:92:CC (10.63.193.51): logged in
feb/02 21:50:55 system,info hotspot ip binding rule changed by ersitizastes
feb/02 21:51:42 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:51:42 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:51:42 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:51:42 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:51:42 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:51:42 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:51:42 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:51:42 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:51:43 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:51:45 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:51:45 wireless,info wlan: data from unknown device 64:6C:B2:51:9E:0D, sent deauth
feb/02 21:52:06 dhcp,info dhcp1 assigned 10.63.194.67 to 64:6C:B2:51:9E:0D
feb/02 21:52:08 system,info hotspot ip binding rule changed by ersitizastes
feb/02 21:52:59 dhcp,info dhcp1 assigned 10.63.193.44 to 6C:2F:2C:1C:E4:DC
feb/02 21:53:00 hotspot,info,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): trying to log in by mac-cookie
feb/02 21:53:00 hotspot,account,info,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): logged in
feb/02 21:53:05 hotspot,info,debug T-64:6C:B2:51:9E:0D (10.63.194.67): trying to log in by trial
feb/02 21:53:05 hotspot,account,info,debug T-64:6C:B2:51:9E:0D (10.63.194.67): logged in
feb/02 21:53:07 dhcp,info dhcp1 deassigned 10.63.194.34 from 20:55:31:74:FC:48
feb/02 21:53:25 dhcp,info dhcp1 assigned 10.63.194.69 to 1C:B7:2C:C4:61:14
feb/02 21:53:52 dhcp,info dhcp1 assigned 10.63.194.34 to 20:55:31:74:FC:48
feb/02 21:54:28 system,info log rule added by ersitizastes
feb/02 21:54:40 hotspot,debug Hotspot: dynamic host 10.63.194.37 removed: login timeout
feb/02 21:54:42 hotspot,debug Hotspot: dhcp host 10.63.194.28 removed: login timeout
feb/02 21:54:51 hotspot,debug Hotspot: dynamic host 10.63.193.150 removed: login timeout
feb/02 21:54:51 dhcp,info dhcp1 deassigned 10.63.194.40 from 34:FC:EF:D1:29:25
feb/02 21:54:53 hotspot,debug Hotspot: dynamic host 10.63.194.68 removed: login timeout
feb/02 21:54:54 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :7659 -> 10.63.192.1:53
feb/02 21:54:54 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.194.33 added, ip 10.63.193.150
feb/02 21:54:54 hotspot,debug Hotspot: new host detected 74:BA:DB:04:26:13/10.63.194.28 by UDP :33474 -> 10.63.192.1:53
feb/02 21:54:54 hotspot,debug Hotspot: dhcp host 74:BA:DB:04:26:13/10.63.194.28 added, ip 10.63.194.28
feb/02 21:54:54 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by UDP :42915 -> 10.63.192.1:53
feb/02 21:54:54 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.13 added, ip 10.63.194.72
feb/02 21:55:15 system,info,account user ersitizastes logged out from 10.63.192.255 via winbox
feb/02 21:55:18 dhcp,info dhcp1 deassigned 10.63.193.51 from 60:D7:AE:C8:92:CC
feb/02 21:55:18 hotspot,debug Hotspot: dhcp host 10.63.193.51 changed type to dynamic (remove after 5s)
feb/02 21:55:18 dhcp,info dhcp1 assigned 10.63.193.51 to 60:D7:AE:C8:92:CC
feb/02 21:55:18 hotspot,debug Hotspot: dynamic host 10.63.193.51 changed type to dhcp (got back lease)
feb/02 21:55:21 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :18135 -> 10.63.192.1:53
feb/02 21:55:21 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.194.18 added, ip 10.63.194.37
feb/02 21:55:26 hotspot,debug Hotspot: dynamic host 10.63.194.70 removed: login timeout
feb/02 21:55:28 hotspot,debug Hotspot: dhcp host 10.63.193.3 removed: login timeout
feb/02 21:55:36 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.69 by TCP :48081 -> 31.13.85.2:443
feb/02 21:55:36 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.194.69 added, ip 10.63.194.73
feb/02 21:55:50 hotspot,debug Hotspot: dynamic host 10.63.194.29 removed: login timeout
feb/02 21:55:54 hotspot,debug Hotspot: dynamic host 10.63.194.71 removed: login timeout
feb/02 21:56:01 hotspot,debug Hotspot: dhcp host 10.63.193.23 removed: login timeout
feb/02 21:56:02 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.28 by UDP :42140 -> 10.63.192.1:53
feb/02 21:56:02 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.28 added, ip 10.63.194.29
feb/02 21:56:03 hotspot,debug Hotspot: dynamic host 10.63.194.45 removed: login timeout
feb/02 21:56:20 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by TCP :42004 -> 173.194.209.188:5228
feb/02 21:56:20 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
feb/02 21:56:32 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by UDP :3590 -> 10.63.192.1:53
feb/02 21:56:32 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.59 added, ip 10.63.194.74
feb/02 21:56:54 hotspot,debug Hotspot: dynamic host 10.63.193.150 removed: login timeout
feb/02 21:56:54 hotspot,debug Hotspot: dhcp host 10.63.194.28 removed: login timeout
feb/02 21:56:54 hotspot,debug Hotspot: dynamic host 10.63.194.72 removed: login timeout
feb/02 21:57:08 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by UDP :38800 -> 10.63.192.1:53
feb/02 21:57:08 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.13 added, ip 10.63.193.150
feb/02 21:57:13 system,info,account user ersitizastes logged in from 10.63.192.255 via winbox
feb/02 21:57:16 dhcp,info dhcp1 deassigned 10.63.193.51 from 60:D7:AE:C8:92:CC
feb/02 21:57:16 hotspot,debug Hotspot: dhcp host 10.63.193.51 changed type to dynamic (remove after 5s)
feb/02 21:57:16 dhcp,info dhcp1 assigned 10.63.193.51 to 60:D7:AE:C8:92:CC
feb/02 21:57:16 hotspot,debug Hotspot: dynamic host 10.63.193.51 changed type to dhcp (got back lease)
feb/02 21:57:21 hotspot,debug Hotspot: dynamic host 10.63.194.37 removed: login timeout
feb/02 21:57:22 dhcp,info dhcp1 deassigned 10.63.194.28 from 74:BA:DB:04:26:13
feb/02 21:57:22 dhcp,info dhcp1 assigned 10.63.194.28 to 74:BA:DB:04:26:13
feb/02 21:57:23 hotspot,debug Hotspot: new host detected F4:F1:E1:F4:62:F6/10.63.193.3 by TCP :60109 -> 183.61.112.123:80
feb/02 21:57:23 hotspot,debug Hotspot: dhcp host F4:F1:E1:F4:62:F6/10.63.193.3 added, ip 10.63.193.3
feb/02 21:57:26 hotspot,debug Hotspot: new host detected 74:BA:DB:04:26:13/10.63.194.28 by UDP :8494 -> 10.63.192.1:53
feb/02 21:57:26 hotspot,debug Hotspot: dhcp host 74:BA:DB:04:26:13/10.63.194.28 added, ip 10.63.194.28
feb/02 21:57:36 hotspot,debug Hotspot: dynamic host 10.63.194.73 removed: login timeout
feb/02 21:57:46 system,info,account user ersitizastes logged in from 10.63.192.255 via telnet
feb/02 21:58:02 hotspot,debug Hotspot: dynamic host 10.63.194.29 removed: login timeout
feb/02 21:58:06 dhcp,info dhcp1 deassigned 10.63.194.41 from 34:FC:EF:D3:AD:1D
feb/02 21:58:13 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.28 by UDP :50240 -> 10.63.192.1:53
feb/02 21:58:13 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.28 added, ip 10.63.194.75
feb/02 21:58:20 hotspot,debug Hotspot: dhcp host 10.63.193.23 removed: login timeout
feb/02 21:58:32 hotspot,debug Hotspot: dynamic host 10.63.194.74 removed: login timeout
feb/02 21:58:38 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by TCP :47184 -> 178.162.219.58:443
feb/02 21:58:38 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
feb/02 21:58:39 dhcp,info dhcp1 assigned 10.63.194.58 to C4:9A:02:5D:A1:DC
feb/02 21:58:39 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.58 by UDP :10227 -> 10.63.192.1:53
feb/02 21:58:39 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.194.58 added, ip 10.63.194.29
feb/02 21:59:08 hotspot,debug Hotspot: dynamic host 10.63.193.150 removed: login timeout
feb/02 21:59:16 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by TCP :42993 -> 158.85.58.9:80
feb/02 21:59:16 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.13 added, ip 10.63.193.150
feb/02 21:59:17 dhcp,info dhcp1 deassigned 10.63.194.33 from EC:88:92:40:CC:8B
feb/02 21:59:23 hotspot,debug Hotspot: dhcp host 10.63.193.3 removed: login timeout
feb/02 21:59:27 hotspot,debug Hotspot: dhcp host 10.63.194.28 removed: login timeout
feb/02 21:59:27 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :1060 -> 10.63.192.1:53
feb/02 21:59:27 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.194.18 added, ip 10.63.194.76
feb/02 21:59:29 hotspot,debug Hotspot: new host detected F4:F1:E1:F4:62:F6/10.63.193.3 by TCP :43232 -> 69.28.57.171:8888
feb/02 21:59:29 hotspot,debug Hotspot: dhcp host F4:F1:E1:F4:62:F6/10.63.193.3 added, ip 10.63.193.3
feb/02 22:00:03 script,error Google Down
feb/02 22:00:07 dhcp,info dhcp1 deassigned 10.63.194.35 from F4:F1:E1:1E:3A:2C
feb/02 22:00:11 dhcp,info dhcp1 assigned 10.63.194.35 to F4:F1:E1:1E:3A:2C
feb/02 22:00:13 hotspot,debug Hotspot: new host detected F4:F1:E1:1E:3A:2C/10.63.194.35 by UDP :65228 -> 10.63.192.1:53
feb/02 22:00:13 hotspot,debug Hotspot: dhcp host F4:F1:E1:1E:3A:2C/10.63.194.35 added, ip 10.63.194.35
feb/02 22:00:13 hotspot,debug Hotspot: dynamic host 10.63.194.75 removed: login timeout
feb/02 22:00:15 dhcp,info dhcp1 deassigned 10.63.193.51 from 60:D7:AE:C8:92:CC
feb/02 22:00:15 hotspot,debug Hotspot: dhcp host 10.63.193.51 changed type to dynamic (remove after 5s)
feb/02 22:00:19 dhcp,info dhcp1 assigned 10.63.193.51 to 60:D7:AE:C8:92:CC
feb/02 22:00:19 hotspot,debug Hotspot: dynamic host 10.63.193.51 changed type to dhcp (got back lease)
feb/02 22:00:24 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.28 by UDP :60884 -> 10.63.192.1:53
feb/02 22:00:24 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.28 added, ip 10.63.194.77
feb/02 22:00:38 hotspot,debug Hotspot: dhcp host 10.63.193.23 removed: login timeout
feb/02 22:00:39 hotspot,debug Hotspot: dynamic host 10.63.194.29 removed: login timeout
feb/02 22:00:40 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.58 by UDP :63722 -> 10.63.192.1:53
feb/02 22:00:40 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.194.58 added, ip 10.63.194.29
feb/02 22:00:53 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by TCP :59332 -> 31.13.73.3:443
feb/02 22:00:53 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
feb/02 22:01:16 hotspot,debug Hotspot: dynamic host 10.63.193.150 removed: login timeout
feb/02 22:01:16 dhcp,info dhcp1 deassigned 10.63.193.37 from 14:1A:A3:68:7E:60
feb/02 22:01:27 hotspot,debug Hotspot: dynamic host 10.63.194.76 removed: login timeout
feb/02 22:01:29 hotspot,debug Hotspot: dhcp host 10.63.193.3 removed: login timeout
feb/02 22:01:32 hotspot,debug Hotspot: new host detected F4:F1:E1:F4:62:F6/10.63.193.3 by UDP :55165 -> 8.8.8.8:53
feb/02 22:01:32 hotspot,debug Hotspot: dhcp host F4:F1:E1:F4:62:F6/10.63.193.3 added, ip 10.63.193.3
feb/02 22:01:37 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by UDP :60193 -> 10.63.192.1:53
feb/02 22:01:37 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.13 added, ip 10.63.193.150
feb/02 22:02:03 script,warning Google Up
feb/02 22:02:13 hotspot,debug Hotspot: dhcp host 10.63.194.35 removed: login timeout
feb/02 22:02:24 hotspot,debug Hotspot: dynamic host 10.63.194.77 removed: login timeout
feb/02 22:02:40 hotspot,debug Hotspot: dynamic host 10.63.194.29 removed: login timeout
feb/02 22:02:44 interface,info ether9 link down
feb/02 22:02:53 hotspot,debug Hotspot: dhcp host 10.63.193.23 removed: login timeout
feb/02 22:03:00 script,error 5g.net 1 Down
feb/02 22:03:03 script,error 5g.net 2 Down
feb/02 22:03:11 interface,info ether9 link up (speed 100M, full duplex)
feb/02 22:03:13 dhcp,info dhcp1 deassigned 10.63.193.16 from 9C:D3:5B:51:B7:AE
feb/02 22:03:30 hotspot,info,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): logged out: keepalive timeout
feb/02 22:03:30 hotspot,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): removing queue
feb/02 22:03:30 hotspot,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): removing address-list
feb/02 22:03:30 hotspot,debug T-6C:2F:2C:1C:E4:DC (10.63.193.44): removing ip->user binding
feb/02 22:03:30 hotspot,debug Hotspot: dhcp host 10.63.193.44 removed: keepalive timeout
feb/02 22:03:32 hotspot,debug Hotspot: dhcp host 10.63.193.3 removed: login timeout
feb/02 22:03:36 hotspot,debug Hotspot: new host detected F4:F1:E1:F4:62:F6/10.63.193.3 by UDP :9639 -> 10.63.192.1:53
feb/02 22:03:36 hotspot,debug Hotspot: dhcp host F4:F1:E1:F4:62:F6/10.63.193.3 added, ip 10.63.193.3
feb/02 22:03:37 hotspot,debug Hotspot: dynamic host 10.63.193.150 removed: login timeout
feb/02 22:03:41 dhcp,info dhcp1 deassigned 10.63.193.23 from 38:2D:D1:A5:04:39
feb/02 22:03:41 dhcp,info dhcp1 assigned 10.63.193.23 to 38:2D:D1:A5:04:39
feb/02 22:03:41 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by UDP :22301 -> 10.63.192.1:53
feb/02 22:03:41 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
feb/02 22:03:42 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.28 by UDP :42807 -> 10.63.192.1:53
feb/02 22:03:42 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.28 added, ip 10.63.193.150
feb/02 22:04:00 script,warning 5g.net 1 Up
feb/02 22:04:00 script,warning 5g.net 2 Up
feb/02 22:04:26 dhcp,info dhcp1 deassigned 10.63.193.51 from 60:D7:AE:C8:92:CC
feb/02 22:04:26 hotspot,debug Hotspot: dhcp host 10.63.193.51 changed type to dynamic (remove after 5s)
feb/02 22:04:31 hotspot,info,debug T-60:D7:AE:C8:92:CC (10.63.193.51): logged out: lost dhcp lease
feb/02 22:04:31 hotspot,debug T-60:D7:AE:C8:92:CC (10.63.193.51): removing queue
feb/02 22:04:31 hotspot,debug T-60:D7:AE:C8:92:CC (10.63.193.51): removing address-list
feb/02 22:04:31 hotspot,debug T-60:D7:AE:C8:92:CC (10.63.193.51): removing ip->user binding
feb/02 22:04:31 hotspot,debug Hotspot: dynamic host 10.63.193.51 removed: lost dhcp lease
feb/02 22:04:33 dhcp,info dhcp1 deassigned 10.63.194.44 from B8:5A:73:B1:50:E0
feb/02 22:04:42 hotspot,info,debug T-64:6C:B2:51:9E:0D (10.63.194.67): logged out: keepalive timeout
feb/02 22:04:42 hotspot,debug T-64:6C:B2:51:9E:0D (10.63.194.67): removing queue
feb/02 22:04:42 hotspot,debug T-64:6C:B2:51:9E:0D (10.63.194.67): removing address-list
feb/02 22:04:42 hotspot,debug T-64:6C:B2:51:9E:0D (10.63.194.67): removing ip->user binding
feb/02 22:04:42 hotspot,debug Hotspot: dhcp host 10.63.194.67 removed: keepalive timeout
feb/02 22:05:02 dhcp,info dhcp1 deassigned 10.63.193.13 from 18:22:7E:2A:5A:5E
feb/02 22:05:04 hotspot,debug Hotspot: new host detected 64:6C:B2:51:9E:0D/10.63.194.67 by UDP :56050 -> 10.63.192.1:53
feb/02 22:05:04 hotspot,info,debug T-64:6C:B2:51:9E:0D (10.63.194.67): trying to log in by mac-cookie
feb/02 22:05:04 hotspot,debug T-64:6C:B2:51:9E:0D (10.63.194.67): using profile <00>
feb/02 22:05:04 hotspot,debug T-64:6C:B2:51:9E:0D (10.63.194.67): adding ip->user binding
feb/02 22:05:04 hotspot,debug Hotspot: dhcp host 64:6C:B2:51:9E:0D/10.63.194.67 added, ip 10.63.194.67
feb/02 22:05:04 hotspot,debug T-64:6C:B2:51:9E:0D (10.63.194.67): adding address-list rule <00>
feb/02 22:05:04 hotspot,debug T-64:6C:B2:51:9E:0D (10.63.194.67): adding queue <256k/256k 0/0 0/0 0/0 8 64k/64k>
feb/02 22:05:04 hotspot,account,info,debug T-64:6C:B2:51:9E:0D (10.63.194.67): logged in
feb/02 22:05:07 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.58 by UDP :40420 -> 10.63.192.1:53
feb/02 22:05:07 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.194.58 added, ip 10.63.194.78
feb/02 22:05:17 dhcp,info dhcp1 assigned 10.63.193.13 to 18:22:7E:2A:5A:5E
feb/02 22:05:18 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.13 by UDP :22291 -> 10.63.192.1:53
feb/02 22:05:18 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.13 added, ip 10.63.194.29
feb/02 22:05:36 hotspot,debug Hotspot: dhcp host 10.63.193.3 removed: login timeout
feb/02 22:05:36 hotspot,debug Hotspot: new host detected F4:F1:E1:F4:62:F6/10.63.193.3 by TCP :35068 -> 173.194.118.68:443
feb/02 22:05:36 hotspot,debug Hotspot: dhcp host F4:F1:E1:F4:62:F6/10.63.193.3 added, ip 10.63.193.3
feb/02 22:05:41 hotspot,debug Hotspot: dhcp host 10.63.193.23 removed: login timeout
feb/02 22:05:42 hotspot,debug Hotspot: dynamic host 10.63.193.150 removed: login timeout
feb/02 22:05:46 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.28 by UDP :40330 -> 10.63.192.1:53
feb/02 22:05:46 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.28 added, ip 10.63.193.150
feb/02 22:06:04 system,info,account user ersitizastes logged out from 10.63.192.255 via winbox
feb/02 22:06:04 system,info,account user ersitizastes logged out from 10.63.192.255 via telnet
feb/02 22:07:07 hotspot,debug Hotspot: dynamic host 10.63.194.78 removed: login timeout
feb/02 22:07:18 hotspot,debug Hotspot: dynamic host 10.63.194.29 removed: login timeout
feb/02 22:07:33 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by UDP :18061 -> 10.63.192.1:53
feb/02 22:07:33 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.59 added, ip 10.63.194.80
feb/02 22:07:36 hotspot,debug Hotspot: dhcp host 10.63.193.3 removed: login timeout
feb/02 22:07:36 hotspot,debug Hotspot: new host detected F4:F1:E1:F4:62:F6/10.63.193.3 by TCP :59255 -> 173.194.118.65:443
feb/02 22:07:36 hotspot,debug Hotspot: dhcp host F4:F1:E1:F4:62:F6/10.63.193.3 added, ip 10.63.193.3
feb/02 22:07:39 dhcp,info dhcp1 deassigned 10.63.193.59 from F8:A9:D0:5A:F4:85
feb/02 22:07:39 dhcp,info dhcp1 assigned 10.63.193.59 to F8:A9:D0:5A:F4:85
feb/02 22:07:46 hotspot,debug Hotspot: dynamic host 10.63.193.150 removed: login timeout
feb/02 22:07:53 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.28 by UDP :49504 -> 10.63.192.1:53
feb/02 22:07:53 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.28 added, ip 10.63.193.150
feb/02 22:07:59 dhcp,info dhcp1 deassigned 10.63.194.58 from C4:9A:02:5D:A1:DC
feb/02 22:07:59 dhcp,info dhcp1 assigned 10.63.194.58 to C4:9A:02:5D:A1:DC
feb/02 22:08:02 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.58 by UDP :51208 -> 10.63.192.1:53
feb/02 22:08:02 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.194.58 added, ip 10.63.194.81
feb/02 22:08:03 script,error Google Down
feb/02 22:08:23 dhcp,info dhcp1 deassigned 10.63.193.90 from C4:3A:BE:D2:D1:20
feb/02 22:08:54 dhcp,info dhcp1 deassigned 10.63.193.23 from 38:2D:D1:A5:04:39
feb/02 22:09:01 script,warning Google Up
feb/02 22:09:33 hotspot,debug Hotspot: dynamic host 10.63.194.80 removed: login timeout
feb/02 22:09:33 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by UDP :52890 -> 10.63.192.1:53
feb/02 22:09:33 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.59 added, ip 10.63.194.29
feb/02 22:09:36 hotspot,debug Hotspot: dhcp host 10.63.193.3 removed: login timeout
feb/02 22:09:44 dhcp,info dhcp1 assigned 10.63.193.23 to 38:2D:D1:A5:04:39
feb/02 22:09:44 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by UDP :2587 -> 10.63.192.1:53
feb/02 22:09:44 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
feb/02 22:09:53 hotspot,debug Hotspot: dynamic host 10.63.193.150 removed: login timeout
feb/02 22:09:53 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.28 by UDP :55006 -> 10.63.192.1:53
feb/02 22:09:53 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.28 added, ip 10.63.193.150
feb/02 22:10:01 hotspot,debug Hotspot: new host detected F4:F1:E1:F4:62:F6/10.63.193.3 by TCP :55498 -> 205.251.251.114:80
feb/02 22:10:01 hotspot,debug Hotspot: dhcp host F4:F1:E1:F4:62:F6/10.63.193.3 added, ip 10.63.193.3
feb/02 22:10:02 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :47629 -> 10.63.192.1:53
feb/02 22:10:02 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.194.18 added, ip 10.63.194.82
feb/02 22:10:02 hotspot,debug Hotspot: dynamic host 10.63.194.81 removed: login timeout
feb/02 22:10:28 hotspot,debug Hotspot: new host detected F4:F1:E1:1E:3A:2C/10.63.194.35 by UDP :46346 -> 8.8.8.8:53
feb/02 22:10:28 hotspot,debug Hotspot: dhcp host F4:F1:E1:1E:3A:2C/10.63.194.35 added, ip 10.63.194.35
feb/02 22:10:45 wireless,info wlan: data from unknown device 00:F4:6F:F6:0A:DF, sent deauth
feb/02 22:10:45 wireless,info wlan: data from unknown device 00:F4:6F:F6:0A:DF, sent deauth
feb/02 22:10:45 wireless,info wlan: data from unknown device 00:F4:6F:F6:0A:DF, sent deauth
feb/02 22:10:45 wireless,info wlan: data from unknown device 00:F4:6F:F6:0A:DF, sent deauth
feb/02 22:11:24 wireless,info wlan: data from unknown device 00:F4:6F:F6:0A:DF, sent deauth
feb/02 22:11:24 wireless,info wlan: data from unknown device 00:F4:6F:F6:0A:DF, sent deauth
feb/02 22:11:24 wireless,info wlan: data from unknown device 00:F4:6F:F6:0A:DF, sent deauth
feb/02 22:11:24 wireless,info wlan: data from unknown device 00:F4:6F:F6:0A:DF, sent deauth
feb/02 22:11:24 wireless,info wlan: data from unknown device 00:F4:6F:F6:0A:DF, sent deauth
feb/02 22:11:26 wireless,info wlan: data from unknown device 00:F4:6F:F6:0A:DF, sent deauth
feb/02 22:11:26 wireless,info wlan: data from unknown device 00:F4:6F:F6:0A:DF, sent deauth
feb/02 22:11:26 wireless,info wlan: data from unknown device 00:F4:6F:F6:0A:DF, sent deauth
feb/02 22:11:26 wireless,info wlan: data from unknown device 00:F4:6F:F6:0A:DF, sent deauth
feb/02 22:11:26 wireless,info wlan: data from unknown device 00:F4:6F:F6:0A:DF, sent deauth
feb/02 22:11:26 wireless,info wlan: data from unknown device 00:F4:6F:F6:0A:DF, sent deauth
feb/02 22:11:33 hotspot,debug Hotspot: dynamic host 10.63.194.29 removed: login timeout
feb/02 22:11:44 hotspot,debug Hotspot: dhcp host 10.63.193.23 removed: login timeout
feb/02 22:11:44 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by TCP :32956 -> 61.145.124.57:80
feb/02 22:11:44 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
feb/02 22:11:53 dhcp,info dhcp1 assigned 10.63.194.84 to 00:F4:6F:F6:0A:DF
feb/02 22:11:53 hotspot,debug Hotspot: new host detected 00:F4:6F:F6:0A:DF/10.63.194.84 by UDP :38280 -> 10.63.192.1:53
feb/02 22:11:53 hotspot,debug Hotspot: dhcp host 00:F4:6F:F6:0A:DF/10.63.194.84 added, ip 10.63.194.84
feb/02 22:11:53 hotspot,debug Hotspot: dynamic host 10.63.193.150 removed: login timeout
feb/02 22:12:01 hotspot,debug Hotspot: dhcp host 10.63.193.3 removed: login timeout
feb/02 22:12:02 hotspot,debug Hotspot: dynamic host 10.63.194.82 removed: login timeout
feb/02 22:12:05 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.28 by UDP :46675 -> 10.63.192.1:53
feb/02 22:12:05 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.28 added, ip 10.63.193.150
feb/02 22:12:06 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :4737 -> 10.63.192.1:53
feb/02 22:12:06 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.194.18 added, ip 10.63.194.86
feb/02 22:12:12 hotspot,info,debug T-00:F4:6F:F6:0A:DF (10.63.194.84): trying to log in by trial
feb/02 22:12:12 hotspot,debug T-00:F4:6F:F6:0A:DF (10.63.194.84): using profile <00>
feb/02 22:12:12 hotspot,debug T-00:F4:6F:F6:0A:DF (10.63.194.84): adding ip->user binding
feb/02 22:12:12 hotspot,debug T-00:F4:6F:F6:0A:DF (10.63.194.84): adding address-list rule <00>
feb/02 22:12:12 hotspot,debug T-00:F4:6F:F6:0A:DF (10.63.194.84): adding queue <256k/256k 0/0 0/0 0/0 8 64k/64k>
feb/02 22:12:12 hotspot,account,info,debug T-00:F4:6F:F6:0A:DF (10.63.194.84): logged in
feb/02 22:12:17 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by UDP :46746 -> 10.63.192.1:53
feb/02 22:12:17 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.59 added, ip 10.63.194.29
feb/02 22:12:21 dhcp,info dhcp1 deassigned 10.63.194.28 from 74:BA:DB:04:26:13
feb/02 22:12:21 dhcp,info dhcp1 assigned 10.63.194.28 to 74:BA:DB:04:26:13
feb/02 22:12:25 hotspot,debug Hotspot: new host detected 74:BA:DB:04:26:13/10.63.194.28 by UDP :44460 -> 10.63.192.1:53
feb/02 22:12:25 hotspot,debug Hotspot: dhcp host 74:BA:DB:04:26:13/10.63.194.28 added, ip 10.63.194.28
feb/02 22:12:25 hotspot,debug Hotspot: new host detected F4:F1:E1:F4:62:F6/10.63.193.3 by UDP :1274 -> 10.63.192.1:53
feb/02 22:12:25 hotspot,debug Hotspot: dhcp host F4:F1:E1:F4:62:F6/10.63.193.3 added, ip 10.63.193.3
feb/02 22:12:28 hotspot,debug Hotspot: dhcp host 10.63.194.35 removed: login timeout
feb/02 22:12:42 dhcp,info dhcp1 assigned 10.63.194.87 to 84:11:9E:C3:1F:FE
feb/02 22:12:47 hotspot,debug Hotspot: new host detected 84:11:9E:C3:1F:FE/10.63.194.87 by TCP :48754 -> 31.13.71.3:443
feb/02 22:12:47 hotspot,debug Hotspot: dhcp host 84:11:9E:C3:1F:FE/10.63.194.87 added, ip 10.63.194.87
feb/02 22:12:52 dhcp,info dhcp1 assigned 10.63.194.85 to 0C:B3:19:E9:AE:30
feb/02 22:12:53 hotspot,debug Hotspot: new host detected 0C:B3:19:E9:AE:30/10.63.194.85 by UDP :44941 -> 10.63.192.1:53
feb/02 22:12:53 hotspot,debug Hotspot: dhcp host 0C:B3:19:E9:AE:30/10.63.194.85 added, ip 10.63.194.85
feb/02 22:12:55 system,info,account user ersitizastes logged in from 10.63.192.255 via winbox
feb/02 22:12:55 system,info,account user ersitizastes logged in from 10.63.192.255 via telnet
feb/02 22:12:57 dhcp,info dhcp1 assigned 10.63.194.88 to 10:D3:8A:17:AB:26
feb/02 22:12:58 hotspot,debug Hotspot: new host detected 10:D3:8A:17:AB:26/10.63.194.88 by TCP :39443 -> 10.63.192.1:7
feb/02 22:12:58 hotspot,debug Hotspot: dhcp host 10:D3:8A:17:AB:26/10.63.194.88 added, ip 10.63.194.88
feb/02 22:13:03 script,error Google Down
feb/02 22:13:04 dhcp,info dhcp1 deassigned 10.63.194.85 from 0C:B3:19:E9:AE:30
feb/02 22:13:04 hotspot,debug Hotspot: dhcp host 10.63.194.85 changed type to dynamic (remove after 5s)
feb/02 22:13:04 dhcp,info dhcp1 assigned 10.63.194.85 to 0C:B3:19:E9:AE:30
feb/02 22:13:04 hotspot,debug Hotspot: dynamic host 10.63.194.85 changed type to dhcp (got back lease)
feb/02 22:13:13 system,info,account user ersitizastes logged out from 10.63.192.255 via telnet
feb/02 22:13:29 system,info,account user ersitizastes logged in from 10.63.192.255 via telnet
feb/02 22:13:44 hotspot,debug Hotspot: dhcp host 10.63.193.23 removed: login timeout
feb/02 22:13:44 hotspot,info,debug T-0C:B3:19:E9:AE:30 (10.63.194.85): trying to log in by trial
feb/02 22:13:44 hotspot,debug T-0C:B3:19:E9:AE:30 (10.63.194.85): using profile <00>
feb/02 22:13:44 hotspot,debug T-0C:B3:19:E9:AE:30 (10.63.194.85): adding ip->user binding
feb/02 22:13:44 hotspot,debug T-0C:B3:19:E9:AE:30 (10.63.194.85): adding address-list rule <00>
feb/02 22:13:44 hotspot,debug T-0C:B3:19:E9:AE:30 (10.63.194.85): adding queue <256k/256k 0/0 0/0 0/0 8 64k/64k>
feb/02 22:13:44 hotspot,account,info,debug T-0C:B3:19:E9:AE:30 (10.63.194.85): logged in
feb/02 22:13:45 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by TCP :60247 -> 183.61.112.123:80
feb/02 22:13:45 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
feb/02 22:13:59 hotspot,debug Hotspot: new host detected F4:F1:E1:1E:3A:2C/10.63.194.35 by UDP :40733 -> 8.8.8.8:53
feb/02 22:13:59 hotspot,debug Hotspot: dhcp host F4:F1:E1:1E:3A:2C/10.63.194.35 added, ip 10.63.194.35
feb/02 22:14:05 hotspot,debug Hotspot: dynamic host 10.63.193.150 removed: login timeout
feb/02 22:14:06 hotspot,debug Hotspot: dynamic host 10.63.194.86 removed: login timeout
feb/02 22:14:09 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :39797 -> 10.63.192.1:53
feb/02 22:14:09 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.194.18 added, ip 10.63.193.150
feb/02 22:14:09 system,info,account user ersitizastes logged out from 10.63.192.255 via telnet
feb/02 22:14:12 dhcp,info dhcp1 assigned 10.63.194.33 to EC:88:92:40:CC:8B
feb/02 22:14:13 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.28 by UDP :46655 -> 10.63.192.1:53
feb/02 22:14:13 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.28 added, ip 10.63.194.89
feb/02 22:14:17 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by UDP :12532 -> 10.63.192.1:53
feb/02 22:14:17 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.194.33 added, ip 10.63.194.90
feb/02 22:14:17 hotspot,debug Hotspot: dynamic host 10.63.194.29 removed: login timeout
feb/02 22:14:25 hotspot,debug Hotspot: dhcp host 10.63.194.28 removed: login timeout
feb/02 22:14:25 hotspot,debug Hotspot: new host detected 74:BA:DB:04:26:13/10.63.194.28 by TCP :51674 -> 173.194.118.73:443
feb/02 22:14:25 hotspot,debug Hotspot: dhcp host 74:BA:DB:04:26:13/10.63.194.28 added, ip 10.63.194.28
feb/02 22:14:25 hotspot,debug Hotspot: dhcp host 10.63.193.3 removed: login timeout
feb/02 22:14:27 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.58 by UDP :49131 -> 10.63.192.1:53
feb/02 22:14:27 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.194.58 added, ip 10.63.194.29
feb/02 22:14:27 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by UDP :19262 -> 10.63.192.1:53
feb/02 22:14:27 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.59 added, ip 10.63.194.91
feb/02 22:14:36 hotspot,debug Hotspot: new host detected F4:F1:E1:F4:62:F6/10.63.193.3 by TCP :40513 -> 173.194.118.98:443
feb/02 22:14:36 hotspot,debug Hotspot: dhcp host F4:F1:E1:F4:62:F6/10.63.193.3 added, ip 10.63.193.3
feb/02 22:14:40 dhcp,info dhcp1 deassigned 10.63.194.58 from C4:9A:02:5D:A1:DC
feb/02 22:14:44 dhcp,info dhcp1 assigned 10.63.194.58 to C4:9A:02:5D:A1:DC
feb/02 22:14:47 hotspot,debug Hotspot: dhcp host 10.63.194.87 removed: login timeout
feb/02 22:14:47 hotspot,debug Hotspot: new host detected 84:11:9E:C3:1F:FE/10.63.194.87 by TCP :46202 -> 173.194.118.71:443
feb/02 22:14:47 hotspot,debug Hotspot: dhcp host 84:11:9E:C3:1F:FE/10.63.194.87 added, ip 10.63.194.87
feb/02 22:14:58 hotspot,debug Hotspot: dhcp host 10.63.194.88 removed: login timeout
feb/02 22:15:06 hotspot,debug Hotspot: new host detected 10:D3:8A:17:AB:26/10.63.194.88 by UDP :60284 -> 10.63.192.1:53
feb/02 22:15:06 hotspot,debug Hotspot: dhcp host 10:D3:8A:17:AB:26/10.63.194.88 added, ip 10.63.194.88
feb/02 22:15:42 system,info,account user ersitizastes logged in from 10.63.192.255 via telnet
feb/02 22:15:45 hotspot,debug Hotspot: dhcp host 10.63.193.23 removed: login timeout
feb/02 22:15:47 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by TCP :53291 -> 69.28.57.171:8888
feb/02 22:15:47 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
feb/02 22:15:47 dhcp,info dhcp1 deassigned 10.63.194.22 from AC:9E:17:0F:63:0D
feb/02 22:15:59 hotspot,debug Hotspot: dhcp host 10.63.194.35 removed: login timeout
feb/02 22:16:01 hotspot,debug Hotspot: new host detected F4:F1:E1:1E:3A:2C/10.63.194.35 by UDP :54913 -> 8.8.4.4:53
feb/02 22:16:01 hotspot,debug Hotspot: dhcp host F4:F1:E1:1E:3A:2C/10.63.194.35 added, ip 10.63.194.35
feb/02 22:16:09 hotspot,debug Hotspot: dynamic host 10.63.193.150 removed: login timeout
feb/02 22:16:11 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.18 by UDP :1741 -> 10.63.192.1:53
feb/02 22:16:11 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.194.18 added, ip 10.63.193.150
feb/02 22:16:13 hotspot,debug Hotspot: dynamic host 10.63.194.89 removed: login timeout
feb/02 22:16:17 hotspot,debug Hotspot: dynamic host 10.63.194.90 removed: login timeout
feb/02 22:16:17 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.194.33 by TCP :45830 -> 108.168.176.245:80
feb/02 22:16:17 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.194.33 added, ip 10.63.194.92
feb/02 22:16:19 dhcp,info dhcp1 deassigned 10.63.194.84 from 00:F4:6F:F6:0A:DF
feb/02 22:16:19 hotspot,debug Hotspot: dhcp host 10.63.194.84 changed type to dynamic (remove after 5s)
feb/02 22:16:19 dhcp,info dhcp1 assigned 10.63.194.84 to 00:F4:6F:F6:0A:DF
feb/02 22:16:19 hotspot,debug Hotspot: dynamic host 10.63.194.84 changed type to dhcp (got back lease)
feb/02 22:16:24 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.28 by UDP :33560 -> 10.63.192.1:53
feb/02 22:16:24 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.28 added, ip 10.63.194.37
feb/02 22:16:25 hotspot,debug Hotspot: dhcp host 10.63.194.28 removed: login timeout
feb/02 22:16:27 hotspot,debug Hotspot: new host detected 74:BA:DB:04:26:13/10.63.194.28 by TCP :52356 -> 216.58.222.14:443
feb/02 22:16:27 hotspot,debug Hotspot: dhcp host 74:BA:DB:04:26:13/10.63.194.28 added, ip 10.63.194.28
feb/02 22:16:27 hotspot,debug Hotspot: dynamic host 10.63.194.29 removed: login timeout
feb/02 22:16:27 hotspot,debug Hotspot: dynamic host 10.63.194.91 removed: login timeout
feb/02 22:16:36 hotspot,debug Hotspot: dhcp host 10.63.193.3 removed: login timeout
feb/02 22:16:41 hotspot,debug Hotspot: new host detected 4C:5E:0C:CA:05:46/10.63.193.59 by TCP :48482 -> 158.85.58.110:80
feb/02 22:16:41 hotspot,debug Hotspot: dynamic host 4C:5E:0C:CA:05:46/10.63.193.59 added, ip 10.63.194.29
feb/02 22:16:47 hotspot,debug Hotspot: dhcp host 10.63.194.87 removed: login timeout
feb/02 22:16:56 system,info,account user ersitizastes logged out from 10.63.192.255 via telnet
feb/02 22:16:59 dhcp,info dhcp1 deassigned 10.63.194.52 from C4:9A:02:61:DA:A3
feb/02 22:16:59 dhcp,info dhcp1 assigned 10.63.194.52 to C4:9A:02:61:DA:A3
feb/02 22:17:00 hotspot,debug Hotspot: new host detected C4:9A:02:61:DA:A3/10.63.194.52 by UDP :24757 -> 10.63.192.1:53
feb/02 22:17:00 hotspot,debug Hotspot: dhcp host C4:9A:02:61:DA:A3/10.63.194.52 added, ip 10.63.194.52
feb/02 22:17:00 system,info,account user ersitizastes logged in from 10.63.192.255 via telnet
feb/02 22:17:00 script,warning Google Up
feb/02 22:17:06 hotspot,debug Hotspot: dhcp host 10.63.194.88 removed: login timeout
feb/02 22:17:16 dhcp,info dhcp1 deassigned 10.63.194.84 from 00:F4:6F:F6:0A:DF
feb/02 22:17:16 hotspot,debug Hotspot: dhcp host 10.63.194.84 changed type to dynamic (remove after 5s)
feb/02 22:17:16 dhcp,info dhcp1 assigned 10.63.194.84 to 00:F4:6F:F6:0A:DF
feb/02 22:17:16 hotspot,debug Hotspot: dynamic host 10.63.194.84 changed type to dhcp (got back lease)
feb/02 22:17:16 dhcp,info dhcp1 deassigned 10.63.194.84 from 00:F4:6F:F6:0A:DF
feb/02 22:17:16 hotspot,debug Hotspot: dhcp host 10.63.194.84 changed type to dynamic (remove after 5s)
feb/02 22:17:16 dhcp,info dhcp1 assigned 10.63.194.84 to 00:F4:6F:F6:0A:DF
feb/02 22:17:16 hotspot,debug Hotspot: dynamic host 10.63.194.84 changed type to dhcp (got back lease)



Can I use station wds instead station pseudobridge, or can I use station-bridge?

Re: v6.35rc is released, new wireless package!

Posted: Wed Feb 03, 2016 9:54 am
by uldis
PeterDoBrasil, as I wrote in the last post try to use station-bridge mode instead of station-pseudobridge if your AP is RouterOS based and that should not cause problems like you have with the pseudobridge option.

Re: v6.35rc is released, new wireless package!

Posted: Wed Feb 03, 2016 3:24 pm
by strods
Version 6.35rc3 will be released today.

Changes since previous version:
*) dude - <changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=104395 >
*) interface - show stats properly in bits not bytes;
*) traffic-monitor - show stats properly in bits not bytes;
*) smips - properly detect smips boards for winbox & webfig;
*) ccr1072 - fix traffic halting when sfp+ 1-4 or 5-8 where all disabled.

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Re: v6.35rc is released, new wireless package!

Posted: Wed Feb 03, 2016 3:33 pm
by Cha0s
How can I upgrade the hAP Lite?

There isn't enough disk space available.
smips cannot upgrade.png

Re: v6.35rc is released, new wireless package!

Posted: Wed Feb 03, 2016 3:48 pm
by PeterDoBrasil
PeterDoBrasil, as I wrote in the last post try to use station-bridge mode instead of station-pseudobridge if your AP is RouterOS based and that should not cause problems like you have with the pseudobridge option.
# Resolved #
station-bridge causes the same problem, I've testet station-wds, now Hotspot runs Propertly, wifi Link is O.K, all my devices are Routerboard, Iám only use BaseBox 2,4 ghz!

[ersitizastes@5g.net 0] > /ip hotspot host print
Flags: S - static, H - DHCP, D - dynamic, A - authorized, P - bypassed
# MAC-ADDRESS ADDRESS TO-ADDRESS SERVER IDLE-TIMEOUT
0 SP ;;; 5g.net 1
4C:5E:0C:C4:41:BE 10.63.192.2 10.63.192.2 Hotspot
1 SP ;;; 5g.net 2
4C:5E:0C:CA:05:46 10.63.192.3 10.63.192.3 Hotspot
2 SP ;;; HP Ether
08:2E:5F:75:6C:56 10.63.192.255 10.63.192.255 Hotspot
3 SP ;;; 5g.net 3
4C:5E:0C:C4:53:F8 10.63.192.4 10.63.192.4 Hotspot
4 SP ;;; HP Wifi
5C:C9:D3:0D:D1:AD 10.63.192.254 10.63.192.254 Hotspot
5 SP ;;; 5g.net 4
4C:5E:0C:C4:4D:F9 10.63.192.5 10.63.192.5 Hotspot
6 H 14:32:D1:10:FE:CE 10.63.193.36 10.63.193.36 Hotspot
7 H F4:F1:E1:1E:3A:2C 10.63.194.35 10.63.194.35 Hotspot
8 H 9C:E6:E7:07:04:65 10.63.193.45 10.63.193.45 Hotspot
9 H 38:2D:D1:A5:04:39 10.63.193.23 10.63.193.23 Hotspot
10 H 48:59:29:E3:59:62 10.63.194.120 10.63.194.120 Hotspot
11 H 34:BE:00:95:74:65 10.63.193.47 10.63.193.47 Hotspot
12 H 50:55:27:A0:E9:AF 10.63.193.133 10.63.193.133 Hotspot
13 H 60:D7:AE:C8:92:CC 10.63.193.51 10.63.193.51 Hotspot


/log print

# feb/ 3/2016 10:43: 7 by RouterOS 6.33
# software id = KPNX-1FGN
#


08:33:31 hotspot,debug Hotspot: dynamic host 10.63.194.40 removed: keepalive timeout
08:34:53 dhcp,info dhcp1 deassigned 10.63.193.51 from 60:D7:AE:C8:92:CC
08:34:53 hotspot,debug Hotspot: dhcp host 10.63.193.51 changed type to dynamic (remove after 5s)
08:34:55 hotspot,debug Hotspot: dynamic host 10.63.193.51 removed: keepalive timeout
08:35:01 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by UDP :4686 -> 10.63.192.1:53
08:35:01 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
08:35:13 dhcp,info dhcp1 assigned 10.63.193.8 to 9C:D9:17:8A:C4:1A
08:35:14 hotspot,debug Hotspot: new host detected 9C:D9:17:8A:C4:1A/10.63.193.8 by UDP :55831 -> 10.63.192.1:53
08:35:14 hotspot,debug Hotspot: dhcp host 9C:D9:17:8A:C4:1A/10.63.193.8 added, ip 10.63.193.8
08:35:43 dhcp,info dhcp1 assigned 10.63.194.136 to B4:30:52:B0:9E:72
08:35:48 hotspot,debug Hotspot: new host detected B4:30:52:B0:9E:72/10.63.194.136 by TCP :38741 -> 192.12.31.96:443
08:35:48 hotspot,debug Hotspot: dhcp host B4:30:52:B0:9E:72/10.63.194.136 added, ip 10.63.194.136
08:36:31 dhcp,info dhcp1 assigned 10.63.192.254 to 5C:C9:D3:0D:D1:AD
08:36:31 dhcp,error dhcp1: failed to add arp entry for IP 10.63.192.254: already have such arp (6)
08:36:34 hotspot,debug Hotspot: bypassed host 10.63.192.254 moved to bridge port <ether9> from <wlan>
08:36:58 dhcp,info dhcp1 assigned 10.63.193.51 to 60:D7:AE:C8:92:CC
08:37:17 hotspot,debug Hotspot: new host detected 60:D7:AE:C8:92:CC/10.63.193.51 by UDP :35646 -> 10.63.192.1:53
08:37:17 hotspot,debug Hotspot: dhcp host 60:D7:AE:C8:92:CC/10.63.193.51 added, ip 10.63.193.51
08:37:58 hotspot,debug Hotspot: new host detected F4:F1:E1:1E:3A:2C/10.63.194.35 by UDP :57227 -> 10.63.192.1:53
08:37:58 hotspot,debug Hotspot: dhcp host F4:F1:E1:1E:3A:2C/10.63.194.35 added, ip 10.63.194.35
08:38:06 dhcp,info dhcp1 deassigned 10.63.193.133 from 50:55:27:A0:E9:AF
08:40:10 hotspot,debug Hotspot: dhcp host 10.63.193.51 removed: keepalive timeout
08:40:47 hotspot,debug Hotspot: dhcp host 10.63.193.8 removed: keepalive timeout
08:42:20 hotspot,debug Hotspot: bypassed host 10.63.192.255 moved to bridge port <ether9> from <ether2>
08:42:26 hotspot,debug Hotspot: bypassed host 10.63.192.3 moved to bridge port <ether9> from <<none>>
08:42:32 hotspot,debug Hotspot: new host detected 8C:3A:E3:07:CA:30/10.63.194.155 by UDP :48503 -> 10.63.192.1:53
08:42:32 hotspot,debug Hotspot: dhcp host 8C:3A:E3:07:CA:30/10.63.194.155 added, ip 10.63.194.155
08:43:00 script,warning 5g.net 2 Up
08:43:44 hotspot,debug Hotspot: dhcp host 10.63.193.6 removed: keepalive timeout
08:44:27 hotspot,debug Hotspot: dhcp host 10.63.194.143 removed: keepalive timeout
08:44:36 hotspot,debug Hotspot: dhcp host 10.63.194.155 removed: keepalive timeout
08:45:54 hotspot,debug Hotspot: new host detected 58:A2:B5:DA:FD:96/10.63.194.39 by UDP :44674 -> 10.63.192.1:53
08:45:54 hotspot,debug Hotspot: dhcp host 58:A2:B5:DA:FD:96/10.63.194.39 added, ip 10.63.194.39
08:46:01 dhcp,info dhcp1 deassigned 10.63.194.39 from 58:A2:B5:DA:FD:96
08:46:01 hotspot,debug Hotspot: dhcp host 10.63.194.39 changed type to dynamic (remove after 5s)
08:46:01 dhcp,info dhcp1 assigned 10.63.194.39 to 58:A2:B5:DA:FD:96
08:46:01 hotspot,debug Hotspot: dynamic host 10.63.194.39 changed type to dhcp (got back lease)
08:46:31 dhcp,info dhcp1 deassigned 10.63.192.254 from 5C:C9:D3:0D:D1:AD
08:47:31 dhcp,info dhcp1 assigned 10.63.194.33 to EC:88:92:40:CC:8B
08:47:35 hotspot,debug Hotspot: new host detected EC:88:92:40:CC:8B/10.63.194.33 by UDP :24236 -> 10.63.192.1:53
08:47:35 hotspot,debug Hotspot: dhcp host EC:88:92:40:CC:8B/10.63.194.33 added, ip 10.63.194.33
08:47:42 hotspot,info,debug T-EC:88:92:40:CC:8B (10.63.194.33): trying to log in by trial
08:47:42 hotspot,debug T-EC:88:92:40:CC:8B (10.63.194.33): using profile <00>
08:47:42 hotspot,debug T-EC:88:92:40:CC:8B (10.63.194.33): adding ip->user binding
08:47:42 hotspot,debug T-EC:88:92:40:CC:8B (10.63.194.33): adding address-list rule <00>
08:47:42 hotspot,debug T-EC:88:92:40:CC:8B (10.63.194.33): adding queue <180k/180k 0/0 0/0 0/0 8 64k/64k>
08:47:42 hotspot,account,info,debug T-EC:88:92:40:CC:8B (10.63.194.33): logged in
08:48:40 dhcp,info dhcp1 assigned 10.63.192.254 to 5C:C9:D3:0D:D1:AD
08:48:40 dhcp,error dhcp1: failed to add arp entry for IP 10.63.192.254: already have such arp (6)
08:49:24 dhcp,info dhcp1 deassigned 10.63.194.150 from C4:9A:02:39:E6:12
08:50:24 dhcp,info dhcp1 deassigned 10.63.194.136 from B4:30:52:B0:9E:72
08:50:24 hotspot,debug Hotspot: dhcp host 10.63.194.136 changed type to dynamic (remove after 5s)
08:50:24 dhcp,info dhcp1 assigned 10.63.194.136 to B4:30:52:B0:9E:72
08:50:24 hotspot,debug Hotspot: dynamic host 10.63.194.136 changed type to dhcp (got back lease)
08:50:30 dhcp,info dhcp1 assigned 10.63.193.59 to F8:A9:D0:5A:F4:85
08:50:47 hotspot,debug Hotspot: new host detected 80:65:6D:56:6E:A5/10.63.194.143 by UDP :44139 -> 10.63.192.1:53
08:50:47 hotspot,debug Hotspot: dhcp host 80:65:6D:56:6E:A5/10.63.194.143 added, ip 10.63.194.143
08:51:18 hotspot,debug Hotspot: new host detected F8:A9:D0:5A:F4:85/10.63.193.59 by UDP :42949 -> 10.63.192.1:53
08:51:18 hotspot,debug Hotspot: dhcp host F8:A9:D0:5A:F4:85/10.63.193.59 added, ip 10.63.193.59
08:52:31 dhcp,info dhcp1 deassigned 10.63.194.151 from C4:42:02:39:9E:90
08:53:19 hotspot,debug Hotspot: new host detected 34:FC:EF:D1:29:25/10.63.193.6 by UDP :55296 -> 10.63.192.1:53
08:53:19 hotspot,debug Hotspot: dhcp host 34:FC:EF:D1:29:25/10.63.193.6 added, ip 10.63.193.6
08:53:24 dhcp,info dhcp1 deassigned 10.63.193.6 from 34:FC:EF:D1:29:25
08:53:24 hotspot,debug Hotspot: dhcp host 10.63.193.6 changed type to dynamic (remove after 5s)
08:53:28 dhcp,info dhcp1 assigned 10.63.193.6 to 34:FC:EF:D1:29:25
08:53:28 hotspot,debug Hotspot: dynamic host 10.63.193.6 changed type to dhcp (got back lease)
08:54:28 hotspot,debug Hotspot: dhcp host 10.63.194.143 removed: keepalive timeout
08:54:45 hotspot,debug Hotspot: dhcp host 10.63.194.39 removed: keepalive timeout
08:55:54 dhcp,info dhcp1 assigned 10.63.194.120 to 48:59:29:E3:59:62
08:56:01 dhcp,info dhcp1 deassigned 10.63.194.144 from 34:FC:EF:CF:50:24
08:56:30 dhcp,info dhcp1 assigned 10.63.193.11 to D0:59:E4:36:95:99
08:56:31 hotspot,debug Hotspot: new host detected D0:59:E4:36:95:99/10.63.193.11 by UDP :20164 -> 10.63.192.1:53
08:56:31 hotspot,debug Hotspot: dhcp host D0:59:E4:36:95:99/10.63.193.11 added, ip 10.63.193.11
08:57:17 hotspot,debug Hotspot: new host detected 48:59:29:E3:59:62/10.63.194.120 by UDP :57118 -> 10.63.192.1:53
08:57:17 hotspot,debug Hotspot: dhcp host 48:59:29:E3:59:62/10.63.194.120 added, ip 10.63.194.120
08:57:56 hotspot,debug Hotspot: new host detected 8C:3A:E3:07:CA:30/10.63.194.155 by UDP :36938 -> 10.63.192.1:53
08:57:56 hotspot,debug Hotspot: dhcp host 8C:3A:E3:07:CA:30/10.63.194.155 added, ip 10.63.194.155
08:57:58 dhcp,info dhcp1 deassigned 10.63.193.13 from 18:22:7E:2A:5A:5E
08:57:58 dhcp,info dhcp1 assigned 10.63.193.13 to 18:22:7E:2A:5A:5E
08:57:59 hotspot,debug Hotspot: new host detected 18:22:7E:2A:5A:5E/10.63.193.13 by TCP :49890 -> 192.12.31.106:5223
08:57:59 hotspot,debug Hotspot: dhcp host 18:22:7E:2A:5A:5E/10.63.193.13 added, ip 10.63.193.13
08:58:38 hotspot,debug Hotspot: dhcp host 10.63.193.11 removed: keepalive timeout
08:58:40 dhcp,info dhcp1 deassigned 10.63.192.254 from 5C:C9:D3:0D:D1:AD
08:59:35 dhcp,info dhcp1 deassigned 10.63.194.153 from 64:89:9A:2B:2D:55
09:00:24 hotspot,debug Hotspot: dhcp host 10.63.194.155 removed: keepalive timeout
09:00:40 dhcp,info dhcp1 deassigned 10.63.194.18 from 34:FC:EF:FF:AD:06
09:01:27 dhcp,info dhcp1 deassigned 10.63.194.152 from 34:FC:EF:C3:61:36
09:01:40 dhcp,info dhcp1 deassigned 10.63.194.26 from C4:9A:02:9E:19:A1
09:02:25 hotspot,debug Hotspot: dhcp host 10.63.194.136 removed: keepalive timeout
09:02:39 dhcp,info dhcp1 deassigned 10.63.193.51 from 60:D7:AE:C8:92:CC
09:03:04 hotspot,debug Hotspot: dhcp host 10.63.193.13 removed: keepalive timeout
09:03:19 wireless,info wlan: data from unknown device 60:D7:AE:C8:92:CC, sent deauth
09:03:19 wireless,info wlan: data from unknown device 60:D7:AE:C8:92:CC, sent deauth
09:04:50 dhcp,info dhcp1 deassigned 10.63.194.155 from 8C:3A:E3:07:CA:30
09:05:09 hotspot,debug Hotspot: dhcp host 10.63.194.120 removed: keepalive timeout
09:05:55 dhcp,info dhcp1 deassigned 10.63.194.136 from B4:30:52:B0:9E:72
09:06:02 dhcp,info dhcp1 assigned 10.63.194.136 to B4:30:52:B0:9E:72
09:06:06 hotspot,debug Hotspot: new host detected B4:30:52:B0:9E:72/10.63.194.136 by UDP :7516 -> 10.63.192.1:53
09:06:06 hotspot,debug Hotspot: dhcp host B4:30:52:B0:9E:72/10.63.194.136 added, ip 10.63.194.136
09:06:10 dhcp,info dhcp1 assigned 10.63.193.14 to 20:62:74:E9:92:B0
09:06:10 hotspot,debug Hotspot: new host detected 20:62:74:E9:92:B0/10.63.193.14 by UDP :58460 -> 10.63.192.1:53
09:06:10 hotspot,debug Hotspot: dhcp host 20:62:74:E9:92:B0/10.63.193.14 added, ip 10.63.193.14
09:06:14 dhcp,info dhcp1 deassigned 10.63.193.14 from 20:62:74:E9:92:B0
09:06:14 hotspot,debug Hotspot: dhcp host 10.63.193.14 changed type to dynamic (remove after 5s)
09:06:14 dhcp,info dhcp1 assigned 10.63.193.14 to 20:62:74:E9:92:B0
09:06:14 hotspot,debug Hotspot: dynamic host 10.63.193.14 changed type to dhcp (got back lease)
09:06:24 hotspot,info,debug T-20:62:74:E9:92:B0 (10.63.193.14): trying to log in by trial
09:06:24 hotspot,debug T-20:62:74:E9:92:B0 (10.63.193.14): using profile <00>
09:06:24 hotspot,debug T-20:62:74:E9:92:B0 (10.63.193.14): adding ip->user binding
09:06:24 hotspot,debug T-20:62:74:E9:92:B0 (10.63.193.14): adding address-list rule <00>
09:06:24 hotspot,debug T-20:62:74:E9:92:B0 (10.63.193.14): adding queue <180k/180k 0/0 0/0 0/0 8 64k/64k>
09:06:24 hotspot,account,info,debug T-20:62:74:E9:92:B0 (10.63.193.14): logged in
09:06:53 dhcp,info dhcp1 assigned 10.63.194.138 to 44:91:DB:51:5E:EB
09:08:58 hotspot,debug Hotspot: dhcp host 10.63.194.35 removed: keepalive timeout
09:10:55 hotspot,info,debug T-20:62:74:E9:92:B0 (10.63.193.14): logged out: keepalive timeout
09:10:55 hotspot,debug T-20:62:74:E9:92:B0 (10.63.193.14): removing queue
09:10:55 hotspot,debug T-20:62:74:E9:92:B0 (10.63.193.14): removing address-list
09:10:55 hotspot,debug T-20:62:74:E9:92:B0 (10.63.193.14): removing ip->user binding
09:10:55 hotspot,debug Hotspot: dhcp host 10.63.193.14 removed: keepalive timeout
09:11:56 dhcp,info dhcp1 deassigned 10.63.194.127 from 14:A3:64:25:0E:91
09:12:34 dhcp,info dhcp1 assigned 10.63.194.135 to 3C:18:9F:33:05:31
09:12:37 hotspot,debug Hotspot: new host detected 3C:18:9F:33:05:31/10.63.194.135 by UDP :60308 -> 10.63.192.1:53
09:12:37 hotspot,debug Hotspot: dhcp host 3C:18:9F:33:05:31/10.63.194.135 added, ip 10.63.194.135
09:13:09 dhcp,info dhcp1 deassigned 10.63.193.4 from AC:D0:74:14:00:59
09:13:39 interface,info ether2 link up (speed 100M, full duplex)
09:13:39 hotspot,debug Hotspot: new host detected F4:F1:E1:1E:3A:2C/10.63.194.35 by UDP :25757 -> 10.63.192.1:53
09:13:39 hotspot,debug Hotspot: dhcp host F4:F1:E1:1E:3A:2C/10.63.194.35 added, ip 10.63.194.35
09:13:42 wireless,info 94:51:03:D3:B6:B8@wlan: connected
09:13:46 dhcp,info dhcp1 assigned 10.63.192.253 to 94:51:03:D3:B6:B8
09:13:47 hotspot,debug Hotspot: new host detected 94:51:03:D3:B6:B8/10.63.192.253 by TCP :40512 -> 108.177.12.188:5228
09:13:47 hotspot,debug Hotspot: dhcp host 94:51:03:D3:B6:B8/10.63.192.253 added, ip 10.63.192.253
09:13:52 interface,info ether2 link down
09:13:52 wireless,info 5C:C9:D3:0D:D1:AD@wlan: connected
09:13:52 dhcp,info dhcp1 assigned 10.63.192.254 to 5C:C9:D3:0D:D1:AD
09:13:52 dhcp,error dhcp1: failed to add arp entry for IP 10.63.192.254: already have such arp (6)
09:13:52 hotspot,debug Hotspot: bypassed host 10.63.192.254 moved to bridge port <wlan> from <ether9>
09:13:54 interface,info ether2 link up (speed 1G, full duplex)
09:13:56 hotspot,debug Hotspot: bypassed host 10.63.192.255 moved to bridge port <ether2> from <ether9>
09:13:58 dhcp,info dhcp1 deassigned 10.63.194.120 from 48:59:29:E3:59:62
09:13:58 dhcp,info dhcp1 assigned 10.63.194.120 to 48:59:29:E3:59:62
09:14:01 hotspot,debug Hotspot: new host detected 48:59:29:E3:59:62/10.63.194.120 by UDP :18584 -> 10.63.192.1:53
09:14:01 hotspot,debug Hotspot: dhcp host 48:59:29:E3:59:62/10.63.194.120 added, ip 10.63.194.120
09:14:11 wireless,info 5C:C9:D3:0D:D1:AD@wlan: disconnected, received disassoc: sending station leaving (8)
09:14:39 dhcp,info dhcp1 assigned 10.63.192.255 to 08:2E:5F:75:6C:56
09:14:39 dhcp,error dhcp1: failed to add arp entry for IP 10.63.192.255: already have such arp (6)
09:14:49 hotspot,debug Hotspot: dhcp host 10.63.193.6 removed: keepalive timeout
09:15:44 hotspot,debug Hotspot: new host detected 6C:2F:2C:1C:E4:DC/10.63.193.44 by UDP :44545 -> 10.63.192.1:53
09:15:44 hotspot,debug Hotspot: dhcp host 6C:2F:2C:1C:E4:DC/10.63.193.44 added, ip 10.63.193.44
09:16:41 dhcp,info dhcp1 deassigned 10.63.194.140 from 9C:65:B0:FA:3F:26
09:17:13 hotspot,debug Hotspot: dhcp host 10.63.194.136 removed: keepalive timeout
09:17:25 hotspot,info,debug T-EC:88:92:40:CC:8B (10.63.194.33): logged out: keepalive timeout
09:17:25 hotspot,debug T-EC:88:92:40:CC:8B (10.63.194.33): removing queue
09:17:25 hotspot,debug T-EC:88:92:40:CC:8B (10.63.194.33): removing address-list
09:17:25 hotspot,debug T-EC:88:92:40:CC:8B (10.63.194.33): removing ip->user binding
09:17:25 hotspot,debug Hotspot: dhcp host 10.63.194.33 removed: keepalive timeout
09:18:06 hotspot,debug Hotspot: dhcp host 10.63.193.59 removed: keepalive timeout
09:18:39 hotspot,debug Hotspot: new host detected F8:A9:D0:5A:F4:85/10.63.193.59 by UDP :47293 -> 10.63.192.1:53
09:18:39 hotspot,debug Hotspot: dhcp host F8:A9:D0:5A:F4:85/10.63.193.59 added, ip 10.63.193.59
09:18:40 dhcp,info dhcp1 deassigned 10.63.193.59 from F8:A9:D0:5A:F4:85
09:18:40 hotspot,debug Hotspot: dhcp host 10.63.193.59 changed type to dynamic (remove after 5s)
09:18:41 hotspot,debug Hotspot: dhcp host 10.63.194.135 removed: keepalive timeout
09:18:44 hotspot,debug Hotspot: dhcp host 10.63.193.44 removed: keepalive timeout
09:18:45 hotspot,debug Hotspot: dynamic host 10.63.193.59 removed: lost dhcp lease
09:18:46 hotspot,debug Hotspot: new host detected F8:A9:D0:5A:F4:85/10.63.193.59 by UDP :63009 -> 10.63.192.1:53
09:18:46 hotspot,debug Hotspot: dynamic host F8:A9:D0:5A:F4:85/10.63.193.59 added, ip 10.63.193.17
09:19:43 dhcp,info dhcp1 assigned 10.63.193.59 to F8:A9:D0:5A:F4:85
09:19:43 hotspot,debug Hotspot: dynamic host 10.63.193.17 removed: dhcp entry overrides dynamic one
09:19:57 hotspot,debug Hotspot: new host detected F8:A9:D0:5A:F4:85/10.63.193.59 by UDP :60884 -> 10.63.192.1:53
09:19:57 hotspot,debug Hotspot: dhcp host F8:A9:D0:5A:F4:85/10.63.193.59 added, ip 10.63.193.59
09:21:48 dhcp,info dhcp1 assigned 10.63.193.22 to 30:19:66:27:D9:9F
09:21:49 hotspot,debug Hotspot: new host detected 30:19:66:27:D9:9F/10.63.193.22 by UDP :35114 -> 10.63.192.1:53
09:21:49 hotspot,debug Hotspot: dhcp host 30:19:66:27:D9:9F/10.63.193.22 added, ip 10.63.193.22
09:22:13 hotspot,debug Hotspot: dhcp host 10.63.193.59 removed: keepalive timeout
09:23:51 hotspot,debug Hotspot: dhcp host 10.63.193.22 removed: keepalive timeout
09:23:52 dhcp,info dhcp1 deassigned 10.63.192.254 from 5C:C9:D3:0D:D1:AD
09:24:21 dhcp,info dhcp1 assigned 10.63.194.146 to C4:42:02:21:02:DC
09:24:48 hotspot,debug Hotspot: new host detected C4:42:02:21:02:DC/10.63.194.146 by TCP :32877 -> 52.16.205.72:5223
09:24:48 hotspot,debug Hotspot: dhcp host C4:42:02:21:02:DC/10.63.194.146 added, ip 10.63.194.146
09:25:41 hotspot,debug Hotspot: dhcp host 10.63.194.35 removed: keepalive timeout
09:26:03 dhcp,info dhcp1 assigned 10.63.193.24 to E4:90:7E:50:12:B3
09:26:04 hotspot,debug Hotspot: new host detected E4:90:7E:50:12:B3/10.63.193.24 by UDP :43829 -> 10.63.192.1:53
09:26:04 hotspot,debug Hotspot: dhcp host E4:90:7E:50:12:B3/10.63.193.24 added, ip 10.63.193.24
09:26:52 hotspot,debug Hotspot: dhcp host 10.63.193.23 removed: keepalive timeout
09:26:55 hotspot,debug Hotspot: dhcp host 10.63.194.146 removed: keepalive timeout
09:27:20 dhcp,info dhcp1 deassigned 10.63.193.14 from 20:62:74:E9:92:B0
09:27:20 dhcp,info dhcp1 assigned 10.63.193.14 to 20:62:74:E9:92:B0
09:27:20 hotspot,debug Hotspot: new host detected 20:62:74:E9:92:B0/10.63.193.14 by UDP :63292 -> 10.63.192.1:53
09:27:20 hotspot,info,debug T-20:62:74:E9:92:B0 (10.63.193.14): trying to log in by mac-cookie
09:27:20 hotspot,debug T-20:62:74:E9:92:B0 (10.63.193.14): using profile <00>
09:27:20 hotspot,debug T-20:62:74:E9:92:B0 (10.63.193.14): adding ip->user binding
09:27:20 hotspot,debug Hotspot: dhcp host 20:62:74:E9:92:B0/10.63.193.14 added, ip 10.63.193.14
09:27:20 hotspot,debug T-20:62:74:E9:92:B0 (10.63.193.14): adding address-list rule <00>
09:27:20 hotspot,debug T-20:62:74:E9:92:B0 (10.63.193.14): adding queue <180k/180k 0/0 0/0 0/0 8 64k/64k>
09:27:20 hotspot,account,info,debug T-20:62:74:E9:92:B0 (10.63.193.14): logged in
09:27:55 hotspot,debug Hotspot: new host detected F4:F1:E1:1E:3A:2C/10.63.194.35 by UDP :54374 -> 10.63.192.1:53
09:27:55 hotspot,debug Hotspot: dhcp host F4:F1:E1:1E:3A:2C/10.63.194.35 added, ip 10.63.194.35
09:27:57 dhcp,info dhcp1 deassigned 10.63.193.24 from E4:90:7E:50:12:B3
09:27:57 hotspot,debug Hotspot: dhcp host 10.63.193.24 changed type to dynamic (remove after 5s)
09:27:59 dhcp,info dhcp1 assigned 10.63.193.24 to E4:90:7E:50:12:B3
09:27:59 hotspot,debug Hotspot: dynamic host 10.63.193.24 changed type to dhcp (got back lease)
09:28:22 dhcp,info dhcp1 deassigned 10.63.194.39 from 58:A2:B5:DA:FD:96
09:28:22 dhcp,info dhcp1 assigned 10.63.194.39 to 58:A2:B5:DA:FD:96
09:29:04 dhcp,info dhcp1 deassigned 10.63.193.24 from E4:90:7E:50:12:B3
09:29:04 hotspot,debug Hotspot: dhcp host 10.63.193.24 changed type to dynamic (remove after 5s)
09:29:05 dhcp,info dhcp1 assigned 10.63.193.24 to E4:90:7E:50:12:B3
09:29:05 hotspot,debug Hotspot: dynamic host 10.63.193.24 changed type to dhcp (got back lease)
09:29:25 dhcp,info dhcp1 deassigned 10.63.193.14 from 20:62:74:E9:92:B0
09:29:25 hotspot,debug Hotspot: dhcp host 10.63.193.14 changed type to dynamic (remove after 5s)
09:29:30 hotspot,info,debug T-20:62:74:E9:92:B0 (10.63.193.14): logged out: lost dhcp lease
09:29:30 hotspot,debug T-20:62:74:E9:92:B0 (10.63.193.14): removing queue
09:29:30 hotspot,debug T-20:62:74:E9:92:B0 (10.63.193.14): removing address-list
09:29:30 hotspot,debug T-20:62:74:E9:92:B0 (10.63.193.14): removing ip->user binding
09:29:30 hotspot,debug Hotspot: dynamic host 10.63.193.14 removed: lost dhcp lease
09:30:03 script,error 5g.net 2 Down
09:30:41 wireless,info 94:51:03:D3:B6:B8@wlan: disconnected, received disassoc: sending station leaving (8)
09:30:45 dhcp,info dhcp1 deassigned 10.63.194.120 from 48:59:29:E3:59:62
09:30:45 hotspot,debug Hotspot: dhcp host 10.63.194.120 changed type to dynamic (remove after 5s)
09:30:50 hotspot,debug Hotspot: dynamic host 10.63.194.120 removed: lost dhcp lease
09:31:00 script,warning 5g.net 2 Up
09:31:15 hotspot,debug Hotspot: new host detected 18:22:7E:2A:5A:5E/10.63.193.13 by UDP :37296 -> 10.63.192.1:53
09:31:15 hotspot,debug Hotspot: dhcp host 18:22:7E:2A:5A:5E/10.63.193.13 added, ip 10.63.193.13
09:31:21 hotspot,debug Hotspot: dynamic host 10.63.193.30 removed: keepalive timeout
09:31:28 hotspot,debug Hotspot: dhcp host 10.63.193.24 removed: keepalive timeout
09:31:47 hotspot,debug Hotspot: dhcp host 10.63.192.253 removed: keepalive timeout
09:31:50 system,info,account user ersitizastes logged in from 10.63.192.255 via winbox
09:31:52 hotspot,info,debug T-18:22:7E:2A:5A:5E (10.63.193.13): trying to log in by trial
09:31:52 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): using profile <00>
09:31:52 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): adding ip->user binding
09:31:52 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): adding address-list rule <00>
09:31:52 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): adding queue <180k/180k 0/0 0/0 0/0 8 64k/64k>
09:31:52 hotspot,account,info,debug T-18:22:7E:2A:5A:5E (10.63.193.13): logged in
09:32:25 hotspot,debug Hotspot: dhcp host 10.63.194.35 removed: keepalive timeout
09:34:59 system,info arp entry changed by ersitizastes
09:34:59 system,info arp entry changed by ersitizastes
09:35:10 system,info,account user ersitizastes logged out from 10.63.192.255 via winbox
09:35:12 interface,info ether2 link down
09:35:13 dhcp,info dhcp1 deassigned 10.63.193.8 from 9C:D9:17:8A:C4:1A
09:35:17 interface,info ether2 link up (speed 1G, full duplex)
09:35:55 system,info,account user ersitizastes logged in from 08:2E:5F:75:6C:56 via winbox
09:36:26 system,info arp entry removed by ersitizastes
09:36:26 system,info arp entry removed by ersitizastes
09:36:32 interface,info ether2 link down
09:36:33 system,info,account user ersitizastes logged out from 08:2E:5F:75:6C:56 via winbox
09:36:37 interface,info ether2 link up (speed 1G, full duplex)
09:36:51 interface,info ether2 link down
09:36:54 interface,info ether2 link up (speed 1G, full duplex)
09:37:28 system,info,account user ersitizastes logged in from 08:2E:5F:75:6C:56 via winbox
09:38:30 dhcp,info dhcp1 deassigned 10.63.192.255 from 08:2E:5F:75:6C:56
09:38:30 system,info dhcp lease changed by ersitizastes
09:38:32 system,info dhcp lease changed by ersitizastes
09:38:37 interface,info ether2 link down
09:38:38 system,info,account user ersitizastes logged out from 08:2E:5F:75:6C:56 via winbox
09:38:42 interface,info ether2 link up (speed 1G, full duplex)
09:38:47 dhcp,info dhcp1 deassigned 10.63.192.253 from 94:51:03:D3:B6:B8
09:38:49 dhcp,info dhcp1 assigned 10.63.192.255 to 08:2E:5F:75:6C:56
09:39:04 system,info,account user ersitizastes logged in from 10.63.192.255 via winbox
09:39:22 system,info,account user ersitizastes logged out from 10.63.192.255 via winbox
09:41:01 dhcp,info dhcp1 deassigned 10.63.193.13 from 18:22:7E:2A:5A:5E
09:41:01 hotspot,debug Hotspot: dhcp host 10.63.193.13 changed type to dynamic (remove after 5s)
09:41:01 dhcp,info dhcp1 assigned 10.63.193.13 to 18:22:7E:2A:5A:5E
09:41:01 hotspot,debug Hotspot: dynamic host 10.63.193.13 changed type to dhcp (got back lease)
09:44:05 dhcp,info dhcp1 assigned 10.63.193.27 to 48:59:29:FA:52:94
09:44:09 hotspot,debug Hotspot: new host detected 48:59:29:FA:52:94/10.63.193.27 by UDP :2270 -> 10.63.192.1:53
09:44:09 hotspot,debug Hotspot: dhcp host 48:59:29:FA:52:94/10.63.193.27 added, ip 10.63.193.27
09:45:38 dhcp,info dhcp1 deassigned 10.63.194.135 from 3C:18:9F:33:05:31
09:45:38 dhcp,info dhcp1 assigned 10.63.194.135 to 3C:18:9F:33:05:31
09:45:41 hotspot,debug Hotspot: new host detected 3C:18:9F:33:05:31/10.63.194.135 by UDP :50695 -> 10.63.192.1:53
09:45:41 hotspot,debug Hotspot: dhcp host 3C:18:9F:33:05:31/10.63.194.135 added, ip 10.63.194.135
09:46:44 hotspot,debug Hotspot: dhcp host 10.63.193.27 removed: keepalive timeout
09:47:02 hotspot,debug Hotspot: new host detected 30:19:66:27:D9:9F/10.63.193.22 by TCP :48594 -> 31.13.73.3:443
09:47:02 hotspot,debug Hotspot: dhcp host 30:19:66:27:D9:9F/10.63.193.22 added, ip 10.63.193.22
09:47:31 dhcp,info dhcp1 deassigned 10.63.194.33 from EC:88:92:40:CC:8B
09:49:12 dhcp,info dhcp1 deassigned 10.63.193.22 from 30:19:66:27:D9:9F
09:49:12 hotspot,debug Hotspot: dhcp host 10.63.193.22 changed type to dynamic (remove after 5s)
09:49:17 hotspot,debug Hotspot: dynamic host 10.63.193.22 removed: lost dhcp lease
09:49:29 dhcp,info dhcp1 assigned 10.63.193.32 to 78:F8:82:E2:F8:1B
09:49:30 hotspot,debug Hotspot: new host detected 78:F8:82:E2:F8:1B/10.63.193.32 by UDP :36672 -> 10.63.192.1:53
09:49:30 hotspot,debug Hotspot: dhcp host 78:F8:82:E2:F8:1B/10.63.193.32 added, ip 10.63.193.32
09:49:43 dhcp,info dhcp1 assigned 10.63.193.22 to 30:19:66:27:D9:9F
09:49:44 hotspot,debug Hotspot: new host detected 30:19:66:27:D9:9F/10.63.193.22 by TCP :33174 -> 31.13.73.3:443
09:49:44 hotspot,debug Hotspot: dhcp host 30:19:66:27:D9:9F/10.63.193.22 added, ip 10.63.193.22
09:49:59 hotspot,debug Hotspot: dhcp host 10.63.194.135 removed: keepalive timeout
09:50:35 hotspot,info,debug T-18:22:7E:2A:5A:5E (10.63.193.13): logged out: keepalive timeout
09:50:35 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): removing queue
09:50:35 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): removing address-list
09:50:35 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): removing ip->user binding
09:50:35 hotspot,debug Hotspot: dhcp host 10.63.193.13 removed: keepalive timeout
09:50:37 dhcp,info dhcp1 assigned 10.63.193.33 to 00:0D:F0:99:D8:9F
09:50:37 hotspot,debug Hotspot: new host detected 00:0D:F0:99:D8:9F/10.63.193.33 by UDP :137 -> 10.63.192.1:137
09:50:37 hotspot,debug Hotspot: dhcp host 00:0D:F0:99:D8:9F/10.63.193.33 added, ip 10.63.193.33
09:50:46 dhcp,info dhcp1 deassigned 10.63.194.143 from 80:65:6D:56:6E:A5
09:50:55 hotspot,debug Hotspot: new host detected 58:A2:B5:DA:FD:96/10.63.194.39 by UDP :56000 -> 10.63.192.1:53
09:50:55 hotspot,debug Hotspot: dhcp host 58:A2:B5:DA:FD:96/10.63.194.39 added, ip 10.63.194.39
09:51:48 dhcp,info dhcp1 deassigned 10.63.194.135 from 3C:18:9F:33:05:31
09:51:48 dhcp,info dhcp1 assigned 10.63.194.135 to 3C:18:9F:33:05:31
09:51:51 hotspot,debug Hotspot: new host detected 3C:18:9F:33:05:31/10.63.194.135 by UDP :50349 -> 10.63.192.1:53
09:51:51 hotspot,debug Hotspot: dhcp host 3C:18:9F:33:05:31/10.63.194.135 added, ip 10.63.194.135
09:51:53 hotspot,debug Hotspot: dhcp host 10.63.193.32 removed: keepalive timeout
09:51:58 dhcp,info dhcp1 deassigned 10.63.194.39 from 58:A2:B5:DA:FD:96
09:51:58 hotspot,debug Hotspot: dhcp host 10.63.194.39 changed type to dynamic (remove after 5s)
09:51:58 dhcp,info dhcp1 assigned 10.63.194.39 to 58:A2:B5:DA:FD:96
09:51:58 hotspot,debug Hotspot: dynamic host 10.63.194.39 changed type to dhcp (got back lease)
09:53:14 hotspot,debug Hotspot: new host detected 18:22:7E:2A:5A:5E/10.63.193.13 by UDP :38200 -> 10.63.192.1:53
09:53:14 hotspot,info,debug T-18:22:7E:2A:5A:5E (10.63.193.13): trying to log in by mac-cookie
09:53:14 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): using profile <00>
09:53:14 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): adding ip->user binding
09:53:14 hotspot,debug Hotspot: dhcp host 18:22:7E:2A:5A:5E/10.63.193.13 added, ip 10.63.193.13
09:53:15 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): adding address-list rule <00>
09:53:15 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): adding queue <180k/180k 0/0 0/0 0/0 8 64k/64k>
09:53:15 hotspot,account,info,debug T-18:22:7E:2A:5A:5E (10.63.193.13): logged in
09:53:28 dhcp,info dhcp1 deassigned 10.63.193.6 from 34:FC:EF:D1:29:25
09:53:56 hotspot,debug Hotspot: dhcp host 10.63.193.33 removed: keepalive timeout
09:54:24 hotspot,debug Hotspot: dhcp host 10.63.193.22 removed: keepalive timeout
09:54:41 hotspot,debug Hotspot: dhcp host 10.63.194.135 removed: keepalive timeout
09:55:57 dhcp,info dhcp1 deassigned 10.63.193.13 from 18:22:7E:2A:5A:5E
09:55:57 hotspot,debug Hotspot: dhcp host 10.63.193.13 changed type to dynamic (remove after 5s)
09:55:57 dhcp,info dhcp1 assigned 10.63.193.13 to 18:22:7E:2A:5A:5E
09:55:57 hotspot,debug Hotspot: dynamic host 10.63.193.13 changed type to dhcp (got back lease)
09:56:06 hotspot,debug Hotspot: dhcp host 10.63.194.39 removed: keepalive timeout
09:56:30 dhcp,info dhcp1 deassigned 10.63.193.11 from D0:59:E4:36:95:99
09:56:49 hotspot,debug Hotspot: new host detected 44:91:DB:51:5E:EB/10.63.194.138 by ICMP type<3> code<3> to 10.63.192.1
09:56:49 hotspot,debug Hotspot: dhcp host 44:91:DB:51:5E:EB/10.63.194.138 added, ip 10.63.194.138
09:57:05 dhcp,info dhcp1 assigned 10.63.194.143 to 80:65:6D:56:6E:A5
09:57:06 hotspot,debug Hotspot: new host detected 80:65:6D:56:6E:A5/10.63.194.143 by UDP :35558 -> 10.63.192.1:53
09:57:06 hotspot,debug Hotspot: dhcp host 80:65:6D:56:6E:A5/10.63.194.143 added, ip 10.63.194.143
09:57:21 dhcp,info dhcp1 assigned 10.63.193.51 to 60:D7:AE:C8:92:CC
09:57:24 hotspot,debug Hotspot: new host detected 60:D7:AE:C8:92:CC/10.63.193.51 by UDP :1963 -> 10.63.192.1:53
09:57:24 hotspot,debug Hotspot: dhcp host 60:D7:AE:C8:92:CC/10.63.193.51 added, ip 10.63.193.51
09:57:31 dhcp,info dhcp1 deassigned 10.63.193.13 from 18:22:7E:2A:5A:5E
09:57:31 hotspot,debug Hotspot: dhcp host 10.63.193.13 changed type to dynamic (remove after 5s)
09:57:36 hotspot,info,debug T-18:22:7E:2A:5A:5E (10.63.193.13): logged out: lost dhcp lease
09:57:36 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): removing queue
09:57:36 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): removing address-list
09:57:36 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): removing ip->user binding
09:57:36 hotspot,debug Hotspot: dynamic host 10.63.193.13 removed: lost dhcp lease
09:57:50 hotspot,debug Hotspot: new host detected 58:A2:B5:DA:FD:96/10.63.194.39 by ICMP type<3> code<3> to 10.63.192.1
09:57:50 hotspot,debug Hotspot: dhcp host 58:A2:B5:DA:FD:96/10.63.194.39 added, ip 10.63.194.39
09:59:35 hotspot,debug Hotspot: dhcp host 10.63.194.143 removed: keepalive timeout
10:00:40 hotspot,debug Hotspot: dhcp host 10.63.194.39 removed: keepalive timeout
10:02:46 dhcp,info dhcp1 assigned 10.63.193.13 to 18:22:7E:2A:5A:5E
10:03:00 dhcp,info dhcp1 assigned 10.63.193.34 to 64:6C:B2:66:CE:DE
10:03:01 hotspot,debug Hotspot: new host detected 64:6C:B2:66:CE:DE/10.63.193.34 by UDP :34396 -> 10.63.192.1:53
10:03:01 hotspot,debug Hotspot: dhcp host 64:6C:B2:66:CE:DE/10.63.193.34 added, ip 10.63.193.34
10:03:14 dhcp,info dhcp1 deassigned 10.63.193.34 from 64:6C:B2:66:CE:DE
10:03:14 hotspot,debug Hotspot: dhcp host 10.63.193.34 changed type to dynamic (remove after 5s)
10:03:14 dhcp,info dhcp1 assigned 10.63.193.34 to 64:6C:B2:66:CE:DE
10:03:14 hotspot,debug Hotspot: dynamic host 10.63.193.34 changed type to dhcp (got back lease)
10:03:37 hotspot,debug Hotspot: new host detected 50:55:27:A0:E9:AF/10.63.193.133 by TCP :53803 -> 58.67.196.175:7006
10:03:37 hotspot,debug Hotspot: dynamic host 50:55:27:A0:E9:AF/10.63.193.133 added, ip 10.63.193.35
10:03:42 dhcp,info dhcp1 assigned 10.63.193.133 to 50:55:27:A0:E9:AF
10:03:42 hotspot,debug Hotspot: dynamic host 10.63.193.35 removed: dhcp entry overrides dynamic one
10:03:43 hotspot,debug Hotspot: new host detected 50:55:27:A0:E9:AF/10.63.193.133 by ICMP type<3> code<3> to 10.63.192.1
10:03:43 hotspot,debug Hotspot: dhcp host 50:55:27:A0:E9:AF/10.63.193.133 added, ip 10.63.193.133
10:03:54 dhcp,info dhcp1 deassigned 10.63.193.23 from 38:2D:D1:A5:04:39
10:04:18 hotspot,debug Hotspot: new host detected 18:22:7E:2A:5A:5E/10.63.193.13 by UDP :48695 -> 10.63.192.1:53
10:04:18 hotspot,info,debug T-18:22:7E:2A:5A:5E (10.63.193.13): trying to log in by mac-cookie
10:04:18 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): using profile <00>
10:04:18 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): adding ip->user binding
10:04:18 hotspot,debug Hotspot: dhcp host 18:22:7E:2A:5A:5E/10.63.193.13 added, ip 10.63.193.13
10:04:18 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): adding address-list rule <00>
10:04:18 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): adding queue <180k/180k 0/0 0/0 0/0 8 64k/64k>
10:04:18 hotspot,account,info,debug T-18:22:7E:2A:5A:5E (10.63.193.13): logged in
10:04:33 hotspot,info,debug T-64:6C:B2:66:CE:DE (10.63.193.34): trying to log in by trial
10:04:33 hotspot,debug T-64:6C:B2:66:CE:DE (10.63.193.34): using profile <00>
10:04:33 hotspot,debug T-64:6C:B2:66:CE:DE (10.63.193.34): adding ip->user binding
10:04:33 hotspot,debug T-64:6C:B2:66:CE:DE (10.63.193.34): adding address-list rule <00>
10:04:33 hotspot,debug T-64:6C:B2:66:CE:DE (10.63.193.34): adding queue <180k/180k 0/0 0/0 0/0 8 64k/64k>
10:04:33 hotspot,account,info,debug T-64:6C:B2:66:CE:DE (10.63.193.34): logged in
10:05:54 hotspot,debug Hotspot: dhcp host 10.63.193.133 removed: keepalive timeout
10:05:56 dhcp,info dhcp1 deassigned 10.63.194.35 from F4:F1:E1:1E:3A:2C
10:05:56 dhcp,info dhcp1 assigned 10.63.194.35 to F4:F1:E1:1E:3A:2C
10:05:57 hotspot,debug Hotspot: new host detected F4:F1:E1:1E:3A:2C/10.63.194.35 by UDP :15502 -> 10.63.192.1:53
10:05:57 hotspot,debug Hotspot: dhcp host F4:F1:E1:1E:3A:2C/10.63.194.35 added, ip 10.63.194.35
10:07:03 script,error 5g.net 2 Down
10:07:28 interface,info ether9 link down
10:07:45 hotspot,info,debug T-18:22:7E:2A:5A:5E (10.63.193.13): logged out: keepalive timeout
10:07:45 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): removing queue
10:07:45 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): removing address-list
10:07:45 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): removing ip->user binding
10:07:45 hotspot,debug Hotspot: dhcp host 10.63.193.13 removed: keepalive timeout
10:07:54 interface,info ether9 link up (speed 100M, full duplex)
10:08:01 script,error 5g.net 1 Down
10:08:10 hotspot,info,debug T-64:6C:B2:66:CE:DE (10.63.193.34): logged out: keepalive timeout
10:08:10 hotspot,debug T-64:6C:B2:66:CE:DE (10.63.193.34): removing queue
10:08:10 hotspot,debug T-64:6C:B2:66:CE:DE (10.63.193.34): removing address-list
10:08:10 hotspot,debug T-64:6C:B2:66:CE:DE (10.63.193.34): removing ip->user binding
10:08:10 hotspot,debug Hotspot: dhcp host 10.63.193.34 removed: keepalive timeout
10:08:32 dhcp,info dhcp1 deassigned 10.63.194.138 from 44:91:DB:51:5E:EB
10:08:32 hotspot,debug Hotspot: dhcp host 10.63.194.138 changed type to dynamic (remove after 5s)
10:08:37 hotspot,debug Hotspot: dynamic host 10.63.194.138 removed: lost dhcp lease
10:08:48 dhcp,info dhcp1 assigned 10.63.194.138 to 44:91:DB:51:5E:EB
10:09:00 script,warning 5g.net 1 Up
10:09:01 script,warning 5g.net 2 Up
10:09:21 hotspot,debug Hotspot: dhcp host 10.63.194.35 removed: keepalive timeout
10:09:23 hotspot,debug Hotspot: dhcp host 10.63.193.51 removed: keepalive timeout
10:09:59 dhcp,info dhcp1 assigned 10.63.193.36 to 14:32:D1:10:FE:CE
10:10:00 hotspot,debug Hotspot: new host detected 60:D7:AE:C8:92:CC/10.63.193.51 by UDP :39064 -> 10.63.192.1:53
10:10:00 hotspot,debug Hotspot: dhcp host 60:D7:AE:C8:92:CC/10.63.193.51 added, ip 10.63.193.51
10:10:00 hotspot,debug Hotspot: new host detected 14:32:D1:10:FE:CE/10.63.193.36 by UDP :62322 -> 10.63.192.1:53
10:10:00 hotspot,debug Hotspot: dhcp host 14:32:D1:10:FE:CE/10.63.193.36 added, ip 10.63.193.36
10:10:07 dhcp,info dhcp1 deassigned 10.63.193.24 from E4:90:7E:50:12:B3
10:11:21 dhcp,info dhcp1 assigned 10.63.193.15 to F8:A9:D0:5E:6A:9F
10:11:22 hotspot,debug Hotspot: new host detected F8:A9:D0:5E:6A:9F/10.63.193.15 by UDP :51915 -> 10.63.192.1:53
10:11:22 hotspot,debug Hotspot: dhcp host F8:A9:D0:5E:6A:9F/10.63.193.15 added, ip 10.63.193.15
10:12:05 dhcp,info dhcp1 deassigned 10.63.194.136 from B4:30:52:B0:9E:72
10:13:00 hotspot,debug Hotspot: new host detected 18:22:7E:2A:5A:5E/10.63.193.13 by UDP :7573 -> 10.63.192.1:53
10:13:00 hotspot,info,debug T-18:22:7E:2A:5A:5E (10.63.193.13): trying to log in by mac-cookie
10:13:00 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): using profile <00>
10:13:00 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): adding ip->user binding
10:13:00 hotspot,debug Hotspot: dhcp host 18:22:7E:2A:5A:5E/10.63.193.13 added, ip 10.63.193.13
10:13:00 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): adding address-list rule <00>
10:13:00 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): adding queue <180k/180k 0/0 0/0 0/0 8 64k/64k>
10:13:00 hotspot,account,info,debug T-18:22:7E:2A:5A:5E (10.63.193.13): logged in
10:13:36 dhcp,info dhcp1 assigned 10.63.193.40 to 8C:3A:E3:6B:34:DD
10:13:40 hotspot,debug Hotspot: new host detected 8C:3A:E3:6B:34:DD/10.63.193.40 by UDP :57360 -> 10.63.192.1:53
10:13:40 hotspot,debug Hotspot: dhcp host 8C:3A:E3:6B:34:DD/10.63.193.40 added, ip 10.63.193.40
10:14:00 dhcp,info dhcp1 assigned 10.63.193.42 to B8:5A:73:A8:5B:84
10:14:01 hotspot,debug Hotspot: new host detected B8:5A:73:A8:5B:84/10.63.193.42 by UDP :50108 -> 10.63.192.1:53
10:14:01 hotspot,debug Hotspot: dhcp host B8:5A:73:A8:5B:84/10.63.193.42 added, ip 10.63.193.42
10:14:38 dhcp,info dhcp1 deassigned 10.63.193.40 from 8C:3A:E3:6B:34:DD
10:14:38 hotspot,debug Hotspot: dhcp host 10.63.193.40 changed type to dynamic (remove after 5s)
10:14:43 hotspot,debug Hotspot: dynamic host 10.63.193.40 removed: lost dhcp lease
10:15:22 hotspot,debug Hotspot: dhcp host 10.63.193.15 removed: keepalive timeout
10:15:44 dhcp,info dhcp1 deassigned 10.63.193.44 from 6C:2F:2C:1C:E4:DC
10:15:48 hotspot,debug Hotspot: new host detected 8C:3A:E3:6B:34:DD/10.63.193.40 by ICMP type<3> code<3> to 10.63.192.1
10:15:48 hotspot,debug Hotspot: dynamic host 8C:3A:E3:6B:34:DD/10.63.193.40 added, ip 10.63.193.43
10:15:48 dhcp,info dhcp1 assigned 10.63.193.40 to 8C:3A:E3:6B:34:DD
10:15:48 hotspot,debug Hotspot: dynamic host 10.63.193.43 removed: dhcp entry overrides dynamic one
10:15:48 hotspot,debug Hotspot: new host detected 8C:3A:E3:6B:34:DD/10.63.193.40 by ICMP type<3> code<3> to 10.63.192.1
10:15:48 hotspot,debug Hotspot: dhcp host 8C:3A:E3:6B:34:DD/10.63.193.40 added, ip 10.63.193.40
10:16:04 hotspot,debug Hotspot: dhcp host 10.63.193.42 removed: keepalive timeout
10:16:30 hotspot,info,debug T-18:22:7E:2A:5A:5E (10.63.193.13): logged out: session timeout
10:16:30 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): removing queue
10:16:30 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): removing address-list
10:16:30 hotspot,debug T-18:22:7E:2A:5A:5E (10.63.193.13): removing ip->user binding
10:16:44 dhcp,info dhcp1 deassigned 10.63.193.22 from 30:19:66:27:D9:9F
10:17:30 hotspot,debug Hotspot: new host detected F4:F1:E1:1E:3A:2C/10.63.194.35 by UDP :56768 -> 10.63.192.1:53
10:17:30 hotspot,debug Hotspot: dhcp host F4:F1:E1:1E:3A:2C/10.63.194.35 added, ip 10.63.194.35
10:18:39 dhcp,info dhcp1 deassigned 10.63.193.51 from 60:D7:AE:C8:92:CC
10:18:39 hotspot,debug Hotspot: dhcp host 10.63.193.51 changed type to dynamic (remove after 5s)
10:18:44 hotspot,debug Hotspot: dynamic host 10.63.193.51 removed: lost dhcp lease
10:19:09 hotspot,debug Hotspot: new host detected 58:A2:B5:DA:FD:96/10.63.194.39 by UDP :63376 -> 10.63.192.1:53
10:19:09 hotspot,debug Hotspot: dhcp host 58:A2:B5:DA:FD:96/10.63.194.39 added, ip 10.63.194.39
10:19:13 dhcp,info dhcp1 deassigned 10.63.194.39 from 58:A2:B5:DA:FD:96
10:19:13 hotspot,debug Hotspot: dhcp host 10.63.194.39 changed type to dynamic (remove after 5s)
10:19:16 dhcp,info dhcp1 assigned 10.63.194.39 to 58:A2:B5:DA:FD:96
10:19:16 hotspot,debug Hotspot: dynamic host 10.63.194.39 changed type to dhcp (got back lease)
10:19:20 dhcp,info dhcp1 assigned 10.63.193.23 to 38:2D:D1:A5:04:39
10:19:21 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by UDP :19688 -> 10.63.192.1:53
10:19:21 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
10:19:34 dhcp,info dhcp1 assigned 10.63.193.51 to 60:D7:AE:C8:92:CC
10:19:35 hotspot,debug Hotspot: new host detected 60:D7:AE:C8:92:CC/10.63.193.51 by UDP :29971 -> 10.63.192.1:53
10:19:35 hotspot,debug Hotspot: dhcp host 60:D7:AE:C8:92:CC/10.63.193.51 added, ip 10.63.193.51
10:19:43 dhcp,info dhcp1 deassigned 10.63.193.59 from F8:A9:D0:5A:F4:85
10:19:54 system,info,account user ersitizastes logged in from 10.63.192.255 via winbox
10:21:21 dhcp,info dhcp1 assigned 10.63.193.45 to 9C:E6:E7:07:04:65
10:21:21 hotspot,debug Hotspot: new host detected 9C:E6:E7:07:04:65/10.63.193.45 by UDP :42299 -> 10.63.192.1:53
10:21:21 hotspot,debug Hotspot: dhcp host 9C:E6:E7:07:04:65/10.63.193.45 added, ip 10.63.193.45
10:22:05 hotspot,debug Hotspot: dhcp host 10.63.193.23 removed: keepalive timeout
10:22:11 hotspot,debug Hotspot: dhcp host 10.63.194.39 removed: keepalive timeout
10:23:29 system,info,account user ftp logged in from 10.63.192.255 via ftp
10:23:29 system,info,account user ftp logged out from 10.63.192.255 via ftp
10:23:50 hotspot,debug Hotspot: dhcp host 10.63.193.40 removed: keepalive timeout
10:24:07 system,info,account user ersitizastes logged out from 10.63.192.255 via winbox
10:24:21 dhcp,info dhcp1 deassigned 10.63.194.146 from C4:42:02:21:02:DC
10:27:03 hotspot,debug Hotspot: dhcp host 10.63.193.13 removed: keepalive timeout
10:27:27 dhcp,info dhcp1 assigned 10.63.194.120 to 48:59:29:E3:59:62
10:27:30 dhcp,info dhcp1 assigned 10.63.193.14 to 20:62:74:E9:92:B0
10:27:30 hotspot,debug Hotspot: new host detected 20:62:74:E9:92:B0/10.63.193.14 by UDP :54776 -> 10.63.192.1:53
10:27:30 hotspot,debug Hotspot: dhcp host 20:62:74:E9:92:B0/10.63.193.14 added, ip 10.63.193.14
10:27:36 hotspot,debug Hotspot: new host detected 38:2D:D1:A5:04:39/10.63.193.23 by UDP :65353 -> 10.63.192.1:53
10:27:36 hotspot,debug Hotspot: dhcp host 38:2D:D1:A5:04:39/10.63.193.23 added, ip 10.63.193.23
10:27:44 dhcp,info dhcp1 deassigned 10.63.193.14 from 20:62:74:E9:92:B0
10:27:44 hotspot,debug Hotspot: dhcp host 10.63.193.14 changed type to dynamic (remove after 5s)
10:27:44 dhcp,info dhcp1 assigned 10.63.193.14 to 20:62:74:E9:92:B0
10:27:44 hotspot,debug Hotspot: dynamic host 10.63.193.14 changed type to dhcp (got back lease)
10:28:11 hotspot,debug Hotspot: new host detected 48:59:29:E3:59:62/10.63.194.120 by UDP :15014 -> 10.63.192.1:53
10:28:11 hotspot,debug Hotspot: dhcp host 48:59:29:E3:59:62/10.63.194.120 added, ip 10.63.194.120
10:29:50 hotspot,debug Hotspot: dhcp host 10.63.193.14 removed: keepalive timeout
10:30:42 system,info,account user ersitizastes logged in from 10.63.192.255 via winbox
10:33:37 dhcp,info dhcp1 assigned 10.63.193.47 to 34:BE:00:95:74:65
10:33:39 hotspot,debug Hotspot: new host detected 34:BE:00:95:74:65/10.63.193.47 by UDP :5717 -> 10.63.192.1:53
10:33:39 hotspot,debug Hotspot: dhcp host 34:BE:00:95:74:65/10.63.193.47 added, ip 10.63.193.47
10:33:59 hotspot,debug Hotspot: new host detected 50:55:27:A0:E9:AF/10.63.193.133 by ICMP type<3> code<3> to 10.63.192.1
10:33:59 hotspot,debug Hotspot: dhcp host 50:55:27:A0:E9:AF/10.63.193.133 added, ip 10.63.193.133
10:34:03 script,error Google Down
10:35:00 script,warning Google Up
10:37:30 dhcp,info dhcp1 assigned 10.63.193.38 to 14:32:D1:1C:E1:6E
10:37:31 hotspot,debug Hotspot: new host detected 14:32:D1:1C:E1:6E/10.63.193.38 by UDP :44954 -> 10.63.192.1:53
10:37:31 hotspot,debug Hotspot: dhcp host 14:32:D1:1C:E1:6E/10.63.193.38 added, ip 10.63.193.38
10:39:41 hotspot,debug Hotspot: dhcp host 10.63.193.38 removed: keepalive timeout
10:40:10 dhcp,info dhcp1 deassigned 10.63.193.51 from 60:D7:AE:C8:92:CC
10:40:10 hotspot,debug Hotspot: dhcp host 10.63.193.51 changed type to dynamic (remove after 5s)
10:40:13 hotspot,debug Hotspot: dynamic host 10.63.193.51 removed: keepalive timeout
10:40:14 dhcp,info dhcp1 assigned 10.63.193.51 to 60:D7:AE:C8:92:CC
10:41:29 dhcp,info dhcp1 deassigned 10.63.194.138 from 44:91:DB:51:5E:EB
10:41:33 dhcp,info dhcp1 assigned 10.63.194.138 to 44:91:DB:51:5E:EB
10:41:34 dhcp,info dhcp1 deassigned 10.63.193.51 from 60:D7:AE:C8:92:CC
10:41:34 dhcp,info dhcp1 assigned 10.63.193.51 to 60:D7:AE:C8:92:CC
10:41:43 system,info,account user ersitizastes logged in from 10.63.192.255 via telnet
10:41:53 hotspot,debug Hotspot: new host detected 60:D7:AE:C8:92:CC/10.63.193.51 by UDP :47478 -> 10.63.192.1:53
10:41:53 hotspot,debug Hotspot: dhcp host 60:D7:AE:C8:92:CC/10.63.193.51 added, ip 10.63.193.51


# From outside AP #

[ersitizastes@5g.net 2] > /interface wireless print
Flags: X - disabled, R - running
0 R ;;; AP Virtual
name="Ap Virtual" mtu=1500 l2mtu=1600 mac-address=4C:5
master-interface=Station WDS mode=ap-bridge ssid="5g.n
wds-default-bridge=bridge wds-ignore-ssid=yes bridge-m
default-forwarding=no default-ap-tx-limit=0 default-cl

1 R ;;; Station WDS
name="Station WDS" mtu=1500 l2mtu=1600 mac-address=4C:
mode=station-wds ssid="" frequency=auto band=2ghz-b/g/
wireless-protocol=nv2-nstreme-802.11 vlan-mode=no-tag
wds-ignore-ssid=yes bridge-mode=enabled default-authen
default-client-tx-limit=0 hide-ssid=no security-profil

# Iám don't understand why -> #
my first AP is in 2,4 ghz, b/g 802.11
but the connected Station always jumps to
b/g/n - nv2-nstreme-802.11

Re: v6.35rc is released, new wireless package!

Posted: Wed Feb 03, 2016 3:52 pm
by Cha0s
Jesus man! Didn't you have anything longer to post?! :-?

Re: v6.35rc is released, new wireless package!

Posted: Wed Feb 03, 2016 7:01 pm
by n21roadie
Jesus man! Didn't you have anything longer to post?! :-?
+1 :lol:

Re: v6.35rc is released, new wireless package!

Posted: Wed Feb 03, 2016 7:09 pm
by jarda
How can I upgrade the hAP Lite?

There isn't enough disk space available.
smips cannot upgrade.png
Put there only separate system package, install it. Then put all other packages you need and install them. You will have more free space further.

Re: v6.35rc is released, new wireless package!

Posted: Wed Feb 03, 2016 7:32 pm
by Cha0s
Thanks, that did the trick!

Posted: Wed Feb 03, 2016 10:00 pm
by jarda
For nothing. Enjoy it.

Re: v6.35rc is released, new wireless package!

Posted: Wed Feb 03, 2016 11:33 pm
by PeterDoBrasil
v6.35rc2 ping time ap to station 8ms, device shows distance with value 1 km
Upgrade v6.35rc3 ap to station 150ms, device shows distance with value 5 km, using the same conditions!

Re: v6.35rc is released, new wireless package!

Posted: Thu Feb 04, 2016 10:50 am
by uldis
v6.35rc2 ping time ap to station 8ms, device shows distance with value 1 km
Upgrade v6.35rc3 ap to station 150ms, device shows distance with value 5 km, using the same conditions!
If the distance is not so far for the link - up to km then try to set the distance to indoors.

Re: v6.35rc is released, new wireless package!

Posted: Thu Feb 04, 2016 12:21 pm
by WirelessRudy
Any word on the default authentication tickbox in station mode?
I should be there I think....

Re: v6.35rc is released, new wireless package!

Posted: Thu Feb 04, 2016 2:11 pm
by kez
Is the default authenticate option gone? Is client now always to connect to units mentioned in the 'Connect List'?
Def-auth missing.PNG
Maybe the question is missed... There is no 'default authenticate' option tickbox anymore......
I can confirm that too.
You guys should try other Winbox version, maybe 3.0 or 3.1.

Re: v6.35rc is released, new wireless package!

Posted: Thu Feb 04, 2016 2:16 pm
by Cha0s
This is on hAP Lite. So I have no other option -but- to use the buggy Winbox 3 unfortunately.

Re: v6.35rc is released, new wireless package!

Posted: Thu Feb 04, 2016 4:03 pm
by strods
Version 6.35rc4 has been released.

Changes since previous version:
*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=104395)
*) certificate - allow manual crl url addition;
*) ipsec - fix console peer aes enc algorithm display;
*) ipsec - fix fast ph2 SA addition;
*) led - fix crash on assigned interface removal;
*) lte - support Alt38XX modem;
*) tile-crypto - fix minor memory leak;
*) wireless-rep - allow to connect to AP after scan;
*) wireless-rep - fix signal leds;
*) wireless-rep - request interface name for setup-repeater;
*) wireless-rep - adjust roaming scan times;
*) wireless-rep - do not allow empty ssid for AP modes.

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Thu Feb 04, 2016 5:27 pm
by satish143
Yesterday I install 6.35rc3 on CCS-1036 Mikrotik Hardware and run following command to test network performance using firewall rules.. i added single rules in firewall to track connection
hping3 --udp --data 512 --rand-source -i u10  <mikrotick ip>
Above command created around ~500k connection in connection table almost max out. CPU was 50%-60% and after 15 min kernel crash and Mikrotik rebooted.

I have opened ticket to support but they are saying it because of connection table full. But I am saying no matter connection table full or kernel should not get panic and crash :(

Does anyone able to produce this issue?

Re: v6.35rc is released, new wireless package!

Posted: Thu Feb 04, 2016 7:29 pm
by Cha0s
How much free ram did it have when it crashed?

Re: v6.35rc is released, new wireless package!

Posted: Thu Feb 04, 2016 11:29 pm
by ALEJANDROgordon
I have a question, this new package will have the ability to change the channel widths?, because now that advantage has only 92xx chips

Re: The Dude, work continues: v6.35rc test builds.

Posted: Fri Feb 05, 2016 2:32 am
by PeterDoBrasil
Yesterday I install 6.35rc3 on CCS-1036 Mikrotik Hardware and run following command to test network performance using firewall rules.. i added single rules in firewall to track connection
hping3 --udp --data 512 --rand-source -i u10  <mikrotick ip>
Above command created around ~500k connection in connection table almost max out. CPU was 50%-60% and after 15 min kernel crash and Mikrotik rebooted.

I have opened ticket to support but they are saying it because of connection table full. But I am saying no matter connection table full or kernel should not get panic and crash :(

Does anyone able to produce this issue?

you are right, rc3 is not good, ping time is much longer as in v.rc2

Re: v6.35rc is released, new wireless package!

Posted: Fri Feb 05, 2016 5:17 am
by bryans2k
in 6.34 VRRP was fixed to verify that it was up after reboot before taking over. It works for Ethernet connections but on SFP connections it still tries to takeover even though other VRRP routers are up and preemption is disabled.

Re: v6.35rc is released, new wireless package!

Posted: Fri Feb 05, 2016 12:28 pm
by strods
Version 6.35rc5 has been released.

Changes since previous version:
*) ssh - fixed connection stalling.

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Re: v6.35rc is released, new wireless package!

Posted: Fri Feb 05, 2016 2:07 pm
by PeterDoBrasil
Wrong background scan results, hit rate 0 %
http://forum.mikrotik.com/viewtopic.php ... 77#p519877

Re: v6.35rc is released, new wireless package!

Posted: Fri Feb 05, 2016 4:08 pm
by Siona
493G - Voltage monitor not working in ROS 6.34.1 and 6.35rc4

Re: v6.35rc is released, new wireless package!

Posted: Fri Feb 05, 2016 7:47 pm
by RabbitAtNet
Version 6.35rc5 has been released.
Hi guys,

great job! The new repeater feature really saves the day. No more hassle with all that WDS settings, at least for simple setups.
I just dropped the RC5 on my hAP lite and it worked right away. Keep it up!

Re: v6.35rc is released, new wireless package!

Posted: Sat Feb 06, 2016 2:08 pm
by NGiannis
Hi to all,

I have updated the packages to v6.35rc5 via the automated procedure of my RB.

I can not find the Wireless background choice on the Scan window.

Have I missed anything?

Re: v6.35rc is released, new wireless package!

Posted: Sat Feb 06, 2016 10:06 pm
by czolo
You have to download wireless-rep packege from all-packages. Put it into your router and reboot.

Re: v6.35rc is released, new wireless package!

Posted: Sun Feb 07, 2016 12:24 am
by meacho
When I use repeater client/AP mode I can't get DHCP IP address on some devices because of station pseudobridge mode used in client connection, but if I switch to station wds mode connection stop working.

Will that be fixed in newer versions?

Re: v6.35rc is released, new wireless package!

Posted: Sun Feb 07, 2016 8:01 am
by KBV
Returned old problem - time is not synchronized with the dynamic NTP servers.
After the command "/system ntp client print" synchronization occurs immediately.

It does occur not on all routers. I could not understand what it depends on.

Re: v6.35rc is released, new wireless package!

Posted: Sun Feb 07, 2016 9:57 pm
by InoX
What's the use of Background Scan if it disconnect radio before ticking it?

Re: v6.35rc is released, new wireless package!

Posted: Sun Feb 07, 2016 10:48 pm
by czolo
Packet throughput is not showing values in /wir reg (in winbox tab), when client have 6.35rc5

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 08, 2016 3:58 am
by Cha0s
What's the use of Background Scan if it disconnect radio before ticking it?
I was thinking the same thing!

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 08, 2016 2:31 pm
by Test471
Background scan does not work via Webfig.

When I try it from Webfig it disconnects clients but when I try the same thing from winbox then it works.

Latest rep package on 951g.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 08, 2016 5:26 pm
by WirelessRudy
Background scan does not work via Webfig.

When I try it from Webfig it disconnects clients but when I try the same thing from winbox then it works.

Latest rep package on 951g.
Like InoX and Cha0s wrote, it also doesn't work on my SXT's.
That's in winbox, the ultimate tool we still prefer to use.
What is indeed the use of the background scan if you need to open the scan window first, which initiates a scan. On remote you can't opt the 'background scan' tickbox anymore since you're already disconnected........

I believe someone else already wrote the option should be ticked 'on' by default.....

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 08, 2016 5:42 pm
by WirelessRudy
Version 6.35rc4 has been released.

Changes since previous version:
*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=104395)
*) certificate - allow manual crl url addition;
*) ipsec - fix console peer aes enc algorithm display;
*) ipsec - fix fast ph2 SA addition;
*) led - fix crash on assigned interface removal;
*) lte - support Alt38XX modem;
*) tile-crypto - fix minor memory leak;
*) wireless-rep - allow to connect to AP after scan;
*) wireless-rep - fix signal leds;
*) wireless-rep - request interface name for setup-repeater;
*) wireless-rep - adjust roaming scan times;
*) wireless-rep - do not allow empty ssid for AP modes.

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
Is this an answer to my question re the missing 'default auth' box?
How do I distill what is happening now from your post?
At times I just need a CPE to make a connection to an AP where only the frequency is set...
I usually have the mac address and the SSID of the AP set in two 'connect-list' rules. But sometimes we make a typo and the only way to check that is to have the CPE set to default auth. It will connect now anyway since most probably the AP is the strongest signal anyway...

How is the function "allow to connect to AP after scan" working? To which AP? On what frequency?

I think the default auth. tick box needs to come back.... 8)

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 08, 2016 9:25 pm
by Cha0s
I have the same questions as WirelessRudy :)

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 08, 2016 10:43 pm
by wispwest
So, will this help improve PtP throughput performance for 802.11n or AC?

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 09, 2016 9:30 am
by strods
Version 6.35rc6 has been released.

Changes since previous version:
*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=104395);
*) ipsec - always re-key ph1 because it was possible that ph1 without DPD would expire;
*) log - try not to loose disk messages and warn if lost any;
*) switch - make "sa-learning=yes" by default when adding Ingress VLAN Translation rules;
*) system - log time changes;
*) trafflow - fix potential deadlock.

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 09, 2016 12:38 pm
by jarda
Why SNTP client is off by default even it was on before the rc6 was installed and cloud time sync is on newly by default?
I dont want to switch the SNTP off silently just by update. Please, make sure the settings keep unchanged when update is installed.

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 09, 2016 7:20 pm
by wispwest
So, will this help improve PtP throughput performance for 802.11n or AC?

I take it the answer is no...

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 09, 2016 7:48 pm
by Siona
Version 6.35rc6 has been released.

Changes since previous version:
*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=104395);
*) ipsec - always re-key ph1 because it was possible that ph1 without DPD would expire;
*) log - try not to loose disk messages and warn if lost any;
*) switch - make "sa-learning=yes" by default when adding Ingress VLAN Translation rules;
*) system - log time changes;
*) trafflow - fix potential deadlock.

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
And what about voltage monitor in 493g?

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 09, 2016 9:06 pm
by whyfly
Is it possible to background scan with a wireless interfaced managed by CAPsMAN?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Feb 10, 2016 1:01 pm
by strods
Version 6.35rc7 has been released.

Changes since previous version:
*) queue-tree - improved nested queue limit calculation;
*) radius - warn radius client if incorrect secret is being used;
*) tile - fixed possible kernel failure with disabled watchdog timer caused by DDoS attack;
*) trafficgen - fix crash when unexpected stream reappears.

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Posted: Wed Feb 10, 2016 4:14 pm
by Siona
Voltage monitor still not working in rc7 on 493g

v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Feb 10, 2016 8:42 pm
by darkprocess
Map lite crashed and don't rebooting after upgrade. It's not the first time that ipdates crash the router. Why ?????

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Feb 11, 2016 5:22 am
by Alessio Garavano
Mmmm.... Interesting!!! Hotspot 2.0 with HTTPS-Redirection and another new features in the last 6.35rc7 :o

https://www.dropbox.com/s/15zj0l5au84gk ... .54.39.png

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Feb 11, 2016 2:12 pm
by strods
6.35rc8 has been released.

Changes since previous version:
*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=104395);
*) hotspot - clean-up all dead entries at once;
*) hotspot - fix possible deadlock;
*) net - rename max-arp-entries to less confusing max-neighbor-entries in CLI;
*) queue - added bucket-size setting to queues in CLI (derived from max-limit);
*) queue - improve "/queue interface" menu in CLI;
*) proxy - store error.html on flash if it is available;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Feb 11, 2016 2:55 pm
by juanvi
Included in new wireless repeater package?
Mmmm.... Interesting!!! Hotspot 2.0 with HTTPS-Redirection and another new features in the last 6.35rc7 :o

[img]https://www.dropbox.com/s/15zj0l5au84gk ... 9.png?dl=0[/img]

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Feb 11, 2016 8:14 pm
by WirelessRudy
While working this pacakge, is there any way the power output reading can be restored on ac models? Or is this limit coming from the chipset?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 12, 2016 4:53 am
by Alessio Garavano
Included in new wireless repeater package?
Mmmm.... Interesting!!! Hotspot 2.0 with HTTPS-Redirection and another new features in the last 6.35rc7 :o

[img]https://www.dropbox.com/s/15zj0l5au84gk ... 9.png?dl=0[/img]
Yes! not tested in other... but i am very happy with these new features and supports!

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sat Feb 13, 2016 10:58 am
by partovi64
HI Dear Friends
Why Delete (note) in outages(services)?!!!!!!!!
We have report by it.
please help me about solve this problem.
OUTAGES.jpg
outages v3.jpg

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sun Feb 14, 2016 11:02 am
by czolo
Included in new wireless repeater package?
No
It was before

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Feb 15, 2016 2:26 am
by bclewl1ns
so i uploaded the new Rc8 to my test system upgraded from 6.3.3.3 to 6.35rc8

upon reboot i no longer have have access to either system via IP. it took them both 2 min to reboot. I do see their mac address's in my network neighbor's list and can connect to them via mac tenet but upon connecting to them i get disconnected.

Also after i connect the mac telnet does not go past the attached image. these are both netmetal 921

screenshot-1.png

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Feb 15, 2016 2:45 am
by bclewl1ns
More info. I finally was able to successfully mac telnet into one of the devices. However the command

interface bridge print show nothing but the interface bridge port print showed the following
screen2.png
why did the upgrade change my interface names and delete my bridge.

After this i removed the interfaces from the nonexistent bridge and created a new bridge. I then added eth1 back to the new bridge. As soon as i did that my mac telnet session froze and I lost the ability to Mac Telenet to the device.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Feb 15, 2016 5:15 am
by PeterDoBrasil
Included in new wireless repeater package?
Mmmm.... Interesting!!! Hotspot 2.0 with HTTPS-Redirection and another new features in the last 6.35rc7 :o

[img]https://www.dropbox.com/s/15zj0l5au84gk ... 9.png?dl=0[/img]
Yes! not tested in other... but i am very happy with these new features and supports!
Why I can't find any over 802.11u? The Question is when Mikrotik will release this Protocol in their AP's configurations! :shock:

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Feb 15, 2016 5:58 am
by PeterDoBrasil
Included in new wireless repeater package?
Mmmm.... Interesting!!! Hotspot 2.0 with HTTPS-Redirection and another new features in the last 6.35rc7 :o

[img]https://www.dropbox.com/s/15zj0l5au84gk ... 9.png?dl=0[/img]
Yes! not tested in other... but i am very happy with these new features and supports!
Very interesting to typing the commands into new terminal, but I'don't understand how works this type of hotspot; how control the users payments, access limits etc, etc??????

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Tue Feb 16, 2016 4:11 am
by Zorro
Why I can't find any over 802.11u? The Question is when Mikrotik will release this Protocol in their AP's configurations! :shock:
we're can only guess, i think.
but my guess is: they not finishing developing code/support for that.
same apply for 802.11s support i think.
HWMP and MME support relatively matured in comparison. (no signs of of olsr or cjdns adoption/consideration, yet, sadly).
so far "ad-hoc" networking (and relevant protocols, like cjdns, HWMP, MME, 802.11s and to some extent OLSR) are new "big things" in networking aswell as 802.11u for inter-networking.
and both 802.11s and 802.11u - make no sense and use one without another in "real applications/cases".
802.11u despite being 5yr old thing - have quite fragmented(among published and freely-available to use/recycle/adopt)code for,which imply lot of efforts to develop support, which imply "not so lightspeed" creation/adoption time for relatively small teams/companies, doing it by themselves.

p.s.
as you can see - "ad-hoc" networking - also become Major trend outside "civilian" sector aswell. aside MANET - there was Several different "battlefield-grade" protocols, products, hardware/solutions based on.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Tue Feb 16, 2016 9:42 am
by strods
6.35rc9 has been released.

Changes since previous version:
*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=104395);
*) l2tp - added support for proxy authentication when receiving forwarded PPPoE sesssions;
*) l2tp - added support for Hidden AVP, it is needed for proxy authentication;
*) ipsec - fix larval SA refresh for display;
*) wireless-rep - added 802.11g/n only band;
*) wireless-rep,capsman - added rate config support;
*) wireless-rep,capsman - added more configuration settings;
*) ssh - simplify login process;
*) ups - fix entering hibernate mode when below battery capacity limit;
*) ups - fix waiting for AC power restore in hibernate mode;
*) lte - fix allowed bands for RBSXTLTE3-7;
*) lte - support for zte mf820s2.

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Tue Feb 16, 2016 3:11 pm
by ganewbie
6.35rc9 has been released.

*) l2tp - added support for proxy authentication when receiving forwarded PPPoE sesssions;
*) l2tp - added support for Hidden AVP, it is needed for proxy authentication;
This fixes the issues with LNS function to carry PPPoE sessions over L2TP tunnels.
Now it could replace Cisco if testing reveal no surprises.

Thanks to the Mikrotik Team

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Tue Feb 16, 2016 3:38 pm
by strods
Version 6.35rc10 has been released.

Changes since previous version:
*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=104395);
*) lte - added ipv6 support for SXT LTE;
*) dhcpv6 client - fix pd hint with empty address;
*) ipsec - fix multiple consecutive dynamic policy flush;
*) winbox - incomplete ARP entries are not refreshed;
*) winbox - fixed multi value field display (i.e. web proxy ports);
*) winbox - added ipv6 firewall missing log option;
*) profiler - classify certificate signing;
*) services - do not show ssh entry under ip services if security package is disabled;
*) queue - added bucket-size setting to queues (derived from max-limit);
*) queue - improve "/queue interface" menu;
*) console - update copyright notice;
*) ip - rename max-arp-entries to less confusing max-neighbor-entries;
*) l2tp - added support for max-sessions.

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Re: v6.35rc is released, new wireless package!

Posted: Tue Feb 16, 2016 3:42 pm
by DjM
Version 6.35rc5 has been released.

Changes since previous version:
*) ssh - fixed connection stalling.
Hello MikroTik support team,

Can you please share more details of this bug?
- In which version was the bug introduced?
- In which cases is the login process stalling?

Thank you

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Tue Feb 16, 2016 3:53 pm
by Cha0s
Any news regarding Voltage being reported wrong on RB2011-UiAS?
http://forum.mikrotik.com/viewtopic.php ... 75#p520275

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Feb 17, 2016 5:38 am
by PeterDoBrasil
6.35rc9 has been released.

Changes since previous version:
*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=104395);
*) l2tp - added support for proxy authentication when receiving forwarded PPPoE sesssions;
*) l2tp - added support for Hidden AVP, it is needed for proxy authentication;
*) ipsec - fix larval SA refresh for display;
*) wireless-rep - added 802.11g/n only band;
*) wireless-rep,capsman - added rate config support;
*) wireless-rep,capsman - added more configuration settings;
*) ssh - simplify login process;
*) ups - fix entering hibernate mode when below battery capacity limit;
*) ups - fix waiting for AC power restore in hibernate mode;
*) lte - fix allowed bands for RBSXTLTE3-7;
*) lte - support for zte mf820s2.

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
I can't find this, in 2,4 ghz device and not in 5,8 ghz (6.35rc10)
wireless-rep - added 802.11g/n only band;

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Feb 17, 2016 7:59 am
by npero
[
I can't find this, in 2,4 ghz device and not in 5,8 ghz (6.35rc10)
wireless-rep - added 802.11g/n only band;

802.11b or 802.11g is working on 2.4GHz not 5GHz look the wikipedia https://en.wikipedia.org/wiki/IEEE_802.11

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Feb 17, 2016 11:06 am
by juanvi
"wireless-rep,capsman - added more configuration settings" and other options questions. Can you explain, put an example, or complete the online manual for:

- CAP's Access rule -> SSID Regexp (SSID is Ap side fixed parameter, cant understand it as an Access rule)

- New CAP's provisioning -> Identity Regexp (thinking abou matching rules for pre-configured CAP's /system/identity? )

Thanks to all inadvance.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Feb 17, 2016 8:36 pm
by PeterDoBrasil
no g-n.png
[
I can't find this, in 2,4 ghz device and not in 5,8 ghz (6.35rc10)
wireless-rep - added 802.11g/n only band;

802.11b or 802.11g is working on 2.4GHz not 5GHz look the wikipedia https://en.wikipedia.org/wiki/IEEE_802.11

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Feb 17, 2016 11:03 pm
by ivicask
no g-n.png
[
I can't find this, in 2,4 ghz device and not in 5,8 ghz (6.35rc10)
wireless-rep - added 802.11g/n only band;

802.11b or 802.11g is working on 2.4GHz not 5GHz look the wikipedia https://en.wikipedia.org/wiki/IEEE_802.11
Yes same here

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Feb 18, 2016 7:24 am
by Zorro
is any decription/changelog for 635rc11, yet ?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Feb 18, 2016 7:39 am
by macgaiver
is any decription/changelog for 635rc11, yet ?
it is on the download page:
What's new in 6.35rc11 (2016-Feb-17 09:09):

*) winbox - added factory-firmware field to system/routerboard;
*) l2tp - ipsec peer & policy sometimes was not removed after l2tp interface disable;
*) pptp - fixed kernel crash when receiving fragmented packet with fragmented header;
*) www - fixed www crash;
*) winbox - fixed email address saving;
For others with wireless band issues -
1) make sure that you are running wireless-rep package;
2) check CLI - features comes to Winbox later that CLI.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Feb 18, 2016 8:22 am
by strods
Version 6.35rc11 has been released yesterday.

Changes since previous version:
*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=104395);
*) winbox - added factory-firmware field to system/routerboard;
*) l2tp - ipsec peer & policy sometimes was not removed after l2tp interface disable;
*) pptp - fixed kernel crash when receiving fragmented packet with fragmented header;
*) www - fixed www crash;
*) winbox - fixed email address saving.

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Feb 18, 2016 11:49 am
by Morpheus1607
*) queue - added bucket-size setting to queues (derived from max-limit);
*) queue - improve "/queue interface" menu;

What does it mean???


I had updated a test device, but it uses no queues. What is the difference to older versions?

i see on the queue interface all interfaces/bridges get an "no-queue"

any information about that?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Feb 18, 2016 2:12 pm
by easyspot
I think its better to have bucket-size value in kb, just like in squid delay pool.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Feb 18, 2016 3:33 pm
by macgaiver
It is radio to max-limit (0,1 is 10%)

HTB (Hierarchical Token Bucket) is finally getting custom size buckets :)
https://en.wikipedia.org/wiki/Token_bucket

basically this option can eliminate any need for bursts options, and allow much more neat hierarchical structures.
I do not understand how it will work if bucket size is 0 :).

Simple burst behavior can be achieved by use values more that 1. For example if you set bucket-size=4 max-limit=10M - first 40Mb will cross the queue with virtually unlimited speed.

I plan to use this analogy when explainig it in future:
05-animal-driven-waterwheels-are-known-in-murcia-as-norias-de-sangre.jpg
bucket size determines amount of delivered water ( traffic) per take, you cannot control the amount of water in the bucket (it always come full), but you can control number of buckets per second, bigger buckets = smaller number of buckets per second = more burstness of the traffic (and i would imagine less load on CPU)

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Feb 18, 2016 11:40 pm
by BartoszP
No way to upgrade 741TC from 6.35rc8 to 6.35.rc11 because of "low memory"
741TC.PNG

v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Feb 18, 2016 11:48 pm
by darkprocess
Edit the queue on this interface. I had the issue with my openvpn connections

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 2:26 am
by PeterDoBrasil
is any decription/changelog for 635rc11, yet ?
it is on the download page:
What's new in 6.35rc11 (2016-Feb-17 09:09):

*) winbox - added factory-firmware field to system/routerboard;
*) l2tp - ipsec peer & policy sometimes was not removed after l2tp interface disable;
*) pptp - fixed kernel crash when receiving fragmented packet with fragmented header;
*) www - fixed www crash;
*) winbox - fixed email address saving;
For others with wireless band issues -
1) make sure that you are running wireless-rep package;
2) check CLI - features comes to Winbox later that CLI.
! No band g/n Option !!!
1.png
2.png
3.png

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 8:17 am
by strods
BartoszP - Upgrade in this device happens within RAM memory;
PeterDoBrasil - For now it is available only through CLI.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 10:56 am
by jarda
BartoszP - Upgrade in this device happens within RAM memory

You must be kidding.



Bartoszp, install system package only, reboot. You will get space and then install only additional packages you need in second stage. After that you will have enough space for future updates. At least so far...

The lacking of ram and flash capacity in new models is awful.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 11:16 am
by hedele
Is RAM upgrade maybe also coming to CCR devices?
The reason I'm asking is that for some reason, RouterOS for tile is HUGE when installed (46 MiB used out of 128 MiB on a CCR1016-12S-1S+), which makes using partitions almost impossible now (barely enough space to perform upgrade when using 2 partitions at 64 MiB each). CCRs have plenty of RAM, but it can't be used for upgrades. Why is installed size on CCRs so large? The .npk is smaller than the powerpc version, but when installed ROS is twice the size!

For that reason I am currently not using partitions on CCR1016s even though I would like to, because i am afraid that with future ROS versions, install/package size will grow even more until I finally run out of space :( If you compare, ROS 6.1 npk for tile had around 14,2 MiB size, ROS 6.32.4 already has 16,5 MiB, and with more and more features being added, the size will probably not get any smaller in the future.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 11:29 am
by strods
It is explained here:
http://wiki.mikrotik.com/wiki/Manual:System/File
Warning: If device has a directory named "flash" in its file list, then files which you want to be kept after system reboot/power cycle must be stored within it. As anything outside of it is kept within a RAM disk and will be lost upon reboot. Note: this does not include .npk upgrade files as they will be applied by upgrade process before system discards the RAM drive content.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 1:21 pm
by Cha0s
He is not kidding. Upgrade happens in RAM, and it does not matter how much storage you have. Upload goes directly into RAMDRIVE. Please stop spreading misinformation about uploading only one package, this just breaks things
Kidding or not, misinformation or not, your suggested method has not worked for me.
While jarda's worked just fine.

So is it misinformation when your method is not working properly?

The bottom line is that using jarda's method I did my job. So fix your software if you don't want 'misinformation' going around.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 1:22 pm
by strods
Most likely you just rebooted device which erased RAM memory and after reboot you had enough space for upgrade.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 1:23 pm
by strods

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 1:49 pm
by Cha0s
Most likely you just rebooted device which erased RAM memory and after reboot you had enough space for upgrade.
http://forum.mikrotik.com/viewtopic.php ... 43#p519443
The device on that screenshot was just rebooted. Since it's with an rc version it was used for testing and not in production.
Thus no ram was used since no special config was done on the device.

So, since I've been doing it wrong for the last 10 years using Mikrotik, what should have been the proper way to upgrade the hAP without resorting to not using the combined package as Jarda suggested (and worked right away) ?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 2:58 pm
by strods
Again - Warning: If device has a directory named "flash"...
Upgrade happens like this only with devices which has flash memory. I guess we have such devices for about a year now.

Do you have actual screen shot where you could see that free RAM memory > necessary memory for upgrade?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 3:00 pm
by Cha0s
No but I know that the free memory was ~11mbyte.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 3:03 pm
by Cha0s
Again - Warning: If device has a directory named "flash"...
Yeah, what about it?
I don't want to store files. I want to upgrade. From what you are saying upgrades happen in RAM. So what does it matter weather there is a flash folder or not?

In general SMIPS is a disaster in terms of usability.
It forces us to use Winbox 3 which is super buggy and it cannot upgrade like every other device model you make...

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 3:18 pm
by PeterDoBrasil
BartoszP - Upgrade in this device happens within RAM memory;
PeterDoBrasil - For now it is available only through CLI.
What means CLI??? I don't understand what is CLI????

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 3:20 pm
by normis
BartoszP - Upgrade in this device happens within RAM memory;
PeterDoBrasil - For now it is available only through CLI.
What means CLI??? I don't understand what is CLI????
CLI means "Command line Interface", when you connect with SSH for example

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 3:23 pm
by strods
Cha0s - About upgrade - my mistake. Every device which has flash memory (except SMIPS) performs upgrade within RAM memory. hAP lite has flash storage but does not have flash folder so upgrade happens within flash directory. Sorry about that. Upgrade bundle + other package is not possible because there is not enough space for it. .

If you have other SMIPS and Winbox related issues, then please report to support@mikrotik.com. We are not aware about still existing issues with SMIPS or Winbox which would break workflow.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 3:25 pm
by jarda
strods and normis,
sorry I made you angry. You have my full respect and I am very gratefull to you for what you are doing.

But this situation is a bit different. You have seen a picture where was clearly visible that BartoszP pressed "download" or "download and install" button in system-packages after checking for update. The response was that there is not enough space for it. Instead of providing him a working solution you stated that update is made in memory. How it is heplful when on my 941s is normally 4-6MB of free ram? His devices run similarly probably.

I would not suggest to him any procedure that I had not tested before. I did not wanted to make such tests at all, but your approach forced me to do so, because I am having the same problems as BartoszP so I have developed a way ho to perform the update even there is not enough space for it... My way works, your statements are for nothing. Yes, finally everyone can make netinstall, but why, if there is a workable workaround?

If you think my suggestions just breaks things, you shoul also explain what things and how will be broken. I have not realised anything like this.

And what is the root cause? I can tell you.

Firstly, it is your decision to make new devices with just 32MB of RAM although I (and others) are telling you that it is too small amount of memory. And besides that, you decided to provide almost any flash memory. OK, I know, 16MB in this case, but not usable to store the packages to be installed, as the running ros is already installed there.

Secondly it is your decision to ship the devices with preinstalled bundled set of packages, many of them disabled, not necessary for "ordinary home users", but just occupying space on flash. More over that, if automatcially updated, these useless packages have to be downloaded and stored to be updated too. You know I was asking you long time ago not to ship devices with one bundled package but with "individually" preinstalled packages so the user could be able to fully remove the ones he does not need. It would free the flash and also the next updates will be smaller so they probably could fit in ram/flash to be updated automatically. It is still not clear for me why are you doing this.

You surely remember why you had to remove the winbox dll file from smips ros and therefore needed to release winbox v.3. I am very curious how you will ensure update operation within ros7. I am expecting the ros7 will be again a bit bigger to store... Maybe it will force you to admit that I was right by doing the things I have suggested to you long time ago and this time again.

Cha0s,
thank you confirming my statements. Obviously you have the same experience.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 3:32 pm
by normis
Looks like you posted before Strods made the post before yours.

So in the end, if you want to use bundle, use bundle. If you want something special, don't use bundle, but install all packages one by one.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 3:37 pm
by strods
Version 6.35rc12 has been released.

Changes since previous version:
*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=104395);
*) pppoe-client - implemented fastpath support;
*) ssl - optimized certificate update;
*) ospf - fixed crash when getting neighbor router-id in NBMA area;
*) romon-ssh - fixed active addresses for romon user;
*) email - fix send cmd server addr override.

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 3:38 pm
by strods
jarda - Sorry. this time it was my mistake. Often also we forget that hAP lite does not have flash folder. I guess I can blame Friday :)

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 3:53 pm
by macgaiver
Wait! What??
*) pppoe-client - implemented fastpath support;
MT you need to stop destroying my weekends, now i need to test this.... :)

I love versions before the big MUM events - all good stuff is coming out.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 4:35 pm
by PeterDoBrasil
BartoszP - Upgrade in this device happens within RAM memory;
PeterDoBrasil - For now it is available only through CLI.
What means CLI??? I don't understand what is CLI????
CLI means "Command line Interface", when you connect with SSH for example
Hey Normis, Is this an Hotspot Bug ????
http://forum.mikrotik.com/viewtopic.php?f=2&t=105022 :(

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 4:38 pm
by BartoszP
... You have seen a picture where was clearly visible that BartoszP pressed "download" or "download and install" button in system-packages after checking for update. The response was that there is not enough space for it............
Firstly, it is your decision to make new devices with just 32MB of RAM although I (and others) are telling you that it is too small amount of memory. And besides that, you decided to provide almost any flash memory. OK, I know, 16MB in this case, but not usable to store the packages to be installed, as the running ros is already installed there.
A. Restart helped ... inmemory upgrade have made my RB741 @ rc11 ... why not to put "inmemory upgrade in progress" instead of "too low space" ?
B. What about situation when my address lists, rules lists will be too big in total for downloading package to make inmemory upgrade ?
C. 16MB flash as a disk is ... TOO SMALL ... what about importing scripts, making backups before upgrade etc. ?
D. "My new preciousssss" ... hAP AC has only 16MB too .... it is strange for such powerfull device ... how to make it main router ?
962.PNG

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 5:45 pm
by strods
BartoszP - Previously it was my mistake. We have many devices which uses flash memory. They all can be divided in two groups - smips devices and other devices. hAP lite is smips device and performs upgrade within flash memory (this I messed up previously). Other devices which has flash memory but are not smips devices are upgraded by using RAM memory.

smips platform is called like that for a reason, It is most simple platform which we have and should be used for simple home configurations. In such cases memory should be used basically only for export files.

As it goes for hAP ac and other devices which are not smips devices but has flash memory - they still are simple home routers. There is plenty space for backup, some other things and, if you need something more, then there is a USB port on which you can attach any USB drive and use as a storage device.

If you have other questions, then please turn to support. This is still 6.35rc topic and problems related to this particular version should be discussed here :)

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 19, 2016 6:29 pm
by zinkpad
Yeah, pppoe-client fastpath support!!! :D :D

Now I can reach 306Mbps download speed (http://www.speedtest.net), and CPU is 34%-40% (on 6.34.2 was 85%), tested on RB951G / Movistar / Spain.

Image

Thanks MikroTik, great job!!

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sat Feb 20, 2016 8:13 am
by milenabraham8
Which one is the latest? I need a latest router. Please reply

Posted: Sat Feb 20, 2016 8:45 am
by jarda
What does it mean - latest router? And why do you need it? Without any information I cannot suggest to you other version than 6.32.3. Even though the 6.32.4 is out already for some time I have not tested it enough yet and I have no need to change the production version so far.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sun Feb 21, 2016 1:53 am
by Sob
It means one point for spammer and zero for jarda, better luck next time. ;)

I don't know if the signature was there before you replied or if it was added later, but it's quite obvious with it. User's first post, does not make much sense, but they made sure they added the signature with link to some commercial activity.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sun Feb 21, 2016 3:55 am
by shifto
Yeah, pppoe-client fastpath support!!! :D :D

Now I can reach 306Mbps download speed (http://www.speedtest.net), and CPU is 34%-40% (on 6.34.2 was 85%), tested on RB951G / Movistar / Spain.

Image

Thanks MikroTik, great job!!
Yes, nice feature indeed. :)

Image

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sun Feb 21, 2016 8:42 am
by jarda
It means one point for spammer and zero for jarda, better luck next time. ;)

I don't know if the signature was there before you replied or if it was added later, but it's quite obvious with it. User's first post, does not make much sense, but they made sure they added the signature with link to some commercial activity.
There is no signature displayed in tapatalk. I am not aware about it.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sun Feb 21, 2016 2:55 pm
by PeterDoBrasil
BartoszP - Upgrade in this device happens within RAM memory;
PeterDoBrasil - For now it is available only through CLI.
What means CLI??? I don't understand what is CLI????
CLI means "Command line Interface", when you connect with SSH for example

Hello Normis! Can You Help me Here?
http://forum.mikrotik.com/viewtopic.php?f=1&t=104879

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Feb 22, 2016 12:23 pm
by notToNew
Tested the repeater-mode on hap-ac lite: it works with win10-laptop, with android-phones,but not with winXP-Wifi.
This simply doesn't get an IP.

11:20:31 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: connected
11:20:31 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: reassociating
11:20:31 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: disconnected, ok
11:20:31 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: connected
11:20:31 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: reassociating
11:20:31 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: disconnected, ok
11:20:31 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: connected
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: reassociating
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: disconnected, ok
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: connected
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: reassociating
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: disconnected, ok
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: connected
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: reassociating
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: disconnected, ok
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: connected
11:20:32 wireless,info 00:0E:35:D6:11:EF@wlan1_ap2: disconnected, received deauth: unspecified (1)

When configuring an non-virtual AP in Mikrotik, the XP-Laptop (with Intel-Hardware) can connect as expected.

Do i miss anything?

--> I love the new feature, it helps me a lot

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Feb 22, 2016 2:31 pm
by strods
notToNew

Please execute this command on your device:
"/system logging add topics=wireless,debug"

After that try to connect again. If logs do not show you error right away, then generate supout file and send it to support@mikrotik.com for checking.

Here you can see how to generate supout file:
http://wiki.mikrotik.com/wiki/Manual:Su ... utput_File

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Tue Feb 23, 2016 9:36 pm
by picacho99
About this nice feature "*) pppoe-client - implemented fastpath support;"

Is the RB3011 RouterOS specific version really supporting fastpath ?
Why this question:
- It not appears listed as supported in the WIKI page on fatspath.
- My testing after applying the firewall rules and having the counter growing...does not seem to provide any CPU saving on RB3011.

Please, Mikrotik, may you clarify this: today, an RB3011 dowloading one TCP stream at 300 Mbits over PPP and having NAT and a basic configuration of firewall rules needs 80% of one CPU to handle this trafic with spikes up to 90% at 1400 mhz frequency...

This device is starting to remember me the buggy RB850x2: lower performance than anticipated, strange problems (software bridge problems,...), features not working (partition not working,...), hardware revisions (I hope this not again, please)...

It would be "funny" to have to go back to an RB2011: starting to become tired to be patient with MIkrotik...RB3011 is not a 100$ device.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Tue Feb 23, 2016 9:50 pm
by picacho99
And when you plan to fix this "dirty" SNTP behaviour in RB3011 ?

605 Feb/23/2016 15:45:19 memory system, info sntp change time Feb/23/2016 15:45:16 => Feb/23/2016 15:45:19
606 Feb/23/2016 15:47:30 memory system, info sntp change time Feb/23/2016 15:47:27 => Feb/23/2016 15:47:30
607 Feb/23/2016 15:48:19 memory system, info sntp change time Feb/23/2016 15:48:18 => Feb/23/2016 15:48:19
608 Feb/23/2016 15:49:25 memory system, info sntp change time Feb/23/2016 15:49:23 => Feb/23/2016 15:49:25
609 Feb/23/2016 15:56:14 memory system, info sntp change time Feb/23/2016 15:56:05 => Feb/23/2016 15:56:14
610 Feb/23/2016 15:57:20 memory system, info sntp change time Feb/23/2016 15:57:18 => Feb/23/2016 15:57:20
611 Feb/23/2016 15:58:25 memory system, info sntp change time Feb/23/2016 15:58:24 => Feb/23/2016 15:58:25
612 Feb/23/2016 16:00:36 memory system, info sntp change time Feb/23/2016 16:00:33 => Feb/23/2016 16:00:36
613 Feb/23/2016 16:01:42 memory system, info sntp change time Feb/23/2016 16:01:40 => Feb/23/2016 16:01:42
614 Feb/23/2016 16:04:26 memory system, info sntp change time Feb/23/2016 16:04:22 => Feb/23/2016 16:04:26
615 Feb/23/2016 16:05:15 memory system, info sntp change time Feb/23/2016 16:05:14 => Feb/23/2016 16:05:15
616 Feb/23/2016 16:06:20 memory system, info sntp change time Feb/23/2016 16:06:19 => Feb/23/2016 16:06:20
617 Feb/23/2016 16:08:31 memory system, info sntp change time Feb/23/2016 16:08:28 => Feb/23/2016 16:08:31
618 Feb/23/2016 16:12:53 memory system, info sntp change time Feb/23/2016 16:12:47 => Feb/23/2016 16:12:53
619 Feb/23/2016 16:37:15 memory system, info sntp change time Feb/23/2016 16:36:41 => Feb/23/2016 16:37:15
620 Feb/23/2016 16:38:20 memory system, info sntp change time Feb/23/2016 16:38:19 => Feb/23/2016 16:38:20
621 Feb/23/2016 16:40:31 memory system, info sntp change time Feb/23/2016 16:40:28 => Feb/23/2016 16:40:31
622 Feb/23/2016 16:42:42 memory system, info sntp change time Feb/23/2016 16:42:39 => Feb/23/2016 16:42:42
623 Feb/23/2016 16:44:53 memory system, info sntp change time Feb/23/2016 16:44:50 => Feb/23/2016 16:44:53
624 Feb/23/2016 16:45:43 memory system, info sntp change time Feb/23/2016 16:45:41 => Feb/23/2016 16:45:43
625 Feb/23/2016 16:49:15 memory system, info sntp change time Feb/23/2016 16:49:11 => Feb/23/2016 16:49:15
626 Feb/23/2016 16:50:21 memory system, info sntp change time Feb/23/2016 16:50:19 => Feb/23/2016 16:50:21
627 Feb/23/2016 16:53:37 memory system, info sntp change time Feb/23/2016 16:53:33 => Feb/23/2016 16:53:37
628 Feb/23/2016 16:54:27 memory system, info sntp change time Feb/23/2016 16:54:25 => Feb/23/2016 16:54:27
629 Feb/23/2016 16:55:32 memory system, info sntp change time Feb/23/2016 16:55:31 => Feb/23/2016 16:55:32
630 Feb/23/2016 16:57:43 memory system, info sntp change time Feb/23/2016 16:57:40 => Feb/23/2016 16:57:43
631 Feb/23/2016 17:11:06 memory system, info sntp change time Feb/23/2016 17:10:47 => Feb/23/2016 17:11:06
632 Feb/23/2016 17:11:55 memory system, info sntp change time Feb/23/2016 17:11:54 => Feb/23/2016 17:11:55
633 Feb/23/2016 17:13:00 memory system, info sntp change time Feb/23/2016 17:12:59 => Feb/23/2016 17:13:00
634 Feb/23/2016 17:15:11 memory system, info sntp change time Feb/23/2016 17:15:08 => Feb/23/2016 17:15:11
635 Feb/23/2016 17:19:21 memory dhcp, info dhcpNoSecure assigned 192.168.60.247 to XXXXXX
636 Feb/23/2016 17:19:33 memory system, info sntp change time Feb/23/2016 17:19:27 => Feb/23/2016 17:19:33
637 Feb/23/2016 17:43:55 memory system, info sntp change time Feb/23/2016 17:43:21 => Feb/23/2016 17:43:55
638 Feb/23/2016 17:45:00 memory system, info sntp change time Feb/23/2016 17:44:59 => Feb/23/2016 17:45:00
639 Feb/23/2016 17:45:50 memory system, info sntp change time Feb/23/2016 17:45:48 => Feb/23/2016 17:45:50
640 Feb/23/2016 17:49:55 memory system, info sntp change time Feb/23/2016 17:49:50 => Feb/23/2016 17:49:55
641 Feb/23/2016 17:51:01 memory system, info sntp change time Feb/23/2016 17:50:59 => Feb/23/2016 17:51:01
642 Feb/23/2016 17:51:50 memory system, info sntp change time Feb/23/2016 17:51:49 => Feb/23/2016 17:51:50
643 Feb/23/2016 17:55:23 memory system, info sntp change time Feb/23/2016 17:55:18 => Feb/23/2016 17:55:23
644 Feb/23/2016 17:58:07 memory system, info sntp change time Feb/23/2016 17:58:03 => Feb/23/2016 17:58:07
645 Feb/23/2016 18:01:23 memory system, info sntp change time Feb/23/2016 18:01:19 => Feb/23/2016 18:01:23
646 Feb/23/2016 18:04:40 memory system, info sntp change time Feb/23/2016 18:04:35 => Feb/23/2016 18:04:40
647 Feb/23/2016 18:05:29 memory system, info sntp change time Feb/23/2016 18:05:28 => Feb/23/2016 18:05:29
648 Feb/23/2016 18:06:34 memory system, info sntp change time Feb/23/2016 18:06:33 => Feb/23/2016 18:06:34
649 Feb/23/2016 18:08:45 memory system, info sntp change time Feb/23/2016 18:08:42 => Feb/23/2016 18:08:45
650 Feb/23/2016 18:22:40 memory system, info sntp change time Feb/23/2016 18:22:21 => Feb/23/2016 18:22:40
651 Feb/23/2016 18:24:51 memory system, info sntp change time Feb/23/2016 18:24:48 => Feb/23/2016 18:24:51
652 Feb/23/2016 18:25:57 memory system, info sntp change time Feb/23/2016 18:25:55 => Feb/23/2016 18:25:57
653 Feb/23/2016 18:30:19 memory system, info sntp change time Feb/23/2016 18:30:13 => Feb/23/2016 18:30:19
654 Feb/23/2016 18:31:08 memory system, info sntp change time Feb/23/2016 18:31:07 => Feb/23/2016 18:31:08
655 Feb/23/2016 18:35:14 memory system, info sntp change time Feb/23/2016 18:35:08 => Feb/23/2016 18:35:14
656 Feb/23/2016 18:36:03 memory system, info sntp change time Feb/23/2016 18:36:02 => Feb/23/2016 18:36:03
657 Feb/23/2016 18:37:08 memory system, info sntp change time Feb/23/2016 18:37:07 => Feb/23/2016 18:37:08
658 Feb/23/2016 18:43:58 memory system, info sntp change time Feb/23/2016 18:43:48 => Feb/23/2016 18:43:58
659 Feb/23/2016 18:44:47 memory system, info sntp change time Feb/23/2016 18:44:46 => Feb/23/2016 18:44:47
660 Feb/23/2016 18:45:52 memory system, info sntp change time Feb/23/2016 18:45:51 => Feb/23/2016 18:45:52
661 Feb/23/2016 18:48:03 memory system, info sntp change time Feb/23/2016 18:48:00 => Feb/23/2016 18:48:03
662 Feb/23/2016 18:52:25 memory system, info sntp change time Feb/23/2016 18:52:19 => Feb/23/2016 18:52:25
663 Feb/23/2016 19:01:09 memory system, info sntp change time Feb/23/2016 19:00:57 => Feb/23/2016 19:01:09
664 Feb/23/2016 19:16:31 memory system, info sntp change time Feb/23/2016 19:16:09 => Feb/23/2016 19:16:31
665 Feb/23/2016 19:31:52 memory system, info sntp change time Feb/23/2016 19:31:31 => Feb/23/2016 19:31:52
666 Feb/23/2016 19:47:13 memory system, info sntp change time Feb/23/2016 19:46:52 => Feb/23/2016 19:47:13
667 Feb/23/2016 20:02:00 memory dhcp, info dhcpNoSecure assigned 192.168.60.240 to uuuuuuuuuuu
668 Feb/23/2016 20:19:17 memory system, info sntp change time Feb/23/2016 20:18:33 => Feb/23/2016 20:19:17
669 Feb/23/2016 20:20:07 memory system, info sntp change time Feb/23/2016 20:20:05 => Feb/23/2016 20:20:07
670 Feb/23/2016 20:21:12 memory system, info sntp change time Feb/23/2016 20:21:11 => Feb/23/2016 20:21:12
671 Feb/23/2016 20:25:43 memory dhcp, info dhcpNoSecure assigned 192.168.60.252 to HHHHHHHH
672 Feb/23/2016 20:28:02 memory system, info sntp change time Feb/23/2016 20:27:52 => Feb/23/2016 20:28:02
673 Feb/23/2016 20:28:51 memory system, info sntp change time Feb/23/2016 20:28:50 => Feb/23/2016 20:28:51
674 Feb/23/2016 20:29:56 memory system, info sntp change time Feb/23/2016 20:29:55 => Feb/23/2016 20:29:56
675 Feb/23/2016 20:36:46 memory system, info sntp change time Feb/23/2016 20:36:36 => Feb/23/2016 20:36:46
676 Feb/23/2016 20:39:29 memory system, info sntp change time Feb/23/2016 20:39:26 => Feb/23/2016 20:39:29
677 Feb/23/2016 20:40:18 memory system, info sntp change time Feb/23/2016 20:40:17 => Feb/23/2016 20:40:18
678 Feb/23/2016 20:41:24 memory system, info sntp change time Feb/23/2016 20:41:22 => Feb/23/2016 20:41:24

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Feb 24, 2016 4:34 am
by ofca
strods,

is there any hope for a minor change to LCD, adding a screen that only displays a logo from branding package or some custom png and nothing else?
More details and some discussion here, http://forum.mikrotik.com/viewtopic.php?f=3&t=104820

I'd be grateful and happy. ;)

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Feb 24, 2016 7:54 am
by jarda
About this nice feature "*) pppoe-client - implemented fastpath support;"

Is the RB3011 RouterOS specific version really supporting fastpath ?
Why this question:
- It not appears listed as supported in the WIKI page on fatspath.
- My testing after applying the firewall rules and having the counter growing...does not seem to provide any CPU saving on RB3011.

Please, Mikrotik, may you clarify this: today, an RB3011 dowloading one TCP stream at 300 Mbits over PPP and having NAT and a basic configuration of firewall rules needs 80% of one CPU to handle this trafic with spikes up to 90% at 1400 mhz frequency...

This device is starting to remember me the buggy RB850x2: lower performance than anticipated, strange problems (software bridge problems,...), features not working (partition not working,...), hardware revisions (I hope this not again, please)...

It would be "funny" to have to go back to an RB2011: starting to become tired to be patient with MIkrotik...RB3011 is not a 100$ device.
Are you really expecting fastpath when firewall rules are implemented?

Try fasttrack in this case.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Feb 24, 2016 2:57 pm
by picacho99
About this nice feature "*) pppoe-client - implemented fastpath support;"

Is the RB3011 RouterOS specific version really supporting fastpath ?
Why this question:
- It not appears listed as supported in the WIKI page on fatspath.
- My testing after applying the firewall rules and having the counter growing...does not seem to provide any CPU saving on RB3011.

Please, Mikrotik, may you clarify this: today, an RB3011 dowloading one TCP stream at 300 Mbits over PPP and having NAT and a basic configuration of firewall rules needs 80% of one CPU to handle this trafic with spikes up to 90% at 1400 mhz frequency...

This device is starting to remember me the buggy RB850x2: lower performance than anticipated, strange problems (software bridge problems,...), features not working (partition not working,...), hardware revisions (I hope this not again, please)...

It would be "funny" to have to go back to an RB2011: starting to become tired to be patient with MIkrotik...RB3011 is not a 100$ device.
Are you really expecting fastpath when firewall rules are implemented?

Try fasttrack in this case.
No, but please, be smart too....before trying to teach please learn to read....and use fair-play...please, perhaps,...

What can provide fastrack if trafic over a pure software based not optimized ppoe client implementation?

This combination of both works like a charm in two tested mono-CPU devices....shared by other contributors in this same topic and configuration.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 26, 2016 8:22 pm
by picacho99
About this nice feature "*) pppoe-client - implemented fastpath support;"

Is the RB3011 RouterOS specific version really supporting fastpath ?
Why this question:
- It not appears listed as supported in the WIKI page on fatspath.
- My testing after applying the firewall rules and having the counter growing...does not seem to provide any CPU saving on RB3011.

Please, Mikrotik, may you clarify this: today, an RB3011 dowloading one TCP stream at 300 Mbits over PPP and having NAT and a basic configuration of firewall rules needs 80% of one CPU to handle this trafic with spikes up to 90% at 1400 mhz frequency...

This device is starting to remember me the buggy RB850x2: lower performance than anticipated, strange problems (software bridge problems,...), features not working (partition not working,...), hardware revisions (I hope this not again, please)...

It would be "funny" to have to go back to an RB2011: starting to become tired to be patient with MIkrotik...RB3011 is not a 100$ device.
Are you really expecting fastpath when firewall rules are implemented?

Try fasttrack in this case.
No, but please, be smart too....before trying to teach please learn to read....and use fair-play...please, perhaps,...

What can provide fastrack if trafic over a pure software based not optimized ppoe client implementation?

This combination of both works like a charm in two tested mono-CPU devices....shared by other contributors in this same topic and configuration.

Ooppss *) pppoe-client - implemented fastpath support.... ????
it works over RB2011 but it does NOT works over RB3011.

Same fiber connection (300/30 Mbits) and RouterOS configuration testing RB2011 and RB3011, with these results:
- RB2011...6.34.2 - CPU usage 100% (298 Mits)
- RB2011...6.35rc12 - CPU usage between 32-38% (305 Mbits)
- RB3011...6.35rc11 and sooner - CPU usage TOTAL: 45%, ONE CPU 80-90%, the OTHER CPU 2-3% (305 Mbits)
- RB3011...6.35rc12 - CPU usage TOTAL: 45%, ONE CPU 80-90%, the OTHER CPU 2-3% (305 Mbits)

Symthom: FP RX counter for PPOE client conection is always zero in RB3011 (not for FP TX...)

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 26, 2016 8:32 pm
by LightnetBarry
*) l2tp - added support for proxy authentication when receiving forwarded PPPoE sesssions;
*) l2tp - added support for Hidden AVP, it is needed for proxy authentication;

I'm presuming this only means that LNS functionality is working and that I still cannot use Mikrotik as a LAC to do Proxy LCP to a Cisco PPPoE server?

Will I ever be able to???

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Feb 26, 2016 9:46 pm
by picacho99
tok, tok....

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sat Feb 27, 2016 11:49 pm
by jondavy
vlan not working on bridge interfaces

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sun Feb 28, 2016 4:24 am
by NGiannis
Hi,

I have two wireless stations where I want to use and share their connection as access point. I am using the first as the main and the second a backup.

I have used as below:
WLAN 1: Station 1
WLAN 2: AP
WLAN 3: Station 2
Untitled.png
When routing only WLAN 3 as station to WLAN 2 as access point on high loads over 50kbps I am facing interruptions.
Any idea?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sun Feb 28, 2016 1:24 pm
by jcsogo
Many many many thanks for implementing fastpath over pppoe. It is a highe improvement to be able to keep using (and recommending) your routers to those people with ISPs using PPPoE.

Kudos!

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sun Feb 28, 2016 9:10 pm
by milandraca
Background scan with NV2 protocol please! Are you work in the backround spectral scan? It would be a ubnt mouth shut!


Thanks for all the nice things!

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Feb 29, 2016 9:36 am
by strods
Version 6.35rc14 has been released.

Changes since previous version:

*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=104395);
*) pppoe-client - implemented fastpath support;
*) pppoe - added rfc4679 support;
*) pppoe-server - added pado-delay option;
*) ppp - close connection if peer wants to re-authenticate;
*) winbox - added missing modp8192 to /ipsec peer dh-group;
*) winbox - limit ospf key to 16 symbols;
*) snmp - fix cpu load reporting to 1min average and change oid to 1.3.6.1.4.1.2021.11.10.0;
*) mpls - do not reset VPLS on TE tunnel re-optimize;
*) lcd - add flip-screen option;
*) lcd - security screen did not show ip addresses on ccr;
*) interface queue - fixed "no-queue" on upgrade;
*) fastpath - fixed rare kernel failure;
*) lte - fixed bandlux modem dialing;
*) wireless-rep - fixed qos frame-priroty when nv2 protocol used in station-wds mode;
*) wireless - improved 1-chain 802.11ac station campability with other vendor multichain APs.


If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Feb 29, 2016 10:04 am
by nz_monkey
Nice work on all the new PPPoE features !

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Feb 29, 2016 11:28 am
by Siona
Voltage monitor on RB493G still not working.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 29, 2016 12:18 pm
by Lombart
Wow! This new wireless-rep is fantastic! All my UDP packets are consistent, I have not lost a single packet! Amazing work guys!
can you share config for wireless-rep ?

can someone post how to config wireless-rep step by step? i've been searching over here and google but can't find the answer

thx before

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Feb 29, 2016 12:44 pm
by WirelessRudy
Version 6.35rc14 has been released.
What happened with rc13?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Feb 29, 2016 1:12 pm
by strods
Any of rc versions can be skipped for multiple reasons. It could be bad, it could be waiting for additional fixes/implementation to work properly, next version can be built before we launch previous one. There are multiple possibilities and that do not mean anything at all.

Re: v6.35rc is released, new wireless package!

Posted: Mon Feb 29, 2016 6:21 pm
by Alessio Garavano
Wow! This new wireless-rep is fantastic! All my UDP packets are consistent, I have not lost a single packet! Amazing work guys!
can you share config for wireless-rep ?

can someone post how to config wireless-rep step by step? i've been searching over here and google but can't find the answer

thx before
yes! +1 for that!

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Tue Mar 01, 2016 12:41 am
by easyspot
Version 6.35rc14 has been released.
What happened with rc13?
Mikrotik crew believe in fengshui that said number 13 is bad so that's why they skip rc13 lol :lol:

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Tue Mar 01, 2016 8:31 am
by strods
Version 6.35rc15 has been released.

Changes since previous version:

*) l2tp - implemented l2tp (and lns) initial fastpath support;
*) ppp - fixed ppp crash;
*) gre - fixed memory leak;
*) netinstall - fixed link negotiation for different sfp modules;
*) snmp - fixed dhcpv4 lease hwaddr format according to mib;
*) rb3011 - fixed high cpu load breaks ethernet stats.

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Tue Mar 01, 2016 6:52 pm
by PeterDoBrasil
Version 6.35rc14 has been released.

Changes since previous version:

*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=104395);
*) pppoe-client - implemented fastpath support;
*) pppoe - added rfc4679 support;
*) pppoe-server - added pado-delay option;
*) ppp - close connection if peer wants to re-authenticate;
*) winbox - added missing modp8192 to /ipsec peer dh-group;
*) winbox - limit ospf key to 16 symbols;
*) snmp - fix cpu load reporting to 1min average and change oid to 1.3.6.1.4.1.2021.11.10.0;
*) mpls - do not reset VPLS on TE tunnel re-optimize;
*) lcd - add flip-screen option;
*) lcd - security screen did not show ip addresses on ccr;
*) interface queue - fixed "no-queue" on upgrade;
*) fastpath - fixed rare kernel failure;
*) lte - fixed bandlux modem dialing;
*) wireless-rep - fixed qos frame-priroty when nv2 protocol used in station-wds mode;
*) wireless - improved 1-chain 802.11ac station campability with other vendor multichain APs.


If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
Iám running v.14 on 4 devices, sxt, Rb2011,BaseBox, without any Problems!

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 02, 2016 1:41 pm
by nobodymb
HAP ac on Version 6.35rc15 l2tp/ipsec is not working on windows 7. On 6.34.2 everything is working fine with same settings

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 02, 2016 2:21 pm
by nkourtzis
HAP ac on Version 6.35rc15 l2tp/ipsec is not working on windows 7. On 6.34.2 everything is working fine with same settings
Same here, since 6.35rc14. PPtP not working either. "Encryption method not supported" even without encryption. Opened a support ticket with supout (Ticket#2016030266000632).

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 02, 2016 4:02 pm
by andersonlich
PPP fixed crash..?
Is that by mean on pppoe-server or pppoe-client?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 03, 2016 8:16 am
by strods
Version 6.35rc16 has been released.

Changes since previous version:
*) l2tp - implemented l2tp and lns fastpath support;
*) pppoe-client - implemented fastpath support;
*) ssh - fix crash on failed scp read;
*) chr - fixed layer7 firewall option/crash.

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 03, 2016 10:30 am
by DariusIII
HAP ac on Version 6.35rc15 l2tp/ipsec is not working on windows 7. On 6.34.2 everything is working fine with same settings
Same here, since 6.35rc14. PPtP not working either. "Encryption method not supported" even without encryption. Opened a support ticket with supout (Ticket#2016030266000632).
Even with latest RC this is still an issue.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 03, 2016 10:41 am
by strods
HAP ac on Version 6.35rc15 l2tp/ipsec is not working on windows 7. On 6.34.2 everything is working fine with same settings
Same here, since 6.35rc14. PPtP not working either. "Encryption method not supported" even without encryption. Opened a support ticket with supout (Ticket#2016030266000632).
Even with latest RC this is still an issue.
I see that message from support is sent to you and we have not received reply.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 03, 2016 5:34 pm
by nkourtzis
Same here, since 6.35rc14. PPtP not working either. "Encryption method not supported" even without encryption. Opened a support ticket with supout (Ticket#2016030266000632).
Even with latest RC this is still an issue.
I see that message from support is sent to you and we have not received reply.

Sorry, missed that. I tried what was suggested, same result. :-(

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Mar 04, 2016 6:08 am
by buckthis
Upgraded to 6.35rc16 (from rc14) on three devices as wireless was starting to act up (slow). Immediately I lost control of the cAPs as the interfaces started bouncing.
(1) - RB2011UiAS-2HnD-IN
(2) - RBcAP 2n

To recover...
I had to disable CAPsMAN interfaces to get control of the two cAPS.
Downgraded all gear to 6.35rc12, no change, wireless was still dead (CAPsMAN was not controlling the cAPs)
Restored configs on all three devices and BAM, everything was back to normal

* using wireless-rep in all version mentioned

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Mar 04, 2016 3:51 pm
by PeterDoBrasil
6.35rc16 my RB2011UiAS-2HnD-IN enabling CAPsMan and usuig the Routers wlan interface as Cap the router reboots every +- 2 minutes, crashes

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Mar 04, 2016 3:57 pm
by raffav
On RC16 if capsman is enable it make the cap to loop boot kernel error

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Mar 04, 2016 4:18 pm
by uldis
On RC16 if capsman is enable it make the cap to loop boot kernel error
This problem is fixed in the latest RouterOS v6.35rc19

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Mar 04, 2016 4:26 pm
by WirelessRudy
On RC16 if capsman is enable it make the cap to loop boot kernel error
This problem is fixed in the latest RouterOS v6.35rc19
rc16 ==> rc19??
Too many failures in between? :?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Mar 04, 2016 4:49 pm
by sergejs
6.35rc19 has been released!

What's new in 6.35rc19 (2016-Mar-04 11:46):

*) ppp - fixed ppp crash (make it work with Windows clients);
*) l2tp - implemented l2tp and lns fastpath/fasttrack support;
*) cerm - revoked certificates not showing as (R)evoked;
*) console - show RouterOS Version in /interface wireless scan;
*) export - bonding did not show up in global export;
*) export - fixed export when ipv6 address was taken from pool
*) fetch - decrease connection idle timeout;
*) ipsec - better flush on proposal change;
*) webfig - show single item groups as optional values;
*) webfig - sort numeric columns numerically even if they contain some text;
*) winbox - added /interface wireless setup-repeater;
*) winbox - added all the rates settings to the capsman;
*) winbox - added flip-screen option to lcd settings;
*) winbox - added missing eap-ttls-mschamv2 method to wireless security profile;
*) winbox - added support for new settings from wireless-rep package;
*) winbox - disable autostart for wireless scan,snooper,align etc. on open;
*) winbox - fixed typo in "echo reply";
*) wireless - fixed crash when ap is in cap mode (introduced in v6.35rc15);
*) pppoe-client - implemented fastpath support;

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Mar 04, 2016 5:52 pm
by raffav
Since the maybe(v34)

this code for sent backup via ftp dont work any more the script broke between the \tool fetch

if i copy the code and past on the terminal

i get the error point
[raffaello@RJ-AT-MK03 - CAP2] >
[raffaello@RJ-AT-MK03 - CAP2] >
[raffaello@RJ-AT-MK03 - CAP2] > /tool fetch address=$ip src-path="$[/system identity get name]_$datetimestring.backup" user=$user password=$pass port=$port upload=ye
s mode=ftp dst-path=($dir."$[/system identity get name]_$datetimestring.backup")
[raffaello@RJ-AT-MK03 - CAP2] > :log info "Sending Backup Mikrotik to FTP Server............."
[raffaello@RJ-AT-MK03 - CAP2] >
[raffaello@RJ-AT-MK03 - CAP2] > /tool fetch address=$ip src-path="$[/system identity get name]_$datetimestring.backup" user=$user password=$pass port=$port upload=ye
status: finished
downloaded: 38KiBg
total: 38KiB-z pause]
duration: 0s

[raffaello@RJ-AT-MK03 - CAP2] > dress=$ip src-path="$[/system identity get name]_$datetimestring.rsc" user=$user password=$pass port=$port upload=yes mode=ftp dst-path=($di
r."$[/system identity get name]_$datetimestring.rsc")


:global thisdate [/system clock get date]

:global datetimestring ([:pick $thisdate 0 3] ."-" . [:pick $thisdate 4 6] ."-" . [:pick $thisdate 7 11])

#IP DO SERVIDOR FTP
:global ip "1.1.1.1"
#SUBDIRETORIO NO SERVIDOR REMOTO FTP
:global dir "/RJ-AT-MK02/"
# PORTA DO FTP
:global port "21"
#USUARIO
:global user "backup"
#SENHA
:global pass "B@ckUp"
log info "Starting Automatic Backup Script Configure By Raffaello"

        

        /system backup save name="$[/system identity get name]_$datetimestring" 
 export file="$[/system identity get name]_$datetimestring" 
   
        :log info "Please wait...!!!"

        :delay 5s

        :log info "Sending Backup Mikrotik to FTP Server............."

        /tool fetch address=$ip src-path="$[/system identity get name]_$datetimestring.backup" user=$user password=$pass port=$port upload=yes mode=ftp dst-path=($dir."$[/system identity get name]_$datetimestring.backup")
       /tool fetch address=$ip  src-path="$[/system identity get name]_$datetimestring.rsc" user=$user password=$pass port=$port upload=yes mode=ftp dst-path=($dir."$[/system identity get name]_$datetimestring.rsc")
        

        :delay 1

        :log info "Finished Backup Script...!!!!"

       :delay 5s

:log info "Deleting backup just created after has sent"
/file remove "$[/system identity get name]_$datetimestring.backup"
/file remove "$[/system identity get name]_$datetimestring.rsc"


Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Mar 04, 2016 5:58 pm
by paoloaga
Too many failures in between? :?
What's the point? RC are for testing purposes and it's legit that they introduce bugs/problems and they have the right to build, test, publish, skip any release they want. You should only be happy that we have been given the opportunity to test while they develope so we can help them (and ourselves) having better stable releases.

With RouterOS configurations can be very complex and it's not possible to test every corner case.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Mar 04, 2016 7:57 pm
by MTusewk
What does the below change mean?

"snmp - fix cpu load reporting to 1min average and change oid to 1.3.6.1.4.1.2021.11.10.0;"

1). Does it mean it is replacing the old Total CPU Load OID 1.3.6.1.4.1.2021.11.52.0?
2). And that earlier it was reporting realtime CPU Load and now this new OID will report 1 min average CPU load?

Kindly please clarify.

Thanks.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sat Mar 05, 2016 12:06 am
by Bigfoot
Since the maybe(v34)

this code for sent backup via ftp dont work any more the script broke between the \tool fetch

if i copy the code and past on the terminal

i get the error point
[raffaello@RJ-AT-MK03 - CAP2] >
[raffaello@RJ-AT-MK03 - CAP2] >
[raffaello@RJ-AT-MK03 - CAP2] > /tool fetch address=$ip src-path="$[/system identity get name]_$datetimestring.backup" user=$user password=$pass port=$port upload=ye
s mode=ftp dst-path=($dir."$[/system identity get name]_$datetimestring.backup")
[raffaello@RJ-AT-MK03 - CAP2] > :log info "Sending Backup Mikrotik to FTP Server............."
[raffaello@RJ-AT-MK03 - CAP2] >
[raffaello@RJ-AT-MK03 - CAP2] > /tool fetch address=$ip src-path="$[/system identity get name]_$datetimestring.backup" user=$user password=$pass port=$port upload=ye
status: finished
downloaded: 38KiBg
total: 38KiB-z pause]
duration: 0s

[raffaello@RJ-AT-MK03 - CAP2] > dress=$ip src-path="$[/system identity get name]_$datetimestring.rsc" user=$user password=$pass port=$port upload=yes mode=ftp dst-path=($di
r."$[/system identity get name]_$datetimestring.rsc")


:global thisdate [/system clock get date]

:global datetimestring ([:pick $thisdate 0 3] ."-" . [:pick $thisdate 4 6] ."-" . [:pick $thisdate 7 11])

#IP DO SERVIDOR FTP
:global ip "1.1.1.1"
#SUBDIRETORIO NO SERVIDOR REMOTO FTP
:global dir "/RJ-AT-MK02/"
# PORTA DO FTP
:global port "21"
#USUARIO
:global user "backup"
#SENHA
:global pass "B@ckUp"
log info "Starting Automatic Backup Script Configure By Raffaello"

        

        /system backup save name="$[/system identity get name]_$datetimestring" 
 export file="$[/system identity get name]_$datetimestring" 
   
        :log info "Please wait...!!!"

        :delay 5s

        :log info "Sending Backup Mikrotik to FTP Server............."

        /tool fetch address=$ip src-path="$[/system identity get name]_$datetimestring.backup" user=$user password=$pass port=$port upload=yes mode=ftp dst-path=($dir."$[/system identity get name]_$datetimestring.backup")
       /tool fetch address=$ip  src-path="$[/system identity get name]_$datetimestring.rsc" user=$user password=$pass port=$port upload=yes mode=ftp dst-path=($dir."$[/system identity get name]_$datetimestring.rsc")
        

        :delay 1

        :log info "Finished Backup Script...!!!!"

       :delay 5s

:log info "Deleting backup just created after has sent"
/file remove "$[/system identity get name]_$datetimestring.backup"
/file remove "$[/system identity get name]_$datetimestring.rsc"

Hi raffav
I have been using this scrip from V5 and I have had no problem with it.
It looks like the tool fetch does not like your src-path and dst-path parameters.
# automated Um  backup  to External FTP
#File name:Um-FTP-Backup
# Get time
:local routeros [ /system package get number=0 value-name=version ]
:local thistime [/system clock get time]
:set thistime ([:pick $thistime 0 2].[:pick $thistime 3 5].[:pick $thistime 6 8])
# Get Date
:local thisdate [/system clock get date];
:local month
   :set month [:pick $thisdate 0 3]
   :if ($month="jan") do { :set month "01"}
   :if ($month="feb") do { :set month "02"}
   :if ($month="mar") do { :set month "03"}
   :if ($month="apr") do { :set month "04"}
   :if ($month="may") do { :set month "05"}
   :if ($month="jun") do { :set month "06"}
   :if ($month="jul") do { :set month "07"}
   :if ($month="aug") do { :set month "08"}
   :if ($month="sep") do { :set month "09"}
   :if ($month="oct") do { :set month "10"}
   :if ($month="nov") do { :set month "11"}
   :if ($month="dec") do { :set month "12"}

:set thisdate ([:pick $thisdate 7 11]."_".$month."_".[:pick $thisdate 4 6])
# This line to generate the file name for System backup - file name will be User_Manager- ServerName? - Date? - Time?
:local FName ("/User_Manager_".[/system identity get name]."_".$thisdate."_".$thistime."_".$routeros.".umb")

# This line to generate the file name for System backup - file name will be User_Manager- ServerName? - Date? - Time
:local FExport ("/BackUp_".[/system identity get name]."_".$thisdate."_".$thistime."_".$routeros.".rsc")

# This line to generate the file name for System backup - file name will be User_Manager- ServerName? - Date? - Time?
:local FBackup ("/BackUp_".[/system identity get name]."_".$thisdate."_".$thistime."_".$routeros.".backup")
:delay 5s;
/system backup save name=$FBackup;
:delay 5s;
/export file=$FExport
:delay 5s;
/tool user-manager database save name=$FName
:delay 5s;

:log info "Backup File's is Create - $FBackup";
:log info "Export File's is Create - $FExport";
:log info "UM Database Backup File is Create - $FName";
:delay 5s;
:log info "System Backup & Export File's is now been send to FTP Server";

# Upload the System Backup to External FTP - change address to your ftp server + user + pass+upload_path
/tool fetch address="192.168.0.105" user="mikrotik" password="mikrotik" mode=ftp src-path="$FExport" dst-path="/$FExport" upload=yes 
:delay 5s;
# Upload the System Backup to External FTP - change address to your ftp server + user + pass+upload_path
/tool fetch address="192.168.0.105" user="mikrotik" password="mikrotik" mode=ftp src-path="$FBackup" dst-path="/$FBackup" upload=yes
:delay 5s
# Upload the System Backup to External FTP - change address to your ftp server + user + pass+upload_path
/tool fetch address="192.168.0.105" user=mikrotik password=mikrotik mode=ftp src-path="$FName" dst-path="/$FName" upload=yes

:log info message="FTP Sending Backup & Export File's is Finish";
:delay 5s;
:foreach i in=[/file find] do={:if ([:typeof [:find [/file get $i name] "BackUp_"]]!="nil") do={/file remove $i}}
:log info message="SystemBackup & Export File's - Removed";

:foreach i in=[/file find] do={:if ([:typeof [:find [/file get $i name] "User_Manager_"]]!="nil") do={/file remove $i}}
:log info message="User-Manager Database Backup File's - Removed";

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sat Mar 05, 2016 4:12 am
by jondavy
please add to the roaming options
roaming-minimum-signal=XX
Roaming minimum-CCQ=XX
(To start the scanning process)

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sun Mar 06, 2016 3:10 am
by raffav
Since the maybe(v34)

this code for sent backup via ftp dont work any more the script broke between the \tool fetch

if i copy the code and past on the terminal

i get the error point
[raffaello@RJ-AT-MK03 - CAP2] >
[raffaello@RJ-AT-MK03 - CAP2] >
[raffaello@RJ-AT-MK03 - CAP2] > /tool fetch address=$ip src-path="$[/system identity get name]_$datetimestring.backup" user=$user password=$pass port=$port upload=ye
s mode=ftp dst-path=($dir."$[/system identity get name]_$datetimestring.backup")
[raffaello@RJ-AT-MK03 - CAP2] > :log info "Sending Backup Mikrotik to FTP Server............."
[raffaello@RJ-AT-MK03 - CAP2] >
[raffaello@RJ-AT-MK03 - CAP2] > /tool fetch address=$ip src-path="$[/system identity get name]_$datetimestring.backup" user=$user password=$pass port=$port upload=ye
status: finished
downloaded: 38KiBg
total: 38KiB-z pause]
duration: 0s

[raffaello@RJ-AT-MK03 - CAP2] > dress=$ip src-path="$[/system identity get name]_$datetimestring.rsc" user=$user password=$pass port=$port upload=yes mode=ftp dst-path=($di
r."$[/system identity get name]_$datetimestring.rsc")


:global thisdate [/system clock get date]

:global datetimestring ([:pick $thisdate 0 3] ."-" . [:pick $thisdate 4 6] ."-" . [:pick $thisdate 7 11])

#IP DO SERVIDOR FTP
:global ip "1.1.1.1"
#SUBDIRETORIO NO SERVIDOR REMOTO FTP
:global dir "/RJ-AT-MK02/"
# PORTA DO FTP
:global port "21"
#USUARIO
:global user "backup"
#SENHA
:global pass "B@ckUp"
log info "Starting Automatic Backup Script Configure By Raffaello"

        

        /system backup save name="$[/system identity get name]_$datetimestring" 
 export file="$[/system identity get name]_$datetimestring" 
   
        :log info "Please wait...!!!"

        :delay 5s

        :log info "Sending Backup Mikrotik to FTP Server............."

        /tool fetch address=$ip src-path="$[/system identity get name]_$datetimestring.backup" user=$user password=$pass port=$port upload=yes mode=ftp dst-path=($dir."$[/system identity get name]_$datetimestring.backup")
       /tool fetch address=$ip  src-path="$[/system identity get name]_$datetimestring.rsc" user=$user password=$pass port=$port upload=yes mode=ftp dst-path=($dir."$[/system identity get name]_$datetimestring.rsc")
        

        :delay 1

        :log info "Finished Backup Script...!!!!"

       :delay 5s

:log info "Deleting backup just created after has sent"
/file remove "$[/system identity get name]_$datetimestring.backup"
/file remove "$[/system identity get name]_$datetimestring.rsc"

Hi raffav
I have been using this scrip from V5 and I have had no problem with it.
It looks like the tool fetch does not like your src-path and dst-path parameters.
# automated Um  backup  to External FTP
#File name:Um-FTP-Backup
# Get time
:local routeros [ /system package get number=0 value-name=version ]
:local thistime [/system clock get time]
:set thistime ([:pick $thistime 0 2].[:pick $thistime 3 5].[:pick $thistime 6 8])
# Get Date
:local thisdate [/system clock get date];
:local month
   :set month [:pick $thisdate 0 3]
   :if ($month="jan") do { :set month "01"}
   :if ($month="feb") do { :set month "02"}
   :if ($month="mar") do { :set month "03"}
   :if ($month="apr") do { :set month "04"}
   :if ($month="may") do { :set month "05"}
   :if ($month="jun") do { :set month "06"}
   :if ($month="jul") do { :set month "07"}
   :if ($month="aug") do { :set month "08"}
   :if ($month="sep") do { :set month "09"}
   :if ($month="oct") do { :set month "10"}
   :if ($month="nov") do { :set month "11"}
   :if ($month="dec") do { :set month "12"}

:set thisdate ([:pick $thisdate 7 11]."_".$month."_".[:pick $thisdate 4 6])
# This line to generate the file name for System backup - file name will be User_Manager- ServerName? - Date? - Time?
:local FName ("/User_Manager_".[/system identity get name]."_".$thisdate."_".$thistime."_".$routeros.".umb")

# This line to generate the file name for System backup - file name will be User_Manager- ServerName? - Date? - Time
:local FExport ("/BackUp_".[/system identity get name]."_".$thisdate."_".$thistime."_".$routeros.".rsc")

# This line to generate the file name for System backup - file name will be User_Manager- ServerName? - Date? - Time?
:local FBackup ("/BackUp_".[/system identity get name]."_".$thisdate."_".$thistime."_".$routeros.".backup")
:delay 5s;
/system backup save name=$FBackup;
:delay 5s;
/export file=$FExport
:delay 5s;
/tool user-manager database save name=$FName
:delay 5s;

:log info "Backup File's is Create - $FBackup";
:log info "Export File's is Create - $FExport";
:log info "UM Database Backup File is Create - $FName";
:delay 5s;
:log info "System Backup & Export File's is now been send to FTP Server";

# Upload the System Backup to External FTP - change address to your ftp server + user + pass+upload_path
/tool fetch address="192.168.0.105" user="mikrotik" password="mikrotik" mode=ftp src-path="$FExport" dst-path="/$FExport" upload=yes 
:delay 5s;
# Upload the System Backup to External FTP - change address to your ftp server + user + pass+upload_path
/tool fetch address="192.168.0.105" user="mikrotik" password="mikrotik" mode=ftp src-path="$FBackup" dst-path="/$FBackup" upload=yes
:delay 5s
# Upload the System Backup to External FTP - change address to your ftp server + user + pass+upload_path
/tool fetch address="192.168.0.105" user=mikrotik password=mikrotik mode=ftp src-path="$FName" dst-path="/$FName" upload=yes

:log info message="FTP Sending Backup & Export File's is Finish";
:delay 5s;
:foreach i in=[/file find] do={:if ([:typeof [:find [/file get $i name] "BackUp_"]]!="nil") do={/file remove $i}}
:log info message="SystemBackup & Export File's - Removed";

:foreach i in=[/file find] do={:if ([:typeof [:find [/file get $i name] "User_Manager_"]]!="nil") do={/file remove $i}}
:log info message="User-Manager Database Backup File's - Removed";


Thanks
very very strange,
today i run my script again and it worked , no modification had been maded
the strange thing is that the version ROS is the same RC19

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Mar 07, 2016 3:33 pm
by janisk
What does the below change mean?

"snmp - fix cpu load reporting to 1min average and change oid to 1.3.6.1.4.1.2021.11.10.0;"

1). Does it mean it is replacing the old Total CPU Load OID 1.3.6.1.4.1.2021.11.52.0?
2). And that earlier it was reporting realtime CPU Load and now this new OID will report 1 min average CPU load?

Kindly please clarify.

Thanks.

1) yes it is replaceing that previous OID as this OID fits the description better for what has to be reported
2) SNMP is not into realtime load reporting as this OID and per core OID require to report 1 minute average load. (as required by RFC or in this case, draft document for the RFC. And following RFC is important so that you as user are not vendor-locked and can use tools that fit your requirements best)

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Mar 07, 2016 4:12 pm
by n21roadie
I don't understand why items listed as new in a RC version are listed again and again in newer RC version
example below is listed in several RC versions as new in this version?
*) pppoe-client - implemented fastpath support;

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Mar 07, 2016 4:25 pm
by sergejs
n21roadie, when the particular feature gets updated or fixed, changelog entry jumps to the top of change list.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Mar 07, 2016 5:03 pm
by Alessio Garavano
Too many failures in between? :?
What's the point? RC are for testing purposes and it's legit that they introduce bugs/problems and they have the right to build, test, publish, skip any release they want. You should only be happy that we have been given the opportunity to test while they develope so we can help them (and ourselves) having better stable releases.

With RouterOS configurations can be very complex and it's not possible to test every corner case.
Yes yes yes... To much stupid people in the forum only doing bad critics!

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Mar 07, 2016 8:41 pm
by sx10
6.35rc19 has been released!

What's new in 6.35rc19 (2016-Mar-04 11:46):

*) ppp - fixed ppp crash (make it work with Windows clients);
Do you have details on this PPP fix? I've had a mysterious random disconnect issue with windows VPNs since 6.30 or so.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Tue Mar 08, 2016 2:01 am
by scampbell
6.35rc19 has been released!
*) winbox - added /interface wireless setup-repeater;
Nice feature !!

When you use this setup repeater button it currently creates a new bridge (called bridge1) and adds WLAN1 plus the new Virtual WLAN into it.

Perhaps this could be modified to ask for a bridge to use (if one is present) or create new and specify name (e.g bridge-repeater) ?

It creates a wlan1-local (actual interface) and wlan1 (virtual interface). It would be nice to have the option to specify better names or perhaps have the virtual I/F called wlan-ap and the physical wlan-station ?

I see it uses station-pseudobridge mode to connect to the prinmary AP which is good if it is non-mikrotik. Does it check to see if it is connecting to a Mikrotik AP to see if it could use station-bridge instead or is this something you need to do manually. I note any Capsman controlled AP's dont yet support bridge mode ?

Good work though Mikrotik :-)

Bucket Size in HTB

Posted: Tue Mar 08, 2016 3:46 pm
by azfar
very good explanation sir. just add more information please.
i am planing to do a MuM presentation on HTB queue Tree and looking for useful and correct information.
i would really appreciate your help.
regards
Azfar Hameed Khan
Email: azfar.hameed.khan@gmail.com


It is radio to max-limit (0,1 is 10%)

HTB (Hierarchical Token Bucket) is finally getting custom size buckets :)
https://en.wikipedia.org/wiki/Token_bucket

basically this option can eliminate any need for bursts options, and allow much more neat hierarchical structures.
I do not understand how it will work if bucket size is 0 :).

Simple burst behavior can be achieved by use values more that 1. For example if you set bucket-size=4 max-limit=10M - first 40Mb will cross the queue with virtually unlimited speed.

I plan to use this analogy when explainig it in future:
05-animal-driven-waterwheels-are-known-in-murcia-as-norias-de-sangre.jpg
bucket size determines amount of delivered water ( traffic) per take, you cannot control the amount of water in the bucket (it always come full), but you can control number of buckets per second, bigger buckets = smaller number of buckets per second = more burstness of the traffic (and i would imagine less load on CPU)

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Tue Mar 08, 2016 6:05 pm
by Beone
Can you please add the 2ghz-g/n modus as well in the regular wireless-cm2 package?

We do not want to upgrade to wireless-rep in a production environment but are really needing the functionality to avoid B clients and B rates to massively teardown the wifi performance

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Tue Mar 08, 2016 11:22 pm
by yottabit
Running rc21 just now on rb962 (hAP ac). I started with a blank config and ended up in a boot loop:
  • Changed wlan1 (2 GHz) to station pseudobridge
  • Scanned
  • Chose a network
  • Clicked connect
  • Appeared to start connecting and then the router rebooted and got stuck in a boot loop.
I had to clear the config. After clearing, I tried again and the same thing happened.

Cleared again, and used it to successfully connect to a different network.

Without console access, how can I get a kernel panic message and/or kernel dump? What would you like to see?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 12:24 am
by yottabit
One suggestion for this release if at all possible, or the very next release: file manipulation in Webfig.

Per this topic from eight years ago, the only way to move files within RouterOS is by using Winbox or by FTP to locahost. I'm fine with that as I enjoy Winbox and use it very often.

However, now that you're reducing the flash capacity of some of these home-targeted devices to 16 MB, and the root file system is a ramdisk, users need an easy way to move files (like config backups) from the ramdisk to the flash/ subdirectory.

Presently this can only be done with Winbox or by using FTP to localhost. Basic and home users will not be using Winbox or FTP, so if there is any way to move the Winbox file dragging feature into Webfig that would be extremely appreciated.

(And hey, if there's a way to add more file manipulation to the CLI too, that would also be great. But Webfig would be the first priority since that's used by more basic users and is platform-agnostic.)

Thanks MikroTik! My order of 23 more rb962/"hAP ac" should arrive at my office tomorrow. :D

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 12:53 am
by Alessio Garavano
Hi MT Guys... what is the real advantage of the repeater mode over the WDS mode on same scenery... now i am testing the repeater mode in my home between 2 hAP and can´t see any difference from the prior WDS scenery.

Thanks!

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 1:04 am
by e4sy
Hi,
Would it be possible to increase the accepted upper limit of the RADIUS client timeout from 10000 ms to 45000-60000 ms ? It would help in implementing RADIUS based 2FA.

6.35rc21 - ugly - took down the whole network !!!

Posted: Wed Mar 09, 2016 2:15 am
by TomjNorthIdaho
Today 3/8/2016 I tested 6.35rc21 with the new wireless package on my DynaDish WDS client. That was a mistake.

This took down my network almost everywhere... The problem went through almost all of my other cisco switches and other networks...

My DynaDish was an 802.11 AC 80 MHz wide WDS link in client-Mode , - which was also passing vlan traffic. I could no longer talk to the either DynaDish over wireless or Ethernet.
It also took out the DynaDish WDS AP running 6.34.2 wireless-cm2 . To get back into the WDS AP using my Ethernet connection, we had to face the WDS AP away from the WDS client so that it was no longer registered - then I could get into the WDS AP running the non RC firmware.

So at this time, I have a remote DynaDish WDS client on the RC firmware and I can not get into it using wireless or the Ethernet. The Ethernet does not even show a link.

Good thing I had other alternate links between my two locations.

Has anybody else encountered this ?

North Idaho Tom Jones

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 2:21 am
by yottabit
Connection to non-Mikrotik and still use one radio for station and AP modes simultaneously.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 2:34 am
by Alessio Garavano
Connection to non-Mikrotik and still use one radio for station and AP modes simultaneously.
This i know... but has another advantage over WDS in performance or something connecting 2 RB in repeater mode?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 2:55 am
by yottabit
No, probably a disadvantage in performance and/or reliability, actually. Specifically this breaks layer-2 since you can't bridge multiple MAC addresses across station mode per 802.11 spec. So you end up using Station Pseudobridge mode which does a sort of NAT for MAC addresses. WDS avoids all that mess.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 3:00 am
by jondavy
please define as default this option in OmniTik and other RouterBards

/interface ethernet poe settings set ether1-poe-in-long-cable=yes

because the outputs PoE outs do not work if not activated this function,
because many find it defective.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 7:50 am
by raffav
ATTENTION
KERNEL BOOT LOOP ON RC21
On rb433 with wireless rep packege kernel boot,
If wifi-rep disable or switched to wifi-cm2 kernel ok
On crs125 all ok

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 7:56 am
by benoga
I use CCR1009 and HAP AC (CapsMan) and have with HAP AC boot loop (6.35.17 and 6.35.21). When i disable CapsMan, then works fine.

(Version 6.35.19 works fine for the HAP AC)

CCR never boot loop, only HAP AC

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 9:37 am
by strods
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

If router goes into reboot loop, then if device has serial port send output of it within text file to support.

If router is rebooting and it does not have serial port, then Netinstall it to older version (With "Keep old configuration" enabled on Netinstall), generate supout file and send it to us.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 1:05 pm
by raffav
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

If router goes into reboot loop, then if device has serial port send output of it within text file to support.

If router is rebooting and it does not have serial port, then Netinstall it to older version (With "Keep old configuration" enabled on Netinstall), generate supout file and send it to us.
On my rb433uah after update to rc21 rb was rebooting after 5-10 seconds after system boot normally
In this middle time a was able to login and try to find the cause since in early rc a got the same kernel boot failure I disable de capsman, but not resolved
So i decided to disable the wifi-rep package after some try and ninja moves I finally got the packege to disable and the problem was gone.

The problem is this crashes didn't made autosupport files
And now the crazy
I had decided to turn wifi-rep again
The result no kernel failure :shock: :shock:
How I can sent the support file since now the rb looks ok?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 2:09 pm
by notToNew
Had the same on 952Ui-5ac2nD. Downgraded to rc19 and it is stable again.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 4:25 pm
by linek1980
RB433AH + wireless-rep-6.35rc21 = KERNEL BOOT LOOP. Rescue : telnet short time between the start and reboot interface wireless disable

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 5:28 pm
by kristaps
linek1980 what wireless card are you running ?
http://routerboard.com/R52NM aka AR92xxx
or http://routerboard.com/R52H aka AR5xxx

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 5:43 pm
by raffav
i think that the kernel boot loop is related to wifi-rep on the 433 or related to wireless card
because at home i use a 433uah as capsman and there was no cap enable on it and also get the kernel boot
i fallback to wifi-cm2 and the problem is gone, with cap enable
i my case the wifi card is a xr2 on both device

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 6:04 pm
by uldis
i think that the kernel boot loop is related to wifi-rep on the 433 or related to wireless card
because at home i use a 433uah as capsman and there was no cap enable on it and also get the kernel boot
i fallback to wifi-cm2 and the problem is gone, with cap enable
i my case the wifi card is a xr2 on both device
Please provide support output file to support@mikrotik.com after you are able to recover the board by disabling the wireless card. That will help us to identify the problem and fix it.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 6:27 pm
by yottabit
Running rc21 just now on rb962 (hAP ac). I started with a blank config and ended up in a boot loop:
  • Changed wlan1 (2 GHz) to station pseudobridge
  • Scanned
  • Chose a network
  • Clicked connect
  • Appeared to start connecting and then the router rebooted and got stuck in a boot loop.
I had to clear the config. After clearing, I tried again and the same thing happened.

Cleared again, and used it to successfully connect to a different network.

Without console access, how can I get a kernel panic message and/or kernel dump? What would you like to see?
I forgot to note in my post that I was using wireless-rep package.

I don't have access to that router anymore, but when my new ones arrive today I'll reproduce and get a supout.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 7:03 pm
by raffav
i think that the kernel boot loop is related to wifi-rep on the 433 or related to wireless card
because at home i use a 433uah as capsman and there was no cap enable on it and also get the kernel boot
i fallback to wifi-cm2 and the problem is gone, with cap enable
i my case the wifi card is a xr2 on both device
Please provide support output file to support@mikrotik.com after you are able to recover the board by disabling the wireless card. That will help us to identify the problem and fix it.

i had already sent
Ticket#2016030966000791

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 10:29 pm
by PeterDoBrasil
v6.35rc21
after upgrade sxt Light lost access to device, device are reboot every 60 seconds, after downgrade to v.6.35rc19 no more problems, I think there is any thing with ether port configuration causing this problem. The unice option to access the device is reset with reset button, and then downgrade to v6.35rc19 :?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 10:30 pm
by PeterDoBrasil
v6.35rc21
after upgrade sxt Light lost access to device, device reboots every 60 seconds, after downgrade to v.6.35rc19 no more problems, I think there is any thing with ether port configuration causing this problem. The unice option to access the device is reset with reset button, and then downgrade to v6.35rc19 :?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Wed Mar 09, 2016 10:50 pm
by raffav
v6.35rc21
after upgrade sxt Light lost access to device, device reboots every 60 seconds, after downgrade to v.6.35rc19 no more problems, I think there is any thing with ether port configuration causing this problem. The unice option to access the device is reset with reset button, and then downgrade to v6.35rc19 :?

disable the wifi-rep and enable the wifi-cm2 and that will work

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 9:37 am
by Naurislv
We have implemented fix which should help with wireless-rep reboot loop. Please test it if you can use rc version on your environment. Fix will be available in RouterOS v6.35rc25.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 11:32 am
by strods
Version 6.35rc25 has been released.

Changes since previous version:

*) tile - fixed rare situation when some cores decide not to take part in packet processing till next reboot;
*) fastpath - fixed crash when packet arrives on disabled interface;
*) capsman - fixed capsman extension channel names;
*) console - fixed print follow in "/ip dns cache" menu
*) ethernet - add option to see S-GPON-ONU module, GPON side SN in "/int eth mon sfp#"
*) ethernet - do not allow to set self as master port;
*) health - always report fan speed (even if it is 0);
*) l2tp - introduced per tunnel allow-fast-path option;
*) webfig - fixed firewall rule sorting did not work in other chains except all;
*) winbox - allow to set multiple dh-groups;
*) winbox - do not show fan statuses in passive cooling CCR1009;
*) winbox - fixed unset options in /routing ospf interface menu;
*) wireless-rep - fix crash on non-HT clients;
*) l2tp - implemented l2tp and lns fastpath/fasttrack support;
*) pppoe-client - implemented fastpath support.

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 11:59 am
by mistry7
Version 6.35rc25 has been released.

Changes since previous version:

*) tile - fixed rare situation when some cores decide not to take part in packet processing till next reboot;
*) fastpath - fixed crash when packet arrives on disabled interface;
*) capsman - fixed capsman extension channel names;
*) console - fixed print follow in "/ip dns cache" menu
*) ethernet - add option to see S-GPON-ONU module, GPON side SN in "/int eth mon sfp#"
*) ethernet - do not allow to set self as master port;
*) health - always report fan speed (even if it is 0);
*) l2tp - introduced per tunnel allow-fast-path option;
*) webfig - fixed firewall rule sorting did not work in other chains except all;
*) winbox - allow to set multiple dh-groups;
*) winbox - do not show fan statuses in passive cooling CCR1009;
*) winbox - fixed unset options in /routing ospf interface menu;
*) wireless-rep - fix crash on non-HT clients;
*) l2tp - implemented l2tp and lns fastpath/fasttrack support;
*) pppoe-client - implemented fastpath support.

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

When i Download and Install 6.35 RC25
My CRS reboot with Kernel Failure
I now use 6.35 RC21
it creates autosupot

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 12:02 pm
by strods
mistry7 - Did it actually upgrade? Or did it boot up with rc21?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 12:07 pm
by anuser
Bug or missing feature in new wireless package?

setup: traffic forwarding @CAPSMAN controller:

- with wireless-fp: client receives IPv6 router advertisement, everything works
- with wireless-rep: client doesn´t receive any IPv6 traffic, no RA at all

(I use the same configuration, just disable/enable wireless-fp/wireless-rep package on both CAPSMAN controller and CAP, also tested with 6.35rc25 on x86)
MikroTik ticket: 2016031066000617

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 12:34 pm
by andriys
- with wireless-fp: client receives IPv6 router advertisement, everything works
- with wireless-rep: client doesn´t receive any IPv6 traffic, no RA at all
Have you switch from wireless-fp to wireless-rep on both CAP (access point) and CAPsMAN (controller)? The wireless-fp implements CAPsMAN v1 while wireless-rep implements CAPsMAN v2 and these are not compatible with each other.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 12:46 pm
by anuser
- with wireless-fp: client receives IPv6 router advertisement, everything works
- with wireless-rep: client doesn´t receive any IPv6 traffic, no RA at all
Have you switch from wireless-fp to wireless-rep on both CAP (access point) and CAPsMAN (controller)? The wireless-fp implements CAPsMAN v1 while wireless-rep implements CAPsMAN v2 and these are not compatible with each other.
Yes I did and realized that I made a mistake.

The Problem is: with CAPsMANv2 and „wireless-rep“ package clients don´t receive any IPv6 traffic, no IPv6 router adverisements at all iff VLAN assignement is done dynamically. Dynamic VLAN assignment within datapath works for IPv4 traffic, though. If I assign a VLAN ID wihin datapath configuration of CAPSMAN, IPv6 and IPv4 is working without any problems.

(with traffic forwarding @CAPSMAN controller)

[UPDATE]

+ It works when I change multicast-helper setting to full on the Cap interface

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 1:23 pm
by mistry7
mistry7 - Did it actually upgrade? Or did it boot up with rc21?

upgrade

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 2:38 pm
by mccreigh
I installed the v6.35rc21 firmware bundle and matching wireless-rep in a RBmAP-2nD access point (1 Ethernet, 1 2.4GHz wireless). I tried the new wireless repeater mode, which uses the one physical wireless interface as a station virtual interface bridged to an access point virtual interface, and it seems to work.

There's one last bit of wireless-to-wireless functionality in consumer travel routers that should now be possible with RouterOS, but I haven't yet seen how. Consider the "Hotspot mode" of the ASUS WL-330N3G travel router. It implements two virtual wireless interfaces on the same physical interface. On its station virtual interface it has a DHCP client and obtains a single IP address. Its Ethernet physical interface and access point virtual interface bridge onto a LAN with a DHCP server, which NATs through the IP address of the station interface. Its access point virtual interface is generally configured with a different SSID and different link security than its station virtual interface.

This mode lets you create a private encrypted wireless LAN in your hotel room so you can use unencrypted protocols among your wireless devices without worrying about other hotel guests being able to see them, even if the hotel's own guest wireless network is unencrypted.

Can this now be done with RouterOS v6.35 including wireless-rep? If so, could someone please explain how?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 3:11 pm
by yottabit
Yes it can. Change wlan1 to station pseudobridge, connect it to a Wi-Fi network by using the scan function. (Remember to setup a security profile if needed for Wi-Fi encryption.) Then setup firewall to src NAT that interface. Create a Virtual AP on the same interface. Ensure both wlan1 and the Virtual AP are joined to a bridge interface. Turn on DHCP server. Should be close to finished. I can send you a working config later if you get stuck.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 4:41 pm
by blimbach
I´ve tried to upgrade my "hap lite" (smips) from rc21 with wireless-rep to rc25 via winbox: System -> Packages.

This doesn´t work with the following error:

ERROR: not enough disk space, 7.7MiB is required and only 7.1 MiB is free.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 4:44 pm
by yottabit
I´ve tried to upgrade my "hap lite" (smips) from rc21 with wireless-rep to rc25 via winbox: System -> Packages.

This doesn´t work with the following error:

ERROR: not enough disk space, 7.7MiB is required and only 7.1 MiB is free.
Have you tried from a fresh boot (i.e., empty ramdisk)?

If it still doesn't work, can you delete one of the wireless packages you no longer need, e.g., wireless-fp and/or wireless-cm2?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 4:59 pm
by blimbach
Thank for the hint yottabit, but it doesn´t work.

It says: Can´t uninstall bundled packages (wireless-cm2 / wireless-fp). Also System-Recources tells me that 40MB RAM are free. It´s only a small CAP i´m testing.

Posted: Thu Mar 10, 2016 5:02 pm
by jarda
Blimbach, you should read from the beginning. Or at least from here...


http://forum.mikrotik.com/viewtopic.php ... 78#p522278

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 5:27 pm
by Sob
..., install system package only, ...
Stupid question: Is this specific to smips where packages are smaller and just system one would probably fit in free space (I don't have any smips device myself, so I can't say for sure), or is there a way (without netinstall), how to do it for mipsbe too? I wanted to get rid of combined package on my mAP Lite and free space was only around 5MB, while system package is almost 7MB.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 5:57 pm
by nkourtzis
When i Download and Install 6.35 RC25
My CRS reboot with Kernel Failure
I now use 6.35 RC21
it creates autosupot
Same here, upgrading a hEX Lite board from RC19. Upgrade fails. Opened support ticket (#2016031066001081).

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 6:19 pm
by mccreigh
Yes it can. Change wlan1 to station pseudobridge, connect it to a Wi-Fi network by using the scan function. (Remember to setup a security profile if needed for Wi-Fi encryption.) Then setup firewall to src NAT that interface. Create a Virtual AP on the same interface. Ensure both wlan1 and the Virtual AP are joined to a bridge interface. Turn on DHCP server. Should be close to finished. I can send you a working config later if you get stuck.
I'd really appreciate a working config that I can dig through to understand.

My other problem is finding a sequence of steps to get from the factory-default RBmAPL-n2D WISP AP configuration to one where the (only) Ethernet interface is on the LAN without losing Winbox connectability. (I can always use the magic button to restore the factory-default configuration, but then I'm right back where I started.) Once I'm controlling the router firmly through its Ethernet interface, I should be able to reconfigure the wlan interface without losing control.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Thu Mar 10, 2016 11:03 pm
by raffav
ATTENTION
RC26
Maybe constant reboot on CHR
verifying if is a isolated case or on all CHR
testing on another CHR
ignore, it was a isolated case !!!

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Mar 11, 2016 1:30 pm
by mistry7
mistry7 - Did it actually upgrade? Or did it boot up with rc21?

with RC26 upgrade works

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Mar 11, 2016 5:34 pm
by raffav
I am getting reboot on CHR
12:08:22 system,error,critical router was rebooted without proper shutdown
when CAPMAN is enable on any wifi pack CM2 or REP

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Fri Mar 11, 2016 7:45 pm
by mccreigh
Yes it can. Change wlan1 to station pseudobridge, connect it to a Wi-Fi network by using the scan function. (Remember to setup a security profile if needed for Wi-Fi encryption.) Then setup firewall to src NAT that interface. Create a Virtual AP on the same interface. Ensure both wlan1 and the Virtual AP are joined to a bridge interface. Turn on DHCP server. Should be close to finished. I can send you a working config later if you get stuck.
I'd really appreciate a working config that I can dig through to understand.

My other problem is finding a sequence of steps to get from the factory-default RBmAPL-n2D WISP AP configuration to one where the (only) Ethernet interface is on the LAN without losing Winbox connectability. (I can always use the magic button to restore the factory-default configuration, but then I'm right back where I started.) Once I'm controlling the router firmly through its Ethernet interface, I should be able to reconfigure the wlan interface without losing control.
Recall that we're discussing a RBmAPL-2nD single-Ethernet single-WAN router, where I wanted to use an existing WLAN as my WAN, and NAT-route it to a LAN consisting of an access point (using the same WiFi radio) with a different SSID and the Ethernet. I hoped that RouterOS v6.35 might at last allow me to do that in a single box. It's working now, thanks to yottabit's vital hints. His one hint that confused me a bit was "ensure that wlan1 and the Virtual AP are joined to a bridge interface". I think he meant that ether1 and the Virtual AP should be joined to a bridge interface. If anybody wants the config, I'll post it.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sat Mar 12, 2016 2:25 am
by PeterDoBrasil
We have implemented fix which should help with wireless-rep reboot loop. Please test it if you can use rc version on your environment. Fix will be available in RouterOS v6.35rc25.
Thank you, Iám using v6.35rc26; no more problems! :lol:

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sat Mar 12, 2016 6:09 pm
by incahex
Rc26
My hex increases the use of mem whitout reason until it hangs. Need to reboot to work again and do the same again.
12 hours more or less until it uses all the memory and need reboot.

No config changes before update. Only from rc 19 to rc 26

Update to include image.
Image

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sat Mar 12, 2016 8:33 pm
by PeterDoBrasil
Mikrotik will launch how much rc's to come to final version ???? 30? 40? 50?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sat Mar 12, 2016 8:51 pm
by nkourtzis
Mikrotik will launch how much rc's to come to final version ???? 30? 40? 50?
If the goal is a more stable release, then the more rc's the better. Other companies do the same, the builds are just not publically available; just designated beta testers have access to them.

If you need stability, use the bugfix version.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sat Mar 12, 2016 8:56 pm
by PeterDoBrasil
Mikrotik will launch how much rc's to come to final version ???? 30? 40? 50?
If the goal is a more stable release, then the more rc's the better. Other companies do the same, the builds are just not publically available; just designated beta testers have access to them.

If you need stability, use the bugfix version.
This was only a question! My prefered update option always is the rc's because there are a lot of good new things!

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Sun Mar 13, 2016 1:59 pm
by kometchtech
In rc26, and it has been in CAPsMAN configuration, from the DHCP Server, which is activated in the other RB, has been confirmed a phenomenon in which the IP address is not passed.
Moreover, instead of immediately occur, but after the elapse of a few hours if you are using.

It has not been output, especially something like anxious to log.

If you have enabled local forwarding, it seems this phenomenon is likely to occur.

Intel 5300AGN ping loss

Posted: Mon Mar 14, 2016 9:16 am
by m94646602
I use 6.35rc26 wireless-rep (AP mode), my laptop (WIN7 INTEL wireless 5300AGN) had a lot of PING loss, when I changed to WIRELESS-CM2, everything is normal.

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Mar 14, 2016 10:59 am
by omidkosari
Is there any chance to implementation of
http://forum.mikrotik.com/viewtopic.php ... 50#p235456
Umetered Content for PPPoE . 'Unmetered Content' services aren't counted against your monthly download/upload inclusion

http://forum.mikrotik.com/viewtopic.php?t=59745

Mikrotik staff ?

Re: v6.35rc [release candidate] is released, new wireless package!

Posted: Mon Mar 14, 2016 11:03 am
by omidkosari
Is there any chance to implementation of
http://forum.mikrotik.com/viewtopic.php ... 50#p235456
Umetered Content for PPPoE . 'Unmetered Content' services aren't counted against your monthly download/upload inclusion

http://forum.mikrotik.com/viewtopic.php?t=59745

Mikrotik staff ?
http://www.cisco.com/c/en/us/products/i ... index.html

Re: Intel 5300AGN ping loss

Posted: Mon Mar 14, 2016 11:06 am
by uldis
I use 6.35rc26 wireless-rep (AP mode), my laptop (WIN7 INTEL wireless 5300AGN) had a lot of PING loss, when I changed to WIRELESS-CM2, everything is normal.
Please contact support@mikrotik.com and attach a support output file which is made when you have the ping loss.