Page 1 of 1

6.34 release candidate version topic!

Posted: Mon Nov 09, 2015 5:37 pm
by w0lt
It seems that ROC 6.34rc1 seems to break OSPF "for some reason" in the CRS210-8G-2S+.
Reverting to ROS 6.32.3 corrects the issue.
I have tried this upgrade/downgrade twice.   :?

6.34 rc topic

Posted: Wed Nov 11, 2015 11:24 am
by strods
6.34rc3 version will be released today:

Changes since 6.34rc1:

*) smb - fixed SMB share crash when connection was cancelled;
*) lcd - fixed LCD crash on fast disable/enable;
*) fastpath - fixed wireless interface fastpath (broken in 6.33);
*) pppoe - fixed compliance to RFC4638 (MTU larger than 1488);
*) webfig - show correctly SFP Tx/Rx;
*) winbox - renamed power-cycle-ping-interval to power-cycle-ping-timeout;
*) CCR1072 - added support for S-RJ01 SFP modules;
*) trafficgen - fixed issue that traffic-generator could not be started twice without reboot;
*) dhcpv4-client - support /32 address assignment;
*) licensing - fix unneeded connection attempts to 169.254.x.x (must be CHR only);
*) dhcpv6-server - replace delay option with preference option;
*) dhcpv6-client - added address acquisition support;
*) dhcpv6 - implement and enable rapid commit by default.

Re: 6.34 release candidate version topic!

Posted: Wed Nov 11, 2015 9:44 pm
by skuykend
Upgraded from 6.33 to 6.34rc3 and lost my ipv6 dhcp-client config. (no entry)

Reverted to 6.33, but still had to add back the client entry.

Re: 6.34 rc topic

Posted: Thu Nov 12, 2015 12:13 am
by w0lt
6.34rc3 version will be released today:

Changes since 6.34rc1:

*) smb - fixed SMB share crash when connection was cancelled;
*) lcd - fixed LCD crash on fast disable/enable;
*) fastpath - fixed wireless interface fastpath (broken in 6.33);
*) pppoe - fixed compliance to RFC4638 (MTU larger than 1488);
*) webfig - show correctly SFP Tx/Rx;
*) winbox - renamed power-cycle-ping-interval to power-cycle-ping-timeout;
*) CCR1072 - added support for S-RJ01 SFP modules;
*) trafficgen - fixed issue that traffic-generator could not be started twice without reboot;
*) dhcpv4-client - support /32 address assignment;
*) licensing - fix unneeded connection attempts to 169.254.x.x (must be CHR only);
*) dhcpv6-server - replace delay option with preference option;
*) dhcpv6-client - added address acquisition support;
*) dhcpv6 - implement and enable rapid commit by default.
CRS210 still does not route correctly using 6.34rc3. Reverting to 6.33 resolves it. This is using a SFP fiber connection to a CRS112 which is successfully running 6.34rc3.
Auto-negotiation on the fiber ports have been disabled. I'm running OSPF.
Remember, 6.33 works perfectly :) , 6.34rc1 or 6.34rc3 doesn't work :( .
I've tried netinstall, no joy. Added a second boot partition so I don't have to keep reinstalling 6.33 when I try 6.34rc
That's a pretty slick feature, I might add... Saves a lot of headache !! :-)

Re: 6.34 release candidate version topic!

Posted: Thu Nov 12, 2015 8:20 am
by janisk
Upgraded from 6.33 to 6.34rc3 and lost my ipv6 dhcp-client config. (no entry)

Reverted to 6.33, but still had to add back the client entry.
we are working on DHCPv6-client, so you might experience some problems with the DHCP-PD client as they are in the same place. If that is important feature you are using for day to day configuration wait at least till rc5 release or newer.

Re: 6.34 release candidate version topic!

Posted: Fri Nov 13, 2015 8:54 am
by PtDragon
Can you fix RouterOS update from winbox please for multiple internet links router?
It has error "No route to host" even if all routers behind this one have access without problems.

Re: 6.34 release candidate version topic!

Posted: Fri Nov 13, 2015 8:59 am
by strods
PtDragon - Please send supout file from your device to support@mikrotik.com

Re: 6.34 release candidate version topic!

Posted: Fri Nov 13, 2015 1:26 pm
by strods
6.34rc5 will be released today.

Changes since 6.34rc3:

*) dns - fix for situation when dynamic dns servers could disappear;
*) packages - show version tag when no bundle is installed;
*) vrrp - fix enabling disabled vrrp interface when vrrp program has exited;
*) winbox - do not send any changes on OK button press if nothing has been changed;
*) sfp - fix 10g ports in 1g mode (introduced in 6.34rc1);
*) dhcpv6-client - added DHCPv6-client functionality for current DHCP-PD client;

Re: 6.34 release candidate version topic!

Posted: Fri Nov 13, 2015 2:34 pm
by Bergante
Curious about the 10 G ports in 1 G mode correction.

Actually there is a problem with 1G SFPs in SFP+ ports, it doesn´t work with autonegotiation enabled. Is it related? A friend has a problem with such a setup.

Re: 6.34 release candidate version topic!

Posted: Fri Nov 13, 2015 6:26 pm
by w0lt
6.34rc5 will be released today.

Changes since 6.34rc3:

*) dns - fix for situation when dynamic dns servers could disappear;
*) packages - show version tag when no bundle is installed;
*) vrrp - fix enabling disabled vrrp interface when vrrp program has exited;
*) winbox - do not send any changes on OK button press if nothing has been changed;
*) sfp - fix 10g ports in 1g mode (introduced in 6.34rc1);
*) dhcpv6-client - added DHCPv6-client functionality for current DHCP-PD client;
Can't seem to find it.. :?

Re: 6.34 release candidate version topic!

Posted: Mon Nov 16, 2015 1:49 am
by andersonlich
CCR1072 - added support for S-RJ01 SFP modules;

Is it ccr1072 will support sfp-t by all that means?

So it supposed that ccr1072 support for sfp-f 1ge ?

Any body can give me clarification about this?

Re: 6.34 release candidate version topic!

Posted: Mon Nov 16, 2015 10:42 am
by chubbs596
Hi Guys

Can we please get driver support for the the following Broadcom 4 ports SFP+ card. It uses the Broadcom BCM57840S controller. I have 1 of these cards based on the http://wiki.mikrotik.com/wiki/Supported ... t_chipsets page I thought it would be supported.

http://www.supermicro.com/products/acce ... tg-b4s.cfm

Re: 6.34 release candidate version topic!

Posted: Mon Nov 16, 2015 7:08 pm
by aboiles
6.34rc5 shows in the tracker page, but is not accessible.
Download still shows 6.34rc3 as the latest.

Re: 6.34 release candidate version topic!

Posted: Mon Nov 16, 2015 8:04 pm
by rzirzi
6.34rc5 will be released today.
...
"Today" have another sense from today :)

Re: 6.34 release candidate version topic!

Posted: Tue Nov 17, 2015 9:18 am
by chubbs596
Hi Guys

Can we please get driver support for the the following Broadcom 4 ports SFP+ card. It uses the Broadcom BCM57840S controller. I have 1 of these cards based on the http://wiki.mikrotik.com/wiki/Supported ... t_chipsets page I thought it would be supported.

http://www.supermicro.com/products/acce ... tg-b4s.cfm

Re: 6.34 release candidate version topic!

Posted: Tue Nov 17, 2015 10:13 am
by normis
Hi Guys

Can we please get driver support for the the following Broadcom 4 ports SFP+ card. It uses the Broadcom BCM57840S controller. I have 1 of these cards based on the http://wiki.mikrotik.com/wiki/Supported ... t_chipsets page I thought it would be supported.

http://www.supermicro.com/products/acce ... tg-b4s.cfm
We can't add drivers. RouterOS drivers come from the used Linux Kernel. We only change kernel in big releases, next change will come in RouterOS v7

Re: 6.34 release candidate version topic!

Posted: Tue Nov 17, 2015 10:34 am
by chubbs596
Hi Normis

This does not really help as we have been hearing about ROSv7 for a long time but not even seen a alpha or beta version, so this could be another 2 years before we see any ROSv7, and in the meantime all new network interfaces is unusable because of old kernel being used. Broadcom have back ported their drivers to even kernel 2.6.x so I cant see how this can not be injected into the v3 kernel used by ROSv6.

Can you please explain? I'm sure we have other users with similar issues.

Re: 6.34 release candidate version topic!

Posted: Tue Nov 17, 2015 2:10 pm
by ufm
Hi Normis

This does not really help as we have been hearing about ROSv7 for a long time but not even seen a alpha or beta version, so this could be another 2 years before we see any ROSv7, and in the meantime all new network interfaces is unusable because of old kernel being used. Broadcom have back ported their drivers to even kernel 2.6.x so I cant see how this can not be injected into the v3 kernel used by ROSv6.

Can you please explain? I'm sure we have other users with similar issues.
Support promised to me ros7 (public alpha) in this year. month and a half left. With interest expect.
Although I believe that ros7 - it is a myth. As an afterlife, for example.

Re: 6.34rc6 After several versions reappeared error USB Flash disk.

Posted: Thu Nov 19, 2015 6:28 pm
by napismizpravu
RB433UAH (power 24V 2A) 6.33 ; 6.34rc3, 6.34rc6

After several versions reappeared error USB Flash disk.

http://forum.mikrotik.com/viewtopic.php ... 80#p507180

Re: 6.34 release candidate version topic!

Posted: Fri Nov 20, 2015 7:15 am
by strods
Version 6.34rc6 has been released.

Changes since previous rc version:

*) pppoe - fixed compliance to RFC4638 (MTU larger than 1488) again;
*) hotspot - fixed trial-uptime parsing from CLI to Winbox/Webbox;
*) lte - added support for multiple E3372 on the same device;
*) modem - added wpd-600n ppp support;
*) dhcpv6 client - support DAD and decline;
*) dhcpv4 server - fix kernel crash when restoring lease with queue for non-existent server;
*) console - fixed incorrect disabled firewall rule matching to "invalid flag";
*) ssh - fix key exchange when first kex packet follows.

Re: 6.34 release candidate version topic!

Posted: Fri Nov 20, 2015 8:58 pm
by nkourtzis
Version 6.34rc6 has been released.

Changes since previous rc version:

*) pppoe - fixed compliance to RFC4638 (MTU larger than 1488) again;

Nope. Still not establishing a connection with anything above 1488. Furhermore, it broke an existing connection which was using encryption, had to go unencrypted.

Re: 6.34 release candidate version topic!

Posted: Sun Nov 22, 2015 5:49 pm
by w0lt
Can't seem to get IPv6 DHCPv6 to work right. Keeps asking me for an "IA". The only way to get it to work is from the command line using the following string:
ipv6 dhcp-c add interface=ether8 add-default-route=yes request=prefix pool-name=IPv6
Anyone else seeing this?

-tp

Re: 6.34 release candidate version topic!

Posted: Mon Nov 23, 2015 8:26 am
by strods
Please everyone who is having issues with PPPoE run this command on your device:
"/system logging add topics=pppoe,debug"

After that try to establish connection again. Now generate supout file and send it to support@mikrotik.com together with problem description. We will look into it. Seems that issue is with specific PPPoE servers because RouterOS + RouterOS works without issues.

Re: 6.34 release candidate version topic!

Posted: Tue Nov 24, 2015 8:36 am
by strods
6.34rc8 version has been released

Changes since 6.34rc6:
*) usermanager - fixed usermanager webpage crash;
*) ipsec - fixed active SAs flushing;
*) bridge - fixed power-cycle-ping for bridge ports (was affecting all bridge);
*) ethernet - fixed link resetting on power-cycle-ping value change;
*) pppoe - made MTU discovery more robust;
*) hotspot - added option to login user manually from cli.

Re: 6.34 release candidate version topic!

Posted: Tue Nov 24, 2015 9:37 pm
by romihg
Can't seem to get IPv6 DHCPv6 to work right. Keeps asking me for an "IA". The only way to get it to work is from the command line using the following string:
ipv6 dhcp-c add interface=ether8 add-default-route=yes request=prefix pool-name=IPv6
Anyone else seeing this?

-tp
[admin@MikroTik] /ipv6 address> print
Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local
# ADDRESS FROM-POOL INTERFACE ADVERTISE
0 IG 2a00:xxxx:xxxx:xxxx::1/64 SiolIPv6 bridge yes
1 DL fe80::4e5e:cff:fe27:d06a/64 bridge no
2 DL fe80::4e5e:cff:fe27:d069/64 ether1 no
3 DL fe80::e/64 pppoe-out1 no

[admin@MikroTik] /ipv6 dhcp-client> print
Flags: D - dynamic, X - disabled, I - invalid
# INTERFACE STATUS PREFIX ADDRESS
0 I pppoe-out1 stopped


And yes same error if i try with new config. Going back to stable

Re: 6.34 release candidate version topic!

Posted: Thu Nov 26, 2015 8:30 am
by strods
Version 6.34rc9 has been released.

Changes since previous version:

*) ppp - fixed dynamic filter rule adding on some firewall filter configurations;
*) vrrp - fixed on-backup script;
*) ethernet - fixed link resetting on power-cycle-ping value change;
*) pppoe - improved MTU discovery compatibility with other vendors;
*) hotspot - fixed login by mac-cookie when roaming among hotspot servers.

Re: 6.34 release candidate version topic!

Posted: Thu Nov 26, 2015 9:50 am
by BartoszP
Dear Strods,

Is there any possibilty that you will be more elaborate on what particulary fix fixed ?

What " fixed on-backup script;" fixed ? Any example ? Description ? Link to forum discussion on that error ? Anything ?

Re: 6.34 release candidate version topic!

Posted: Thu Nov 26, 2015 11:10 am
by MartijnVdS
Dear Strods,

Is there any possibilty that you will be more elaborate on what particulary fix fixed ?

What " fixed on-backup script;" fixed ? Any example ? Description ? Link to forum discussion on that error ? Anything ?
http://wiki.mikrotik.com/wiki/Manual:In ... _reference

VRRP can execute a script when the node switches to "backup" mode. And apparently, that was buggy.

Re: 6.34 release candidate version topic!

Posted: Thu Nov 26, 2015 11:46 am
by BartoszP
I know that VRRP could execute scripts.
I am asking what was buggy ? Should I be worry if I use it ? Maybe I am "fighting" similar problem which is the ROS error but not mine ?
"Apparently it was buggy" is not the expected answer.

Re: 6.34 release candidate version topic!

Posted: Thu Nov 26, 2015 12:19 pm
by macgaiver
I know that VRRP could execute scripts.
I am asking what was buggy ? Should I be worry if I use it ? Maybe I am "fighting" similar problem which is the ROS error but not mine ?
"Apparently it was buggy" is not the expected answer.
Question should be - is it working for you? If yes, do not worry, keep using it. If you notice some problem then it is good time to upgrade. Time of global bugs in RouterOS is almost over, most of bugs now are very specific to particular configuration and particular installation. This forum is getting boring, and that is already saying something :) - that everything mostly works :)

Re: 6.34 release candidate version topic!

Posted: Thu Nov 26, 2015 12:40 pm
by BartoszP
Forum is boring ?? ....do not read it :-)

The rule of thumb is "Not broken, do not fix it" but it is "bleeding edge" topic so why not to inform users what and why was fixed ?
I am asking but it does not mean that I have problem. Maybe SOMEONE ELSE has ? Maybe SOMEONE ELSE has unexpected ROS behoviour and it could resolve problem.
I know that "Speech is silver, silence is golden" but too much silence does not help in communication.

Re: 6.34 release candidate version topic!

Posted: Thu Nov 26, 2015 12:53 pm
by ebreyit
Following work from the guys at Mikrotik I can confirm that RFC4638 1500MTU via PPPoE on standard UK FTTC connections is now working with 6.34rc9

Tested on CCR1009, SXT SA5, and a RB2011 so far with ECI B-FOCuS, and Huawei HG612 Modems (as supplied by OpenReach, unmodified)

Tested on 4 Entanet accounts(4 different cabinets)

Will be testing more ISP's shortly

Instruction for the OR supplied white box modems
  1. Just increase the MTU to 1508 on the interface connected to the Modem then reboot the modem(takes ages for the modem to respond otherwise)
  2. Increase the MTU and MRU on the PPPoE client to 1500
  3. Once successfully established @1500, remove any TCP MSS Mangle rules etc.
Version 6.34rc9 has been released.

Changes since previous version:

*) ppp - fixed dynamic filter rule adding on some firewall filter configurations;
*) vrrp - fixed on-backup script;
*) ethernet - fixed link resetting on power-cycle-ping value change;
*) pppoe - improved MTU discovery compatibility with other vendors;
*) hotspot - fixed login by mac-cookie when roaming among hotspot servers.

Re: 6.34 release candidate version topic!

Posted: Thu Nov 26, 2015 6:40 pm
by w0lt
Still having the same IPv6 DHCP issue with ROS 6.34rc9, when requesting a prefix:
IPv6 DHCP rc9.png

Re: 6.34 release candidate version topic!

Posted: Fri Nov 27, 2015 9:03 am
by strods
Version 6.34rc11 has been released.

Changes since 6.34rc9:

*) hotspot - fixed login by mac-cookie when roaming among hotspot servers;
*) hotspot - add html-directory-override for read-only directory on usb flash;
*) hotspot - add uptime, byte and packet counter variables to logout script;
*) net - fix statistics counters jumping up to 4G;
*) vrrp - fix arp=reply-only;
*) vrrp - do not warn about version mismatch if VRID does not match;
*) vrrp - allow VRRP to work behind firewall and NAT rules;
*) firewall - SIP helper update for newer Cisco phones.

Re: 6.34 release candidate version topic!

Posted: Fri Nov 27, 2015 11:09 am
by andriys
*) firewall - SIP helper update for newer Cisco phones.
Hi strods. Can you clarify, please, which SIP features/headers are now additionally supported?

Re: 6.34 release candidate version topic!

Posted: Fri Nov 27, 2015 1:00 pm
by sergejs
The patch applies for newer Cisco phones, and enables NAT traversal for Cisco IP phones ( e.g. 794x, 796x).
If anybody has such phones, it would be great to get feedback, how they work in NAT environment.

Re: 6.34 release candidate version topic!

Posted: Tue Dec 01, 2015 3:46 pm
by strods
6.34rc12 has been released.

Changes since previous version:

*) hotspot - show cookie add/remove events in hotspot,debug log;
*) hotspot - allow static entries with the same mac on multiple hotspot servers;
*) hotspot - do not remove mac-cookie in case of radius timeout;
*) hotspot - added byte limits option for default-trial users;
*) email - make password field sensitive in console;
*) dhcpv6-client - add 0x in front of DUID;
*) dhcpv6-server - fix state on rapid commit;
*) dhcpv6-server - fix preference option in packet generation;
*) upnp - fixed memory leak;
*) ipsec - make sure that dynamic policy always has dynamic flag;
*) ssh - avoid double session cleanup;
*) CAPsMAN - use CAP name in log when remote-cap is deleted (wireless-cm2).

Re: 6.34 release candidate version topic!

Posted: Tue Dec 01, 2015 5:00 pm
by ismets
Hi
Last night update 34.rc11 my backup router CCR1036-12G-4S on datacenter.

Cant boot :oops:

Re: 6.34 release candidate version topic!

Posted: Tue Dec 01, 2015 9:10 pm
by Kevo
We've apparently been having some SIP helper issues since loading 6.34rc11 on a 750GL. This is the first new version I've tried on it since 6.30.4. The problem is intermittent and has been happening off and on. I've just started looking into it.

The problem appears to involve bogus sip invites. I haven't dug into it much yet, but we got a failed authentication in the log for a SIP invite at an address we did not intend to be talking to.

We have cable internet service and the address in the invite URL was another CPE address presumably connected to the same cable infrastructure we are. At the time this happened we were trying to call out on a sip trunk and that call failed with this.

app_dial.c: -- Called SIP/outbound-trunk/19995551111
chan_sip.c: Failed to authenticate on INVITE to '<sip:47887@70.x.x.x>;tag=as7a309b79'
app_dial.c: -- SIP/outbound-trunk-0000000d is circuit-busy

The 70.x.x.x address is what I believe to be another CPE attached at the same router we are. It's a one hop traceroute.

I tried turning off the SIP helper, but calls wouldn't go through then, so I turned it back on and left direct media off. Seems to work, but the problem was intermittent, so I'm still waiting to see if that actually changed anything.

Before this update everything had been working fine for a long time.

Re: 6.34 release candidate version topic!

Posted: Wed Dec 02, 2015 11:49 pm
by Kevo
Settings changes didn't fix the SIP issue. I may try downgrading later and see if it goes away. It's going to be a hassle to try and capture packets on our sip box since it runs on a Pi.

Re: 6.34 release candidate version topic!

Posted: Thu Dec 03, 2015 11:52 am
by thantoldo
*) upnp - fixed memory leak

Anything more enlightening? Archs, configuration affected?

Regards,

Thanos

Re: 6.34 release candidate version topic!

Posted: Thu Dec 03, 2015 3:40 pm
by strods
Version 6.34rc14 has been released.

Changes since previous version:
*) dhcpv6 - varius changes on client, server, relay optimization.
*) ethernet - fixed 10/100Mbps autonegotiation fails on RB922UAGS ether1;
*) arp - show incoplete arp entries.

Re: 6.34 release candidate version topic!

Posted: Thu Dec 03, 2015 5:48 pm
by w0lt
Still having the same IPv6 DHCP issue with ROS 6.34rc9, when requesting a prefix:
IPv6 DHCP rc9.png
This problem still exists with v6.34rc14.
Works fine with v6.33.2

-tp

Re: 6.34 release candidate version topic!

Posted: Fri Dec 04, 2015 2:12 am
by Kevo
My SIP problem seems to be unrelated to the upgrade. Just a coincidence that the problem occurred shortly after the upgrade.

Re: 6.34 release candidate version topic!

Posted: Fri Dec 04, 2015 6:30 pm
by krisjanis
Version 6.34rc16 has been released.

Changes since previous version:
*) dude - “The reports of my death have been greatly exaggerated”;
*) dude - dude RouterOS package added for tile and x86 (CHR) arhitecture;
*) dude - initial work on dude intergration into RouterOS;
*) webfig - didn't show zero values in CRS ingress/egress vlan translation rules;
*) netwatch - make work with ping timeouts more precise;
*) btest - fix crash on stop/start with fastpath enabled;
*) hotspot - added missing favicon.ico in hotspot html pages;

Re: 6.34 release candidate version topic!

Posted: Fri Dec 04, 2015 7:44 pm
by aboiles
RB2011UiAS-2HnD upgrade from 6.34rc12 to 6.34rc16 resulted in endless reboot.

RB951G-2HnD upgrade from 6.34rc12 to 6.34rc16 worked correctly

UPDATE--

RouterBOOT booter 3.24

RouterBoard 2011UiAS-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 from nand... OK
setting up elf image... OK
jumping to kernel code
ERROR: no system package found!
Kernel panic - not syncing: Attempted to kill init!
Rebooting in 1 seconds..

netinstall 6.33.2, upgraded via package manager to 6.34r16 with no issues

????

Re: 6.34 release candidate version topic!

Posted: Mon Dec 07, 2015 5:18 pm
by RusConSPb
RB2011UiAS-2HnD upgrade from 6.34rc12 to 6.34rc16 resulted in endless reboot.

RB951G-2HnD upgrade from 6.34rc12 to 6.34rc16 worked correctly
?
Almost same thing with "Stable" version"

After update from 6.33.1 to 6.33.3 two of four my Mikrotiks didn't not boot!!! This firmware is not compatible with all devices/configurations! Do not update your production routers...

2 RB951G-2HnD updated successfully

1 RB2011UiAS didn't boot after update - stopped on "Starting Services" with all ethernet status LEDs off (no second beep). :shock:

1 RB751G-2HnD didn't boot after update - stopped somewhere during boot. :shock:

I was able to reset both routers and after restoring config from backup - it was stopped again. After it I tested latest Beta and 6.33.2 - same result.

After downgrading to 6.33.1 and restoring config from backup - everything working again... :)

Now I'm afraid to do future upgrades... something wrong with this new firmwares... be aware!!!!!



Dear MikroTik - is there any way to see, why my routers doesn't boot after latest firmware updates?

Re: 6.34 release candidate version topic!

Posted: Tue Dec 08, 2015 2:18 am
by tagno25
Still having the same IPv6 DHCP issue with ROS 6.34rc9, when requesting a prefix:
IPv6 DHCP rc9.png
This problem still exists with v6.34rc14.
Works fine with v6.33.2

-tp
6.34rc3 added the ability to request a IPv6 address via the DHCPv6-client.

You currently have to add the IPv6 DHCP client via the terminal. The GUI does not have a way to set the request type (address and/or prefix).

example:
/ipv6 dhcp-client add interface=ether1 request=address,prefix pool=test

If you have request include prefix, then you must set a pool.

Re: 6.34 release candidate version topic!

Posted: Tue Dec 08, 2015 11:04 am
by strods
Version 6.34rc18 has been released.

Changes since previous version:

*) usb - enable ch341 serial module;
*) lte - make sure that both LTE miniPCI-e cards are recognised;
*) ppp - make PPP active print radius & !radius conditions work;
*) winbox - show fast-path per interface counters;
*) log - log link up/down events only when link actually has changed its state;
*) romon - fixed crash on RoMON if fast-path was active;
*) romon - do not accept multicast id;
*) winbox - show Common-Name of certificates in certificate list;
*) e-mail - do not reset server address after changing configuration;
*) winbox - added units to PCQ queue fields;
*) winbox - added LCD menu for RB3011;
*) smb - show correct interface name in SMB debug logs;
*) net - do not break connection when interface is added to bridge.

Re: 6.34 release candidate version topic!

Posted: Tue Dec 08, 2015 12:37 pm
by SirDJNeo
First post... Just my 2cents

I see there has finally been made progress on Hotspot side of things with Trial Bytes limit.

^^Something that I had scripted for about 2 years now, so its nice to see something more built in now.

Before I get into the issues, must say that works well, and have been looking forward to it since starting with mainly hotspot use of non wireless router-boards. Nice to see it built in for once, which will save me some CPU power with some older gen 32M 750s.

Is there any reason why the method used to limit per trial user is done by some magical user that is force added with upgrade, instead of for the server profile?

There are a few issues:

You cannot change which server profile its attached to, meaning that if you have 4 profiles with VLAN's you are still limited to the one global for ALL and not for just the server which results in being constrained by not being able to allow 50MB on one profile and 100MB on the other perhaps.

Also the fact that you currently cant change the Comment on the user is also an unknown?? Would be nice having it look neater instead.

Is there any reason why its can't be added to the server profile like the current global setting with trial on prior versions to 6.34RC? As that would make it usable for having multiple server profiles, aswell as there is already Uptime limit, reset limit and choice of User Profile already pre-built into the Server profile.

Surely can't be too much effort to add additional option to the global server profile than creating a extra user that contains the use of multiple server profiles.

Besides that, great work keep it up!

Re: 6.34 release candidate version topic!

Posted: Tue Dec 08, 2015 7:45 pm
by dimsoft
I install 6.34rc and Ipv6 per pppoe as dhcpv6 client has broken.
I update to 6.34rc18 but status DHCPv6 Client is stoped.

How run IPv6 ?

Re: 6.34 release candidate version topic!

Posted: Wed Dec 09, 2015 8:34 am
by strods
Version 6.34rc19 has been released.

Changes since previous version:

*) CHR - implemented trial support for different CHR speed tiers;
*) dhcpv6-client - fix add route/address;

Re: 6.34 release candidate version topic!

Posted: Wed Dec 09, 2015 9:49 am
by kometchtech
I install 6.34rc and Ipv6 per pppoe as dhcpv6 client has broken.
I update to 6.34rc18 but status DHCPv6 Client is stoped.

How run IPv6 ?
Current situation seems to be able to support only at the command.
[admin@Mikrotik] /ipv6 dhcp-client> add interface=ether5 request=prefix add-default-route=no pool-name=ipoe pool-prefix-length=56 use-peer-dns=no

Re: 6.34 release candidate version topic!

Posted: Wed Dec 09, 2015 10:29 am
by dimsoft
Version 6.34rc19 has been released.

Changes since previous version:

*) CHR - implemented trial support for different CHR speed tiers;
*) dhcpv6-client - fix add route/address;
IPv6 dont work

[zagvozkin@Franko-CCR1009] /ipv6 dhcp-client> /ipv6 dhcp-client print detail
Flags: D - dynamic, X - disabled, I - invalid
0 I interface=pppoe-dom290 status=stopped duid="0x000300014c5e0c0339fe" dhcp-server-v6=:: request=prefix add-default-route=yes use-peer-dns=yes pool-name="ipoe" pool-prefix-length=64 prefix-hint=::/0

Re: 6.34 release candidate version topic!

Posted: Wed Dec 09, 2015 10:30 am
by dimsoft
Current situation seems to be able to support only at the command.
[admin@Mikrotik] /ipv6 dhcp-client> add interface=ether5 request=prefix add-default-route=no pool-name=ipoe pool-prefix-length=56 use-peer-dns=no
at 6.34rc19 dont work

Re: 6.34 release candidate version topic!

Posted: Wed Dec 09, 2015 5:40 pm
by jondavy
WinBox queue, when used Parent: x does not show the hierarchy only after some filtering column

Re: 6.34 release candidate version topic!

Posted: Wed Dec 09, 2015 7:32 pm
by zennik
Found a nice little bug in RC19.

Profile-defined Routes in PPTP/L2TP/OVPN connections aren't being sent to the correct tunnels

Site A is 192.168.146.0/24
Site B is 192.168.144.0/24
Site C is 192.168.1.0/24

Right now, it's pushing 1.0/24 and 144.0/24 to site C, and 146.0/24 to site A

Re: 6.34 release candidate version topic!

Posted: Wed Dec 09, 2015 7:34 pm
by zennik
And apparently rebooting the router again cleared up that little problem. Still concerning.

Re: 6.34 release candidate version topic!

Posted: Wed Dec 09, 2015 9:23 pm
by andriys
Profile-defined Routes in PPTP/L2TP/OVPN connections aren't being sent to the correct tunnels
What are profile-defined routes? Where exactly have you managed to define them?

Re: 6.34 release candidate version topic!

Posted: Wed Dec 09, 2015 10:08 pm
by htluvit
6.34rc8 version has been released

Changes since 6.34rc6:
*) usermanager - fixed usermanager webpage crash;
*) ipsec - fixed active SAs flushing;
*) bridge - fixed power-cycle-ping for bridge ports (was affecting all bridge);
*) ethernet - fixed link resetting on power-cycle-ping value change;
*) pppoe - made MTU discovery more robust;
*) hotspot - added option to login user manually from cli.
Could you please provide the CLI command to login user manually? I couldnt find it anywhere on the latest RC firmware

Re: 6.34 release candidate version topic!

Posted: Fri Dec 11, 2015 2:33 pm
by nkourtzis
Hello.

I found out something that for me is kind of a bug. Say you have a not always-on interface, such as a pppoe connection, and you have manually added it to UPnP. When the connection is established, if the "use UPnP" setting is set to yes, it tries to add itself to UPnP-enabled interfaces and since it already exists there, it cannot do that. When this happens, the connection is aborted and an error is logged. This behaviour is wrong, since the requirement for the connection to be UPnP-enabled is already met even if it is added by hand. So the connection should not fail altogether, but rather issue a warning instead of an error and still connect.

N.

Re: 6.34 release candidate version topic!

Posted: Fri Dec 11, 2015 9:59 pm
by zennik
Profile-defined Routes in PPTP/L2TP/OVPN connections aren't being sent to the correct tunnels
What are profile-defined routes? Where exactly have you managed to define them?
I push it out via RADIUS, but there's a field under PPP Secrets for you to define what to route to the far end of a tunnel once it is established.

Re: 6.34 release candidate version topic!

Posted: Fri Dec 11, 2015 10:24 pm
by RafGan
Hello.

After upgrade to 6.34rc20 I can't login on my router, x86 based - Winbox (both versions): login timeout, telnet/ssh: connection closed (after about one minute waiting). Without this behaviour, other jobs are OK. Router is far away from me.
Any help?

Regards,
RafGan

Re: 6.34 release candidate version topic!

Posted: Fri Dec 11, 2015 11:13 pm
by compctech
Hello.

After upgrade to 6.34rc20 I can't login on my router, x86 based - Winbox (both versions): login timeout, telnet/ssh: connection closed (after about one minute waiting). Without this behaviour, other jobs are OK. Router is far away from me.
Any help?

Regards,
RafGan

I am having the same issues on x86. Can't login at the console as well. Dude updated and the Windows client updated and can login to dude.

Re: 6.34 release candidate version topic!

Posted: Sat Dec 12, 2015 1:16 am
by Rhapsody01
Hello.

After upgrade to 6.34rc20 I can't login on my router, x86 based - Winbox (both versions): login timeout, telnet/ssh: connection closed (after about one minute waiting). Without this behaviour, other jobs are OK. Router is far away from me.
Any help?

Regards,
RafGan

I am having the same issues on x86. Can't login at the console as well. Dude updated and the Windows client updated and can login to dude.
Same here, except routeros also reboots randomly.
Was on 6.33.1, updated to 6.34RC20.
Bad credentials are filtered out normaly, but good ones timeout.

Any help here would be greatly appreciated :)

Regards,
Fabien

Re: 6.34 release candidate version topic!

Posted: Sat Dec 12, 2015 5:31 am
by MAYAKNET
Hello.

After upgrade to 6.34rc20 I can't login on my router, x86 based - Winbox (both versions): login timeout, telnet/ssh: connection closed (after about one minute waiting). Without this behaviour, other jobs are OK. Router is far away from me.
Any help?

Regards,
RafGan

Agree.
The same situation...
It is a pity not wait and updated, need urgent help ...

RU:

Не обновляйтесь на 6.34rc20 у кого она стоит на x86 - потеря доступа к железке...

Posted: Sat Dec 12, 2015 6:11 am
by jarda
I wonder still again and again why so much people install rc or whatever new versions of ros on productive and or distant devices. These versions are for testing purposes only. Everyone should carefully select what wersion he will deploy and make his own tests on lab devices to be at least somehow confident that it is not harmful.

If you cannot access remote device you have to go there and check what happened. Most probably none on the forum can help you with this. For critical devices it is smart to have another rb nearby connected by serial cable to each other so you can try to see serial console remotely. Remote resetator could be helpful too.

Re:

Posted: Sat Dec 12, 2015 7:35 am
by MAYAKNET
I wonder still again and again why so much people install rc or whatever new versions of ros on productive and or distant devices. These versions are for testing purposes only. Everyone should carefully select what wersion he will deploy and make his own tests on lab devices to be at least somehow confident that it is not harmful.

If you cannot access remote device you have to go there and check what happened. Most probably none on the forum can help you with this. For critical devices it is smart to have another rb nearby connected by serial cable to each other so you can try to see serial console remotely. Remote resetator could be helpful too.

Well done! Bravo!

Now tell me what to do for those who can come and get it hung from the device.

P.S. Still available update 6.34rc20, though like how to understand what can cause a serious problem ...

Re: 6.34 release candidate version topic!

Posted: Sun Dec 13, 2015 12:19 am
by uenderson
I'm testing the 6.34rc19 version in a 1036, and three times when trying to use the torch occurred kernel error.
Image
-----------------
Image


make downgrade and:
Image

Re: 6.34 release candidate version topic!

Posted: Sun Dec 13, 2015 12:59 pm
by kiketg
Hello.

After upgrade to 6.34rc20 I can't login on my router, x86 based - Winbox (both versions): login timeout, telnet/ssh: connection closed (after about one minute waiting). Without this behaviour, other jobs are OK. Router is far away from me.
Any help?

Regards,
RafGan

I am having the same issues on x86. Can't login at the console as well. Dude updated and the Windows client updated and can login to dude.

Same situation here, on x86. Can't login ssh, winbox, telnet, mactelnet, web. None work.

Re: 6.34 release candidate version topic!

Posted: Mon Dec 14, 2015 3:59 am
by MAYAKNET
Is there somebody who will tell us how to be. The problem is serious and urgent. The equipment in front of me. But there is no access, and many settings BGP filters, etc.
Nothing but RouterOS reinstallation does not occur, and it is so much work done settings.
Help me find a way out.

Re: 6.34 release candidate version topic!

Posted: Mon Dec 14, 2015 10:05 am
by strods
6.34rc21 version has been released.

Changes since 6.34rc19:

*) quicket - support CAP mode on all existing wireless packages;
*) kernel - general improvement for core process scheduling;
*) wlan - add united states3 country;
*) fast-path - fix locking issue which could lead to reboot loop (introduced in 6.34rc20);
*) userman4 - try loading signup files from db path first;
*) sstp - allow to limit tls version to v1.2 only;
*) chr - make tool profile work on 64bit x86;
*) dhcpv6-server - added binding server=all option;
*) btest - improve UDP tx rate precision;
*) btest - fix potential crash after btest release;
*) hotspot - added html-directory-override & recognize default hotspot user;
*) hotspot - fixed export of default trial user;
*) hotspot - fixed memory leak on https requests;
*) winbox - added + & - to igmp proxy mfc;
*) winbox - allow to specify amsdu-limit & amsdu-threshold on 11n wifi cards;
*) winbox - allow to specify traffic-monitor threshold in k & M units + specify that those are bits;
*) winbox - added multicast-buffering & keepalive-frames settings to wireless interfaces.

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

Re: 6.34 release candidate version topic!

Posted: Mon Dec 14, 2015 12:10 pm
by nkourtzis
*) kernel - general improvement for core process scheduling

Elaborate please? Effects?

Re: 6.34 release candidate version topic!

Posted: Mon Dec 14, 2015 12:27 pm
by kiketg
Hello.

After upgrade to 6.34rc20 I can't login on my router, x86 based - Winbox (both versions): login timeout, telnet/ssh: connection closed (after about one minute waiting). Without this behaviour, other jobs are OK. Router is far away from me.
Any help?

Regards,
RafGan

I am having the same issues on x86. Can't login at the console as well. Dude updated and the Windows client updated and can login to dude.

Same situation here, on x86. Can't login ssh, winbox, telnet, mactelnet, web. None work.
The only way to get access again, that i found, is netinstalling RouterOS on that x86 with problem, check "keep old configuration" checkbox, and select the packages (6.33.3) everything works fine.

Re: 6.34 release candidate version topic!

Posted: Mon Dec 14, 2015 12:28 pm
by strods
nkourtzis - If your router was rebooting itself with kernel failure, then after upgrade it might not do it.

Re: 6.34 release candidate version topic!

Posted: Mon Dec 14, 2015 12:50 pm
by kaptain46
Hi guys,
I see on change log this interesting feature:

*) hotspot - added option to login user manually from cli

But I cannot find any new function about it on /ip hotspot

Does anyone already test it?

Re: 6.34 release candidate version topic!

Posted: Mon Dec 14, 2015 1:14 pm
by strods
We have received confirmation that x86 lock-up issue is fixed with 6.34rc21.

Re: 6.34 release candidate version topic!

Posted: Mon Dec 14, 2015 1:48 pm
by keithy
Hi,

Thanks for bringing the Dude development back to life :)

I cant find the dude client download though??

Re: 6.34 release candidate version topic!

Posted: Mon Dec 14, 2015 1:57 pm
by normis
Hi,

Thanks for bringing the Dude development back to life :)

I cant find the dude client download though??
It looks like only TILE is missing the Client. You can download it from x86 section, it is the same for all architectures.

Re: 6.34 release candidate version topic!

Posted: Tue Dec 15, 2015 10:15 am
by nkourtzis
After upgrading to rc21, I see a constantly higher cpu load on all my devices than before. My devices are not very busy, so the increase is not causing any problems. CPU in the graph has gone from about 1-2% to 4-5%. I am just wondering whether is it normal.

Re: 6.34 release candidate version topic!

Posted: Tue Dec 15, 2015 10:16 am
by normis
After upgrading to rc21, I see a constantly higher cpu load on all my devices than before. My devices are not very busy, so the increase is not causing any problems. CPU in the graph has gone from about 1-2% to 4-5%. I am just wondering whether is it normal.
Check "Tools -> Profile" to see what specifically is causing it.

Re: 6.34 release candidate version topic!

Posted: Tue Dec 15, 2015 11:18 am
by nkourtzis
After upgrading to rc21, I see a constantly higher cpu load on all my devices than before. My devices are not very busy, so the increase is not causing any problems. CPU in the graph has gone from about 1-2% to 4-5%. I am just wondering whether is it normal.
Check "Tools -> Profile" to see what specifically is causing it.
I cannot be sure, because I do not have knowledge of the respective percentages before the upgrade. Also it is not easy to derive any conclusions from instantaneous readings. It would be useful to have some historical data in profiling (like accumulative cpu time of each process etc). Also, what is this "unclassified" category? It seems to have a higher cpu share in older devices (such as an Omnitik).

Re: 6.34 release candidate version topic!

Posted: Tue Dec 15, 2015 11:20 am
by normis
After upgrading to rc21, I see a constantly higher cpu load on all my devices than before. My devices are not very busy, so the increase is not causing any problems. CPU in the graph has gone from about 1-2% to 4-5%. I am just wondering whether is it normal.
Check "Tools -> Profile" to see what specifically is causing it.
I cannot be sure, because I do not have knowledge of the respective percentages before the upgrade. Also it is not easy to derive any conclusions from instantaneous readings. It would be useful to have some historical data in profiling (like accumulative cpu time of each process etc). Also, what is this "unclassified" category? It seems to have a higher cpu share in older devices (such as an Omnitik).
Normally Unclassified should be 0. If you have something there above a few percent, you should make a supout.rif file and email support.

Re: 6.34 release candidate version topic!

Posted: Tue Dec 15, 2015 3:19 pm
by Zorro
*) kernel - general improvement for core process scheduling

Elaborate please? Effects?
thats would be perhaps some Tile arch improvements, leading to *mindblowing* performance boost and scalability, lol ;)
but more likely its MIPS-BE arch fine-tuning, cuz since R 5.xx and R6.0x versions MIPS ISA and instruction set considerably reshuffled and tweaked toward SIMD data-flow(ASE and DSP usage strongly discouraged thus, even in "custom-made SDK's"like supplied by SoC vendors).
generally thats imply(thanks to re-inforced, normalised/aligned access to input-output, especially memory access)wastly better input-output and less delays and bitter IPC, especially integer(and R7 may bring newer FPU aswell as PEZY-style super-scalar portions with out-of order, perhaps, but R7 MIPS was still 1 year away ~ or so, yet :).

Re: 6.34 release candidate version topic!

Posted: Wed Dec 16, 2015 5:03 pm
by pbr3000
but R7 MIPS was still 1 year away ~ or so, yet :).
I really like your optimism! :lol:

Re: 6.34 release candidate version topic!

Posted: Thu Dec 17, 2015 2:25 pm
by strods
Version 6.34rc22 has been released.

Changes since previous version:

*) ssh - fix session clean-up;
*) ipsec - fix phase2 hmac-sha-256-128 truncation len from 96 to 128
This will break compatibility with all previous versions and any other
currently compatible software using sha256 hmac for phase2;
*) fetch - added 30 second connection time-out;
*) led - add wlan led to RB951Ui
*) dhcpv6-client - fix next resend time rounding error;
*) ssh, ftp - make read, write user group policy aware;
*) tunnel - fix keep-alive (introduced in 6.34rc);
*) net - do not allow to add new firewall rule before built-in;
*) cerm - show last crl update time.

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

Re: 6.34 release candidate version topic!

Posted: Thu Dec 17, 2015 3:06 pm
by grusu
I try to update on RB951G-2HnD test echipament from 6.34rc20 but with no success.
I find "System rebooted because of kernel failure" message on log.
New packages: routeros-mipsbe-6.34rc22.npk and ntp-6.34rc22-mipsbe.npk is on router file system.

Re: 6.34 release candidate version topic!

Posted: Fri Dec 18, 2015 12:05 am
by jondavy
in Winbox and in terminal in wireless section, hide the option and button of the CAP if the wireless-cm package is not enabled or installed

or warn that to use this option you must enable the wireless-cm package

it does not make sense appear this option without the package and it will not work,
and this confuses people.

Re: 6.34 release candidate version topic!

Posted: Fri Dec 18, 2015 12:53 am
by SirDJNeo
Still not getting any response on this:
Capture.JPG
Is there a specific reason why it has not been added to the server profile???

Re: 6.34 release candidate version topic!

Posted: Fri Dec 18, 2015 1:25 am
by InoX
To many columns? :D

Re: 6.34 release candidate version topic!

Posted: Fri Dec 18, 2015 1:52 am
by Beone
v6.34rc22 breaks TCP MSS clamping features for PPP interfaces

Re: 6.34 release candidate version topic!

Posted: Fri Dec 18, 2015 2:06 am
by BartoszP
*) ipsec - fix phase2 hmac-sha-256-128 truncation len from 96 to 128
This will break compatibility with all previous versions and any other currently compatible software using sha256 hmac for phase2;
So how to upgrade if all connections will be lost without upgrading all devices at once ?

Re: 6.34 release candidate version topic!

Posted: Fri Dec 18, 2015 3:32 am
by jondavy
Winbox not properly shown at the top of the page if I select all
Time, Date, CPU, Memory and Uptime

Re: 6.34 release candidate version topic!

Posted: Fri Dec 18, 2015 5:37 am
by kometchtech
*) ipsec - fix phase2 hmac-sha-256-128 truncation len from 96 to 128
This will break compatibility with all previous versions and any other
currently compatible software using sha256 hmac for phase2;
Want to know more details about this.

Re: 6.34 release candidate version topic!

Posted: Fri Dec 18, 2015 7:37 am
by strods
InoX - In next rc version columns will be renamed. Half of them are FastPath counters;
grusu - You will have to use Netinstall because 6.34rc20 was buggy version;
jondavy - We will look into this;
Beone - Please send supout files to support@mikrotik.com
BartoszP - That is exactly why we mentioned this in changelog. You have to find a way how to upgrade without losing connection to specific devices. Maybe change type of IPSec, upgrade and then change it back;
jondavy - What is wrong with Winbox? Please send screen shots to support@mikrotik.com
kometchtech - We have made sha256 compliant to current RFC, not old sha-256-96 draft

Re: 6.34 release candidate version topic!

Posted: Fri Dec 18, 2015 9:09 am
by nkourtzis
I try to update on RB951G-2HnD test echipament from 6.34rc20 but with no success.
I find "System rebooted because of kernel failure" message on log.
New packages: routeros-mipsbe-6.34rc22.npk and ntp-6.34rc22-mipsbe.npk is on router file system.

What saved my ass with this bug was a backup partition that I had on my device, which was running a slightly older ROS version. Booted to this, upgraded it and then copied it to the first one. It adds just a bit of maintainance overhead, but can save the day in some occasions. I am telling you this for future reference...

Re: 6.34 release candidate version topic!

Posted: Fri Dec 18, 2015 5:49 pm
by Zorro
would be nice to hear bit more about kernel-level improvements highlighted/mentioned in 6.34 descriptions.
would it be newer kernel or some features/code, backported to ?
( more likely last option, since only ROS 7 would had newer (4.3.3 ?) kernel, GCC/toolchain and relevant Tile improvements.)
also judging from recent Juniper disclosure about breach into their firmware of undisclosed source and similar changes in all xBSD networking stack and subsequent outcry among IT/telecom/itsec guys/world - its may be affecting relevant fixes too.
but R7 MIPS was still 1 year away ~ or so, yet :).
I really like your optimism! :lol:
judging from recent shift to 6.05 and from r7 timeline - its more likely to be within 10 months. so "one year" was reasonable/safe approximation, i think.
its more debatable survivability of MIPS "in general" than particular arch/generation delivery/production schedule.
also different ISA/arch generation release/schedule and based on it, devices - enteriely different things. R5 was happen to be late 2012 thing, but chips was surfaced bit later. and etc and etc, so on.

Re: 6.34 release candidate version topic!

Posted: Fri Dec 18, 2015 10:13 pm
by picacho99
This thread is to discuss about this candidate software version or to collect speculations and personal opinions about the stars in the sky ?!
Mikrotik does not like to share, only when "willing" to launch something new ....of course always late and incomplete but to improve definitelly over the time: always the same pattern.

Re: 6.34 release candidate version topic!

Posted: Fri Dec 18, 2015 10:28 pm
by Zorro
This thread is to discuss about this candidate software version or to collect speculations and personal opinions about the stars in the sky ?!
Mikrotik does not like to share, only when "willing" to launch something new ....of course always late and incomplete but to improve definitelly over the time: always the same pattern.
hardly its something specific, new and thus worthy to discuss and/or relevant to topic thing, thus.
and yes, hardly other networking companies are differ, lol. in fact, most are Lot worser :)

Re: 6.34 release candidate version topic!

Posted: Sat Dec 19, 2015 12:30 am
by picacho99
Mikrotik ?

Re: 6.34 release candidate version topic!

Posted: Sat Dec 19, 2015 11:58 pm
by pbr3000
This thread is to discuss about this candidate software version or to collect speculations and personal opinions about the stars in the sky ?!
Mikrotik does not like to share, only when "willing" to launch something new ....of course always late and incomplete but to improve definitelly over the time: always the same pattern.
The Zorro's reply is about "kernel - general improvement for core process scheduling" in the changelog from v6.34. From there he extrapolates to other issues that I found valid (and accurate).

Re: 6.34 release candidate version topic!

Posted: Mon Dec 21, 2015 8:19 am
by strods
General kernel improvement was an simple upgrade which can fix some of kernel failures on devices where CPU is 100% loaded.

Re: 6.34 release candidate version topic!

Posted: Mon Dec 21, 2015 12:08 pm
by strods
6.34rc23 version is released.

Changes since previous version:
*) crypto - fixed kernel failure in talitos HW encryption;
*) net - do not allow to add new firewall rule before built-in (reverted);
*) wireless - regular “wireless” package is now retired and replaced by "wireless-fp" and "wireless-cm2";
*) winbox - include FP in fast-path column names.

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

Re: 6.34 release candidate version topic!

Posted: Mon Dec 21, 2015 12:31 pm
by honzam
6.34rc23 version is released.

*) wireless - regular “wireless” package is now retired and replaced by "wireless-fp" and "wireless-cm2";
What is this?

regular wireless was removed in 6.30
*) removed wireless package from routeros bundle package,
new wireless-fp is left in place and wireless-cm2 added as option;

Re: 6.34 release candidate version topic!

Posted: Mon Dec 21, 2015 12:45 pm
by strods
honzam - If you use wireless package then you will not be able to upgrade. You must install either "wireless-fp" or "wireless-cm2" on your device, remove "wireless" package and upgrade after that.

Previous change simply removed "wireless" package from bundle. Now "wireless" package does not exist at all. Until 6.34rc23 "wireless" package was still available in our download page under "Extra packages".

Re: 6.34 release candidate version topic!

Posted: Mon Dec 21, 2015 2:00 pm
by honzam
Thank you for the explanation

Re: 6.34 release candidate version topic!

Posted: Tue Dec 22, 2015 3:10 pm
by raffav
Hello

i am unable to resolve DNS, using 6.34rc22-rc23 on the crs-125, but from crs i have internet access.
the CRS is connect to a 433 where get internet access
 resolve www.google.com
failure: dns server failure
11:13:06 system,info dns changed by Vaselli 
11:13:08 dns,packet --- sending udp query to 8.8.8.8:53: 
11:13:08 dns,packet id:e1d2 rd:1 tc:0 aa:0 qr:0 ra:0 QUERY 'no error' 
11:13:08 dns,packet question: www.google.com:A:IN 
11:13:17 dns,packet --- sending udp query to 8.8.8.8:53: 
11:13:17 dns,packet id:84a6 rd:1 tc:0 aa:0 qr:0 ra:0 QUERY 'no error' 
11:13:17 dns,packet question: cloud.mikrotik.com:A:IN 
11:14:17 dns,packet --- sending udp query to 8.8.8.8:53: 
11:14:17 dns,packet id:90e8 rd:1 tc:0 aa:0 qr:0 ra:0 QUERY 'no error' 
11:14:17 dns,packet question: cloud.mikrotik.com:A:IN 

Re: 6.34 release candidate version topic!

Posted: Tue Dec 22, 2015 3:13 pm
by normis
console and Winbox use different DNS settings. Using the GUI you use the DNS Server configured in your Windows computer. Using the command line, you use "ip dns" settings.

So in this case I guess your Windows PC has another DNS configured, but the 192.168.99.1 DNS is not responding. Try to enter 8.8.8.8 in your "ip dns" menu

Re: 6.34 release candidate version topic!

Posted: Tue Dec 22, 2015 3:20 pm
by raffav
console and Winbox use different DNS settings. Using the GUI you use the DNS Server configured in your Windows computer. Using the command line, you use "ip dns" settings.

So in this case I guess your Windows PC has another DNS configured, but the 192.168.99.1 DNS is not responding. Try to enter 8.8.8.8 in your "ip dns" menu

ignore the 192.168.99.1, it was not apllyed the server is 8.8.8.8

I am remotey accessing this CRS and 433 iam not in the same lan


CRS
[Vaselli@CRS] > resolve www.google.com
failure: dns server failure
[Vaselli@CRS] > ip dns print 
                servers: 8.8.8.8
        dynamic-servers: 
  allow-remote-requests: yes
    max-udp-packet-size: 4096
   query-server-timeout: 0ms
    query-total-timeout: 0ms
             cache-size: 2048KiB
          cache-max-ttl: 2d
             cache-used: 11KiB
[Vaselli@CRS] > ip dns cache print 
Flags: S - static 
 #   NAME        ADDRESS                                       TTL         
 0 S google      8.8.8.8                                       2d          
 1 S google      8.8.4.4                                       2d          
[Vaselli@CRS] > ip dns static print 
Flags: D - dynamic, X - disabled, R - regexp 
 #     NAME       ADDRESS                                      TTL         
 0     google     8.8.8.8                                      2d          
 1     google     8.8.4.4                                      2d  
 
RB433
[Vaselli@Raffa's MK] > resolve www.google.com
[Vaselli@Raffa's MK] > ip dns print          
                servers: 8.8.8.8
        dynamic-servers: 
  allow-remote-requests: yes
    max-udp-packet-size: 512
   query-server-timeout: 2s
    query-total-timeout: 10s
             cache-size: 2048KiB
          cache-max-ttl: 1w
             cache-used: 16KiB
[Vaselli@Raffa's MK] > ip dns cache print    
Flags: S - static 
 #   NAME       ADDRESS                                      TTL         
 0 S google     8.8.8.8                                      1d          
 1 S google     8.8.4.4                                      1d          
 2 S oi         200.222.122.132                              1d          
 3 S oi         200.222.123.100                              1d          
 4   therich... 192.237.140.116                              23h30m36s   
 5   cloud.m... 91.188.51.139                                1h26m10s    
 6   cloud.m... 81.198.87.240                                1h26m10s    
 7   costco.ca  170.167.8.7                                  4h8m53s     
 8   wikimap... 192.69.192.210                               20m33s      
[Vaselli@Raffa's MK] > ip dns static print 
Flags: D - dynamic, X - disabled, R - regexp 
 #     NAME      ADDRESS                                     TTL         
 0     Google    8.8.8.8                                     1d          
 1     Google    8.8.4.4                                     1d          
 2     OI        200.222.122.132                             1d          
 3     OI        200.222.123.100                             1d          
[Vaselli@Raffa's MK] > 

Re: 6.34 release candidate version topic!

Posted: Tue Dec 22, 2015 3:22 pm
by normis
How can I know what to ignore? Please post full and correct config so we can find the issue.

Re: 6.34 release candidate version topic!

Posted: Tue Dec 22, 2015 3:29 pm
by raffav
How can I know what to ignore? Please post full and correct config so we can find the issue.
ok, what part of the conf do you whant ?

Re: 6.34 release candidate version topic!

Posted: Tue Dec 22, 2015 3:38 pm
by normis
output of the command /export
and output of the ping to the DNS server that you will see in the export

Re: 6.34 release candidate version topic!

Posted: Tue Dec 22, 2015 3:50 pm
by raffav
/interface ethernet
set [ find default-name=ether23 ] comment=\
    "TRUNK TO 433UAH -eth2 (old-TRUNK TO CCR)"
/ip neighbor discovery
set ether23 comment="TRUNK TO 433UAH -eth2 (old-TRUNK TO CCR)"
/interface vlan
add interface=ether23 l2mtu=1584 name=vlan99_MGT vlan-id=99
/interface ethernet
set [ find default-name=ether2 ] master-port=ether23
set [ find default-name=ether3 ] master-port=ether23
set [ find default-name=ether4 ] master-port=ether23
set [ find default-name=ether5 ] master-port=ether23
set [ find default-name=ether6 ] master-port=ether23
set [ find default-name=ether7 ] master-port=ether23
set [ find default-name=ether8 ] disabled=yes master-port=ether23
set [ find default-name=ether9 ] master-port=ether23
set [ find default-name=ether10 ] master-port=ether23
set [ find default-name=ether11 ] master-port=ether23
set [ find default-name=ether12 ] master-port=ether23
set [ find default-name=ether13 ] master-port=ether23
set [ find default-name=ether14 ] master-port=ether23
set [ find default-name=ether15 ] master-port=ether23
set [ find default-name=ether16 ] master-port=ether23
set [ find default-name=ether17 ] master-port=ether23
set [ find default-name=ether18 ] master-port=ether23
set [ find default-name=ether19 ] master-port=ether23
set [ find default-name=ether20 ] comment="DECODER TV OI" master-port=ether23
set [ find default-name=ether21 ] comment="TRUNK TO 433UAH -eth3" \
    master-port=ether23
set [ find default-name=ether22 ] comment="TRUNK TO OI FIBRA" master-port=\
    ether23
/ip neighbor discovery
set ether20 comment="DECODER TV OI"
set ether21 comment="TRUNK TO 433UAH -eth3"
set ether22 comment="TRUNK TO OI FIBRA"
/interface ethernet switch
set forward-unknown-vlan=no
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip ipsec proposal
set [ find default=yes ] enc-algorithms=aes-128-cbc
/system logging action
set 0 memory-lines=10000
set 1 disk-file-name=""
/tool user-manager customer
set admin access=\
    own-routers,own-users,own-profiles,own-limits,config-payment-gw
/interface ethernet switch egress-vlan-tag
add tagged-ports=ether23 vlan-id=2
add tagged-ports=ether23 vlan-id=3
add tagged-ports=ether23 vlan-id=4
add tagged-ports=ether23 vlan-id=5
add tagged-ports=ether23 vlan-id=6
add tagged-ports=ether22,ether23 vlan-id=210
add tagged-ports=ether22,ether23 vlan-id=220
add tagged-ports=ether19,ether23 vlan-id=7
add tagged-ports=ether19,ether23,switch1-cpu vlan-id=99
/interface ethernet switch ingress-vlan-translation
add customer-vid=0 new-customer-vid=2 ports=\
    ether2,ether3,ether4,ether5,ether6,ether7,ether8 sa-learning=yes
add customer-vid=0 new-customer-vid=4 ports=ether14 sa-learning=yes
add customer-vid=0 new-customer-vid=5 ports=ether15 sa-learning=yes
add customer-vid=0 new-customer-vid=6 ports=ether16 sa-learning=yes
add customer-vid=0 new-customer-vid=3 ports=\
    ether9,ether10,ether11,ether12,ether13 sa-learning=yes
add customer-vid=0 new-customer-vid=220 ports=ether20 sa-learning=yes
add customer-vid=0 new-customer-vid=7 ports=ether17,ether18 sa-learning=yes
/interface ethernet switch vlan
add ports=ether2,ether3,ether4,ether5,ether6,ether7,ether8,ether23 vlan-id=2
add ports=ether9,ether10,ether11,ether12,ether13,ether23 vlan-id=3
add ports=ether14,ether23 vlan-id=4
add ports=ether15,ether23 vlan-id=5
add ports=ether16,ether23 vlan-id=6
add ports=ether22,ether23 vlan-id=210
add ports=ether20,ether22,ether23 vlan-id=220
add ports=ether19,ether23 vlan-id=7
add ports=ether19,ether23,switch1-cpu vlan-id=99
/interface wireless cap
set caps-man-addresses=192.168.99.1 certificate=request discovery-interfaces=\
    ether23 interfaces=*1 lock-to-caps-man=yes
/ip address
add address=192.168.88.2/24 interface=ether1 network=192.168.88.0
add address=192.168.99.2/24 interface=vlan99_MGT network=192.168.99.0
/ip cloud
set ddns-enabled=yes
/ip dns
set allow-remote-requests=yes cache-max-ttl=2d query-server-timeout=0ms \
    query-total-timeout=0ms servers=8.8.8.8
/ip dns static
add address=8.8.8.8 name=google ttl=2d
add address=8.8.4.4 name=google ttl=2d
/ip route
add distance=1 gateway=192.168.99.1
/ip service
set telnet address=\
    192.168.2.0/24,192.168.3.0/24,192.168.99.0/24,172.16.4.0/24
set ftp disabled=yes
set www port=8787
set ssh port=222
set api port=8730
set winbox port=8292
set api-ssl port=8731
/lcd
set backlight-timeout=15m
/lcd pin
set pin-number=8723
/routing igmp-proxy
set quick-leave=yes
/routing igmp-proxy interface
add
/system clock
set time-zone-autodetect=no time-zone-name=America/Sao_Paulo
/system identity
set name=CRS
/system lcd
set contrast=0 enabled=no port=parallel type=24x4
/system lcd page
set time disabled=yes display-time=5s
set resources disabled=yes display-time=5s
set uptime disabled=yes display-time=5s
set packets disabled=yes display-time=5s
set bits disabled=yes display-time=5s
set version disabled=yes display-time=5s
set identity disabled=yes display-time=5s
set vlan99_MGT disabled=yes display-time=5s
set wlan1 disabled=yes display-time=5s
set ether1 disabled=yes display-time=5s
set ether2 disabled=yes display-time=5s
set ether3 disabled=yes display-time=5s
set ether4 disabled=yes display-time=5s
set ether5 disabled=yes display-time=5s
set ether6 disabled=yes display-time=5s
set ether7 disabled=yes display-time=5s
set ether8 disabled=yes display-time=5s
set ether9 disabled=yes display-time=5s
set ether10 disabled=yes display-time=5s
set ether11 disabled=yes display-time=5s
set ether12 disabled=yes display-time=5s
set ether13 disabled=yes display-time=5s
set ether14 disabled=yes display-time=5s
set ether15 disabled=yes display-time=5s
set ether16 disabled=yes display-time=5s
set ether17 disabled=yes display-time=5s
set ether18 disabled=yes display-time=5s
set ether19 disabled=yes display-time=5s
set ether20 disabled=yes display-time=5s
set ether21 disabled=yes display-time=5s
set ether22 disabled=yes display-time=5s
set ether23 disabled=yes display-time=5s
set ether24 disabled=yes display-time=5s
set sfp1 disabled=yes display-time=5s
/system logging
add topics=dns,packet
/system ntp client
set enabled=yes primary-ntp=200.192.232.8 secondary-ntp=200.160.0.8
/tool romon
set enabled=yes
/tool romon port
add
/tool user-manager database
set db-path=user-manager
Vaselli@CRS] > ping 8.8.8.8
  SEQ HOST                                     SIZE TTL TIME  STATUS                                                                                                        
    0 8.8.8.8                                    56  52 4ms  
    1 8.8.8.8                                    56  52 5ms  
    2 8.8.8.8                                    56  52 6ms  
    3 8.8.8.8                                    56  52 6ms  
    4 8.8.8.8                                    56  52 6ms  
    5 8.8.8.8                                    56  52 6ms  
    6 8.8.8.8                                    56  52 5ms  
    7 8.8.8.8                                    56  52 6ms  
    sent=8 received=8 packet-loss=0% min-rtt=4ms avg-rtt=5ms max-rtt=6ms

Re: 6.34 release candidate version topic!

Posted: Tue Dec 22, 2015 4:08 pm
by strods
Your server query timeout values are 0.

Use:
/ip dns set query-server-timeout=2s query-total-timeout=10s

Re: 6.34 release candidate version topic!

Posted: Tue Dec 22, 2015 4:23 pm
by raffav
Your server query timeout values are 0.

Use:
/ip dns set query-server-timeout=2s query-total-timeout=10s

Thanks,
that "0s" was weird i dont touch the crs setting for a while i only set up to schedule to auto update the ros version

Re: 6.34 release candidate version topic!

Posted: Tue Dec 22, 2015 8:15 pm
by SirDJNeo
Capture.JPG
This is really going to be an issue in the future if not resolved.

Can anyone give feedback as to the reason why the bytes limit has not been imported into per server profile?

Will save me extra scripting if it can be added into the server profile than being added as GLOBAL for all.

Means add something that scripted works better as it can be done per server profile where this locks it down completely.

Thanks

Re: 6.34 release candidate version topic!

Posted: Wed Dec 23, 2015 6:00 pm
by krisjanis
@SirDJNeo

What is the exact problem with modifying the values in default-trial user entry? It's values are applied to all new users that connect as trial clients.

Also it can be done with individual default-trial user for each server. Check wiki article for example on this:
http://wiki.mikrotik.com/wiki/Manual:Trial_user_limits

Re: 6.34 release candidate version topic!

Posted: Wed Dec 23, 2015 7:31 pm
by SirDJNeo
@krisjanis

The issue is with it being globally set and not per server profile.

Meaning if I have 6 Server Profiles on one of my CCR1016's or CCR1009's then the ability to be able to set the trial byte limit per server profile would be useful vs forcing all 6+ on 250MB vs being able to set each one separately. Especially when all 6 profiles / hotspot seperations have different requirements.

Currently this can be done via scripting but seeing as the devs were nice enough to add a method to be able to set the users bytes limit with a "Default User" then ability to have it be able to set per profile like the uptime and reset time can be set per server profile would be nice.

But without being able to set it per server profile either entails that I need to put a 2nd CCR1016 next to it for a second server profile or just do it all via script.

If you understand what I mean.

EDIT:
Unless I am understanding incorrectly and that for every server profile one of the default user's automatically get added?
If so, I will retest again. But why would it not just be added directly into the server profile vs into the Users?

Re: 6.34 release candidate version topic!

Posted: Wed Dec 23, 2015 7:43 pm
by SirDJNeo
Ah, I see... For 2nd server profile if you don't want the GLOBAL one then you have to set one manually....

Any comment on the reason why it was not implemented straight into the Server profile like the uptime limits have been set?

That being besides for the counters that get wiped in case of power outage anyway, especially here in wonderful South Africa...

#relieved for not needing more scripting

BUG for the GLOBAL one though:
XZ.JPG
The Server Profile for global can be changed, even with warning. but doesn't seem to have any affect besides the drop down name...

Re: 6.34 release candidate version topic!

Posted: Mon Dec 28, 2015 11:07 am
by strods
6.34rc27 version has been released.

Changes since previous version:
*) sshd - resolved shared secret mismatch issue;
*) net - do not show L2MTU in VLAN compact export;
*) net - fixed net crash when firewall jump rule points to disabled custom chain;
*) net - apply slave config only if master config has been changed.

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

Re: 6.34 release candidate version topic!

Posted: Mon Dec 28, 2015 12:19 pm
by krisjanis
@SirDJNeo

Thank you for the note on default-trial server change winbox bug.

Re: 6.34 release candidate version topic!

Posted: Tue Dec 29, 2015 11:28 am
by foxch2
Yesterday I updated to 27 release

I have a script sending in the mail logs. Now error sending

12:00:32 system,e-mail,error Error sending e-mail <Log dec/29/2015>: invalid BODY

the text of the script
:log info "Log Backup Sended to email...";
:local sysname [/system identity get name];
:local sysver [/system package get system version];
#read log
:local logcontent
:foreach int in=[/log find ] do={
:set logcontent ("$logcontent\r\n" .[/log get $int time]. " - " .[/log get $int message])
}
#send email
/tool e-mail send to=**@*** subject=([/system identity get name] . " Log " . [/system clock get date]) body=("Log of $sysname\nRouterOS version: \
$sysver\nTime and Date stamp: " . [/system clock get time] . " " . [/system clock get date] . "\n " . \
$logcontent);

#delete old log
/system logging action set memory memory-lines=1
/system logging action set memory memory-lines=1000

:log info "System log cleared by email-log-backup script...";
the script text has not changed. Earlier notifications were sent

Re: 6.34 release candidate version topic!

Posted: Tue Dec 29, 2015 12:35 pm
by strods
Exact same script works for me perfectly on same version.

Try to print body instead of sending message. Maybe you can notice something there:

:put ("Log of $sysname\nRouterOS version: \
$sysver\nTime and Date stamp: " . [/system clock get time] . " " . [/system clock get date] . "\n " . \
$logcontent)

Re: 6.34 release candidate version topic!

Posted: Tue Dec 29, 2015 1:10 pm
by foxch2
Exact same script works for me perfectly on same version.

Try to print body instead of sending message. Maybe you can notice something there:

:put ("Log of $sysname\nRouterOS version: \
$sysver\nTime and Date stamp: " . [/system clock get time] . " " . [/system clock get date] . "\n " . \
$logcontent)
still error

launched through the terminal
/tool e-mail send to=**@*** subject=([/system identity get name] . " Log " . [/system clock get date]) body=(" ");
still error in body

Re: 6.34 release candidate version topic!

Posted: Tue Dec 29, 2015 1:22 pm
by foxch2
even if i remove the "body" from the request , the error still in it

Re: 6.34 release candidate version topic!

Posted: Tue Dec 29, 2015 2:41 pm
by strods
Try to send e-mail. After that generate supout file and together with problem description send it to support@mikrotik.com

Remember that this is users forum (where support team sometimes take a look to see if some common issues appears). To get actual help you have to contact support@mikrotik.com

Re: 6.34 release candidate version topic!

Posted: Tue Dec 29, 2015 3:52 pm
by strods
Version 6.34rc29 will be released today.

Changes since previous version:
*) arm - fix usb modem modules on ARM;
*) dhcpv6-client - fixed stopped state;
*) net - fixed possible kernel failure/lock-up;
*) netinstall - sort packages by name.

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

Re: 6.34 release candidate version topic!

Posted: Tue Dec 29, 2015 9:36 pm
by Zorro
is there ANY chance to had manageable "disable reset button/hole" switch in newer versions?

Re: 6.34 release candidate version topic!

Posted: Wed Dec 30, 2015 8:16 am
by strods
Zorro - Please create separate topics for questions like this. This is version related topic.

What you are asking for has been implemented already for a while:
http://wiki.mikrotik.com/wiki/Manual:Ro ... bootloader

Re: 6.34 release candidate version topic!

Posted: Wed Dec 30, 2015 2:24 pm
by strods
6.34rc30 version will be released today.

Changes since previous version:
*) chr - license fix for AWS and similar solutions.

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

Re: 6.34 release candidate version topic!

Posted: Wed Dec 30, 2015 3:29 pm
by mistry7
Usermanger is missing in RC30 arm Zip file

Re: 6.34 release candidate version topic!

Posted: Thu Dec 31, 2015 12:33 am
by neredera
6.34rc30 gives for a S+32LC10D wrong values as TX power:
  MikroTik RouterOS 6.34rc30 (c) 1999-2015       http://www.mikrotik.com/

[?]             Gives the list of available commands
command [?]     Gives help on the command and list of arguments

[Tab]           Completes the command/word. If the input is ambiguous,
                a second [Tab] gives possible options

/               Move up to base level
..              Move up one level
/command        Use command at the base level
[admin@MikroTik2] > interface ethernet monitor 25
                      name: sfpplus2-slave-local
                    status: link-ok
          auto-negotiation: done
                      rate: 10Gbps
               full-duplex: yes
           tx-flow-control: no
           rx-flow-control: no
               advertising: 
  link-partner-advertising: 
        sfp-module-present: yes
               sfp-rx-lose: no
              sfp-tx-fault: no
                  sfp-type: SFP-or-SFP+
        sfp-connector-type: LC
       sfp-link-length-9um: 10000m
           sfp-vendor-name: Mikrotik
    sfp-vendor-part-number: S+32LC10D
       sfp-vendor-revision: 1.0
         sfp-vendor-serial: MT50420H7983
    sfp-manufacturing-date: 15-05-10
            sfp-wavelength: 1330nm
           sfp-temperature: 43C
        sfp-supply-voltage: 3.181V
       sfp-tx-bias-current: 34mA
              sfp-tx-power: -40dBm
              sfp-rx-power: -5.613dBm

[admin@MikroTik2] > system routerboard print 
       routerboard: yes
             model: CRS226-24G-2S+
     serial-number: 4C7E045BC537
     firmware-type: qca8513
  current-firmware: 3.22
  upgrade-firmware: 3.22
[admin@MikroTik2] > 


[admin@MikroTik] > interface ethernet monitor 9
                      name: sfpplus2-slave-local
                    status: link-ok
          auto-negotiation: done
                      rate: 10Gbps
               full-duplex: yes
           tx-flow-control: no
           rx-flow-control: no
               advertising: 
  link-partner-advertising: 
        sfp-module-present: yes
               sfp-rx-lose: no
              sfp-tx-fault: no
                  sfp-type: SFP-or-SFP+
        sfp-connector-type: LC
       sfp-link-length-9um: 10000m
           sfp-vendor-name: Mikrotik
    sfp-vendor-part-number: S+23LC10D
       sfp-vendor-revision: 1.0
         sfp-vendor-serial: MT50420H7097
    sfp-manufacturing-date: 15-04-21
            sfp-wavelength: 1270nm
           sfp-temperature: 49C
        sfp-supply-voltage: 3.211V
       sfp-tx-bias-current: 37mA
              sfp-tx-power: -40dBm
              sfp-rx-power: -5.081dBm

[admin@MikroTik] > system routerboard print 
       routerboard: yes
             model: CRS210-8G-2S+
     serial-number: 583A05910292
     firmware-type: qca8513
  current-firmware: 3.22
  upgrade-firmware: 3.22

Re: 6.34 release candidate version topic!

Posted: Thu Dec 31, 2015 2:05 am
by spacemind
MicroSD is not detected on CCR1009 Desktop since 6.30.4, tried different cards and not working.

btw: whats smart card slot for ? which cards are supported ?

Re: 6.34 release candidate version topic!

Posted: Thu Dec 31, 2015 6:48 pm
by sx10
6.34rc23 version is released.

Changes since previous version:
*) crypto - fixed kernel failure in talitos HW encryption;
Do you have any details on this? I reported an issue with kernel failures on tile when using AES GCM (back on 11/19) and I'm wondering if this is related. I never heard back from support other than saying they would try to fix it.

Re: 6.34 release candidate version topic!

Posted: Thu Dec 31, 2015 9:30 pm
by IntrusDave
6.34rc23 version is released.

Changes since previous version:
*) crypto - fixed kernel failure in talitos HW encryption;
Do you have any details on this? I reported an issue with kernel failures on tile when using AES GCM (back on 11/19) and I'm wondering if this is related. I never heard back from support other than saying they would try to fix it.
It appears so, I was able to move all of my VPNs back to GCM without any crashes.

Re: 6.34 release candidate version topic!

Posted: Sat Jan 02, 2016 11:54 am
by Qper
why RoMON has a limitation in the name identity another Mikrotik ?

Image

Re: 6.34 release candidate version topic!

Posted: Mon Jan 04, 2016 11:56 am
by juanvi
why RoMON has a limitation in the name identity another Mikrotik ?

Image

I have similar issues with CapsMan CAp's Identity. Do not remember exactly, but long names and/or special characters were the cause.

Re: 6.34 release candidate version topic!

Posted: Mon Jan 04, 2016 12:28 pm
by strods
Qper - This is not version related issue so please create another topic. What is the problem here? If router identity is default MikroTik then it will be shown also here. If you connect to router and change identity then you will see it also in RoMON neighbours list.

Re: 6.34 release candidate version topic!

Posted: Tue Jan 05, 2016 12:04 am
by IntrusDave
why RoMON has a limitation in the name identity another Mikrotik ?

Image
You have the default identity for all your routers. Change it, and the Identity will change in RoMON.
/system identity set name=Router_Name

Re: 6.34 release candidate version topic!

Posted: Tue Jan 05, 2016 3:01 pm
by mistry7
Usermanger Paket still missing in 6.34 RC30 for ARM Plattform

Re: 6.34 release candidate version topic!

Posted: Tue Jan 05, 2016 3:29 pm
by strods
On ARM devices UserManager will not work within RouterOS v6. That is why packet is not available for download.

http://wiki.mikrotik.com/wiki/User_Mana ... er_Manager
"The MikroTik User Manager works on x86, MIPS, PowerPC and TILE processor based routers."

Re: 6.34 release candidate version topic!

Posted: Tue Jan 05, 2016 10:41 pm
by Qper
Qper - This is not version related issue so please create another topic. What is the problem here? If router identity is default MikroTik then it will be shown also here. If you connect to router and change identity then you will see it also in RoMON neighbours list.
If the name is long, RMON only displays mikrotik.
If the name has more than 31 characters displays only mikrotik.
Check it out

Re: 6.34 release candidate version topic!

Posted: Wed Jan 06, 2016 8:28 am
by strods
Qper - Now it is clear. Issue is reported to our developers. Thank you for your report. In future I suggest that you report directly to support@mikrotik.com

Re: 6.34 release candidate version topic!

Posted: Wed Jan 06, 2016 10:39 am
by mistry7
On ARM devices UserManager will not work within RouterOS v6. That is why packet is not available for download.

http://wiki.mikrotik.com/wiki/User_Mana ... er_Manager
"The MikroTik User Manager works on x86, MIPS, PowerPC and TILE processor based routers."

thats are bad news!

Re: 6.34 release candidate version topic!

Posted: Fri Jan 08, 2016 9:56 am
by strods
6.34rc32 version is released.

Changes since previous version:
*) net - fix bridge firewall chain check (broken since 6.33.2);
*) net - show fp counters in /interface monitor aggregate;
*) romon - allow to see device identity if it is longer than 31 character;
*) smb - fix crash when changing user which has open session;
*) tunnel - fix complaining about loop after ~248 days;
*) vrrp - make sure that VRRP gets state on bootup;
*) webfig - recognize properly CHR;
*) winbox - show only actual switch-cpu ports in switch setting combobox;

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

Re: 6.34 release candidate version topic!

Posted: Fri Jan 08, 2016 2:17 pm
by strods
6.34rc34 version is released.

Changes since previous version:
*) upnp - fixed missing in-interface option for dynamic dst-nat rules;
*) upnp - added comment for dynamic dst-nat rules to inform what host/program required it;

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

Re: 6.34 release candidate version topic!

Posted: Sat Jan 09, 2016 2:16 pm
by hurley12345
Version 6.34rc29

Changes since previous version:
*) arm - fix usb modem modules on ARM;
*) dhcpv6-client - fixed stopped state;
*) net - fixed possible kernel failure/lock-up;
*) netinstall - sort packages by name.

Can you please elaborate on
*) net - fixed possible kernel failure/lock-up;
as we have tile routers locking up and are at our wits end to isolate what triggers the lockup?
thanks

Re: 6.34 release candidate version topic!

Posted: Sun Jan 10, 2016 2:16 pm
by nescafe2002
*) upnp - fixed missing in-interface option for dynamic dst-nat rules;
*) upnp - added comment for dynamic dst-nat rules to inform what host/program required it;
Nice enhancement!

Image

Re: 6.34 release candidate version topic!

Posted: Mon Jan 11, 2016 7:36 am
by ufm
6.34rc32 version is released.

Changes since previous version:
*) net - fix bridge firewall chain check (broken since 6.33.2);
Nice.
Where I can download 6.33.4 with bugfix?

Re: 6.34 release candidate version topic!

Posted: Mon Jan 11, 2016 9:24 am
by macgaiver
*) upnp - fixed missing in-interface option for dynamic dst-nat rules;
*) upnp - added comment for dynamic dst-nat rules to inform what host/program required it;
Nice enhancement!

Image
This enhancement got me in to "Teredo disabling spree" on all office PCs with Win10 this weekend... why it is enabled by default?
Yes, thanks for the feature it makes it much easier to manage dst-nat now.

Re: 6.34 release candidate version topic!

Posted: Tue Jan 12, 2016 2:46 am
by Zorro
*) upnp - fixed missing in-interface option for dynamic dst-nat rules;
*) upnp - added comment for dynamic dst-nat rules to inform what host/program required it;
Nice enhancement!

Image
This enhancement got me in to "Teredo disabling spree" on all office PCs with Win10 this weekend... why it is enabled by default?
Yes, thanks for the feature it makes it much easier to manage dst-nat now.
its funny, cuz its my favorite defaults (not only for Win10 machines).
using ADK or DISM or even better NTLite(which isn't free, sadly) - you can customize such(or many other things with ease in both installed machines and installation images/mediums).
but prohibiting unauthorized teredo, 6to4, isatap and other transitioning tech(including ipip, ipoe and other protocols, including restricting ipv6 itself) - is generally good practice not only from terms of security.

p.s.
you may also notice, that MS put into default win10 images somewhat quirky "debug adapter" and other WWAN miniports, annoying just like how WU repeatedly re-install ISATAP in past years. same about extra-protocols, that enabled and bound to interfaces "by default" aswell. or services(how many use "workstation" or "server" services in small offices, w/o AD usage ? for example).

Re: 6.34 release candidate version topic!

Posted: Tue Jan 12, 2016 2:52 am
by Zorro
i not know what those "kernel improvements" mean exactly, but they improve things a Lot, actually.
even in trivial tasks, such as web broswing or using winbox(both generic stuff or using built-in wiki viewer ;) - response improved Notably. i not know how much MicroTik paid for updated SDK/Compiler for MIPS(i doubt they use GCC. especially for wireless module), but it definitely Worthy thing. i just hope its not break something other(like security flaws and etc).

Re: 6.34 release candidate version topic!

Posted: Tue Jan 12, 2016 5:54 pm
by vosgessystemes
@Mikrotik When do you get out the stable version of 6.34 ? This month ? After ?

Re: 6.34 release candidate version topic!

Posted: Thu Jan 14, 2016 3:54 pm
by strods
6.34rc36 version will be released today.

Changes since previous version:
*) dhcpv6-client - fix ia lifetime check;
*) ipsec - fixed kernel failure after underlying tunnel has been disabled/enabled;
*) ipsec - prioritize proposals;
*) ipsec - support multiple DH groups for phase 1;
*) log - reopen log file if deleted;
*) netinstall - fix apply default config;
*) packing - fix tcp/udp checksums when simple packing is used;
*) tile - make sure that SFP rj45 modules that use forced 1G FD settings work correctly after system reboot;
*) tile - fix ipsec freeze after SA updates;
*) wireless - added WPS buttons support on hAP and hAP ac lite.

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

Re: 6.34 release candidate version topic!

Posted: Thu Jan 14, 2016 6:56 pm
by sx10
I'm really excited to see all these great enhancements and fixes, but is there any end in sight for 6.34? It's been in RC for over 2 months and you're still adding new features. I'd really like to get some of these enhancements in production. Any plans for a release date?

Re: 6.34 release candidate version topic!

Posted: Thu Jan 14, 2016 7:40 pm
by Zorro
i was just only hope that WPS buttons support in newer RB - dind't become part of "default config", because its make wifi exploitable as hell :/
also would like bit reduced "default" TX powers in 2x and 3x WiFi-enabled devices (2-4Db should be enough? someone can do math better, perhaps)
(to avoid legal problems with early adopters/Rockie networkers, not familar with regulations/restrictions aswell as to reduce EMI).

Re: 6.34 release candidate version topic!

Posted: Fri Jan 15, 2016 10:38 am
by ditonet
@strods
*) ipsec - prioritize proposals;
*) ipsec - support multiple DH groups for phase 1;
Can you explain it? How it works?

Regards,

Re: 6.34 release candidate version topic!

Posted: Fri Jan 15, 2016 11:26 am
by mrz
Now you can choose multiple DH groups in phase1
and all the chosen protcols are sorted from strongest to weakest protocol before sending proposals to remote peer.

Re: 6.34 release candidate version topic!

Posted: Fri Jan 15, 2016 4:14 pm
by ditonet
@mrz
Now you can choose multiple DH groups in phase1
and all the chosen protcols are sorted from strongest to weakest protocol before sending proposals to remote peer.
Thanks a lot, it looks that currently this option is supported only from command-line, not from Winbox.
And what about *) ipsec - prioritize proposals;?

Regards,

Re: 6.34 release candidate version topic!

Posted: Fri Jan 15, 2016 4:36 pm
by mrz
second part of the sentence
all the chosen protocols are sorted from strongest to weakest protocol before sending proposals to remote peer.

Re: 6.34 release candidate version topic!

Posted: Fri Jan 15, 2016 5:01 pm
by ditonet
@mrz
Thanks, I thought that it was separate functionality.

Regards,

Re: 6.34 release candidate version topic!

Posted: Tue Jan 19, 2016 9:29 am
by strods
6.34rc39 version has been released.

Changes since previous version:

*) dude - The reports of my death have been greatly exaggerated;
*) dude - dude RouterOS package added for tile and x86 (CHR) architecture;
*) dude - initial work on dude integration into RouterOS;
*) chr - fix SSH key import on AWS;
*) crs212 - fix 1Gbps ether1 linking problem;
*) timezone - use backward timezone aliases;
*) lte - support serial port for DellWireless 5570;
*) lte - improved dhcp handling on interfaces that doesn't support it;
*) ipsec - allow my-id address specification in main mode;
*) dhcpv6 client - fix remove when client reappears on restart;
*) default config - fix for hAP family devices with one wireless;
*) firewall - added inversion support for "limit" option;
*) firewall - added bit rate matching for "limit" option;
*) firewall - improved performance for "limit" option.

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

Re: 6.34 release candidate version topic!

Posted: Tue Jan 19, 2016 10:51 am
by Ghazaryan
Hi everybody I have question about traffic flow in my router 6.32.3.In this version TX trafic does not show in ether2 (local) show only rx traffic, ether3 (internet) i can not see local trafic rx i know about it
( http://wiki.mikrotik.com/wiki/Manual:IP/Traffic_Flow ),i add more interfaces but dont see
how can i read local RX and TX traffics in the old version 4.11 it work ok

Re: 6.34 release candidate version topic!

Posted: Wed Jan 20, 2016 9:42 am
by strods
Version 6.34rc41 has been released.

Changes since previous version:

*) mipsle - architecture support dropped (last fully supported version 6.32.3);
*) mac-telnet - fixed backspace when typing login username;
*) address-list - properly remove unused address-lists from drop-downs;
*) sstp - allow ECDHE when pfs enabled;
*) lte - fixed info command for Cinterion EHS5-E modem;
*) fast-path - fixed kernel crash on on/off;
*) fetch - fixed closure after 30 seconds;
*) ppp - fixed rare kernel crash (introduced in v6.33);
*) ppp - do not allow empty name ppp secrets;
*) licensing - fixed that some old 7 symbol keys could not be upgraded;
*) ssh - fixed possible kernel crash;
*) console - fixed crash on creating variable with "?" in it;
*) winbox - fixed tab names to correspond to console;
*) webfig - fixed firewall connection-bytes option;
*) webfig - fixed switch port "default vlan id" has missing "auto" value.

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

Re: 6.34 release candidate version topic!

Posted: Wed Jan 20, 2016 9:59 am
by dadaniel
Why is to-adresses column not enabled by default? No need to write to-addresses in comment field...!

*) upnp - added comment for dynamic dst-nat rules to inform what host/program required it;
Nice enhancement!

Image

Re: 6.34 release candidate version topic!

Posted: Wed Jan 20, 2016 10:14 am
by macgaiver
Why is to-adresses column not enabled by default? No need to write to-addresses in comment field...!
Now all views are saved, so you can select it yourself and use it. Each configuration have it's unique important fields, you can't keep everyone happy.

Re: 6.34 release candidate version topic!

Posted: Wed Jan 20, 2016 10:37 am
by serjrd
CCR-1072, 6.34rc39
Just now got this message in my console:

jan/19/2016 10:25:21 system,error,critical System rebooted because of kernel failure
jan/19/2016 10:25:21 system,error,critical router was rebooted without proper shutdown, probably kernel failure

I can only attribute this to enabling fasttrack, but it wasn't an immediate reaction to that and happened in about 30-60 seconds after it.

Emailed you an autosupout.rif file.
Is there anything else I can send you to be able to track this down?

Posted: Wed Jan 20, 2016 10:42 am
by jarda
Oh no. Mipsle support drop during subminor version development? What happened? Is it for always?

Re: 6.34 release candidate version topic!

Posted: Wed Jan 20, 2016 10:43 am
by ebreyit
Is there anything else I can send you to be able to track this down?
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.

Think they get everything they need from this unless it involves external factors where packet captures also come in handy

Re:

Posted: Wed Jan 20, 2016 11:01 am
by macgaiver
Oh no. Mipsle support drop during subminor version development? What happened? Is it for always?
It looks like it - same thing happened to 6.33.5 also - check download page.
anyway - support period was impressive, my last mipsle purchase was in 2008.

Re: 6.34 release candidate version topic!

Posted: Wed Jan 20, 2016 2:15 pm
by raffav
*) address-list - properly remove unused address-lists from drop-downs;
how it suppose to work?

i create a address-list TEST1
set up a demo Nat with src-address-list=TEST1>apply>ok

delete the address-list TEST1
go to nat but the address-list=TEST1 on demo nat still there

Re: 6.34 release candidate version topic!

Posted: Wed Jan 20, 2016 2:25 pm
by strods
raffav - This change is for situation like this but after you have disabled address-list of firewall rule in past you could see this list still in drop down menu but now you can not.

Of course it will still exist in such case. You can type anything under address list fields in firewall rules. You do not have to have actual entries in address list.

Re: 6.34 release candidate version topic!

Posted: Wed Jan 20, 2016 2:42 pm
by raffav
raffav - This change is for situation like this but after you have disabled address-list of firewall rule in past you could see this list still in drop down menu but now you can not.

Of course it will still exist in such case. You can type anything under address list fields in firewall rules. You do not have to have actual entries in address list.
hum...

so to clean up the "old address-list" need to disable the address-list field on the rule and re enable it?


and what is the propose to type anything on the address-list? i.e: make a rule only work in some situation like dynamic address-list ?

Re: 6.34 release candidate version topic!

Posted: Wed Jan 20, 2016 3:17 pm
by strods
raffav - if you set anything on any firewall rule address-list fields then it will show up as a hint in other firewall rules under address-list fields. In past if you did add something on this field and after that did remove it, then it still showed up in drop list even it was not active anywhere. Now that is fixed.

Re: 6.34 release candidate version topic!

Posted: Thu Jan 21, 2016 2:02 pm
by honzam
hAP ac lite - In Quick Set please make WISP AP DUAL
It is missing

Re:

Posted: Mon Jan 25, 2016 11:08 am
by Zorro
Oh no. Mipsle support drop during subminor version development? What happened? Is it for always?
some obsoleted mips branches - already deprecated by linux kernel and toolchain long ago
(some LTS kernels and compilers are remain slightly-maintained, but its not really as great a moving upstream are).
so apparently MikroTik - moved upstream and updated some code.
other xxk and smips - are still supported by, as you can notice.
i can only guess that implementing some things - may eventually break mipsle support, even without moving upstream(partially cause less maintained toolchain for, maybe)
but removing "legacy" 5.xx ROS from download for SMIPS - make no sense, contrary(and eventually result in series of "conspiraction theorists" "explanations" ;)

Re: Re:

Posted: Mon Jan 25, 2016 11:40 am
by andriys
but removing "legacy" 5.xx ROS from download for SMIPS - make no sense
Removing? SMIPS is a relatively recent beast, RouterOS v5.x for SMIPS has never existed.

Re: Re:

Posted: Mon Jan 25, 2016 11:54 am
by normis
but removing "legacy" 5.xx ROS from download for SMIPS - make no sense
Removing? SMIPS is a relatively recent beast, RouterOS v5.x for SMIPS has never existed.
MIPS-LE was removed. Not SMIPS.

MIPS-LE were really old devices, like the RB112. They never worked good with v6.
SMIPS never existed for v5.

Re: Re:

Posted: Mon Jan 25, 2016 11:54 am
by Zorro
but removing "legacy" 5.xx ROS from download for SMIPS - make no sense
Removing? SMIPS is a relatively recent beast, RouterOS v5.x for SMIPS has never existed.
sorry, that MY mistake, obviously.
"thinking bout MIPSLE and looking intoo SMIPS" or/and vice versa effect, apparently, thanks to new "download" section appearance, which is more eye-stressfull, but direct.

Re: Re:

Posted: Mon Jan 25, 2016 10:11 pm
by jarda
but removing "legacy" 5.xx ROS from download for SMIPS - make no sense
Removing? SMIPS is a relatively recent beast, RouterOS v5.x for SMIPS has never existed.
MIPS-LE was removed. Not SMIPS.

MIPS-LE were really old devices, like the RB112. They never worked good with v6.
SMIPS never existed for v5.
MIPS-LE is not only RB112, but for example RB133 or RB532 which are still well supported by 6.32.3. Maybe also by 6.33.x, but I dont have such experience as I do not use this version in production. Your statement that thay never worked good with v6 is obviously not true. I still do not understand why the support for MIPS-LE was dropped so suddenly.

Re: 6.34 release candidate version topic!

Posted: Mon Jan 25, 2016 10:20 pm
by jarda
Why dude opened ports are not shown / manageable by IP - Services? All services provided by router should be listed there.

Citation from documentation http://wiki.mikrotik.com/wiki/Manual:IP/Services:
This document lists protocols and ports used by various MikroTik RouterOS services. It helps you to determine why your MikroTik router listens to certain ports, and what you need to block/allow in case you want to prevent or grant access to the certain services. Please see the relevant sections of the Manual for more explanations.
I would like to see there also all PPP servers and other services like UPNP, DNS, DHCP, NTP, SNMP and all others (even not manageably) to have one place where all active ports on the device are shown at once giving full overview to the administrator to know what ports are currently opened. Well, this part is more a "feature request" for aligning the reality with documentation than question. I admit.

Re: 6.34 release candidate version topic!

Posted: Tue Jan 26, 2016 8:48 am
by sergejs
jarda, ip services include RouterOS used servers (most of them), however some of them are not included that are configuration optional (for example PPTP server, OVPN server or The Dude server).
Thank you for the feature suggestion about The Dude, currently it will stay under /dude, later we will see what we can do.

Re: 6.34 release candidate version topic!

Posted: Tue Jan 26, 2016 12:29 pm
by bommi
*) sstp - allow ECDHE when pfs enabled;
Does this mean you switched to a newer openssl library in this version?
When will it be possible to connect to the webinterface using pfs with dhe or ecdhe?

Re: 6.34 release candidate version topic!

Posted: Tue Jan 26, 2016 2:31 pm
by strods
6.34rc45 version has been released.

Changes since previous version:

*) capsman - fix radius accounting stop message;
*) cerm - allow to sign certificates from imported CAs created with RouterOS;
*) ldp - fix MPLS PDU max length;
*) net - improve 64bit interface stats support;
*) routerboard - print factory-firmware version in routerboard menu;
*) snmp - add oid from ucd mib for total cpu load OID 1.3.6.1.4.1.2021.11.52.0;
*) winbox - add extra items automaticly to multiline fields if at least one of them is required;
*) winbox - implemented full ipv6 dhcp client;
*) winbox - update blocked flag if user changed blocked field in dhcp server lease;
*) winbox/webfig - fixed version column ordering in ip neighbors list.

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

Re: 6.34 release candidate version topic!

Posted: Tue Jan 26, 2016 3:52 pm
by BartoszP
*) routerboard - print factory-firmware version in routerboard menu;
Do I check correct menu ?
411.png

Re: 6.34 release candidate version topic!

Posted: Tue Jan 26, 2016 3:55 pm
by normis
"print" refers to command line

Re: 6.34 release candidate version topic!

Posted: Tue Jan 26, 2016 4:05 pm
by vosgessystemes
I have a 404 error on the Dude package URL : http://download.mikrotik.com/dude-6.34rc45-tile.npk

Normal ?

Br

Re: 6.34 release candidate version topic!

Posted: Tue Jan 26, 2016 4:06 pm
by normis
I have a 404 error on the Dude package URL : http://download.mikrotik.com/dude-6.34rc45-tile.npk

Normal ?

Br
Try this URL http://download2.mikrotik.com/routeros/ ... 34rc45.npk

Re: 6.34 release candidate version topic!

Posted: Tue Jan 26, 2016 4:08 pm
by vosgessystemes
I have a 404 error on the Dude package URL :
http://download.mikrotik.com/dude-6.34rc45-tile.npk

Normal ?

Br
Try this URL http://download2.mikrotik.com/routeros/ ... 34rc45.npk
Perfect ! Have you a changelog for this package ? Any fix since dude-6.34rc41.npk ?

Re: 6.34 release candidate version topic!

Posted: Tue Jan 26, 2016 4:10 pm
by normis
Perfect ! Have you a changelog for this package ? Any fix since dude-6.34rc41.npk ?
Special topic for that http://forum.mikrotik.com/viewtopic.php ... 82#p517782

Re: 6.34 release candidate version topic!

Posted: Tue Jan 26, 2016 4:40 pm
by IPANetEngineer
We have an issue that has been reported to support and wanted to see how many others are having the same issue.

When using MPLS Traffic Engineering tunnels and MP-BGP with VRFs, if the BGP peering goes down and back up, traffic stops forwarding until the Traffic Engineering interface is disabled and re-enabled.

When looking at a packet capture, it appears the outer label is missing in the MPLS label stack. Once the TE interface is bounced, the label shows back up in the capture.

Has anyone else run into this or similar issues with deploying Traffic Engineering tunnels?

Re: 6.34 release candidate version topic!

Posted: Wed Jan 27, 2016 2:50 am
by jondavy
Here we are using several VPLS and also this fall and coming back after a few minutes,
with version 6.33.5 (stable) in RB1100AHx2, RB1100AH

Re: 6.34 release candidate version topic!

Posted: Wed Jan 27, 2016 2:41 pm
by Ulypka
i have similar problem with mpls
i correct this problem delete route from bgp and then advertise again

Re: 6.34 release candidate version topic!

Posted: Wed Jan 27, 2016 10:16 pm
by nz_monkey
We have an issue that has been reported to support and wanted to see how many others are having the same issue.

When using MPLS Traffic Engineering tunnels and MP-BGP with VRFs, if the BGP peering goes down and back up, traffic stops forwarding until the Traffic Engineering interface is disabled and re-enabled.

When looking at a packet capture, it appears the outer label is missing in the MPLS label stack. Once the TE interface is bounced, the label shows back up in the capture.

Has anyone else run into this or similar issues with deploying Traffic Engineering tunnels?
We have had the same problem.

Re: 6.34 release candidate version topic!

Posted: Wed Jan 27, 2016 10:40 pm
by bclewl1ns
so I have an issue that started with RC41. I have a CCR1036-12G-EM

after the RC41 upgrade. The router loses the ability to show files, resources and Authentication to the router takes about 3 min. I have reset the router, uninstalled Dude and rebuilt from scratch to have the same thing happen.

I was able to get it upgraded to RC45 today. Now about every 5 min the watchdog timer reboots the router.

anyone else having this issue??

I have downgraded to 6.33.5 to see if that resolves the problem.

Re: 6.34 release candidate version topic!

Posted: Wed Jan 27, 2016 10:56 pm
by bclewl1ns
A little more info. If I turn off the watchdog timer. the system loses the ability to reboot remotely. I have to manually power off the router.

Re: 6.34 release candidate version topic!

Posted: Wed Jan 27, 2016 10:58 pm
by bclewl1ns
It does seam that downgrading the router to 6.33.5 fixed the reboot and lockup problem.

Re: 6.34 release candidate version topic!

Posted: Wed Jan 27, 2016 11:31 pm
by bclewl1ns
So after a while running on 6.33.5 I upgraded to 6.34rc45 It took the router almost 5 min to reboot. When it did I am right back to were i started.

The router takes about 2 min to let me log in.
It takes the file list about 5 min before it shows any files.
I have lost the ability to create a sup file or to reboot the router
I can not reset the router remotely anymore.
The system resources show's no cpu's at all
The log shows timeout while waiting for program 20

Kind of frustrating as the system was working well under RC15 but since i upgraded to RC41 and on this has been a constant problem. Are these all tested before they are released?

Additionally, on the Winbox title bar it no longer shows the router model or Identity just the login and ip
Also if i open up a terminal box it takes about 5 min to get to a prompt.
winbox.tiff

Re: 6.34 release candidate version topic!

Posted: Thu Jan 28, 2016 6:46 pm
by IPANetEngineer
We have an issue that has been reported to support and wanted to see how many others are having the same issue.

When using MPLS Traffic Engineering tunnels and MP-BGP with VRFs, if the BGP peering goes down and back up, traffic stops forwarding until the Traffic Engineering interface is disabled and re-enabled.

When looking at a packet capture, it appears the outer label is missing in the MPLS label stack. Once the TE interface is bounced, the label shows back up in the capture.

Has anyone else run into this or similar issues with deploying Traffic Engineering tunnels?
We have had the same problem.
Glad to know someone else is having this issue, in working with MikroTik on the ticket we have open, it appears they have found the bug and fixed it and the fix will be included in 6.34.

Can't wait for 6.34 :-)

Re: 6.34 release candidate version topic!

Posted: Fri Jan 29, 2016 10:18 am
by fragtion
In the latest Mikrotik newsletter (https://indd.adobe.com/view/c0e6f614-be ... 0ef4539904), according to Page 3, "New version of RouterOS will support single radio AP/Client for repeater support", presumably on supported models only. When can we expect this feature / in which new version of RouterOS? The news is not clear as to whether it will be the upcoming version of RouterOS, or a future version somewhere later down the line? Thank you

Re: 6.34 release candidate version topic!

Posted: Fri Jan 29, 2016 12:40 pm
by docmarius
Not specific to this release, but there should be a bus selection option for USB Power reset under WinBox for RB922 (and probably others using differentiated bus lines for USB and PCIe USB):
NetMetal_USB_Reset.jpg
This issue makes it impossible to use USB power reset from WinBox.

Re: 6.34 release candidate version topic!

Posted: Fri Jan 29, 2016 2:30 pm
by strods