What's new in 6.8rc1 (2014-Jan-02 09:46):

*) bgp - don't show community 'internet' in BGP advertisements;
*) ipsec - enable hardware acceleration for aes-cbc-128 + md5|sha1|sha256 aead on tilera cpus;
*) ospf - fixed checksum calculation for OSPFv3 AS-external-LSAs;
*) default configuration - changed dhcp server lease time to 10 minutes;
*) fixed port isolation on CRSs (bug introduced in v6.6);
*) smb - added support for SMB 2.002
*) timezone information updated;
*) ppp - fixed ppp bridging (did not work since v6.6);
*) improved speed of PPP, PPPoE, PPTP & L2TP on multicore routers;
*) address-list - fix crash when adding two identical address list entries (not allowed any more);
*) fixed multicast forwarding on CCRs;

Does anyone tested ipsec on ccr now? I wonder if it will take 1G.

6.8rc1 kills L2TP on CCR for me.

Not sure if perhaps this is a setup issue, but any other version of ROS it works. Move to 6.8rc1, it breaks. Move back 1 version, it works again.

I don't have time to troubleshoot or produce supout files as this is sadly in production (Stupid me)

Does anyone else notice L2TP issues? Or serious changes over the versions that could cause my config to need to be changed?

Make sure to upgrade to todays build (always)

I can't risk any more games with this router. It's in production (Again my stupid mistake)

Please confirm if there was a known L2TP bug between these releases. Simple question.

I did a upgrade + reset on my CRS

Now is all working fine (before only 10mbit if one of the devices was 10 mbit)
Also did a board firmware upgrade

you guys should re-name it to RC2 if there's a revision. I just re-downloaded it as the same file, same size, just different dates on it. I can't even tell what was changed from the Jan 2nd and the one released back in December

you guys should re-name it to RC2 if there's a revision. I just re-downloaded it as the same file, same size, just different dates on it. I can't even tell what was changed from the Jan 2nd and the one released back in December

+1... generally new releases have different version numbers. I have never seen anyone release a new version (different build times, etc) with the same version numbers.

absolutely horrible. I have a PtP I just tested this on. It would link up for about 10-20 seconds, then stay registered, but the rates would drop to 6/162 and not pass any traffic until "-" I minus it off the Master forcing it to re-register, and the process repeats.

if you have any wireless or point-to-points, don't use this firmware!

you guys should re-name it to RC2 if there's a revision. I just re-downloaded it as the same file, same size, just different dates on it. I can't even tell what was changed from the Jan 2nd and the one released back in December

+1... generally new releases have different version numbers.

+2. Make better naming. RC2, RC3 etc....

you guys should re-name it to RC2 if there's a revision. I just re-downloaded it as the same file, same size, just different dates on it. I can't even tell what was changed from the Jan 2nd and the one released back in December

+1... generally new releases have different version numbers.

+2. Make better naming. RC2, RC3 etc....

+1

I want you to put in the file name, date at least if it is not.

you guys should re-name it to RC2 if there's a revision. I just re-downloaded it as the same file, same size, just different dates on it. I can't even tell what was changed from the Jan 2nd and the one released back in December

+1... generally new releases have different version numbers.

+2. Make better naming. RC2, RC3 etc....

+4

+1

Hi Norman,

Can you assist to check on the following ticket that I've report to support team? Being a month already however I did not get any response after which from my correspond to check for update.
http://forum.mikrotik.com/viewtopic.php?f=2&t=80298

Please at least let me know if someone is looking into this issue to be fix? Do that need more time to check?

absolutely horrible. I have a PtP I just tested this on. It would link up for about 10-20 seconds, then stay registered, but the rates would drop to 6/162 and not pass any traffic until "-" I minus it off the Master forcing it to re-register, and the process repeats.

if you have any wireless or point-to-points, don't use this firmware!

The same here. Checked on an Omnitik as AP and a Sextant as client, with an NV2 link between them (actually it is a PtMP link with more clients, but I upgraded only one of them).

It seems to me that the time before the problem kicks in depends heavily on the amount of traffic flowing through the wireless link: more traffic and the link goes down within seconds; less traffic and it can stay on for a day or more.

Downgraded the AP (Omnitik) to 6.7 and it became stable. The Sextant, still on 6.8 rc1, remained unstable. When the latter was also downgraded, the link became stable again.

I wonder if this means that there is some work going on under the hood on the wireless section...

Try the newest version 6.8RC1(2014-01-08 14:00:28)。
L2TP work fine for me:)

wispwest and nkourtzis, we were able to reproduce this problem. We fixed this problem, you can redownload the v6.8rc1 - Nv2 should work stable
again.

Hey Uldis,

Could you take a look at: http://forum.mikrotik.com/viewtopic.php?f=1&t=80421
So far every 6.8rc1 build since this year (starting from the 2-1-2014 build), give kernel panics.
Cannot create supouts sadly, because of the reboots the kernel panic issues, it keeps rebooting in a loop.

Hey Uldis,

Could you take a look at: http://forum.mikrotik.com/viewtopic.php?f=1&t=80421
So far every 6.8rc1 build since this year (starting from the 2-1-2014 build), give kernel panics.
Cannot create supouts sadly, because of the reboots the kernel panic issues, it keeps rebooting in a loop.

we fixed this problem, you can redownload the v6.8rc1.

Hey Uldis,

Could you take a look at: http://forum.mikrotik.com/viewtopic.php?f=1&t=80421
So far every 6.8rc1 build since this year (starting from the 2-1-2014 build), give kernel panics.
Cannot create supouts sadly, because of the reboots the kernel panic issues, it keeps rebooting in a loop.

we fixed this problem, you can redownload the v6.8rc1.

If you changed something to fix it, shouldn't you really call that v6.8rc2 ? Sort of confusing when you change things or fix something and call it the same release.

If you changed something to fix it, shouldn't you really call that v6.8rc2 ? Sort of confusing when you change things or fix something and call it the same release.

http://en.wikipedia.org/wiki/Continual_ ... nt_process

What's new in 6.8rc1 (2014-Jan-02 09:46):

*) improved speed of PPP, PPPoE, PPTP & L2TP on multicore routers

Will this update include a fix for Ticket#2011122766000641, concerning packet loss if PPP packets arrive out of order?

What's new in 6.8rc1 (2014-Jan-10 13:52):

*) dhcp client - support interfaces in bridge;
*) dhcp - parse decimal strings and IP addreses in options value;
*) bgp - don't show community 'internet' in BGP advertisements;
*) ipsec - enable hardware acceleration for aes-cbc-128 + md5|sha1|sha256 aead on tilera cpus;
*) ospf - fixed checksum calculation for OSPFv3 AS-external-LSAs;
*) default configuration - changed dhcp server lease time to 10 minutes;
*) fixed port isolation on CRSs (bug introduced in v6.6);
*) smb - added support for SMB 2.002
*) timezone information updated;
*) ppp - fixed ppp bridging (did not work since v6.6);
*) improved speed of PPP, PPPoE, PPTP & L2TP on multicore routers;
*) address-list - fix crash when adding two identical address list entries (not allowed any more);
*) fixed multicast forwarding on CCRs;
*) firewall - improved address-type matcher, and added it for ipv6 aswell;

where to obtain said download?

You Need to have "Development version testing" Access on main mikrotik.com page.
BTW new build online

What's new in 6.8rc1 (2014-Jan-15 12:45):

The 15-01-2014 build fixes the kernel panics!

The 15-01-2014 build fixes the kernel panics!

On what type routerboard?

You Need to have "Development version testing" Access on main mikrotik.com page.

How do I obtain this?

You Need to have "Development version testing" Access on main mikrotik.com page.

How do I obtain this?

write to support@mikrotik.com

The 15-01-2014 build fixes the kernel panics!

On what type routerboard?

CCR1016-12G

Updates 6.8rc1, which is published 2014-01-16 What?
Contents are worried about the release notes has not been updated.

+5 for correct naming of builds. RC2... RC3... RC444

Our system is built in a way, that we can change these numbers if we release these versions. Currently we don't release them, they are internal "patches" of previous builds. We would have to do something differently then. But as you know, these are unofficial internal releases anyway.

deleted

+5 for correct naming of builds. RC2... RC3... RC444

Normis, why Mikrotik don´t hear these requests?

See above

Release date? Today?

No, not today. The changes we are making, are not yet finished.

Our system is built in a way, that we can change these numbers if we release these versions. Currently we don't release them, they are internal "patches" of previous builds. We would have to do something differently then. But as you know, these are unofficial internal releases anyway.

Add some sort of sequence number to your internal build names. Timestamp of when the build begins or revision number should work.

high ping to station pppoe in 6.8.rc1 build 16/01/2014....... in 6.6 1ms..

*) improved speed of PPP, PPPoE, PPTP & L2TP on multicore routers;

Can confirm I got another ~200 mbps while torrenting on my 1gbps connection running routeros 6.8rc1 under ESXi on a Celeron G1610T (sole VM, ~70% cpu load, pppoe connection, ~60 firewall rules).

I reported a problem with Quickset crashing the router in 6.7. This problem was acknowledged by support and I was told MikroTik would try to fix it in the next release. The ticket is #2013120766000022

Will this be fixed in 6.8?

I reported a problem with Quickset crashing the router in 6.7. This problem was acknowledged by support and I was told MikroTik would try to fix it in the next release. The ticket is #2013120766000022

Will this be fixed in 6.8?

You can test the latest build and see:
http://www.mikrotik.com/download/share/ ... 6.8rc1.npk

What's new in 6.8rc1 (2014-Jan-21 11:25):

*) wireless - improved 11n and nv2 stability;
*) dhcp client - support interfaces in bridge;
*) dhcp - parse decimal strings and IP addreses in options value;
*) bgp - don't show community 'internet' in BGP advertisements;
*) ipsec - enable hardware acceleration for aes-cbc + md5|sha1|sha256 aead on tilera cpus;
*) ospf - fixed checksum calculation for OSPFv3 AS-external-LSAs;
*) default configuration - changed dhcp server lease time to 10 minutes;
*) fixed port isolation on CRSs (bug introduced in v6.6);
*) smb - added support for SMB 2.002
*) timezone information updated;
*) ppp - fixed ppp bridging (did not work since v6.6);
*) improved speed of PPP, PPPoE, PPTP & L2TP on multicore routers;
*) address-list - fix crash when adding two identical address list entries (not allowed any more);
*) fixed multicast forwarding on CCRs;
*) firewall - improved address-type matcher, and added it for ipv6 aswell;

MT: A bit more info about nv2 and n information?

You can see that support in recent times does not give advice.
What's new edition of the old mistakes.

Even I do not know it seems that the problem only on RB951G 6.8rc1 on the second router CRS125 all ok

serious problem with PPPOE SERVER bridge and when client disconnects, the other customers mikrotik drops after 20 seconds, problem with BCP, in all versions,. customer who left hung equipment, and the right client mikrotik disconnected, after 20 seconds than the other turned off the device.

You can see that support in recent times does not give advice.
What's new edition of the old mistakes.

Even I do not know it seems that the problem only on RB951G 6.8rc1 on the second router CRS125 all ok

Did you contact support? Please tell me the ticket number and I will check what is wrong there

mietus, some possible nv2 lockups/crash are fixed and also speed for the 802.11n might be more stable.

mietus, some possible nv2 lockups/crash are fixed and also speed for the 802.11n might be more stable.

And it seems with nv2 ping isnt jumping like before, now stable 3ms under 40/40mbit btest.

its better Mtik, now its really better

mietus, some possible nv2 lockups/crash are fixed and also speed for the 802.11n might be more stable.

mmmm very nice. ;]

mietus, some possible nv2 lockups/crash are fixed and also speed for the 802.11n might be more stable.

Realy good news! You've to clean code while integrating .ac

mietus, some possible nv2 lockups/crash are fixed and also speed for the 802.11n might be more stable.

Realy good news! You've to clean code while integrating .ac

Or finishing off Wireless Controller

What's new in 6.8rc1 (2014-Jan-21 11:25):

*) wireless - improved 11n and nv2 stability;
*) dhcp client - support interfaces in bridge;
*) dhcp - parse decimal strings and IP addreses in options value;
*) bgp - don't show community 'internet' in BGP advertisements;
*) ipsec - enable hardware acceleration for aes-cbc + md5|sha1|sha256 aead on tilera cpus;
*) ospf - fixed checksum calculation for OSPFv3 AS-external-LSAs;
*) default configuration - changed dhcp server lease time to 10 minutes;
*) fixed port isolation on CRSs (bug introduced in v6.6);
*) smb - added support for SMB 2.002
*) timezone information updated;
*) ppp - fixed ppp bridging (did not work since v6.6);
*) improved speed of PPP, PPPoE, PPTP & L2TP on multicore routers;
*) address-list - fix crash when adding two identical address list entries (not allowed any more);
*) fixed multicast forwarding on CCRs;
*) firewall - improved address-type matcher, and added it for ipv6 aswell;

Definitly not fixed. 2 CRS125's back to back with VLAN trunking has both switches opposite eachother traffic repeated on all ports.

Issues still present:
unicast-fdb is populated with incorrect data (port is always set to 24 regardless of any setting)
isolation level per vlan cannot be set
svl cannot bet set per vlan, reboot clears it
mac-level isolation cannot be saved, reboot clears it
vlan-level isolation cannot be saved, reboot clears it

Realy good news! You've to clean code while integrating .ac

Or finishing off Wireless Controller

Which one would you prefer ?

*) wireless - improved 11n and nv2 stability;

Normis !!! Fantastic news!
You are working/improving NV2 protocol and wireless section!!!!!!!!!

Can you give us some more details of this change?
Improve throughput / latency? It solves some stalemate?

Can we try it? If so, where is the download link?

*) wireless - improved 11n and nv2 stability;

Normis !!! Fantastic news!
You are working/improving NV2 protocol and wireless section!!!!!!!!!

Can you give us some more details of this change?
Improve throughput / latency? It solves some stalemate?

Can we try it? If so, where is the download link?

some possible nv2 lockups/crash are fixed and also speed for the 802.11n might be more stable.

Contact support@mikrotik.com and we could allow you access for the development version section.

Realy good news! You've to clean code while integrating .ac

Or finishing off Wireless Controller

Which one would you prefer ?

Lets make a poll ... I vote for WLC ..

JF

*) wireless - improved 11n and nv2 stability;

Normis !!! Fantastic news!
You are working/improving NV2 protocol and wireless section!!!!!!!!!

Can you give us some more details of this change?
Improve throughput / latency? It solves some stalemate?

Can we try it? If so, where is the download link?

It is fix for this problem
http://forum.mikrotik.com/viewtopic.php ... nv2+lockup

Realy good news! You've to clean code while integrating .ac

Or finishing off Wireless Controller

Which one would you prefer ?

I vote WLC

*) wireless - improved 11n and nv2 stability;

Normis !!! Fantastic news!
You are working/improving NV2 protocol and wireless section!!!!!!!!!

Can you give us some more details of this change?
Improve throughput / latency? It solves some stalemate?

Can we try it? If so, where is the download link?

It is fix for this problem
http://forum.mikrotik.com/viewtopic.php ... nv2+lockup

Yes, that is fixed in this release.

Everything was already promised in previous versions. When will it work in reality and I will be happy. When will it be released v6.8?

It is updated at 2014-01-24 08:58:53 with, Although it is daily build,
Why date of package contents has become a thing of yesterday are you?

What about problem with no country set? It is quite frustrating...
When quickset window isn’t closed and i log again to router using Winbox it automatically disconnect.
I notice in wireless setting options that instead of Poland it switch automatically to "no country set"
It happens on every SXT and SXT Lite since 6.1 version. Would be nice to have it fixed.

Realy good news! You've to clean code while integrating .ac

Or finishing off Wireless Controller

Which one would you prefer ?

I vote for WLC!

+1 for WLC

hmm, @MT what was added to latest build, file increased from 9,81 MB to 11,6 MB, it's some kind of surprise?

What's new in 6.8rc1 (2014-Jan-24 15:06):

*) bridge - default protocol-mode changed to RSTP for new bridges,
fixed bridge mac address changing when port (with lowest mac address) goes down
*) userman - improve startup time;
*) sstp client - support server name verification from certificate;
*) wireless - improved 11n and nv2 stability;
*) dhcp client - support interfaces in bridge;
*) dhcp - parse decimal strings and IP addreses in options value;
*) bgp - don't show community 'internet' in BGP advertisements;
*) ipsec - enable hardware acceleration for aes-cbc + md5|sha1|sha256 aead on tilera cpus;
*) ospf - fixed checksum calculation for OSPFv3 AS-external-LSAs;
*) default configuration - changed dhcp server lease time to 10 minutes;
*) fixed port isolation on CRSs (bug introduced in v6.6);
*) smb - added support for SMB 2.002
*) timezone information updated;
*) ppp - fixed ppp bridging (did not work since v6.6);
*) improved speed of PPP, PPPoE, PPTP & L2TP on multicore routers;
*) address-list - fix crash when adding two identical address list entries (not allowed any more);
*) fixed multicast forwarding on CCRs;
*) firewall - improved address-type matcher, and added it for ipv6 aswell;

After one day of action rb951g hung wifi card.
routeros-mipsbe-6.8rc1 was updated at 2014-01-24 14:30

After restarting the communication device has been restored.

Any news about IGMP proxy bugs?

Did anyone noticed that latest mipsbe .npk file is bigger?
11.6MB instead of usual 9.8MB.
I'm very curious what made such difference.

Regards,

Did anyone noticed that latest mipsbe .npk file is bigger?
11.6MB instead of usual 9.8MB.
I'm very curious what made such difference.

Regards,

eh.. look a bit above from your posts

I think it maybe some part of wlc.

AFAIK 'WLC' will be a separated package.
I've compared separated package files,
only 'system-mipsbe.npk' is bigger than usually.

Regards,

Realy good news! You've to clean code while integrating .ac

Or finishing off Wireless Controller

Which one would you prefer ?

I vote WLC

+1

Sent from my SCH-I545 using Tapatalk

hmm

jan/02/1970 01:00:12 system,info installed routeros-mipsbe-6.8rc1
jan/02/1970 01:00:15 script,warning defconf: penta chains are only for 'ac' boards
jan/02/1970 01:00:30 interface,info ether1 link up (speed 100M, full duplex)

extra MB in .npk looks like initial support of new hardware

Hi,
Running 6.8rc1 (Jan/24/2014 15:06:50) on CCR1036-8G-2S+. I have connection tracking disabled, however if I create a firewall address list the contrack table starts filling (despite being disabled and not auto). I wouldn't have expected connection tracking to be required for an address list and this wasn't the behaviour in 6.7.

jan/02/1970 01:00:12 system,info installed routeros-mipsbe-6.8rc1
jan/02/1970 01:00:15 script,warning defconf: penta chains are only for 'ac' boards

Nice what script do you use? It seems that we can on MUM enjoy the new AC Goodies

jan/02/1970 01:00:12 system,info installed routeros-mipsbe-6.8rc1
jan/02/1970 01:00:15 script,warning defconf: penta chains are only for 'ac' boards

Nice what script do you use? It seems that we can on MUM enjoy the new AC Goodies

none, just upraded 911G board

After one day of action rb951g hung wifi card.
routeros-mipsbe-6.8rc1 was updated at 2014-01-24 14:30

After restarting the communication device has been restored.

Please tell us exactly what happens to the wireless interface - you couln't see it form the clients device, or no traffic was going? Disabling/enabling the wireless card didn't help?
Were you able to make support output file when the problem happened and sent to support@mikrotik.com?

Any news about IGMP proxy bugs?

I want to know the same thing.

Is it now possible to disable DHCP options in the DHCP Client?

I can't remove hostname or clientid -- they keep coming back!

See ticket: 2014011766000899

Amendment to an earlier post on 6.8rc1 rb 951g router just hangs. In such a way that the internal watchdog nothing was done. There is no communication on any ports is also not on wifi. After the restart does not see normal speeds on the ports need to enable disable the port .

# Jan/28/2014 7: 4:25 to RouterOS 6.8rc1
# Software id = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
#
jan/02/1970 1:00:15 interface , info v.p1.olkusz link up
jan/02/1970 1:00:15 interface , info v.p4.login link up
jan/02/1970 1:00:15 interface , info v.p2.nkt link up
jan/02/1970 1:00:15 interface , info v.p5.akwawit link up
jan/02/1970 1:00:15 interface , info v.MBIZ link up
jan/02/1970 1:00:20 interface , info e03.lan link up (speed 10M half duplex )
jan/02/1970 1:00:20 interface , info e02.lan link up (speed 10M half duplex )
jan/02/1970 1:00:20 interface , info e05.lan link up (speed 1000M , full duplex )
jan/02/1970 1:00:20 interface , info e04.lan link up (speed 1000M , full duplex )
jan/02/1970 1:00:20 wireless , debug w01 : 0:16 : EA : EE: 35:62 attempts is associate
jan/02/1970 1:00:20 wireless , debug w01 : 0:16 : EA : EE: 35:62 in local ACL , accept
jan/02/1970 1:00:20 wireless , info 0:16 : EA : EE: 35:62 @ w01 : connected
jan/02/1970 1:00:21 interface , info e05.lan link down
jan/02/1970 1:00:23 interface , info e05.lan link up (speed 1000M , full duplex )
jan/02/1970 1:00:32 interface , info e01.wan link up (speed 1000M , full duplex )
7:01:58 system , error , critical router was rebooted without proper shutdown
7:02:24 system , info, account user admin logged in from 192,168,254,110 via winbox
7:03:23 system , info device changed by admin
7:03:25 system , info device changed by admin
7:03:25 interface , info e03.lan link down
7:03:28 interface , info e03.lan link up (speed 10M half duplex )
7:03:32 system , info device changed by admin
7:03:42 system , info device changed by admin
7:03:43 interface , info e04.lan link down
7:03:46 interface , info e04.lan link up (speed 1000M , full duplex )
7:04:02 system , info, account user admin logged in from 192,168,254,110 via telnet

What to write on support. I'll write only when they solve the problems previously reported.
It has only to do downgrade

Hello all,
despite that NV2 was fixed in 6.8rc1, i would not recommend to use this release with SXT 5nd r2, because ether1 port flapping issue.

fixed bridge mac address changing when port (with lowest mac address) goes down

MT, please do the same for bonding =)

Hello all,
despite that NV2 was fixed in 6.8rc1, i would not recommend to use this release with SXT 5nd r2, because ether1 port flapping issue.

6.8rc1 is no release SW. Hope this is fixed for the release.

Seems MT has longer SW-Release cycles at the moment and makes more Betas for testing.

I would love to wait another month for 6.8 with all fixes included.

Hello all,
despite that NV2 was fixed in 6.8rc1, i would not recommend to use this release with SXT 5nd r2, because ether1 port flapping issue.

Please clarify what port flapping issue you mean, include your ticket number so I can check status. Thanks

Hello all,
despite that NV2 was fixed in 6.8rc1, i would not recommend to use this release with SXT 5nd r2, because ether1 port flapping issue.

Please clarify what port flapping issue you mean, include your ticket number so I can check status. Thanks

labdien braliukai

Ok. lets try
in short: after upgrade SXT 5ndr2 to 6.8rc1 randomly ether1 port goes down and up continuosly. it can be seen on pc connected to CPE. After downgrade to 6.7 flapping disappiers, but during speedtest, ether1 simply hangs (traffic isnt passing through ether1)
only way to restore ether1 - to reboot SXT.

now we are testing other cpe's to recreate same situation.

EDIT:
The Ticket ID is 2014012866000574

SXT Lite 5ND r2 does not connect to acces point
SXT stops scanning on channel access point and stop, but not connecting
Disable, enable wlan1 solves the problem but not always
I checked various channel symptom of the same.

SXT Lite 5ND r2 does not connect to acces point
SXT stops scanning on channel access point and stop, but not connecting
Disable, enable wlan1 solves the problem but not always
I checked various channel symptom of the same.

what does the wireless,debug log say on both CPE and AP side when not connecting?

SXT Lite 5ND r2 does not connect to acces point
SXT stops scanning on channel access point and stop, but not connecting
Disable, enable wlan1 solves the problem but not always
I checked various channel symptom of the same.

what does the wireless,debug log say on both CPE and AP side when not connecting?

Log on access point nothing shows
log on client station also clear
station connected when I disable anable wlan1

This is just Info log, please enable also Debug log (in system logging, add new topic with "wireless" and "debug")

Does this happen only one SXT lite, or also on other devices connected to the same AP?

This is just Info log, please enable also Debug log (in system logging, add new topic with "wireless" and "debug")

Does this happen only one SXT lite, or also on other devices connected to the same AP?

Symptom has already performed at several sxt connected to different acces point
On the RB711 symptom does not occur

I have the same problem as described above

i have made a support ticket#2014012366000654

I confirm the problem. part 5 sxt r2 not connect to 20\40 if you are installing only 20 worked . part 5 sxt r2 didn't work at certain frequencies, for example in the range 5300-5320 not seen base. when changing frequencies on 5180 everything works. (we are talking about nv2).

I have 30 clients connected to the ap . when changing frequencies can connect the 20 to 25 clients a frequency on which all 30 clients. ether net to the nearest city-50 km

After upgrade OmniTik-UPA to 6.8 and firmware to 3.11, it died, after inspection on the site, we found port flapping.

EDIT
OmniTik even not loading from nand. And ticking :)

2nd edit

affected CPE SXT (6.8) still crashing under load (10/10Mbit udp btest) after 10s

going to netinstall

affected CPE SXT (6. still crashing under load (10/10Mbit udp btest) after 10s

In V6.8 works fine. I tried BW test (10/10) 1minute. No crash

affected CPE SXT (6. still crashing under load (10/10Mbit udp btest) after 10s

In V6.8 works fine. I tried BW test (10/10) 1minute. No crash

Seems hw fault, because other devices works as expected.

Dial on demand does not work on the RC that was released briefly this morning. A L2TP (and sstp) client that worked in previous releases (6.6 and earlier including 5.x) would not start. The interface did work if dial on demand was deactivated and was started manually.

on ver. 6.8rc1 this problem still exists
although the network is aviable on scan RB SXT 5nD r2 canot connect to ap,
after reboot it can connect but not on every frequency.

log from SXT 5nD r2:
wireless,debug wlan1: no network that satisfies connect-list, by default choose with strongest signal
no log on ap

other clients working on RB SXT 5HPnD can conect to the same network with no problem on every frequency


Network conf.
cpe:
name="wlan1" mtu=1500 mac-address=D4:CA:6D:C1:63:59 arp=enabled
interface-type=Atheros AR9300 mode=station ssid="ssid"
frequency=5520 band=5ghz-a/n channel-width=20/40mhz-ht-above
scan-list=default wireless-protocol=nv2-nstreme-802.11 wds-mode=disabled
wds-default-bridge=none wds-ignore-ssid=no bridge-mode=enabled
default-authentication=yes default-forwarding=yes default-ap-tx-limit=0
default-client-tx-limit=0 hide-ssid=no security-profile=default
compression=no

ap:
name="wlan1" mtu=1500 mac-address=D4:CA:6D:10:A6:2C arp=enabled
interface-type=Atheros AR92xx mode=ap-bridge ssid="ssid"
frequency=5805 band=5ghz-onlyn channel-width=20/40mhz-ht-above
scan-list=default wireless-protocol=nv2 wds-mode=disabled
wds-default-bridge=none wds-ignore-ssid=no bridge-mode=enabled
default-authentication=yes default-forwarding=yes default-ap-tx-limit=0
default-client-tx-limit=0 hide-ssid=no security-profile=default
compression=no

Dial on demand does not work on the RC that was released briefly this morning. A L2TP (and sstp) client that worked in previous releases (6.6 and earlier including 5.x) would not start. The interface did work if dial on demand was deactivated and was started manually.

i confirm that dial on demand dose not work

emboro, thank you very much for the report. We will try to fix this problem as soon as possible.

is it just me or 6.8 x86 using more ram then 6.7?
it doubled the used ram

is it just me or 6.8 x86 using more ram then 6.7?
it doubled the used ram

What type of device you have? what features do you use?

well normal x86 .. level4 routing my network...
nothing change since 6.7 only the increase of used ram, that doubled...

supout attached

Here is our X86 after upgrade to v6.9
Please make one file after reboot (fresh start) and another after a while, when RAM is filled up. We will compare the two files, and will check what eats the memory in your device.

graphing image

fresh start sup attach

fresh start sup attach

this is a user forum, please send the files to support@mikrotik.com

fresh start sup attach

this is a user forum, please send the files to support@mikrotik.com

wops... done