/interface bridge
add fast-forward=no igmp-snooping=no name=bridge-vlans vlan-filtering=yes
/interface vlan
add interface=bridge-vlans name=vlan40 vlan-id=40
add interface=bridge-vlans name=vlan41 vlan-id=41
add interface=bridge-vlans name=vlan42 vlan-id=42
/interface bridge port
add bridge=bridge-vlans interface=ether1 pvid=40
add bridge=bridge-vlans interface=ether24-Trunk
/interface bridge vlan
add bridge=bridge-vlans tagged="bridge-vlans,ether24-Trunk" vlan-ids=40
add bridge=bridge-vlans tagged="bridge-vlans,ether24-Trunk" vlan-ids=41
add bridge=bridge-vlans tagged="bridge-vlans,ether24-Trunk" vlan-ids=42
/ip address
add address=192.168.40.254/24 interface=vlan40 network=192.168.40.0
add address=192.168.41.254/24 interface=vlan41 network=192.168.41.0
add address=192.168.42.254/24 interface=vlan42 network=192.168.42.0
set name=R1
Yea sure that will work but cant see that that is the correct way to do this as you loose the hardware offload on this type off config.Put a bridge in your bridge?Has anyone tested ROMON in 6.41rc47?
Seems that is not working.
Also, can someone explain how QinQ vlans would be programmed in the new Bridge vlan implementation?
go to
/ip neighbor discovery-settings menu
and set discover-interface-list=all
It will be released when its ready.The support promised the next rc release will have a fix for my crash. That was one and a half week ago...
Will we have a release any time soon?
Hopefully a new RC early next week, but they pretty much shut down development during a MUM, which started Thursday.The support promised the next rc release will have a fix for my crash. That was one and a half week ago...
Will we have a release any time soon?
/inteface bridge vlan (here you define bridge vlan and member ports att taged or untaged. Here tag bridge self to.......Hardware offload for Vlans using the bridge ports on CRS212 does not seem to work?
/interface bridge
add igmp-snooping=no name=bridge1
add igmp-snooping=no name=bridge2
/interface vlan
add interface=sfp10 name=sfp10-vlan100 vlan-id=100
add interface=sfp10 name=sfp10-vlan101 vlan-id=101
/interface bridge port
add bridge=bridge1 interface=sfp2
add bridge=bridge1 interface=sfp10-vlan100
add bridge=bridge2 interface=sfp5
add bridge=bridge interface=sfp10-vlan101
The actual non-vlan members seems to be enabled for the hwoffload, but not the VLANS. Should this be done in another way?
Running 6.41rc47 on CRS212-1G-10S-1S+
/Mikael
do not do this, our system on average 1~5 seconds to process the radius packageWhat's new in 6.41rc50 (2017-Oct-30 10:13):
*) radius - limited RADIUS timeout maximum value to 3 seconds;
stop right there. this stuff above literally translates to wave2, right?What's new in 6.41rc50 (2017-Oct-30 10:13):
*) wireless - new driver with initial support for 160 and 80+80 MHz channel width;
I thought 802.11ac Wave2 was MU-MIMO as well as 160MHz / 80+80MHz channels? And to date, I believe all the the wireless chipsets that Mikrotik has shipped in products are Wave1. But maybe this is a little accidental show-of-hand towards new products, which of course would need software support.stop right there. this stuff above literally translates to wave2, right?
Wave2 you say... You mean like this:
stop right there. this stuff above literally translates to wave2, right?
What's new in 6.41rc50 (2017-Oct-30 10:13):
*) radius - limited RADIUS timeout maximum value to 3 seconds;
do not do this, our system on average 1~5 seconds to process the radius packageWhat's new in 6.41rc50 (2017-Oct-30 10:13):
*) radius - limited RADIUS timeout maximum value to 3 seconds;
please leave this field customizable
What's new in 6.41rc50 (2017-Oct-30 10:13):
*) radius - limited RADIUS timeout maximum value to 3 seconds;
Yup, seems like MT was overstepping. Seems like something that should be a default value adjustment that is still configurable.a very bad idea, this field generally needs to remove the limits, so that I myself can set the desired value, for example, even 15-20 secondsWhat's new in 6.41rc50 (2017-Oct-30 10:13):
*) radius - limited RADIUS timeout maximum value to 3 seconds;
having the same issue on CRS317. i use classic RouterOS vlan trunking on crs317 because i can not pass VLANs to routers with current version of RouterOSHi,
Is it just me or did the new bridge implementation just vanish in 6.41rc50 - On CRS212-1G-10S-1S+ Im back with masterports and no hardware offload in menu?
/Mikael
They've done that already. This was initially implemented in 6.40 (rc36 I believe) and and then pulled for 6.40 stable. I really don't think it will be necessary to that again.Just wanted to tell you guys implementing very good thing, but new RC seems to be very long in development so far. It is not common to see 50 (!) RCs per release (and not yet 6.41 released this far), and this looks like it will be just dangerous to install in into prod for too many changes (beside new bridge implementation).
Would you mind to hear if I ask you to introduce two releases at the end: say, 6.41 with all changes but without new bridge implementation (so new changes will be tested beside all mess that can be involved with new bridging) , and another one, say 6.42 (or 6.411) with just bridge 'revolution'? This appears to be wise to monitor the effect of new bridge implementation without any other changes. Just in case, you know!
+1 we are using OTP that validates a bit slow sometimes we want 10 seconds... Don't do this.do not do this, our system on average 1~5 seconds to process the radius packageWhat's new in 6.41rc50 (2017-Oct-30 10:13):
*) radius - limited RADIUS timeout maximum value to 3 seconds;
please leave this field customizable
Done what? In released version? With no roll back? Hey, you must be kidding me!They've done that already.
They had some of the new bridge code in 6.40rc and reverted it for the final 6.40, then put it back in for 6.41rc. At this point a lot of their new devices are starting to rely on it though.Done what? In released version? With no roll back? Hey, you must be kidding me!They've done that already.
Yes, look at the forum thread for 6.40rc, in 6.40rc36 the new bridge implementation was introduced. It was reverted in 6.40rc41 so that 6.40 could be released to stable without it. We are now in 6.41rc and it is here to stay. In that release you got exactly what you were asking for. The bridge was brought in, you should've installed it, tried out and then when 6.40 went into production you'd get the old master implementation back. The way this particular change works, it's very difficult to keep both implementations in the code base and swap between them especially without introducing new confusion and issues.Done what? In released version? With no roll back? Hey, you must be kidding me!They've done that already.
What I talk about is the we shoudl split new bridge implementation from all these other changes, for good reason: bridge change is BIG one so this alone should be tested very serious. When it comes to big RB-based network, we'd want to check any consequnces and react accordingly. 6.40rc36 introduced h/w bridging but then it was rolled back, so no tests in the wild was done.
6.42 is full of other changes. This is why if you just upgrade RB to 6.42, you'll never know whay caused problem should they arise: new h/w bridge code or any of these changes you can see in the changelog.
And yes, when it comes to upgrade, say, 100 remote devices, I'd prefer to turn on serious new feature one at the time, don't you like this approach?
I do appreciate MT for their passion to create better platform but big changes is something risky, so isolating BIG changes is kind of good idea, I think.
Yes, it has. It happened in 6.41rc47 (see here):Has the routerboot firmware version naming changed in 6.41rc?
!) routerboot - RouterBOOT version numbering system merged with RouterOS;
I'd rather vote for keeping it separate. I believe it's simply safer, and if you have a boot-loop you will at least have an idea of what failed- loader or OS.If routerboot firmware now follows the ROS version, I would very much like it to automatically get upgraded too during the upgrade of ROS.
Or at least give the user an option to do that in one go.
Having to do double reboots on every upgrade would not be very convenient
I know that. I'm awre of new bridge implementation and keep my eyes on it, but you missed the point: when MT ships the release I'd prefer to keep two releases, one with just new bridging, another one with the rest of current changelog but without bridging (or in reversed order, first one with just changes, then with just bridge).Yes, look at the forum thread for 6.40rc, in 6.40rc36 the new bridge implementation was introduced. It was reverted in 6.40rc41 so that 6.40 could be released to stable without it.
Good question. If you look at f/w changelog you'll notice there is not that many changes that affects your device. So apply each firmware upgrade released is an overkill, and should be bound to specific models.For me the more important question about boot firmware is: Will the firmware version change with every RouterOS release even if no changes are made? Suppose you installed RouterOS 6.41, then upgraded firmware to 6.41. RouterOS 6.41.1 ships with no changes to the firmware. Is the available firmware version 6.41 or 6.41.1?
So, is this an updated driver (kernel module) from the ASIC vendor (e.g. Atheros) which has also some bugfixes/features from the vendor?What's new in 6.41rc50 (2017-Oct-30 10:13):
*) wireless - new driver with initial support for 160 and 80+80 MHz channel width;
I'd say we'll when 1) it'll be released and 2) when we'll live with it at least several releases.is the new bridge implementation without issues now?
It does scan but it isn't passive.*) wireless - added passive scan functionality (CLI only);
Any info on this?
MikroTik Support Number: 2017110722001161What's new in 6.41rc50 (2017-Oct-30 10:13):
Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.
Before an upgrade:
1) Remember to make backup/export files before an upgrade and save them on another storage device;
2) Make sure the device will not lose power during upgrade process;
3) Device has enough free storage space for all RouterOS packages to be downloaded.
Changes since previous 6.41rc release:
!) bridge - general implementation of hw-offload bridge (introduced in v6.40rc36);
!) detnet - implemented "/interface detect-internet" feature;
https://wiki.mikrotik.com/wiki/Manual:Detect_internet
*) bridge - set "igmp-snooping=no" by default on new bridges;
*) crs3xx - added ingress/egress rate input limits;
*) dhcp-client - limited DHCP client "default-route-distance" minimal value to 1;
*) dhcp-server - added "option-set" argument (CLI only);
*) discovery - use "/interface list" instead of interface name under neighbor discovery settings;
*) health - fixed bogus voltage readings on CCR1009;
*) ike1 - fixed crash after downgrade if DH groups 19,20,21 were used for phase1;
*) ike1 - fixed crash on xauth if user does not exist;
*) ipv6 - fixed IPv6 addresses constructed from prefix and static address entry;
*) lte - added "/interface lte apn" menu (Passthrough requires reconfiguration);
*) lte - added Passthrough support;
*) lte - fixed user authentication for R11e-LTE when new firmware is used;
*) m11g - improved ethernet performance on high load;
*) netinstall - fixed missing "/flash/etc" on first bootup;
*) quickset - renamed router IP static DNS name to "router.lan"
*) radius - limited RADIUS timeout maximum value to 3 seconds;
*) sms - fixed minor problem for SMS delivery;
*) webfig - added favicon file;
*) webfig - fixed terminal graphic user interface under Safari browser;
*) winbox - do not show unnecessary tabs from "Switch" menu;
*) wireless - new driver with initial support for 160 and 80+80 MHz channel width;
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.
nov/06 18:36:22 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -70
nov/06 18:37:21 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 18:37:21 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -71
nov/06 18:37:26 wireless,info DC:3A:5E:95:9B:BF@wlan1: reassociating
nov/06 18:37:26 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, ok
nov/06 18:37:26 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
nov/06 18:51:34 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 18:51:34 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -60
nov/06 19:04:24 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, group key exchange timeout
nov/06 19:04:24 wireless,info AC:18:26:4C:A6:EC@wlan1: disconnected, group key exchange timeout
nov/06 19:04:39 wireless,info AC:18:26:4C:A6:EC@wlan1: connected, signal strength -90
nov/06 19:04:46 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -61
nov/06 19:35:22 wireless,info E8:DE:27:14:C5:39@wlan2: connected, signal strength -65
nov/06 19:35:22 wireless,info E8:DE:27:14:C5:39@wlan1: disconnected, registered to other interface
nov/06 19:54:24 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, group key exchange timeout
nov/06 19:54:26 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
nov/06 19:54:34 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 19:54:35 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -67
nov/06 20:02:20 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 20:02:20 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -77
nov/06 20:05:41 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 20:05:41 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -68
nov/06 20:09:24 wireless,info AC:18:26:4C:A6:EC@wlan1: disconnected, group key exchange timeout
nov/06 20:09:34 wireless,info AC:18:26:4C:A6:EC@wlan1: connected, signal strength -80
nov/06 20:09:36 wireless,info AC:18:26:4C:A6:EC@wlan1: reassociating
nov/06 20:09:36 wireless,info AC:18:26:4C:A6:EC@wlan1: disconnected, ok
nov/06 20:09:36 wireless,info AC:18:26:4C:A6:EC@wlan1: connected, signal strength -75
nov/06 20:09:41 wireless,info AC:18:26:4C:A6:EC@wlan1: disconnected, unicast key exchange timeout
nov/06 20:10:00 wireless,info AC:18:26:4C:A6:EC@wlan1: connected, signal strength -76
nov/06 20:10:15 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 20:10:16 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -71
nov/06 20:10:21 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 20:10:21 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -64
nov/06 20:10:21 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received deauth: class 2 frame received (6)
nov/06 20:10:34 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -61
nov/06 20:19:23 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 20:19:24 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -66
nov/06 20:19:24 wireless,info AC:18:26:4C:A6:EC@wlan1: disconnected, group key exchange timeout
nov/06 20:19:29 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 20:20:47 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -67
nov/06 20:20:50 wireless,info AC:18:26:4C:A6:EC@wlan1: connected, signal strength -82
nov/06 20:22:32 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 20:22:32 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -75
nov/06 20:27:05 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 20:27:11 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -63
nov/06 20:27:16 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 20:27:25 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -60
nov/06 20:29:24 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, group key exchange timeout
nov/06 20:29:25 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -67
nov/06 20:31:39 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 20:31:44 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -71
nov/06 20:34:24 wireless,info AC:18:26:4C:A6:EC@wlan1: disconnected, group key exchange timeout
nov/06 20:34:44 wireless,info AC:18:26:4C:A6:EC@wlan1: connected, signal strength -79
nov/06 20:34:47 wireless,info AC:18:26:4C:A6:EC@wlan1: reassociating
nov/06 20:34:47 wireless,info AC:18:26:4C:A6:EC@wlan1: disconnected, ok
nov/06 20:34:47 wireless,info AC:18:26:4C:A6:EC@wlan1: connected, signal strength -84
nov/06 20:34:52 wireless,info AC:18:26:4C:A6:EC@wlan1: disconnected, unicast key exchange timeout
nov/06 20:35:28 wireless,info AC:18:26:4C:A6:EC@wlan1: connected, signal strength -76
nov/06 20:36:51 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 20:36:52 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -67
nov/06 20:36:57 wireless,info DC:3A:5E:95:9B:BF@wlan1: reassociating
nov/06 20:36:57 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, ok
nov/06 20:36:57 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
nov/06 20:39:11 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 20:39:11 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -66
nov/06 20:48:42 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 20:49:01 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -66
nov/06 21:33:26 wireless,info E8:DE:27:14:C5:39@wlan2: reassociating
nov/06 21:33:26 wireless,info E8:DE:27:14:C5:39@wlan2: disconnected, ok
nov/06 21:33:26 wireless,info E8:DE:27:14:C5:39@wlan2: connected, signal strength -65
nov/06 21:44:24 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, group key exchange timeout
nov/06 21:44:24 wireless,info 6C:3B:6B:EB:59:99@wlan1: disconnected, group key exchange timeout
nov/06 21:44:27 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -72
nov/06 21:44:27 wireless,info 6C:3B:6B:EB:59:99@wlan1: connected, signal strength -60, wants bridge
nov/06 21:44:31 wireless,info DC:3A:5E:95:9B:BF@wlan1: reassociating
nov/06 21:44:31 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, ok
nov/06 21:44:31 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -60
nov/06 21:45:54 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 21:45:54 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -60
nov/06 21:49:24 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, group key exchange timeout
nov/06 21:49:24 wireless,info 6C:3B:6B:EB:59:99@wlan1: disconnected, group key exchange timeout
nov/06 21:49:25 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -64
nov/06 21:49:26 wireless,info 6C:3B:6B:EB:59:99@wlan1: connected, signal strength -59, wants bridge
nov/06 21:53:43 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 21:53:44 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -60
nov/06 21:57:18 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 21:57:37 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -66
nov/06 22:01:16 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 22:01:17 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
nov/06 22:01:23 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 22:01:23 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
nov/06 22:04:36 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 22:04:37 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -71
nov/06 22:04:42 wireless,info DC:3A:5E:95:9B:BF@wlan1: reassociating
nov/06 22:04:42 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, ok
nov/06 22:04:42 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -67
nov/06 22:07:24 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 22:07:25 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
nov/06 22:11:45 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 22:11:46 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -71
nov/06 22:11:51 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 22:11:51 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -60
nov/06 22:11:51 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received deauth: class 2 frame received (6)
nov/06 22:12:04 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
nov/06 22:19:15 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 22:19:21 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -59
nov/06 22:19:26 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 22:19:34 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -60
nov/06 22:31:40 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 22:31:41 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -75
nov/06 22:39:04 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 22:39:05 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -69
nov/06 22:39:10 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 22:39:41 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -67
nov/06 22:51:22 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 22:51:23 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -67
nov/06 22:59:24 wireless,info 6C:3B:6B:EB:59:99@wlan1: disconnected, group key exchange timeout
nov/06 22:59:24 wireless,info 68:C4:4D:EE:F0:DF@wlan2: disconnected, group key exchange timeout
nov/06 22:59:40 wireless,info 6C:3B:6B:EB:59:99@wlan1: connected, signal strength -76, wants bridge
nov/06 23:03:18 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 23:03:24 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -70
nov/06 23:03:29 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 23:03:37 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -61
nov/06 23:12:12 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 23:12:13 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -68
nov/06 23:12:18 wireless,info DC:3A:5E:95:9B:BF@wlan1: reassociating
nov/06 23:12:18 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, ok
nov/06 23:12:18 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -60
nov/06 23:12:23 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 23:12:31 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -60
nov/06 23:15:43 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -71
nov/06 23:16:00 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 23:16:01 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -70
nov/06 23:16:06 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 23:16:24 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -72
nov/06 23:16:29 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 23:16:48 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
nov/06 23:16:50 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -44
nov/06 23:17:01 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
nov/06 23:17:06 wireless,info DC:3A:5E:95:9B:BF@wlan1: reassociating
nov/06 23:17:06 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, ok
nov/06 23:17:06 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -72
nov/06 23:17:11 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 23:17:37 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -75
nov/06 23:18:50 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 23:18:56 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -66
nov/06 23:19:01 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 23:19:14 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -66
nov/06 23:19:19 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 23:19:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
nov/06 23:19:28 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -66
nov/06 23:20:15 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 23:20:16 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -66
nov/06 23:20:21 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 23:20:34 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
nov/06 23:21:08 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 23:21:09 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
nov/06 23:24:49 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 23:24:53 wireless,info 68:C4:4D:EE:F0:DF@wlan2: connected, signal strength -52
nov/06 23:24:55 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -61
nov/06 23:25:39 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -64
nov/06 23:28:13 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -52
nov/06 23:28:28 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 23:28:34 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -64
nov/06 23:28:47 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
nov/06 23:29:04 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -50
nov/06 23:29:24 wireless,info 6C:3B:6B:EB:59:99@wlan1: disconnected, group key exchange timeout
nov/06 23:29:24 wireless,info AC:18:26:4C:A6:EC@wlan1: disconnected, group key exchange timeout
nov/06 23:29:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
nov/06 23:29:36 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 23:29:58 wireless,info 6C:3B:6B:EB:59:99@wlan1: connected, signal strength -69, wants bridge
nov/06 23:30:00 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -70
nov/06 23:30:09 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -60
nov/06 23:30:12 wireless,info AC:18:26:4C:A6:EC@wlan1: connected, signal strength -79
nov/06 23:30:15 wireless,info AC:18:26:4C:A6:EC@wlan1: reassociating
nov/06 23:30:15 wireless,info AC:18:26:4C:A6:EC@wlan1: disconnected, ok
nov/06 23:30:15 wireless,info AC:18:26:4C:A6:EC@wlan1: connected, signal strength -83
nov/06 23:30:17 wireless,info AC:18:26:4C:A6:EC@wlan1: reassociating
nov/06 23:30:17 wireless,info AC:18:26:4C:A6:EC@wlan1: disconnected, ok
nov/06 23:30:17 wireless,info AC:18:26:4C:A6:EC@wlan1: connected, signal strength -79
nov/06 23:30:18 wireless,info AC:18:26:4C:A6:EC@wlan1: reassociating
nov/06 23:30:18 wireless,info AC:18:26:4C:A6:EC@wlan1: disconnected, ok
nov/06 23:30:18 wireless,info AC:18:26:4C:A6:EC@wlan1: connected, signal strength -82
nov/06 23:30:23 wireless,info AC:18:26:4C:A6:EC@wlan1: disconnected, unicast key exchange timeout
nov/06 23:30:43 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
nov/06 23:33:35 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 23:33:59 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -64
nov/06 23:34:04 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 23:34:24 wireless,info 6C:3B:6B:EB:59:99@wlan1: disconnected, group key exchange timeout
nov/06 23:34:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
nov/06 23:34:29 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -59
nov/06 23:34:40 wireless,info 6C:3B:6B:EB:59:99@wlan1: connected, signal strength -64, wants bridge
nov/06 23:35:01 wireless,info AC:18:26:4C:A6:EC@wlan1: connected, signal strength -78
nov/06 23:35:06 wireless,info AC:18:26:4C:A6:EC@wlan1: disconnected, unicast key exchange timeout
nov/06 23:35:33 wireless,info AC:18:26:4C:A6:EC@wlan1: connected, signal strength -74
nov/06 23:35:34 wireless,info AC:18:26:4C:A6:EC@wlan1: disconnected, received deauth: class 2 frame received (6)
nov/06 23:38:46 wireless,info AC:18:26:4C:A6:EC@wlan1: connected, signal strength -77
nov/06 23:38:53 wireless,info AC:18:26:4C:A6:EC@wlan1: disconnected, unicast key exchange timeout
nov/06 23:39:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
nov/06 23:40:18 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -64
nov/06 23:40:39 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -67
nov/06 23:41:50 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -59
nov/06 23:42:22 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
nov/06 23:42:24 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -50
nov/06 23:43:00 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
nov/06 23:43:13 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -64
nov/06 23:44:07 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 23:44:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
nov/06 23:44:30 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -71
nov/06 23:45:29 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
nov/06 23:45:49 wireless,info E8:DE:27:14:C5:39@wlan2: reassociating
nov/06 23:45:49 wireless,info E8:DE:27:14:C5:39@wlan2: disconnected, ok
nov/06 23:45:49 wireless,info E8:DE:27:14:C5:39@wlan2: connected, signal strength -65
nov/06 23:45:49 wireless,info E8:DE:27:14:C5:39@wlan2: reassociating
nov/06 23:45:49 wireless,info E8:DE:27:14:C5:39@wlan2: disconnected, ok
nov/06 23:45:49 wireless,info E8:DE:27:14:C5:39@wlan2: connected, signal strength -64
nov/06 23:45:49 wireless,info E8:DE:27:14:C5:39@wlan2: reassociating
nov/06 23:45:49 wireless,info E8:DE:27:14:C5:39@wlan2: disconnected, ok
nov/06 23:45:49 wireless,info E8:DE:27:14:C5:39@wlan2: connected, signal strength -64
nov/06 23:45:49 wireless,info E8:DE:27:14:C5:39@wlan2: reassociating
nov/06 23:45:49 wireless,info E8:DE:27:14:C5:39@wlan2: disconnected, ok
nov/06 23:45:49 wireless,info E8:DE:27:14:C5:39@wlan2: connected, signal strength -67
nov/06 23:46:01 wireless,info E8:DE:27:14:C5:39@wlan1: connected, signal strength -66
nov/06 23:46:01 wireless,info E8:DE:27:14:C5:39@wlan2: disconnected, registered to other interface
nov/06 23:49:29 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 23:49:34 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
nov/06 23:52:55 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
nov/06 23:53:21 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -45
nov/06 23:54:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
nov/06 23:54:55 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -70
nov/06 23:55:00 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 23:55:32 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -64
nov/06 23:55:37 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
nov/06 23:56:32 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -71
nov/06 23:58:28 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -44
nov/06 23:59:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
nov/06 23:59:31 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -62
00:02:46 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
00:02:47 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -66
00:02:53 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
00:02:54 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -66
00:04:18 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
00:04:24 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -63
00:06:40 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
00:07:22 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -64
00:09:15 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -43
00:09:20 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, unicast key exchange timeout
00:09:24 wireless,info 6C:3B:6B:EB:59:99@wlan1: disconnected, group key exchange timeout
00:09:28 wireless,info 6C:3B:6B:EB:59:99@wlan1: connected, signal strength -71, wants bridge
00:10:51 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -46
00:11:18 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
00:11:56 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -67
00:12:01 wireless,info DC:3A:5E:95:9B:BF@wlan1: reassociating
00:12:01 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, ok
00:12:01 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -73
00:12:06 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
00:12:28 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
00:12:37 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -67
00:13:25 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
00:13:26 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -67
00:13:28 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
00:13:59 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
00:14:00 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -70
00:17:05 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -52
00:17:10 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, unicast key exchange timeout
00:17:19 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
00:17:44 wireless,info 68:C4:4D:EE:F0:DF@wlan1: connected, signal strength -87
00:17:44 wireless,info 68:C4:4D:EE:F0:DF@wlan2: disconnected, registered to other interface
00:18:01 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -76
00:18:06 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
00:18:20 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -71
00:20:29 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -62
00:25:26 wireless,info 68:C4:4D:EE:F0:DF@wlan1: disconnected, received deauth: sending station leaving (3)
00:25:39 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
00:25:47 wireless,info 68:C4:4D:EE:F0:DF@wlan2: connected, signal strength -78
00:28:09 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
00:29:09 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -62
00:31:50 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -62
00:33:04 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
00:33:41 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -62
00:34:43 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -64
00:36:37 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
00:36:45 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
00:36:50 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -71
00:36:58 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
00:41:46 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
00:41:47 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -64
00:41:52 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
00:42:28 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -63
00:43:26 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
00:43:32 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -67
00:43:59 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -62
00:44:06 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -75
00:44:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
00:44:24 wireless,info 6C:3B:6B:EB:59:99@wlan1: disconnected, group key exchange timeout
00:44:29 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
00:44:35 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -70
00:44:42 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
00:44:42 wireless,info 6C:3B:6B:EB:59:99@wlan1: connected, signal strength -69, wants bridge
00:44:43 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -64
00:47:02 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
00:47:07 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -67
00:49:05 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
00:51:33 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
00:51:39 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -62
00:58:36 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -63
00:59:20 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
00:59:25 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -62
00:59:29 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -79
01:00:36 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
01:04:15 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
01:05:30 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
01:05:31 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -67
01:05:35 wireless,info DC:3A:5E:95:9B:BF@wlan1: reassociating
01:05:35 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, ok
01:05:35 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -59
01:09:41 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
01:09:46 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -61
01:09:51 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -66
01:12:10 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
01:12:16 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -64
01:14:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
01:16:06 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
01:16:24 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -60
01:16:53 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -65
01:19:15 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
01:19:24 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, group key exchange timeout
01:19:24 wireless,info 6C:3B:6B:EB:59:99@wlan1: disconnected, group key exchange timeout
01:19:24 wireless,info E8:DE:27:14:C5:39@wlan1: disconnected, group key exchange timeout
01:19:39 wireless,info 6C:3B:6B:EB:59:99@wlan1: connected, signal strength -65, wants bridge
01:19:46 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -64
01:20:00 wireless,info E8:DE:27:14:C5:39@wlan2: connected, signal strength -65
01:20:16 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -68
01:20:32 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
01:21:10 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -66
01:21:15 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
01:21:33 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -62
01:24:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
01:26:12 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
01:26:18 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -61
01:26:48 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -64
01:26:58 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -62
01:28:41 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
01:31:10 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -66
01:31:55 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
01:32:01 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -58
01:32:06 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
01:32:33 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -63
01:32:36 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
01:32:37 wireless,info DC:3A:5E:95:9B:BF@wlan1: reassociating
01:32:37 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, ok
01:32:37 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -70
01:32:40 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
01:34:36 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
01:34:37 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
01:35:55 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
01:35:55 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -68
01:37:39 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -67
01:39:21 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
01:39:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
01:39:26 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -70
01:40:44 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
01:40:45 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -71
01:41:44 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -66
01:43:01 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
01:43:39 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
01:43:44 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
01:43:46 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
01:44:02 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -71
01:51:20 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -63
01:56:28 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
02:03:30 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -63
02:07:27 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -66
02:08:36 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
02:09:04 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
02:12:32 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -64
02:13:26 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
02:13:35 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
02:13:40 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -59
02:16:29 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -63
02:21:36 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
02:24:24 wireless,info 10:02:B5:B0:AD:47@wlan2: disconnected, group key exchange timeout
02:28:10 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -69
02:29:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
02:33:33 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -66
02:34:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
02:41:05 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
02:41:10 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -62
02:41:15 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -62
02:44:55 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -63
02:46:23 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
02:47:47 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
02:47:53 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -63
02:49:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
02:51:07 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
02:51:08 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -58
02:53:25 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -63
02:54:24 wireless,info 00:0F:60:08:1F:5B@wlan1: disconnected, group key exchange timeout
02:54:24 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, group key exchange timeout
02:54:28 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -66
02:56:09 wireless,info 00:0F:60:08:1F:5B@wlan1: connected, signal strength -53
02:56:14 wireless,info 00:0F:60:08:1F:5B@wlan1: disconnected, unicast key exchange timeout
02:56:15 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
02:56:38 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -70
02:58:35 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
02:59:25 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -66
03:04:24 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, group key exchange timeout
03:04:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
03:04:36 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -64
03:07:12 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -62
03:10:22 wireless,info 00:0F:60:08:1F:5B@wlan1: connected, signal strength -55
03:12:23 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
03:15:39 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -64
03:17:00 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
03:17:19 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -63
03:22:30 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
03:31:02 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -64
03:32:36 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
03:34:45 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -62
03:36:05 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -70
03:39:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
03:39:50 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
03:46:38 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -64
03:48:09 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
03:50:55 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
03:50:56 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
03:51:43 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -64
03:52:42 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
03:52:48 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -64
03:55:40 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
03:55:46 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -63
04:04:20 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -61
04:04:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
04:04:24 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, group key exchange timeout
04:04:28 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
04:07:16 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -80
04:09:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
04:09:29 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
04:19:36 wireless,info 68:C4:4D:EE:F0:DF@wlan1: connected, signal strength -78
04:19:37 wireless,info 68:C4:4D:EE:F0:DF@wlan2: disconnected, registered to other interface
04:28:35 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -62
04:33:40 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
04:34:46 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -65
04:40:34 wireless,info 68:C4:4D:EE:F0:DF@wlan1: disconnected, received deauth: sending station leaving (3)
04:40:37 wireless,info 68:C4:4D:EE:F0:DF@wlan2: connected, signal strength -82
04:47:01 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -62
04:52:10 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
04:56:33 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -65
05:01:40 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
05:10:05 wireless,info B8:A1:75:48:3C:29@wlan1: connected, signal strength -64
05:10:10 wireless,info B8:A1:75:48:3C:29@wlan1: disconnected, unicast key exchange timeout
05:10:42 wireless,info B8:A1:75:48:3C:29@wlan1: connected, signal strength -76
05:11:48 wireless,info 68:C4:4D:EE:F0:DF@wlan1: connected, signal strength -81
05:11:51 wireless,info 68:C4:4D:EE:F0:DF@wlan2: disconnected, registered to other interface
05:14:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
05:14:37 wireless,info B8:A1:75:48:3C:29@wlan1: disconnected, received disassoc: sending station leaving (8)
05:14:38 wireless,info B8:A1:75:48:3C:29@wlan1: connected, signal strength -75
05:16:33 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -72
05:16:48 wireless,info B8:A1:75:48:3C:29@wlan1: disconnected, received disassoc: sending station leaving (8)
05:17:48 wireless,info B8:A1:75:48:3C:29@wlan1: connected, signal strength -69
05:17:53 wireless,info B8:A1:75:48:3C:29@wlan1: disconnected, unicast key exchange timeout
05:18:04 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
05:18:25 wireless,info B8:A1:75:48:3C:29@wlan1: connected, signal strength -86
05:19:48 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
05:19:48 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
05:20:17 wireless,info 68:C4:4D:EE:F0:DF@wlan1: disconnected, received deauth: sending station leaving (3)
05:20:26 wireless,info 68:C4:4D:EE:F0:DF@wlan2: connected, signal strength -77
05:22:44 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -63
05:23:35 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -75
05:25:54 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
05:25:54 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -62
05:27:52 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
05:31:33 wireless,info 68:C4:4D:EE:F0:DF@wlan1: connected, signal strength -84
05:31:33 wireless,info 68:C4:4D:EE:F0:DF@wlan2: disconnected, registered to other interface
05:44:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
05:46:52 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -64
05:48:56 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -64
05:49:54 wireless,info 68:C4:4D:EE:F0:DF@wlan1: disconnected, received deauth: sending station leaving (3)
05:49:57 wireless,info 68:C4:4D:EE:F0:DF@wlan1: connected, signal strength -78
05:50:02 wireless,info 68:C4:4D:EE:F0:DF@wlan1: disconnected, received deauth: sending station leaving (3)
05:50:09 wireless,info 68:C4:4D:EE:F0:DF@wlan2: connected, signal strength -81
05:54:05 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
05:55:14 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
05:56:23 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -64
05:56:28 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
05:56:39 wireless,info 68:C4:4D:EE:F0:DF@wlan1: connected, signal strength -80
05:56:42 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -71
05:56:42 wireless,info 68:C4:4D:EE:F0:DF@wlan2: disconnected, registered to other interface
05:56:45 wireless,info 68:C4:4D:EE:F0:DF@wlan1: disconnected, received deauth: sending station leaving (3)
05:56:47 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
05:56:48 wireless,info 68:C4:4D:EE:F0:DF@wlan2: connected, signal strength -78
05:56:49 wireless,info B8:A1:75:48:3C:29@wlan1: disconnected, extensive data loss
05:57:00 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -74
05:57:05 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
05:57:22 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
05:57:23 wireless,info DC:3A:5E:95:9B:BF@wlan2: connected, signal strength -77
06:01:07 wireless,info 68:C4:4D:EE:F0:DF@wlan1: connected, signal strength -78
06:01:07 wireless,info 68:C4:4D:EE:F0:DF@wlan2: disconnected, registered to other interface
06:02:37 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -73
06:03:37 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
06:04:01 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -65
06:09:12 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
06:13:16 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -62
06:16:31 wireless,info 68:C4:4D:EE:F0:DF@wlan1: disconnected, received deauth: sending station leaving (3)
06:16:39 wireless,info 68:C4:4D:EE:F0:DF@wlan2: connected, signal strength -79
06:17:02 wireless,info 68:C4:4D:EE:F0:DF@wlan1: connected, signal strength -73
06:17:03 wireless,info 68:C4:4D:EE:F0:DF@wlan2: disconnected, registered to other interface
06:18:00 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -75
06:18:21 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
06:19:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
06:23:34 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -80
06:24:23 wireless,info 68:C4:4D:EE:F0:DF@wlan1: disconnected, received deauth: sending station leaving (3)
06:24:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
06:24:34 wireless,info 68:C4:4D:EE:F0:DF@wlan1: connected, signal strength -72
06:26:38 wireless,info 68:C4:4D:EE:F0:DF@wlan1: disconnected, received deauth: sending station leaving (3)
06:26:41 wireless,info 68:C4:4D:EE:F0:DF@wlan2: connected, signal strength -83
06:33:36 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -87
06:41:37 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -62
06:44:24 wireless,info 6C:3B:6B:EB:59:99@wlan1: disconnected, group key exchange timeout
06:44:29 wireless,info 6C:3B:6B:EB:59:99@wlan1: connected, signal strength -65, wants bridge
06:46:41 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
06:49:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
06:49:24 wireless,info 6C:3B:6B:EB:59:99@wlan1: disconnected, group key exchange timeout
06:49:26 wireless,info 6C:3B:6B:EB:59:99@wlan1: connected, signal strength -68, wants bridge
06:49:34 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -76
06:54:24 wireless,info 00:0F:60:08:1F:5B@wlan1: disconnected, group key exchange timeout
06:54:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
06:54:24 wireless,info 6C:3B:6B:EB:59:99@wlan1: disconnected, group key exchange timeout
06:54:28 wireless,info 6C:3B:6B:EB:59:99@wlan1: connected, signal strength -67, wants bridge
06:54:54 wireless,info 00:0F:60:08:1F:5B@wlan1: connected, signal strength -55
07:00:00 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -72
07:00:32 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
07:00:33 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -73
07:01:08 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
07:01:21 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -79
07:08:28 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -62
07:09:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
07:09:25 wireless,info E8:DE:27:14:C5:39@wlan2: reassociating
07:09:25 wireless,info E8:DE:27:14:C5:39@wlan2: disconnected, ok
07:09:25 wireless,info E8:DE:27:14:C5:39@wlan2: connected, signal strength -65
07:11:52 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -70
07:13:59 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, received disassoc: sending station leaving (8)
07:16:38 wireless,info 68:C4:4D:EE:F0:DF@wlan1: connected, signal strength -84
07:16:41 wireless,info 68:C4:4D:EE:F0:DF@wlan2: disconnected, registered to other interface
07:16:57 wireless,info 68:C4:4D:EE:F0:DF@wlan2: connected, signal strength -87
07:16:57 wireless,info 68:C4:4D:EE:F0:DF@wlan1: disconnected, registered to other interface
07:17:05 wireless,info 68:C4:4D:EE:F0:DF@wlan2: disconnected, extensive data loss
07:19:24 wireless,info 00:0F:60:08:1F:5B@wlan1: disconnected, group key exchange timeout
07:19:24 wireless,info 6C:3B:6B:EB:59:99@wlan1: disconnected, group key exchange timeout
07:19:24 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
07:19:26 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -58
07:19:26 wireless,info 6C:3B:6B:EB:59:99@wlan1: connected, signal strength -66, wants bridge
07:19:56 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
07:19:58 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -55
07:20:10 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
07:20:18 wireless,info 00:0F:60:08:1F:5B@wlan1: connected, signal strength -54
07:20:55 wireless,info 2C:F0:A2:1F:56:4B@wlan2: connected, signal strength -61
07:24:24 wireless,info 2C:F0:A2:1F:56:4B@wlan2: disconnected, group key exchange timeout
08:52:30 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -65
08:53:11 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, received deauth: sending station leaving (3)
08:54:58 wireless,info 2C:F0:A2:1F:56:4B@wlan1: connected, signal strength -79
08:56:18 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -76
08:56:51 wireless,info E8:DE:27:14:C5:39@wlan2: disconnected, extensive data loss
08:57:22 wireless,info 10:02:B5:B0:AD:47@wlan2: connected, signal strength -70
08:57:30 wireless,info E8:DE:27:14:C5:39@wlan2: connected, signal strength -62
09:39:09 system,info verified routeros-mipsbe-6.41rc52.npk
09:39:09 system,info installed routeros-mipsbe-6.41rc52
09:39:09 system,info router rebooted
09:39:12 bridge,info "br1" mac address changed to F6:20:18:E8:60:F6
09:39:15 wireless,info F4:30:B9:B3:0F:ED@wlan1: connected, signal strength -59
09:39:16 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -66
09:39:16 wireless,info 6C:3B:6B:EB:59:99@wlan1: connected, signal strength -69, wants bridge
09:39:21 wireless,info 00:0F:60:08:1F:5B@wlan1: connected, signal strength -54
09:39:23 wireless,info B8:3E:59:B3:9B:0B@wlan2: connected, signal strength -46
09:39:24 interface,info ether1 link up (speed 1G, full duplex)
09:39:33 wireless,info E8:DE:27:14:C5:39@wlan2: connected, signal strength -65
09:40:00 wireless,info E8:DE:27:14:C5:39@wlan2: disconnected, received deauth: sending station leaving (3)
09:40:11 system,info,account user admin logged in from 10.211.11.11 via ssh
09:40:13 wireless,info 10:02:B5:B0:AD:47@wlan2: connected, signal strength -70
09:41:47 system,info cloud change time Nov/07/2017-09:40:30 => Nov/07/2017-09:41:47
09:43:21 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, received disassoc: sending station leaving (8)
09:43:27 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -70
09:44:37 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -68
09:44:42 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, unicast key exchange timeout
09:44:46 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -70
09:44:51 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, unicast key exchange timeout
09:45:13 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -73
09:45:36 wireless,info F4:30:B9:B3:0F:ED@wlan1: disconnected, group key exchange timeout
09:45:36 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, group key exchange timeout
09:45:36 wireless,info 6C:3B:6B:EB:59:99@wlan1: disconnected, group key exchange timeout
09:45:36 wireless,info 84:10:0D:B0:12:8F@wlan1: disconnected, group key exchange timeout
09:45:51 wireless,info 6C:3B:6B:EB:59:99@wlan1: connected, signal strength -69, wants bridge
09:45:55 wireless,info 84:10:0D:B0:12:8F@wlan1: connected, signal strength -79
09:46:00 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -66
09:46:05 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
09:46:46 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -63
09:46:51 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
09:48:18 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -72
09:48:23 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
09:49:04 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
09:49:09 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
09:49:22 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -63
09:49:27 wireless,info DC:3A:5E:95:9B:BF@wlan1: disconnected, unicast key exchange timeout
09:49:41 wireless,info DC:3A:5E:95:9B:BF@wlan1: connected, signal strength -65
RouterOS 6.41rc52 ships with firmware version 6.41rc50... So looks like nothing changed except the version bump.For me the more important question about boot firmware is: Will the firmware version change with every RouterOS release even if no changes are made? Suppose you installed RouterOS 6.41, then upgraded firmware to 6.41. RouterOS 6.41.1 ships with no changes to the firmware. Is the available firmware version 6.41 or 6.41.1?
Or people had other RADIUS services (devices) connecting to it. You know, because that never happens. #genius. Depending on the IOS version Cisco will timeout at 5 seconds. MikroTik employees. If you are confronted with the choice between allowing something to be configurable with a sensible default vs a static unchanging value always choose configurable.RADIUS timeout value was reduced due to the fact that there is no point of higher value than 3s. Neither of RouterOS RADIUS services would wait more than 3s for a reply from RADIUS server. If you had value higher than 3 seconds, then either configuration will work with timeout set to 3s or it was not working properly even with higher value.
Anyway, RADIUS timeout (even set to 3s) is too high and requires debugging and network improvements since router should not wait so long for a reply from RADIUS server.
I've upgraded a mAP-Lite from 6.40.4 to 6.41rc52.RouterOS 6.41rc52 ships with firmware version 6.41rc50... So looks like nothing changed except the version bump.For me the more important question about boot firmware is: Will the firmware version change with every RouterOS release even if no changes are made? Suppose you installed RouterOS 6.41, then upgraded firmware to 6.41. RouterOS 6.41.1 ships with no changes to the firmware. Is the available firmware version 6.41 or 6.41.1?
Oh, funny... I have a system that is running RouterOS 6.41rc52, with current and upgrade firmware at 6.41rc50. Started a firmware upgrade, after a reboot I can confirm your results.I've upgraded a mAP-Lite from 6.40.4 to 6.41rc52.RouterOS 6.41rc52 ships with firmware version 6.41rc50... So looks like nothing changed except the version bump.For me the more important question about boot firmware is: Will the firmware version change with every RouterOS release even if no changes are made? Suppose you installed RouterOS 6.41, then upgraded firmware to 6.41. RouterOS 6.41.1 ships with no changes to the firmware. Is the available firmware version 6.41 or 6.41.1?
The firmware prior to the upgrade was on v3.41.
So it showed me that the upgrade firmware is 6.41rc50.
But after I upgraded the firmware I got this:
Current Firmware: 6.41rc52
Upgrade Firmware: 6.41rc50
http://prntscr.com/h7w38h
Forum police @andirys will probably ask you to post in feature request.When do we get LACP with Hardware offload in this new bridge implementation in routeros on switch devices such as CRS326-24G-2S+ and CRS-317-1G-16s+
Creating a bond and attaching it to the bride is done in software now and good know the cpu's in the switches is weak as hell.
How this works? Firewall is not using included list.*) interface - added option to join and exclude "/interface list" from one and another;
The default firewall is using lists now. When you have upgraded from versions previous to 6.40 all the time and neverHow this works? Firewall is not using included list.*) interface - added option to join and exclude "/interface list" from one and another;
you need to add your bridge interface to tagged ports.I tryed to configure VLANs using the bridge hw offloading feature (CRS326). Basically:
/interface bridge port
add bridge=bridge interface=ether2 pvid=200
...
add bridge=bridge tagged=... untagged=ether02,.. vlan-ids=200
...
/interface bridge set bridge vlan-filtering=yes
I stuck in two tasks.
A) How to I secure the ports like "/interface ethernet switch port set ether3 vlan-mode=secure vlan-header=always-strip" on https://wiki.mikrotik.com/wiki/Manual:S ... Offloading?
I tried
/interface bridge port add bridge=bridge frame-types=admit-only-untagged-and-priority-tagged ingress-filtering=yes interface=ether03 pvid=200
but I do not really understand if it does what I want.
B) I cannot access the RouterOS using a VLAN port. But I didn't found, how to configure VLAN for the switch host port?
Devices in the Wireless Wire kit come with Level 3 licenses - will it work with more than one client, or is it necessary to buy a Level 4 license to test 60GHz PtMP?*) w60g - general work on PtMP implementation for 60 GHz connections;
Same here, 951g2hndI've upgraded a mAP-Lite from 6.40.4 to 6.41rc52.RouterOS 6.41rc52 ships with firmware version 6.41rc50... So looks like nothing changed except the version bump.For me the more important question about boot firmware is: Will the firmware version change with every RouterOS release even if no changes are made? Suppose you installed RouterOS 6.41, then upgraded firmware to 6.41. RouterOS 6.41.1 ships with no changes to the firmware. Is the available firmware version 6.41 or 6.41.1?
The firmware prior to the upgrade was on v3.41.
So it showed me that the upgrade firmware is 6.41rc50.
But after I upgraded the firmware I got this:
Current Firmware: 6.41rc52
Upgrade Firmware: 6.41rc50
http://prntscr.com/h7w38h
routerboard: yes
model: 951G-2HnD
serial-number: 4F4********
firmware-type: ar9344
factory-firmware: 3.10
current-firmware: 6.41rc52
upgrade-firmware: 6.41rc50
Firmware type: ar7240
Factory firmware: 3.02
Current firmware: 3.33
Update firmware:
Possibly a read-only property "upgrade-available" is the easiest way to solve this?Oh, funny... I have a system that is running RouterOS 6.41rc52, with current and upgrade firmware at 6.41rc50. Started a firmware upgrade, after a reboot I can confirm your results.
Well, that will make my upgrade notification scripts go crazy... :-p
This makes no sense to me whatsoever. We have had it happen several times (in a particular scenario documented further below) where we had the timeout at first set to 3000 ms and the customer could not connect (due to the unusually high latency for bidirectional satellite Internet), but immediately after increasing the timeout, the customer connected successfully (after repeated automated connection attempts up until the instant of change). You are saying this is a coincidence? It seems really hard to believe given how many times it failed before making the change (several hours) and how immediately the change corrected the issue (after hours of trying to connect every minute and failing, the first connection after the change (30 seconds later) was successful).RADIUS timeout value was reduced due to the fact that there is no point of higher value than 3s. Neither of RouterOS RADIUS services would wait more than 3s for a reply from RADIUS server. If you had value higher than 3 seconds, then either configuration will work with timeout set to 3s or it was not working properly even with higher value.
Anyway, RADIUS timeout (even set to 3s) is too high and requires debugging and network improvements since router should not wait so long for a reply from RADIUS server.
It is not just one location - we have 15 such locations. We would need 15 RADIUS servers. These locations have no air conditioning and so the internal shelter goes up to 40C in the summer and down to -30C in the winter. Local RADIUS server is NOT a good idea.I would say your network could be redesigned so that the RADIUS requests do not have to go over the satellite. Apparently you are using the MikroTik as a local access concentrator for several customers that then use the same satellite link. It would help a lot to have the RADIUS service local to that location. Of course usermanager is very limited, but a small computer with a RADIUS server and maybe some other services for the customer (a webproxy, a local webserver, VoIP PBX, etc) could help the customers living with this high-latency link.
Ignoring the part about RADIUS taking more than 3 seconds being unacceptable for the time being, as described by strods, this change should not have resulted in a regression of functionality, as the RADIUS client inside routerOS was not honoring timeouts above 3 seconds to begin with. Based on what mducharme says above, this does not appear to be the case.RADIUS timeout value was reduced due to the fact that there is no point of higher value than 3s. Neither of RouterOS RADIUS services would wait more than 3s for a reply from RADIUS server. If you had value higher than 3 seconds, then either configuration will work with timeout set to 3s or it was not working properly even with higher value.
Anyway, RADIUS timeout (even set to 3s) is too high and requires debugging and network improvements since router should not wait so long for a reply from RADIUS server.
Regarding all this with firmware, i have found this in changelog in RC channel:I have installed it on an old RB750 I use for some test.
It shows:I.e. there is nothing after upgrade firmware and the upgrade button does nothing (no log entry).Code: Select allFirmware type: ar7240 Factory firmware: 3.02 Current firmware: 3.33 Update firmware:
Edit: I installed 6.40.5, upgraded the firmware to 3.41 from there, then went back to 6.41 (2 partitions on the router...) and
the issue is still the same.
Exactly, my own observations of the behavior of earlier versions do not jibe with what strods claims to be the case. It seems extremely unlikely that it was coincidental that the issue vanished when I made the change, given the circumstances.He reports that he's seeing different behavior with the timeout hard-set to 3sec, when compared to the 6sec available before. This is a regression in functionality and directly contrary to the information given by MT (strods) - in short, this is a bug. Either MT themselves are incorrect about the behaviour of the client when given timeouts above 3s (and mducharme's 6s timeout on older FW versions was making a difference), or something else has changed that otherwise breaks his admittedly unusual but completely valid configuration.
No I haven't, only because I would have to upgrade to 6.41 at one of those satellite sites (15 of our 45 sites are connected via satellite). However I don't need a test to tell me what effect limiting the maximum value will have when we are currently using 6000 ms, and given my previous experiences. We could maybe get by with 5000ms, possibly even 4000ms, but if the RADIUS server thinks the customer is still logged in, it will only authenticate in 3000ms if the stars are in perfect alignment due to the extra time required to pull the list of logged in customers. Due to the power requirements of the satellite amplifiers they cannot be connected to the UPS, so when the power goes down at the site (some sites are on unreliable diesel) the satellite feed goes down immediately. If customers log off during this time (common b/c they usually lose power as well), the RADIUS disconnect notification doesn't make it to the RADIUS server because, with the satellite link down, there is no way for the packet to reach its destination. When the site comes back up again, the RADIUS server sees the customers trying to log in again and it thinks they are already logged in, so before it sends the 'accept' or 'reject' it has to go to the router and check to see if they actually are still logged in. Customers sometimes share their PPPoE credentials with friends to try to give them free service, so this check is necessary to protect against that.mducharme: Have you opened a support ticket for this regression & provided supout.rifs etc? This isn't an official support channel, and it sounds like you should be talking to support if you aren't already.
You have 15 sites of a problematic type for which it costs $1000 to make a support visit and you don't have a way to test a similar site from home (a subscription to the same satellite service)?No I haven't, only because I would have to upgrade to 6.41 at one of those satellite sites (15 of our 45 sites are connected via satellite).
The dishes are 2.4 or 3.8 meters, so they are big (larger than a home satellite service). It is not easy like putting up an Xplornet dish on a home, these are very big and very heavy, they cannot be roof or wall mounted, unless maybe the roof was concrete and very thick, able to support the weight. So the dish would generally need to be on the ground with a concrete pad for stability and fencing to avoid people standing in front of the beam. Even if we had a place to install such a thing in our downtown urban office building, each dish has its own upload channel, so there would need to be one assigned to a "test dish" but all are in use since actual sites are priority. Therefore to operate a test dish with no channels we would need to shut down one of the 15 sites to free up a channel to bring up a test dish. It would be great to have a test system, it would make certain things easier, but it is just not feasible for all those reasons, so we have lived without it.You have 15 sites of a problematic type for which it costs $1000 to make a support visit and you don't have a way to test a similar site from home (a subscription to the same satellite service)?
Really? It all does not seem very professional...
Don't need a satellite dish to emulate the behaviour of a typical satellite link:You have 15 sites of a problematic type for which it costs $1000 to make a support visit and you don't have a way to test a similar site from home (a subscription to the same satellite service)?
125ms need to reach satellite and 125ms to reach earth. Why you need HUGE timeout ? You bounce signal multiple times to orbit and back?We could maybe get by with 5000ms, possibly even 4000ms, but if the RADIUS server thinks the customer is still logged in, it will only authenticate in 3000ms if the stars are in perfect alignment due to the extra time required to pull the list of logged in customers.
You need only ONE snmpget to understand what happens with equipment and connected users - check sysUpTimeInstance (.1.3.6.1.2.1.1.3.0) and if it goes back - assume "power lost, all users disconnected" and drop it manually in radius. it's not rocket science.Due to the power requirements of the satellite amplifiers they cannot be connected to the UPS, so when the power goes down at the site (some sites are on unreliable diesel) the satellite feed goes down immediately. If customers log off during this time (common b/c they usually lose power as well), the RADIUS disconnect notification doesn't make it to the RADIUS server because, with the satellite link down, there is no way for the packet to reach its destination. When the site comes back up again, the RADIUS server sees the customers trying to log in again and it thinks they are already logged in, so before it sends the 'accept' or 'reject' it has to go to the router and check to see if they actually are still logged in. Customers sometimes share their PPPoE credentials with friends to try to give them free service, so this check is necessary to protect against that.
We try to centralize as much as possible and minimize the equipment at the site, less equipment means less that can break - it is cheaper for me to fly to Hawaii than to go to some of our sites. The central RADIUS server is a necessity for us, and it is just not viable to optimize it more than we already have. We have already had to change some FreeRADIUS code to use snmpbulkwalk instead of snmpwalk to avoid needing 25-30 second timeouts, and I do not think we can reduce this any further given our previous efforts to provide QoS to prioritize RADIUS packets.
Ping to the site across the satellite link is at least 600ms round trip, so 300ms each way. I have never seen latency drop below that. You are suggesting that round trip latency should be 250 ms or slightly higher, but that is just not realistic.125ms need to reach satellite and 125ms to reach earth. Why you need HUGE timeout ? You bounce signal multiple times to orbit and back?
That requires extra programming, and won't work in some scenarios. The RADIUS server itself (FreeRADIUS) already has the SNMP check built in to poll the list of interfaces in event that it thinks the customer is already logged in - this did not need to be scripted as it is a built in feature, the RADIUS server does this SNMP check while the NAS is waiting for the 'accept' or 'reject'. What you are describing is an external script that would keep track of the uptime for each router and be able to tell if one went back and just disconnect the sessions for that router. It is certainly possible but such a script would have to be carefully tested. That also wouldn't help with a scenario where the router did not go down but the satellite lost power. A brief power outage would not knock the router offline, so the sysuptime would not go back. Unfortunately this also happens fairly frequently, so a solution that doesn't address this would not help.You need only ONE snmpget to understand what happens with equipment and connected users - check sysUpTimeInstance (.1.3.6.1.2.1.1.3.0) and if it goes back - assume "power lost, all users disconnected" and drop it manually in radius. it's not rocket science.
Sweet. No more Layer 7 for HTTPS blocking*) firewall - added "tls-host" firewall matcher (CLI only);
+1Sweet. No more Layer 7 for HTTPS blocking*) firewall - added "tls-host" firewall matcher (CLI only);
How it works? Which packet matches? Does it support wildcards?
I presume this is just a special case of a Layer 7 with some pre-defined pattern, and only works when SNI is used.Sweet. No more Layer 7 for HTTPS blocking*) firewall - added "tls-host" firewall matcher (CLI only);
How it works? Which packet matches? Does it support wildcards?
It could be an iptables module specific to that function instead of abstracting a L7 filter. Like this https://github.com/Lochnair/xt_tlsI presume this is just a special case of a Layer 7 with some pre-defined pattern, and only works when SNI is used.Sweet. No more Layer 7 for HTTPS blocking*) firewall - added "tls-host" firewall matcher (CLI only);
How it works? Which packet matches? Does it support wildcards?
Any info about this? passive scan has been implemented for a long time*) wireless - added passive scan option for wireless scan mode;
No need for SNI, CN of certificate is in plaintext whether SNI is used or not.I presume this is just a special case of a Layer 7 with some pre-defined pattern, and only works when SNI is used.Sweet. No more Layer 7 for HTTPS blocking*) firewall - added "tls-host" firewall matcher (CLI only);
How it works? Which packet matches? Does it support wildcards?
It's not clear, from the changelog, but: If I remember it right, Mikrotik didn't support passive scan with 802.11ac, only b, g, n. Maybe this is it, at long last.Any info about this? passive scan has been implemented for a long time*) wireless - added passive scan option for wireless scan mode;
At a guess, its based on xt_tls which can support wildcards, see https://github.com/Lochnair/xt_tlsSweet. No more Layer 7 for HTTPS blocking*) firewall - added "tls-host" firewall matcher (CLI only);
How it works? Which packet matches? Does it support wildcards?
If this is it, then we only now have to wait for spectral scan and power adjustment in 802.11ac and we will be seeing sweet dreams.It's not clear, from the changelog, but: If I remember it right, Mikrotik didn't support passive scan with 802.11ac, only b, g, n. Maybe this is it, at long last.Any info about this? passive scan has been implemented for a long time*) wireless - added passive scan option for wireless scan mode;
nkourtzis wrote:Can it possibly be that we approaching the end of v6 development? Just wondering...
Was wondering just the same.. yet ROS still lacks many basic features..Dear all, has the development of ROS slowed down or is it my wrong impresion? One RC sub-version every one to two weeks where it used to be every two to three days and even then, very sparse changelog. Even this thread has become relatively quiet.
Can it possibly be that we approaching the end of v6 development? Just wondering...
Agreed, these are some of the basic features i was talking about.New bridge implementation need:
Hardware LACP bonding.
Hardware setting per port of learning mode for mac-adresses max number and what to do when max is reached and or port/device restarted.
per port ingress and egress hardware rate limiting.
dhcp snooping with guard
arp snooping with guard
Option to hardware block malicious traffic in the above dhcp and arp concept.
In all essence be a real provider switch compairable to other switch vendors.
Other stuff is needed as well but that is for another day and discussion. This is what I think is needed before this new implementation is ready to hit the streets.
New bridge implementation need:
Hardware LACP bonding.
Hardware setting per port of learning mode for mac-adresses max number and what to do when max is reached and or port/device restarted.
per port ingress and egress hardware rate limiting.
dhcp snooping with guard
arp snooping with guard
Option to hardware block malicious traffic in the above dhcp and arp concept.
In all essence be a real provider switch compairable to other switch vendors.
Other stuff is needed as well but that is for another day and discussion. This is what I think is needed before this new implementation is ready to hit the streets.
True, now wise to roll up this "breaking" changes in "ordinary" release. Many people used to apply updates without reading out readme-s, or without huge testing, and this will break many setups around the world.I am wondering when they dare to release 6.41 as a "current" version with this risky "New bridge implementation" that will likely cause problems once it is widely deployed into many different field configurations (that combine VLAN tagging on switch and bridge now).
You may be right in that this could actually be released as part of "v7" so people are aware there are many changes and testing (rather than routine updating) is required.
+1In their shoes I would concurrently release a new 6.40.x in bugfix and stable, forcing all system to switch to bugfix channel as update default (6.40.x should then live in bugfix for long time).
For admins ready to 6.41 it would be simple enough as manually switch to current again; in this way all systems upgraded in a automatic/silent mode would be quite safe.
It would be quite useful to create another forum topic to let users report their setups that failed to convert from master-slave to new bridge implementation. At least, this may be good to add these situation into config converter.For admins ready to 6.41 it would be simple enough as manually switch.
I noticed that too. But 6.41 is a big step, with bridge hardware offloading and whatnot. I believe they are testing the (numerous) bugs already found, and preparing for another RC - or the gold one.Dear mikrotik, why has development slowed down? In the past we used to see a new rc every 3-5 days.
Maybe renaming the V6.41RC to V7, since they introduced many new features.What was the highest rc version ?
I also think they are fixing bugs, tweaking some functionality
Or maybe they are focus working on version 7 [emoji16]
Enviado de meu XT1580 usando Tapatalk
That is never going to work! They need to separate some of the changes into subreleases and packages, including RC versions, or this version is never going to materialize.V7 should have new kernel and totally new implementation of some functionalities. Do not skip so far...
What's actually the issue having 6.41 with the new bridge implementation? If it works it works...That is never going to work! They need to separate some of the changes into subreleases and packages, including RC versions, or this version is never going to materialize.V7 should have new kernel and totally new implementation of some functionalities. Do not skip so far...
I vote for releasing a V7 based on 6.41RC with a new kernel (first as an RC), then make that a "current" version and await the reports of all the new minor problems, then (or partly in parallel) release all the "totally new implementations of some functionalities" as optional packages like it was done before with wireless and routing.
So the people interested in new functionality and prepared to be confronted with some bugs can test in parallel with the baseline users.
Yes, if it works... but yesterday I spent quite some time trying to migrate an existing complex configuration consisting ofWhat's actually the issue having 6.41 with the new bridge implementation? If it works it works...
Why not show the configuration in case theres a "bug" and "use-case" that they aren't aware of that isnt working?Yes, if it works... but yesterday I spent quite some time trying to migrate an existing complex configuration consisting ofWhat's actually the issue having 6.41 with the new bridge implementation? If it works it works...
multiple bridges for different VLANs to the new 6.41RC and I have so far been unable to do so.
Ok, to be honest it still worked after merely upgrading it, but with the existing split bridges with VLAN subinterfaces as ports.
I tried to migrate to a single bridge with VLANs inside and several tagged and untagged member ports, and it simply did not work.
So a blind upgrade to 6.41 would probably survive, merely losing the switching (master-port) hardware assistance.
However there is still work to do (maybe on the software, maybe on my configuration skills) before several similar routers can run 6.41.
Well I first want to investigate a bit more in both 6.40 and 6.41 what can be done to first make this config more optimal and then migrate it.Why not show the configuration in case theres a "bug" and "use-case" that they aren't aware of that isnt working?
Good pointDear mikrotik, why has development slowed down? In the past we used to see a new rc every 3-5 days.
Given that routine current update about to introduce new bridge implementation that potentially break router config (and even downgrade won't help since the config will be already broken by autoconvert process), I won't call it "stable" or vote for keeping it up, actually.mikrotik team, no matter how long it takes, ios, junos does not have a weekly update, more are stable, the important thing is that the software stays stable,
so keep it up 8)
Maybe freezing due to the holidays at the end of the year?Good pointDear mikrotik, why has development slowed down? In the past we used to see a new rc every 3-5 days.
Posting some roadmap for hardware development and also for ROS development would be nice replacement for new ROS release.Maybe freezing due to the holidays at the end of the year?Good point :?Dear mikrotik, why has development slowed down? In the past we used to see a new rc every 3-5 days.
Many companies do this.
In Poland we say: "Hit the table and the scissors will make a sound"What's new in 6.41rc61 (2017-Dec-06 08:15): ..
Please explain the process of transformation. Say if I have eth2 as Master-port, and eth3..eth5 as Slaves, and used eth2 in firewall rule, will this rule be changes to one that will use newly-created bridge? Will IP be reassigned from master port to bridge create from these master and its slave ports?What's new in 6.41rc61 (2017-Dec-06 08:15):
+1or at least make the ROS upgrade process to automatically upgrade Routerboot also.
Mostly there are no changes for all but really new devices or hardware. The only thing you might need this upgrade is when you add new hardware (like SFP module) or you can see you MT works unusually bad.without knowing whether there are any changes in the version or not, is not ideal.
I'd like to know a bit more about this change.*) capsman - use "adaptive-noise-immunity" value from CAP local configuration;
ok, but how is the process downgrade?+1or at least make the ROS upgrade process to automatically upgrade Routerboot also.
I believe this is similar to how antenna gain setting is being handled. Simply set the desired value of the adaptive-noise-immunity option in your radio interface configuration before turning CAP mode on, and that value will be used for this particular radio when you join it to your CAPs manager.I'd like to know a bit more about this change.*) capsman - use "adaptive-noise-immunity" value from CAP local configuration;
"firewall - added "tls-host" firewall matcher "
I believe this is similar to how antenna gain setting is being handled. Simply set the desired value of the adaptive-noise-immunity option in your radio interface configuration before turning CAP mode on, and that value will be used for this particular radio when you join it to your CAPs manager.I'd like to know a bit more about this change.*) capsman - use "adaptive-noise-immunity" value from CAP local configuration;
+1MK,
please do You think about it just a few minutes? 6.41rc61 still the same...!
2 years old bug with TX Rate on all smartphones with android. TX Rate is always only 54Mbps but RX Rate is 72.2Mbps-20MHz/1S/SGI.
viewtopic.php?t=102908
+1 it must be repairedMK,
please do You think about it just a few minutes? 6.41rc61 still the same...!
2 years old bug with TX Rate on all smartphones with android. TX Rate is always only 54Mbps but RX Rate is 72.2Mbps-20MHz/1S/SGI.
viewtopic.php?t=102908
+1MK,
please do You think about it just a few minutes? 6.41rc61 still the same...!
2 years old bug with TX Rate on all smartphones with android. TX Rate is always only 54Mbps but RX Rate is 72.2Mbps-20MHz/1S/SGI.
viewtopic.php?t=102908
+1MK,
please can You think about it just a few minutes? 6.41rc61 still the same...!
2 years old bug with TX Rate on all smartphones with android. TX Rate is always only 54Mbps but RX Rate is 72.2Mbps-20MHz/1S/SGI.
viewtopic.php?t=102908
Do you have support output files from older RC where the static bridge ports were working ok? Did you make a new support output file after the upgrade where the bridge ports disappeared?My static ports in all bridges just disappear after reboot on CAPsMAN controller router.
RB2011UAS-2HnD ROS 6.41rc61.
Also on SXT ac, clients are diconnected from time to time (every few minutes). In rc56 was perfect.
New bugs?
/interface bridge
add admin-mac=64:D1:54:DA:33:50 auto-mac=no name=#master protocol-mode=none \
pvid=666 vlan-filtering=yes
/interface ethernet
set [ find default-name=ether2 ] comment="1-10 Cust1 7/8/9/10"
set [ find default-name=ether3 ] comment="1-09 untagged 250 voice proper"
set [ find default-name=ether4 ] comment="reserved Cust1"
set [ find default-name=ether5 ] comment="1-05 Cust2"
set [ find default-name=ether6 ] comment="Reserved Cust2"
set [ find default-name=ether7 ] comment="1-11 Cust3"
set [ find default-name=ether8 ] comment="1-12 Cust3"
set [ find default-name=ether9 ] comment="1-13 Cust3"
set [ find default-name=ether10 ] comment="1-14 Cust3"
set [ find default-name=ether11 ] comment="1-17 Cust3"
set [ find default-name=ether12 ] comment="1-18 Cust3"
set [ find default-name=ether13 ] comment="2-1 Cust4"
set [ find default-name=ether14 ] comment="2-3 Cust4"
set [ find default-name=ether15 ] comment="2-7 Cust4"
set [ find default-name=ether16 ] comment="2-11 Cust4"
set [ find default-name=ether17 ] comment="2-13 Cust4"
set [ find default-name=sfp-sfpplus1 ] speed=1Gbps
/interface vlan
add interface=sfp-sfpplus1 name=s1.250 vlan-id=250
add interface=sfp-sfpplus1 name=s1.550 vlan-id=550
add interface=sfp-sfpplus1 name=s1.552 vlan-id=552
add interface=sfp-sfpplus1 name=s1.553 vlan-id=553
add interface=sfp-sfpplus1 name=s1.554 vlan-id=554
add interface=sfp-sfpplus1 name=s1.666 vlan-id=666
/interface list
add name=MAN
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/interface bridge port
add bridge=#master interface=ether2 pvid=552
add bridge=#master interface=ether3 pvid=250
add bridge=#master interface=ether4 pvid=552
add bridge=#master interface=ether5 pvid=550
add bridge=#master interface=ether6 pvid=550
add bridge=#master interface=ether7 pvid=553
add bridge=#master interface=ether8 pvid=553
add bridge=#master interface=ether9 pvid=553
add bridge=#master interface=ether10 pvid=553
add bridge=#master interface=ether11 pvid=553
add bridge=#master interface=ether12 pvid=553
add bridge=#master interface=ether13 pvid=554
add bridge=#master interface=ether14 pvid=554
add bridge=#master interface=ether15 pvid=554
add bridge=#master interface=ether16 pvid=554
add bridge=#master interface=ether17 pvid=554
add bridge=#master interface=ether18
add bridge=#master interface=ether19
add bridge=#master interface=ether20 pvid=666
add bridge=#master interface=ether21 pvid=666
add bridge=#master interface=ether22 pvid=666
add bridge=#master interface=ether23 pvid=666
add bridge=#master interface=ether24 pvid=666
add bridge=#master interface=sfp-sfpplus2
add bridge=#master interface=ether1 pvid=552
add bridge=#master interface=sfp-sfpplus1
/interface bridge vlan
add bridge=#master tagged=sfp-sfpplus1,sfp-sfpplus2 untagged=ether2,ether4 \
vlan-ids=552
add bridge=#master tagged=sfp-sfpplus1,sfp-sfpplus2 untagged=ether3 vlan-ids=\
250
add bridge=#master tagged=sfp-sfpplus1,sfp-sfpplus2 untagged=ether5,ether6 \
vlan-ids=550
add bridge=#master tagged=sfp-sfpplus1,sfp-sfpplus2 untagged=\
ether7,ether8,ether9,ether10,ether11,ether12 vlan-ids=553
add bridge=#master tagged=sfp-sfpplus1,sfp-sfpplus2 untagged=\
ether13,ether14,ether15,ether16,ether17 vlan-ids=554
add bridge=#master tagged=sfp-sfpplus1 untagged=\
ether20,ether21,ether22,ether23,ether24 vlan-ids=666
/interface list member
add interface=s1.666 list=MAN
add interface=s1.552 list=MAN
/interface bridge
add admin-mac=64:D1:54:DA:33:50 auto-mac=no name=#master protocol-mode=none pvid=666 vlan-filtering=yes
/interface bridge
add fast-forward=no igmp-snooping=no name=bridge priority=0x1000 protocol-mode=none vlan-filtering=yes
/interface vlan
add interface=bridge name=vlan4 vlan-id=4
/ip address
add address=192.168.0.4/24 interface=vlan4 network=192.168.0.0
Do you have support output files from older RC where the static bridge ports were working ok? Did you make a new support output file after the upgrade where the bridge ports disappeared?My static ports in all bridges just disappear after reboot on CAPsMAN controller router.
RB2011UAS-2HnD ROS 6.41rc61.
Also on SXT ac, clients are diconnected from time to time (every few minutes). In rc56 was perfect.
New bugs?
About wireless disconnection Only the AP was upgraded the to the newest RC version or also the Clients as well? What are the disconnect messages? Do you have a support output files?
Send all that info to support@mikrotik.com
Thanks bjornr,Sure thing!
The docs I referenced uses pvid=1 for the bridge and for holding the VLANs, so my bridge sets no pvid. Instead, I've assigned the IP directly to a VLANCode: Select all/interface bridge add fast-forward=no igmp-snooping=no name=bridge priority=0x1000 protocol-mode=none vlan-filtering=yes
No, my VLANs (and their IP addresses) are defined on an RB850G connected to the CRS326.Thanks bjornr,Sure thing!
The docs I referenced uses pvid=1 for the bridge and for holding the VLANs, so my bridge sets no pvid. Instead, I've assigned the IP directly to a VLANCode: Select all/interface bridge add fast-forward=no igmp-snooping=no name=bridge priority=0x1000 protocol-mode=none vlan-filtering=yes
Yesterday I played around with your example, it looks like you have VLAN's originating in the ROS641.rc61 and pushing them forward.
Your CCR1009 running 6.40 should be configured with either software based bridges for VLANs or the Ethernet switch per normal methods.Thanks bjornr,Sure thing!
The docs I referenced uses pvid=1 for the bridge and for holding the VLANs, so my bridge sets no pvid. Instead, I've assigned the IP directly to a VLANCode: Select all/interface bridge add fast-forward=no igmp-snooping=no name=bridge priority=0x1000 protocol-mode=none vlan-filtering=yes
Yesterday I played around with your example, it looks like you have VLAN's originating in the ROS641.rc61 and pushing them forward. In my usecase I have the VLAN's originating in a previous hop. In the updated diagram below I have further clarified. I have tried to play with two scenarios's.
In scenario 1 I have added the interface vlans to the physical port that carries the VLAN's from the previous hop. In this configuration, devices in my management lan can see the gateway at CCR1009 and mac winbox and ip winbox. I can set a dhcpclient on the vlan interface 666 on crs326. From the management vlan I cannot see mac winbox, cannot access mac winbox or ip winbox the dhcp received IP. I can only manage through Romon to the CCR1009 and connect back to the CRS326
In scenario 2 I have added the vlans as you said, to the bridge and removed them from sfp1. In this scenario my management vlan hosts can access a fixed ip set on vlan 666 interface and mac winbox. The dhcp client does not work anymore, there is no communication with CCR1009. If I try to add vlan 666 to sfp1 I stil l cannot access CCR1009. However in IP neigbors I do see the CCR1009.
For now that leaves me with scenario 1 since that I a usable scanario with Romon. Am wondering is others also have experience here with this problem?
Here you can find my updated diagram: https://superyupkent.stackstorage.com/s/IA9etV8NMlY70Wy
Thanks Alex
/interface bridge add name=br1 protocol-mode=stp priority=0x1000
/interface vlan add interface=br1 vlan-id=552 name=br1-vlan552
/interface vlan add interface=br1 vlan-id=666 name=br1-vlan666
/ip address interface=br1-vlan552 address=10.5.52.1/24
/ip address interface=br1-vlan666 address=172.25.20.1/24
/interface bridge port add bridge=br1 interface=eth-crs326-1
/interface bridge port add bridge=br1 interface=eth-crs326-2
/interface bridge port add bridge=br1 interface=eth-crs326-3
/interface bridge add name=br1 vlan-filtering=yes priority=0x3000 protocol-mode=stp pvid=1
/interface bridge vlan set [ find where vlan-ids=1 and bridge=br1 ] untagged=br1 tagged=""
/interface bridge vlan add bridge=br1 vlan-ids=552 tagged=br1,sfp1 untagged=""
/interface bridge vlan add bridge=br1 vlan-ids=666 tagged=br1,sfp1 untagged=""
/interface vlan add interface=br1 vlan-id=552 name=br1-vlan552
# ^^ add your dhcp client or ip address to the VLAN interface of br1-vlan552
I'm sorry. It seems the problem only occurs when I turn on the hw-offload.Using or not using the hw-offload does not affect the situation.
I have described my efforts and I have problems as well, also in a configuration where different VLANs are in different bridges in the 6.40 version and I tried migration to 6.41RC.I read the thread and did not find the description of a similar problem. It surprises me.
So is this list of DNS servers configured in the DHCP Networks for this DHCP Server/Pool? I'm running a couple systems on 6.41rc61 and have DHCP Servers on two interfaces that assign DNS to the clients. I'm not having an issue with it.Support,
I have found an issue with v6.41rc61 and DHCP. I have several networks and ip pools configured but have found that upgrading to the rc61 build the dhcp server is handing out DNS server that the ccr1036 is using. This is not the same list of DNS server client should use. I have test reverted to rc58 and 6.40.5 to correct the issue. Loading rc61 will recreate the issue.
Thank you,
Planetcoop
Support,
I have found an issue with v6.41rc61 and DHCP. I have several networks and ip pools configured but have found that upgrading to the rc61 build the dhcp server is handing out DNS server that the ccr1036 is using. This is not the same list of DNS server client should use. I have test reverted to rc58 and 6.40.5 to correct the issue. Loading rc61 will recreate the issue.
Thank you,
Planetcoop
I believe I also have run into this behavior. I had two different routers (configured similarly) both have several (but not all) ports disappear (not in print or export) from the bridge on system reboot. Though after adding them back and rebooting again, they were in there.Do you have support output files from older RC where the static bridge ports were working ok? Did you make a new support output file after the upgrade where the bridge ports disappeared?My static ports in all bridges just disappear after reboot on CAPsMAN controller router.
RB2011UAS-2HnD ROS 6.41rc61.
Also on SXT ac, clients are diconnected from time to time (every few minutes). In rc56 was perfect.
New bugs?
About wireless disconnection Only the AP was upgraded the to the newest RC version or also the Clients as well? What are the disconnect messages? Do you have a support output files?
Send all that info to support@mikrotik.com
Uldis, sorry, I have not support files. Right now I'm trying do several reboot with disappeared ports after another upgrade to rc61, but ports still exists. I have made suppout files with working configurations on both versions. Maybe time of working is to short. Next reboot will be done tomorrow.
SXT ac have actual this same problem on rc56 - maybe channel overlapping with diffrent networks - I will give a feedback.
yup, that is the issue....Support,
I have found an issue with v6.41rc61 and DHCP. I have several networks and ip pools configured but have found that upgrading to the rc61 build the dhcp server is handing out DNS server that the ccr1036 is using. This is not the same list of DNS server client should use. I have test reverted to rc58 and 6.40.5 to correct the issue. Loading rc61 will recreate the issue.
Thank you,
Planetcoop
See topic at link viewtopic.php?f=1&t=128454
### CCR1036 ###
/interface bridge
add name=bridge1 vlan-filtering=no
/interface bridge port
add bridge=bridge1 interface=sfpplus1
/interface bridge vlan
add bridge=bridge1 tagged=bridge1,sfpplus1 vlan-ids=10
/interface vlan
add interface=bridge1 vlan-id=10 name=vlan10
/interface bridge
set bridge1 vlan-filtering=yes
### CRS226 ###
/interface bridge
add name=bridge1 vlan-filtering=no
/interface bridge port
add bridge=bridge1 interface=sfpplus1
add bridge=bridge1 interface=ether1
/interface ethernet switch ingress-vlan-translation
add ports=ether1 customer-vid=0 new-customer-vid=10 sa-learning=yes
/interface ethernet switch egress-vlan-tag
add tagged-ports=switch1-cpu,sfpplus1 vlan-id=10
/interface ethernet switch vlan
add ports=switch1-cpu,sfpplus1,ether1 vlan-id=10 learn=yes
/interface ethernet switch
set drop-if-invalid-or-src-port-not-member-of-vlan-on-ports=ether1
/interface vlan
add interface=bridge1 vlan-id=10 name=vlan10
While not directly answering your question. Please do not use overlapping IP space for your VPN. I know some of the wiki articles set it up that way. By changing to a non overlapping IP space it will just work, no Proxy-ARP magic needed.Hi,
is proxy-arp on v6.41rc61 working? I have CCR1036 directly connected to CRS226. I have vlan trunk on bridge between them. On CRS226 I have acces port and connected device with IP, i can ping IP from router and switch.
I configured L2TP/IPsec and OVPN services, both are working, but I can't ping the device IP from VPN client. Where should be problem? I tried to setup proxy-arp on bridge, on vlan interfaces on router and also on switch, but nothing helped.
Pavel
Hi idlemind,While not directly answering your question. Please do not use overlapping IP space for your VPN. I know some of the wiki articles set it up that way. By changing to a non overlapping IP space it will just work, no Proxy-ARP magic needed.Hi,
is proxy-arp on v6.41rc61 working? I have CCR1036 directly connected to CRS226. I have vlan trunk on bridge between them. On CRS226 I have acces port and connected device with IP, i can ping IP from router and switch.
I configured L2TP/IPsec and OVPN services, both are working, but I can't ping the device IP from VPN client. Where should be problem? I tried to setup proxy-arp on bridge, on vlan interfaces on router and also on switch, but nothing helped.
Pavel
My ppp subnet is, let's say, 10.10.10.0/24 and vlan10 subnet is 192.168.10.0/24.Hi,
I have a router CCR1036 directly connected to a switch CRS226 via vlan trunk on bridge1 (with rstp) through sfpplus1 port. There is a IP device connected to ether1 access port on CRS226. WAN is ether8 port on CCR1036. I can do ping from both, CCR1036 and CRS226, to IP device.
I succesfully run L2TP/IPsec and OVPN services, both are working, but I can't ping from both to IP device when connected from VPN client. I tried to setup proxy-arp on bridge1, sfpplus1, vlan10 and ether8 interfaces, but nothing helped me to rich IP device from VPN client.
Where should be problem please? Running v6.41rc61Code: Select all### CCR1036 ### /interface bridge add name=bridge1 vlan-filtering=no /interface bridge port add bridge=bridge1 interface=sfpplus1 /interface bridge vlan add bridge=bridge1 tagged=bridge1,sfpplus1 vlan-ids=10 /interface vlan add interface=bridge1 vlan-id=10 name=vlan10 /interface bridge set bridge1 vlan-filtering=yes ### CRS226 ### /interface bridge add name=bridge1 vlan-filtering=no /interface bridge port add bridge=bridge1 interface=sfpplus1 add bridge=bridge1 interface=ether1 /interface ethernet switch ingress-vlan-translation add ports=ether1 customer-vid=0 new-customer-vid=10 sa-learning=yes /interface ethernet switch egress-vlan-tag add tagged-ports=switch1-cpu,sfpplus1 vlan-id=10 /interface ethernet switch vlan add ports=switch1-cpu,sfpplus1,ether1 vlan-id=10 learn=yes /interface ethernet switch set drop-if-invalid-or-src-port-not-member-of-vlan-on-ports=ether1 /interface vlan add interface=bridge1 vlan-id=10 name=vlan10
Pavel
### ping from CCR1036 to IP device on CRS226 through vlan10 interface ###
[user@CCR1036] > ping 192.168.10.2 src-address=192.168.10.1
SEQ HOST SIZE TTL TIME STATUS
0 192.168.10.2 56 64 0ms
sent=1 received=1 packet-loss=0% min-rtt=0ms avg-rtt=0ms max-rtt=0ms
### ping from CCR1036 to IP device on CRS226 through ppp local interface ###
[user@CCR1036] > ping 192.168.10.2 src-address=10.10.10.1
SEQ HOST SIZE TTL TIME STATUS
0 192.168.10.2 timeout
sent=1 received=0 packet-loss=100%
Wow!.. What does it account?*) dhcp-server - added basic RADIUS accounting;
What does this feature do?*) wireless - added support for CHARGEABLE_USER_ID in EAP Accounting;
Implements rfc4372, I guess.What does this feature do?*) wireless - added support for CHARGEABLE_USER_ID in EAP Accounting;
DHCP server, DNS setings still does not work.
If you are experiencing problems with DHCP on latest RouterOS version, then please do the following:
1) Run this command on router - "/system logging add topics=dhcp"
2) Renew DHCP client;
3) Generate supout file;
4) Send this file to support@mikrotik.com and provide problem description.
We are not being able to reproduce such problem between two RouterOS devices. If DHCP client is not receiving/adding DHCP parameters, then this must be something specific and in order to fix this we need to see this on an actual example.
Can you tell me more about this?*) ipsec - improved hardware accelerated IPSec performance on 750Gr3;
I only send settings and logs.If you are experiencing problems with DHCP on latest RouterOS version, then please do the following:
1) Run this command on router - "/system logging add topics=dhcp"
2) Renew DHCP client;
3) Generate supout file;
4) Send this file to support@mikrotik.com and provide problem description.
We are not being able to reproduce such problem between two RouterOS devices. If DHCP client is not receiving/adding DHCP parameters, then this must be something specific and in order to fix this we need to see this on an actual example.
+++++++++++ DHCP server +++++++++++++
/ip dhcp-server network> print
Flags: D - dynamic
# ADDRESS GATEWAY DNS-SERVER WINS-SERVER DOMAIN
0 192.168.0.0/24 192.168.0.1 192.168.0.1
1 192.168.30.0/24 192.168.30.1 192.168.30.1
2 192.168.90.0/24 192.168.90.1 192.168.90.1
/ip dns> print
servers: 213.191.128.8,8.8.8.8,4.2.2.2
dynamic-servers:
allow-remote-requests: yes
max-udp-packet-size: 4096
query-server-timeout: 2s
query-total-timeout: 10s
max-concurrent-queries: 100
max-concurrent-tcp-sessions: 20
cache-size: 2048KiB
cache-max-ttl: 1w
cache-used: 168KiB
+++++++++++++++++ DHCP Client ++++++++++++++++
/ip dhcp-client> print detail
Flags: X - disabled, I - invalid
0 interface=ether1 add-default-route=yes default-route-distance=0 use-peer-dns=yes use-peer-ntp=yes dhcp-options=hostname,clientid status=bound
address=192.168.0.5/24 gateway=192.168.0.1 dhcp-server=192.168.0.1 primary-dns=192.168.0.1 secondary-dns=213.191.128.8 primary-ntp=161.53.123.5
secondary-ntp=66.199.22.67 expires-after=23h51m19s
/ip dns> print
servers:
dynamic-servers: 192.168.0.1,213.191.128.8,8.8.8.8,4.2.2.2
allow-remote-requests: no
max-udp-packet-size: 4096
query-server-timeout: 2s
query-total-timeout: 10s
max-concurrent-queries: 100
max-concurrent-tcp-sessions: 20
cache-size: 2048KiB
cache-max-ttl: 1w
cache-used: 9KiB
+++++++++++++++Log Debug++++++++++++
17:04:11 dhcp,debug,state dhcp-client on ether1 entering <renewing...> state
17:04:11 dhcp,debug,packet dhcp-client on ether1 sending request with id 2667306647 to 192.168.0.1
17:04:11 dhcp,debug,packet ciaddr = 192.168.0.5
17:04:11 dhcp,debug,packet chaddr = 6C:3B:6B:00:00:01
17:04:11 dhcp,debug,packet Msg-Type = request
17:04:11 dhcp,debug,packet Parameter-List = Subnet-Mask,Classless-Route,Router,Static-Route,Domain-Server,NTP-Server,CAPWAP-Server,Vendor-Specific
17:04:11 dhcp,debug,packet Host-Name = "name"
17:04:11 dhcp,debug,packet Client-Id = 01-6C-3B-6B-00:00:01
17:04:11 dhcp,debug,packet dhcp-client on ether1 received ack with id 2667306647 from 192.168.0.1
17:04:11 dhcp,debug,packet ciaddr = 192.168.0.5
17:04:11 dhcp,debug,packet yiaddr = 192.168.0.5
17:04:11 dhcp,debug,packet siaddr = 192.168.0.1
17:04:11 dhcp,debug,packet chaddr = 6C:3B:6B:00:00:01
17:04:11 dhcp,debug,packet Msg-Type = ack
17:04:11 dhcp,debug,packet Server-Id = 192.168.0.1
17:04:11 dhcp,debug,packet Address-Time = 86400
17:04:11 dhcp,debug,packet Subnet-Mask = 255.255.255.0
17:04:11 dhcp,debug,packet Router = 192.168.0.1
17:04:11 dhcp,debug,packet Domain-Server = 192.168.0.1,213.191.128.8,8.8.8.8,4.2.2.2
17:04:11 dhcp,debug,packet NTP-Server = 161.53.123.5,66.199.22.67
17:04:11 dhcp,debug,state dhcp-client on ether1 entering <bound> state
17:08:34 dhcp,debug,state dhcp-client on ether1 entering <renewing...> state
17:08:34 dhcp,debug,packet dhcp-client on ether1 sending request with id 2667306647 to 192.168.0.1
17:08:34 dhcp,debug,packet ciaddr = 192.168.0.5
17:08:34 dhcp,debug,packet chaddr = 6C:3B:6B:00:00:01
17:08:34 dhcp,debug,packet Msg-Type = request
17:08:34 dhcp,debug,packet Parameter-List = Subnet-Mask,Classless-Route,Router,Static-Route,Domain-Server,NTP-Server,CAPWAP-Server,Vendor-Specific
17:08:34 dhcp,debug,packet Host-Name = "name"
17:08:34 dhcp,debug,packet Client-Id = 01-6C-3B-6B-00-00-01
17:08:34 dhcp,debug,packet dhcp-client on ether1 received ack with id 2667306647 from 192.168.0.1
17:08:34 dhcp,debug,packet ciaddr = 192.168.0.5
17:08:34 dhcp,debug,packet yiaddr = 192.168.0.5
17:08:34 dhcp,debug,packet siaddr = 192.168.0.1
17:08:34 dhcp,debug,packet chaddr = 6C:3B:6B:00:00:01
17:08:34 dhcp,debug,packet Msg-Type = ack
17:08:34 dhcp,debug,packet Server-Id = 192.168.0.1
17:08:34 dhcp,debug,packet Address-Time = 86400
17:08:34 dhcp,debug,packet Subnet-Mask = 255.255.255.0
17:08:34 dhcp,debug,packet Router = 192.168.0.1
17:08:34 dhcp,debug,packet Domain-Server = 192.168.0.1,213.191.128.8,8.8.8.8,4.2.2.2
17:08:34 dhcp,debug,packet NTP-Server = 161.53.123.5,66.199.22.67
17:08:34 dhcp,debug,state dhcp-client on ether1 entering <bound> state
I tried to run this version on my 750Gr3 but became totally unreachable after a few minutes.Can you tell me more about this?*) ipsec - improved hardware accelerated IPSec performance on 750Gr3;
I only send settings and logs.If you are experiencing problems with DHCP on latest RouterOS version, then please do the following:
1) Run this command on router - "/system logging add topics=dhcp"
2) Renew DHCP client;
3) Generate supout file;
4) Send this file to support@mikrotik.com and provide problem description.
We are not being able to reproduce such problem between two RouterOS devices. If DHCP client is not receiving/adding DHCP parameters, then this must be something specific and in order to fix this we need to see this on an actual example.
It is easy to reproduce the problem because it is so behaving on all router boards.
Code: Select all+++++++++++ DHCP server +++++++++++++ /ip dhcp-server network> print Flags: D - dynamic # ADDRESS GATEWAY DNS-SERVER WINS-SERVER DOMAIN 0 192.168.0.0/24 192.168.0.1 192.168.0.1 1 192.168.30.0/24 192.168.30.1 192.168.30.1 2 192.168.90.0/24 192.168.90.1 192.168.90.1 /ip dns> print servers: 213.191.128.8,8.8.8.8,4.2.2.2 dynamic-servers: allow-remote-requests: yes max-udp-packet-size: 4096 query-server-timeout: 2s query-total-timeout: 10s max-concurrent-queries: 100 max-concurrent-tcp-sessions: 20 cache-size: 2048KiB cache-max-ttl: 1w cache-used: 168KiB +++++++++++++++++ DHCP Client ++++++++++++++++ /ip dhcp-client> print detail Flags: X - disabled, I - invalid 0 interface=ether1 add-default-route=yes default-route-distance=0 use-peer-dns=yes use-peer-ntp=yes dhcp-options=hostname,clientid status=bound address=192.168.0.5/24 gateway=192.168.0.1 dhcp-server=192.168.0.1 primary-dns=192.168.0.1 secondary-dns=213.191.128.8 primary-ntp=161.53.123.5 secondary-ntp=66.199.22.67 expires-after=23h51m19s /ip dns> print servers: dynamic-servers: 192.168.0.1,213.191.128.8,8.8.8.8,4.2.2.2 allow-remote-requests: no max-udp-packet-size: 4096 query-server-timeout: 2s query-total-timeout: 10s max-concurrent-queries: 100 max-concurrent-tcp-sessions: 20 cache-size: 2048KiB cache-max-ttl: 1w cache-used: 9KiB +++++++++++++++Log Debug++++++++++++ 17:04:11 dhcp,debug,state dhcp-client on ether1 entering <renewing...> state 17:04:11 dhcp,debug,packet dhcp-client on ether1 sending request with id 2667306647 to 192.168.0.1 17:04:11 dhcp,debug,packet ciaddr = 192.168.0.5 17:04:11 dhcp,debug,packet chaddr = 6C:3B:6B:00:00:01 17:04:11 dhcp,debug,packet Msg-Type = request 17:04:11 dhcp,debug,packet Parameter-List = Subnet-Mask,Classless-Route,Router,Static-Route,Domain-Server,NTP-Server,CAPWAP-Server,Vendor-Specific 17:04:11 dhcp,debug,packet Host-Name = "name" 17:04:11 dhcp,debug,packet Client-Id = 01-6C-3B-6B-00:00:01 17:04:11 dhcp,debug,packet dhcp-client on ether1 received ack with id 2667306647 from 192.168.0.1 17:04:11 dhcp,debug,packet ciaddr = 192.168.0.5 17:04:11 dhcp,debug,packet yiaddr = 192.168.0.5 17:04:11 dhcp,debug,packet siaddr = 192.168.0.1 17:04:11 dhcp,debug,packet chaddr = 6C:3B:6B:00:00:01 17:04:11 dhcp,debug,packet Msg-Type = ack 17:04:11 dhcp,debug,packet Server-Id = 192.168.0.1 17:04:11 dhcp,debug,packet Address-Time = 86400 17:04:11 dhcp,debug,packet Subnet-Mask = 255.255.255.0 17:04:11 dhcp,debug,packet Router = 192.168.0.1 17:04:11 dhcp,debug,packet Domain-Server = 192.168.0.1,213.191.128.8,8.8.8.8,4.2.2.2 17:04:11 dhcp,debug,packet NTP-Server = 161.53.123.5,66.199.22.67 17:04:11 dhcp,debug,state dhcp-client on ether1 entering <bound> state 17:08:34 dhcp,debug,state dhcp-client on ether1 entering <renewing...> state 17:08:34 dhcp,debug,packet dhcp-client on ether1 sending request with id 2667306647 to 192.168.0.1 17:08:34 dhcp,debug,packet ciaddr = 192.168.0.5 17:08:34 dhcp,debug,packet chaddr = 6C:3B:6B:00:00:01 17:08:34 dhcp,debug,packet Msg-Type = request 17:08:34 dhcp,debug,packet Parameter-List = Subnet-Mask,Classless-Route,Router,Static-Route,Domain-Server,NTP-Server,CAPWAP-Server,Vendor-Specific 17:08:34 dhcp,debug,packet Host-Name = "name" 17:08:34 dhcp,debug,packet Client-Id = 01-6C-3B-6B-00-00-01 17:08:34 dhcp,debug,packet dhcp-client on ether1 received ack with id 2667306647 from 192.168.0.1 17:08:34 dhcp,debug,packet ciaddr = 192.168.0.5 17:08:34 dhcp,debug,packet yiaddr = 192.168.0.5 17:08:34 dhcp,debug,packet siaddr = 192.168.0.1 17:08:34 dhcp,debug,packet chaddr = 6C:3B:6B:00:00:01 17:08:34 dhcp,debug,packet Msg-Type = ack 17:08:34 dhcp,debug,packet Server-Id = 192.168.0.1 17:08:34 dhcp,debug,packet Address-Time = 86400 17:08:34 dhcp,debug,packet Subnet-Mask = 255.255.255.0 17:08:34 dhcp,debug,packet Router = 192.168.0.1 17:08:34 dhcp,debug,packet Domain-Server = 192.168.0.1,213.191.128.8,8.8.8.8,4.2.2.2 17:08:34 dhcp,debug,packet NTP-Server = 161.53.123.5,66.199.22.67 17:08:34 dhcp,debug,state dhcp-client on ether1 entering <bound> state
They're just trying to achieve feature parity with the RADNSS "functionality" in IPv6.Don't waste your time. I 've got an answer from MT today:
-----------------------------------------------
Hello,
Is DHCP client receiving DNS server specified under DHCP server network settings and DNS servers used by router itself?
If this is correct, then this is how RouterOS works. We will in future add option which will allow to enable/disable such functionality.
Best regards,
Martins S.
-----------------------------------------------
Maybe, but better is the enemy of good. Things, that works great a lot of time, should not be changed at the same time of major implements in one version of OS. DHCP server is a certain service in network. Also, infos for users (administrators) are very important.They're just trying to achieve feature parity with the RADNSS "functionality" in IPv6.
Can you tell me more about this?
I tried to run this version on my 750Gr3 but became totally unreachable after a few minutes.
When I put a heavy load on IPSEC by using several connections the load is not distributed and the first core goes to 100% and the fourth sometimes follows. I hoped this change would distribute the load better.
*) route - improved reliability on routing table update;
more info?
I tried to run this version on my 750Gr3 but became totally unreachable after a few minutes.
When I put a heavy load on IPSEC by using several connections the load is not distributed and the first core goes to 100% and the fourth sometimes follows. I hoped this change would distribute the load better.
My ticket number is: 2017121522004034 and I sent in an autosupport and support fileThe fix addresses exactly this issue. Were you able to recover the router after the loss of reachability? Are you able to reproduce the issue somehow?
If you can make a serial connection, you can check the boot process ...Successfully updated a CRS109-8G-1S-2HnD to version 6.41rc66, then installed the firmware update to version 6.41rc65 and rebooted. Now the device is stuck at 'staring services', which is displayed on the lcd display. No link on interfaces...
Anybody seen this? Is there any chance to recover without reset?
I connected a serial cable and messages are shown at boot time:If you can make a serial connection, you can check the boot process ...Successfully updated a CRS109-8G-1S-2HnD to version 6.41rc66, then installed the firmware update to version 6.41rc65 and rebooted. Now the device is stuck at 'staring services', which is displayed on the lcd display. No link on interfaces...
Anybody seen this? Is there any chance to recover without reset?
Perhaps, there is no way to recover only by netinstall.
RouterBOOT booter 6.41rc65
CRS109-8G-1S-2HnD
CPU frequency: 600 MHz
Memory speed: 200 MHz
Memory size: 128 MiB
NAND size: 128 MiB
Press any key within 2 seconds to enter setup..
loading kernel... OK
setting up elf image... OK
jumping to kernel code
Starting...
Starting services...
MikroTik 6.41rc66 (testing)
e-mt-01 Login:
The device ran nearly every rc release from 6.41 series.From what earlier version did you upgrade? 6.41RC too or before?
Done.It looks like it is time for netinstall and restore backup.
When it has more than 16MB flash (which unfortunately is quite common lately) you can partition the flash andLet's hope this does not happen more often.
The RADIUS accounting packets for DHCP sessions do not include the User-Name attribute, which should be set as the MAC address of the client, just as it had been sent in the authentication request.What's new in 6.41rc66 (2017-Dec-14 13:53):
*) dhcp-server - added basic RADIUS accounting;
When can we se this hardware based LACP in Router Os?CRS317-1G-16S+RM is powered by a next generation switching chip, giving you wire speed performance for all sixteen 10GbE ports with any Ethernet frame size. New features such as hardware-based Spanning Tree Protocol and Link Aggregation (LACP) provide enhanced protection and true professional performance for your demanding network.
Looks like demo Routerboards find final version 6.41... Is the release being prepare right now?
And demo3 http://demo3.mt.lv/webfig/#System:Packa ... or_UpdatesLooks like demo Routerboards find final version 6.41... Is the release being prepare right now?
And no mention of the bridge update!Looks like demo Routerboards find final version 6.41... Is the release being prepare right now?
The list of changes there is from some older version, it's not showing the correct change list.And no mention of the bridge update!Looks like demo Routerboards find final version 6.41... Is the release being prepare right now?