Community discussions

MikroTik App
 
kliq
just joined
Posts: 1
Joined: Wed Sep 17, 2014 4:49 pm

Re: v6.19 released

Wed Sep 17, 2014 5:06 pm

There is a problem with RB SXT G-5HPnD r2. This board restarting itself because of kernel failure and log is like this "00:42:21 system,error,critical router was rebooted without proper shutdown by watchdog timer ".
how is your watchdog configured? maybe it is pinging some address
Watchdog is configured by default, no configuration is set.
Hi all,

We've been working with Mikrotik since v2.9.5 and have followed the progress and changes at Mikrotik for a number of years. We thought we'd throw our 2 cents in on the forums and maybe help pinpoint a few issues. :)

We have been rolling out 6.19 and picked up on similar issues as faced by gemwk2; on about 20 6.19 devices we have deployed, 4 of them are constantly (2-3 times daily) rebooting due to watchdog timeout.

The watchdog is configured in different ways on all 4 devices, all but one are watching a specific IP and the 4th is just enabled as default. We did try disable the watchdog but the board needed a hard reboot as it froze a couple of hours later. If any other information is required please let us know.
 
User avatar
noyo
Member Candidate
Member Candidate
Posts: 116
Joined: Sat Jan 28, 2012 12:25 am
Location: Mazury - Poland
Contact:

Re: v6.19 released

Wed Sep 17, 2014 5:39 pm

There is a problem with RB SXT G-5HPnD r2. This board restarting itself because of kernel failure and log is like this "00:42:21 system,error,critical router was rebooted without proper shutdown by watchdog timer ".
how is your watchdog configured? maybe it is pinging some address
Watchdog is configured by default, no configuration is set.
See if your CPU jumps to 100%.
U is not so with Lite5 update 5.26 -> 6.19. Yesterday I turned off the wireless-fp and it did not work. Today, some three hours ago in August alone restarted.
Watchdog also have a default set.
Mikrotik a confused and August restaruje.
cpu_lite5.png
You do not have the required permissions to view the files attached to this post.
 
visalink
Frequent Visitor
Frequent Visitor
Posts: 69
Joined: Thu Oct 03, 2013 1:42 am

Re: v6.19 released

Wed Sep 17, 2014 5:44 pm

We upgrade a pair of 493AH routers to 6.19, and saw EoIP start dropping packets > 1422 bytes. Rolled back to 6.17, no problems.

We did not, however, upgrade the far end of the EoIP tunnels, which may or may not have wound up working better.
I also have this problem.
I'm moving to VPLS.
 
User avatar
nsayer
Frequent Visitor
Frequent Visitor
Posts: 78
Joined: Thu Jun 02, 2011 5:32 pm
Location: Santa Clara, CA, US

Re: v6.19 released

Wed Sep 17, 2014 9:58 pm

Sometime between 6.16 and 6.19 L2TP VPN between my mac and iPhone and my routerboard has broken.

I went in and made sure that the configuration was correct (so far as I know), including "enable IPSec" and adding the shared secret on the L2TP server page.

What I get on the mac side is "IPSec connection failed <IKE Error 65535 (0xffff) Unknown error>"

and in the system log,

IKE Packet: receive success. (Initiator, Main-Mode message 4).
try to get pskey by the peer's address.
couldn't find the pskey by address [routerboard].
couldn't find the pskey for [routerboard].

I'm really, really, REALLY sure the shared secret is the same on both sides.

WTF?
 
User avatar
armandfumal
Member Candidate
Member Candidate
Posts: 158
Joined: Wed Apr 25, 2012 5:50 pm
Location: Weiswampach,LUX
Contact:

Re: v6.19 released

Wed Sep 17, 2014 11:21 pm

t's terribly sad that we have to pay for underdeveloped software.
Also a shame that mkrotik tests its software on the clients :(
It is your choice. You can also go to Cisco and pay thousand euro for the device and many more for the service...
MKT do a very good job...
 
User avatar
noyo
Member Candidate
Member Candidate
Posts: 116
Joined: Sat Jan 28, 2012 12:25 am
Location: Mazury - Poland
Contact:

Re: v6.19 released

Wed Sep 17, 2014 11:26 pm

t's terribly sad that we have to pay for underdeveloped software.
Also a shame that mkrotik tests its software on the clients :(
It is your choice. You can also go to Cisco and pay thousand euro for the device and many more for the service...
MKT do a very good job...
Man, you pay for it. I really want to buy the product on a half fit?
Think out what you're saying.
I like solutions Mikrotik, I would not trade them for anything at all else, but wants a product who works.
 
User avatar
armandfumal
Member Candidate
Member Candidate
Posts: 158
Joined: Wed Apr 25, 2012 5:50 pm
Location: Weiswampach,LUX
Contact:

Re: v6.19 released

Wed Sep 17, 2014 11:27 pm

Winbox v3 is required for router’s configuration.
Welp... no more rc testing (or upgrading, for that matter) for me then...
I'll stay on 6.18 on all of my devices, since EoIP (which I use it a lot) is broken on 6.19.
6.18 was a great release (the first really stable and usable one with no major bugs for my use-cases in the whole 6.x branch) and I hold on to it dearly.
I'm using EoIP on CCR, RB2011, RG951 without any issues with 6.19, work stable...
 
User avatar
noyo
Member Candidate
Member Candidate
Posts: 116
Joined: Sat Jan 28, 2012 12:25 am
Location: Mazury - Poland
Contact:

Re: v6.19 released

Wed Sep 17, 2014 11:31 pm

Winbox v3 is required for router’s configuration.
Welp... no more rc testing (or upgrading, for that matter) for me then...
I'll stay on 6.18 on all of my devices, since EoIP (which I use it a lot) is broken on 6.19.
6.18 was a great release (the first really stable and usable one with no major bugs for my use-cases in the whole 6.x branch) and I hold on to it dearly.
I'm using EoIP on CCR, RB2011, RG951 without any issues with 6.19, work stable...
And for me as you can see in the graph is not stable. I uwielu people also is not stabile, that in itself is already available 6.20rc shows that there are errors.
Apparently, your network will not fully benefit from the opportunities mikrotik.

I lite5 restart once a day, so do not tell me that it is stable, because it is not.
 
User avatar
armandfumal
Member Candidate
Member Candidate
Posts: 158
Joined: Wed Apr 25, 2012 5:50 pm
Location: Weiswampach,LUX
Contact:

Re: v6.19 released

Wed Sep 17, 2014 11:46 pm

And for me as you can see in the graph is not stable. I uwielu people also is not stabile, that in itself is already available 6.20rc shows that there are errors.
Apparently, your network will not fully benefit from the opportunities mikrotik.

I lite5 restart once a day, so do not tell me that it is stable, because it is not.
we have hundred mkt devices under 6.19 without any big issues, may be your problem is coming to specific usage in your config, your case must be analysed by MKT support...
 
TikUser
newbie
Posts: 48
Joined: Thu Jul 04, 2013 2:40 pm
Location: EU

Re: v6.19 released

Thu Sep 18, 2014 1:56 am

I'm having a very strange issue. My backup files on the 493g are getting bigger and bigger, but the configuration is the same. Only the textual backups have the same size. Where is the problem? Any suggestions?
The rb493g has 2 wifi cards inserted. One is disabled, and the other serves as AP (2.4GHz).
You do not have the required permissions to view the files attached to this post.
 
User avatar
patrikg
Member Candidate
Member Candidate
Posts: 224
Joined: Thu Feb 07, 2013 6:38 pm
Location: Stockholm, Sweden

Re: v6.19 released

Thu Sep 18, 2014 10:34 am

The backup files, i assume that it also take backup of the logs and much more.
Not only the config.
 
snoppy
just joined
Posts: 6
Joined: Mon Aug 11, 2014 10:48 am

Re: v6.19 released

Thu Sep 18, 2014 11:40 am

Hello
we have some CCR1036-8G-2S+EM
when traffic grow up to 3Gb/s and more, SNMP does not work correctly.
this ccr connected to other switch
and SNMP statistic from this switch-port has not failures, and traffic 3.5Gb/s

this problem in all versions, whitch we tested and uses
from 6.13 to 6.19, and all 6.20rcX.
You do not have the required permissions to view the files attached to this post.
 
User avatar
vadimbn
Frequent Visitor
Frequent Visitor
Posts: 60
Joined: Sun Aug 25, 2013 6:41 pm
Location: Russia, Berdsk
Contact:

Re: v6.19 released

Thu Sep 18, 2014 6:19 pm

I observe a memory leak on this version of RouterOS. Ticket#2014091866000668 has been created.
You do not have the required permissions to view the files attached to this post.
 
User avatar
nsayer
Frequent Visitor
Frequent Visitor
Posts: 78
Joined: Thu Jun 02, 2011 5:32 pm
Location: Santa Clara, CA, US

Re: v6.19 released

Thu Sep 18, 2014 7:04 pm

Sometime between 6.16 and 6.19 L2TP VPN between my mac and iPhone and my routerboard has broken.

I went in and made sure that the configuration was correct (so far as I know), including "enable IPSec" and adding the shared secret on the L2TP server page.

What I get on the mac side is "IPSec connection failed <IKE Error 65535 (0xffff) Unknown error>"

and in the system log,

IKE Packet: receive success. (Initiator, Main-Mode message 4).
try to get pskey by the peer's address.
couldn't find the pskey by address [routerboard].
couldn't find the pskey for [routerboard].

I'm really, really, REALLY sure the shared secret is the same on both sides.

WTF?
Bueller?
 
maxfava
Member Candidate
Member Candidate
Posts: 224
Joined: Mon Oct 17, 2005 12:30 am

Re: v6.19 released

Thu Sep 18, 2014 11:16 pm

Normis,
I noted 6.19 has changed mcs ht user interface in winbox on AC devices when I set fixed data rate.
Could you kindly address me how new User Interface works?
Before was with check box and able to set single mcs rate, now is a drop down box showin from 0-9, 0-8, 0-7.

Thanks.
Massimo
 
User avatar
nsayer
Frequent Visitor
Frequent Visitor
Posts: 78
Joined: Thu Jun 02, 2011 5:32 pm
Location: Santa Clara, CA, US

Re: v6.19 released

Fri Sep 19, 2014 4:52 pm

Sometime between 6.16 and 6.19 L2TP VPN between my mac and iPhone and my routerboard has broken.

I went in and made sure that the configuration was correct (so far as I know), including "enable IPSec" and adding the shared secret on the L2TP server page.

What I get on the mac side is "IPSec connection failed <IKE Error 65535 (0xffff) Unknown error>"

and in the system log,

IKE Packet: receive success. (Initiator, Main-Mode message 4).
try to get pskey by the peer's address.
couldn't find the pskey by address [routerboard].
couldn't find the pskey for [routerboard].

I'm really, really, REALLY sure the shared secret is the same on both sides.

WTF?
Bueller?
Bueller?
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7041
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v6.19 released

Fri Sep 19, 2014 6:45 pm

Enable ipsec debug logs, try to connect and after failure generate supout file. Send this file to support at mikrotik.com
 
OlegM
newbie
Posts: 38
Joined: Fri Jan 18, 2013 5:53 pm

Re: v6.19 released

Fri Sep 19, 2014 10:39 pm

Tell me how to write the rules in the firewall to use Layer 7, to block sites by domain, that would not die CCR. I certainly understand that this issue is not the place, but on x86 does not fall even when the error interfaces, and CCR constant problems.
 
User avatar
paoloaga
Member Candidate
Member Candidate
Posts: 227
Joined: Tue Mar 08, 2011 2:52 am
Location: Lugano - Switzerland
Contact:

Re: v6.19 released

Sat Sep 20, 2014 3:51 am

do I miss something or the IPv6 iBGP route reflection doesn't work?
 
joegoldman
Forum Veteran
Forum Veteran
Posts: 766
Joined: Mon May 27, 2013 2:05 am

Re: v6.19 released

Sat Sep 20, 2014 7:15 am

Finally upgraded my core CCR's to 6.19 last night - so far no problems but some problems I held off reporting from my old version still exist.

Normally I am sitting 3-10% CPU usage, but it will randomly spike to 50+% CPU usage with no major network events. From some of the profiles I've been able to capture it seems to be the networking process spiking but they are sporadic and only last for ~5 seconds so I can't even capture a supout.

It is still painfully slow to filter and search the route table. I have about 540k IPv4 routes loaded and I can do a x.x.x.x in dst-address filter without it taking MINUTES, or searching where blackhole=yes or comment="blah". I dont mind 20-30 seconds but minutes is too long when investigating issues.
Surely there is a better way like referencing the FIB directly as if it does when actually doing the routing?

I used to have another issue where /system resources CPU % would differ from the reported 'idle' amount (inversed) in the profiler, by up to 5-10%, but this seems better, still closely looking though.
 
User avatar
noyo
Member Candidate
Member Candidate
Posts: 116
Joined: Sat Jan 28, 2012 12:25 am
Location: Mazury - Poland
Contact:

Re: v6.19 released

Sat Sep 20, 2014 10:08 am

See if your CPU jumps to 100%.
U is not so with Lite5 update 5.26 -> 6.19. Yesterday I turned off the wireless-fp and it did not work. Today, some three hours ago in August alone restarted.
Watchdog also have a default set.
Mikrotik a confused and August restaruje.
cpu_lite5.png
In my case it helped to /system reset-configuration no-defaults=yes and the configuration of RB again.
Uptime 1d and 7h
lite5_next.png
You do not have the required permissions to view the files attached to this post.
 
User avatar
karina
Member
Member
Posts: 460
Joined: Sat Feb 06, 2010 2:18 am
Location: Spain

Re: v6.19 released

Sat Sep 20, 2014 10:38 pm

This is insane! I've updated RouterOS to 6.19 last evening in multiple organizations and today they are calling me that WiFi authentication is not working, since I'm using userman :shock: How can you offer "stable" version with such a huge mistake?

I really need to download PPC version of fixed package ASAP, presented links are not working, there is still the old broken one, I tried http://download2.mikrotik.com/routeros/ ... sgdfgwgwer - contains broken package. I don't use any cache.
With due respect zervan, the mistake is upgrading production routers to the latest version quite so quick. I would advise testing before deploying any software or if not possible watch the forum while others test
 
Begetan
Frequent Visitor
Frequent Visitor
Posts: 97
Joined: Mon Jul 11, 2011 11:49 am

Re: v6.19 released

Sun Sep 21, 2014 3:52 am

I put CCR-12G-4S-EM with ROS 6.19, made configuration of SNTP client. Put DNS name instead of IP.
Then I upload ntp package and restart device, after that I completelly lost connections.

I have to go at morning and immediattely fix the problem. Could anyone tell me which version is good for CCR?
It looks like NTP is broken here and this is the worst release ever! Please provide me link to official package 6.18 for Tile.
 
User avatar
honzam
Forum Guru
Forum Guru
Posts: 2394
Joined: Wed Feb 27, 2008 10:27 pm
Location: Czech Republic

Re: v6.19 released

Sun Sep 21, 2014 9:54 am

I put CCR-12G-4S-EM with ROS 6.19, made configuration of SNTP client. Put DNS name instead of IP.
Then I upload ntp package and restart device, after that I completelly lost connections.

I have to go at morning and immediattely fix the problem. Could anyone tell me which version is good for CCR?
It looks like NTP is broken here and this is the worst release ever! Please provide me link to official package 6.18 for Tile.
http://download2.mikrotik.com/routeros/ ... e-6.18.npk
 
User avatar
nz_monkey
Forum Guru
Forum Guru
Posts: 2096
Joined: Mon Jan 14, 2008 1:53 pm
Location: Over the Rainbow
Contact:

Re: v6.19 released

Mon Sep 22, 2014 2:05 am

This is insane! I've updated RouterOS to 6.19 last evening in multiple organizations and today they are calling me that WiFi authentication is not working, since I'm using userman :shock: How can you offer "stable" version with such a huge mistake?

I really need to download PPC version of fixed package ASAP, presented links are not working, there is still the old broken one, I tried http://download2.mikrotik.com/routeros/ ... sgdfgwgwer - contains broken package. I don't use any cache.
With due respect zervan, the mistake is upgrading production routers to the latest version quite so quick. I would advise testing before deploying any software or if not possible watch the forum while others test
+1 we are still running 6.5 in prod, and are only now an entire year later evaluating 6.19 for our next upgrade.
 
Zdenekhb
just joined
Posts: 10
Joined: Tue Apr 24, 2012 9:18 am

Re: v6.19 released

Mon Sep 22, 2014 11:42 am

Tested 6.19 on SXT5G-HnD Link... but Throughput is very bad.

Link is Only-N, 20/40 above, nv2 signal -40dB to -45dB on both chains. no wireles-fs enabled

6.19 winbox freeze ... try BTest and Throughput is 1-10mbps (WTF?) in 1TCP connection

Downgrade to 6.18 Try Btest and Throughput si 70-80Mbps in 1TCP connection.

Zdenek
 
zyzelis
Member Candidate
Member Candidate
Posts: 213
Joined: Sun Apr 08, 2012 9:25 pm

Re: v6.19 released

Mon Sep 22, 2014 11:47 am

Tested 6.19 on SXT5G-HnD Link... but Throughput is very bad.

Link is Only-N, 20/40 above, nv2 signal -40dB to -45dB on both chains. no wireles-fs enabled

6.19 winbox freeze ... try BTest and Throughput is 1-10mbps (WTF?) in 1TCP connection

Downgrade to 6.18 Try Btest and Throughput si 70-80Mbps in 1TCP connection.

Zdenek
What about other end?
Try to enable wireless-fp with 6.19 and i think your wtf will change to wow :).
 
onnoossendrijver
Member
Member
Posts: 486
Joined: Mon Jul 14, 2008 11:10 am
Location: The Netherlands

Re: v6.19 released

Mon Sep 22, 2014 1:37 pm

Tested 6.19 on SXT5G-HnD Link... but Throughput is very bad.

Link is Only-N, 20/40 above, nv2 signal -40dB to -45dB on both chains. no wireles-fs enabled

6.19 winbox freeze ... try BTest and Throughput is 1-10mbps (WTF?) in 1TCP connection

Downgrade to 6.18 Try Btest and Throughput si 70-80Mbps in 1TCP connection.

Zdenek
Well, -40 to -45 is a bit strong. Try adjusting it to -50 to -55.
 
k0st3k
just joined
Posts: 4
Joined: Mon Jul 09, 2012 12:10 pm

Re: v6.19 released

Mon Sep 22, 2014 10:52 pm

how to uninstall dude ? :)
dude6.19.JPG
You do not have the required permissions to view the files attached to this post.
 
jarda
Forum Guru
Forum Guru
Posts: 7756
Joined: Mon Oct 22, 2012 4:46 pm

Re: v6.19 released

Tue Sep 23, 2014 12:31 pm

Netinstall? Or maybe from console if possible?
 
k0st3k
just joined
Posts: 4
Joined: Mon Jul 09, 2012 12:10 pm

Re: v6.19 released

Tue Sep 23, 2014 1:20 pm

Netinstall? Or maybe from console if possible?
in console not possible.......i think only netinstall can help :shock:
 
voxframe
Member Candidate
Member Candidate
Posts: 126
Joined: Thu Dec 16, 2010 2:51 pm

Re: v6.19 released

Tue Sep 23, 2014 3:28 pm

Any updates on 6.20 progress?
 
User avatar
zervan
Member
Member
Posts: 329
Joined: Fri Aug 20, 2010 10:43 pm
Location: Slovakia
Contact:

Re: v6.19 released

Tue Sep 23, 2014 10:17 pm

With due respect zervan, the mistake is upgrading production routers to the latest version quite so quick. I would advise testing before deploying any software or if not possible watch the forum while others test
I was explaining that: I thought that since there are public RC versions to download, each "stable" version is tested enough. Now I know that I was wrong. Why I upgraded so early? Because today is the last working day of public holiday here and there is only small part of users in those organizations working. Next week it would be worse.

Sorry, but if a software is stated as "stable release", it should work and it is not good to test each version again. Here in 6.19 I found two bugs which are serious for my usage, but only a few users use this specific functions. Which version should I stay in? Almost in each version I've found some bugs, hoping next release will fix them. In some version before there was a bug related to multiple SSTP sessions (disconnecting), it was fixed. Some bugs nobody else reported here, just me - e. g. DHCP Leases Address List problem (it should be fixed in 6.20rc6, but it was just partially, still not fixed in 6.20rc9 which I tested latest). So what should I wait for? This kind of bugs I will not see immediately - it will take a time. Waiting is not a solution.

Many will agree that Mikrotik should really improve development. Why not to have odd (new functions and improvements) and even (just fixes) versions? I am recommending and implementing Mikrotik products - but it is shame when my customers are complaining that something stopped to work after upgrade.
 
User avatar
noyo
Member Candidate
Member Candidate
Posts: 116
Joined: Sat Jan 28, 2012 12:25 am
Location: Mazury - Poland
Contact:

Re: v6.19 released

Tue Sep 23, 2014 10:36 pm

I would urge you not to upgrade to 6.xx, is broken. MikroTik not fully test their software, only counts on the free beta testers
We pay, require an efficient software


All v6.xx is fucked in full.
I had updated a couple of RB711, Lite5, RB2011, RB912 to v6.19 or 6.7, and each August restarts from time to time due to the watchdog.
Watchdog has never been set - the default configuration.

After the downgrade v6.19 to v6.7 CPU up to 100% (ipsec). IPsec has never been used.

It helps to CPU 100% IPSEC:
/system package disable security
/system reboot
#waiting for restart

/export file=conf
/system package enable security
/system reboot
#waiting for restart

/system reset-configuration no-defaults=yes keep-users=yes run-after-reset=conf.rsc
#waiting for restart
#A couple of times I did not work, so I need inputs on the mac and perform again


Ticket#2014091366000293
Looks like some problems with installation. Would it be possible to netisntall
that boards, It will format all partitions and install valid RouterOS version
Downgrade ALL to v5.26 and firmware 3.10.
 
littlebill
Member Candidate
Member Candidate
Posts: 234
Joined: Sat Apr 30, 2011 3:11 am

Re: v6.19 released

Wed Sep 24, 2014 3:42 am

6.7 sstp server 2011 --- Map2n 6.19 sstp client. upload will never go above .75 mbit,

i was barely able to get down to 6.7 and i was able to go over 7mbit on tunnel, but i have the same IPsec 100 % cpu usage

i tried netinstall 6.7 but the unit will not boot correctly with default config. it came shipped at 6.15, so not sure it can go that low, really wish it would, unit is kind of useless right now

and no i won't upgrade off 6.7 till we have proven vpn is working reliably
 
savage
Forum Guru
Forum Guru
Posts: 1263
Joined: Mon Oct 18, 2004 12:07 am
Location: Cape Town, South Africa
Contact:

Re: v6.19 released

Wed Sep 24, 2014 12:09 pm

Hopefully this is a cosmetic bug...
[admin@MikroTik] > /system resource print
uptime: 10m55s
version: 6.19
build-time: Aug/26/2014 14:05:51
free-memory: 1841.2MiB
total-memory: 1893.6MiB
cpu: Intel(R)
cpu-count: 16
cpu-frequency: 2127MHz
cpu-load: 0%
free-hdd-space: 146.5GiB
total-hdd-space: 146.7GiB
write-sect-since-reboot: 14730
write-sect-total: 14730
architecture-name: x86
board-name: x86
platform: MikroTik
[admin@MikroTik] >
The server has 12GB of memory, not 2GB. It looks like the 1 before the 2 has been cut off (both in winbox, as well as console).

Also experiencing RX errors on a Intel 10Gig interface (looks like a constant 1/sec), currently downgrading to 6.18 to see if it's version related or not.
 
snoppy
just joined
Posts: 6
Joined: Mon Aug 11, 2014 10:48 am

Re: v6.19 released

Wed Sep 24, 2014 1:11 pm

memory more then 2G can used onle in CCR
on other platforms ROS only 2G max.
 
mperdue
Member Candidate
Member Candidate
Posts: 290
Joined: Wed Jun 30, 2004 8:18 pm

Re: v6.19 released

Wed Sep 24, 2014 5:33 pm

Our system is running a mixture of 6.1 on the AP's and 5.6 on the clients.

I pulled copies of 6.9 and decided to first upgrade the miscellaneous units that I had here in the office.

Out of 13 units upgraded to 6.9, 6 units would not restart or respond after reboot.

3 rb133c's (using mipsle code)
1 rb 411 (using mipsbe code)
1 rb 750 (using mipsbe code)
1 rb 911 ((using mipsbe code)

I managed to recover the 411, 750 and 911 units using netinstall and did manage to get 6.9 on it.
The rb133c's won't take any version that I offer them. Though I am going to take them home this weekend and try using a an old win xp machine com ports due to the usb com port option I am trying to use in a Win 7 machine.

I simply can not take the chance of upgrading clients and not having there units upgrade as expected. I can not pay for service calls to go replace units when they fail to upgrade. And I have probibly 20% of my network still on rb133c's which I have had a 100% failure rate on.

Has anyone else's experience been this way?

Regards,
Michael Perdue
SmythNet, CEO
www.smyth.net
276-783-3333
 
Thalid
newbie
Posts: 38
Joined: Sun Mar 31, 2013 11:33 pm

Re: v6.19 released

Wed Sep 24, 2014 5:49 pm

3 rb133c's (using mipsle code)
These units are probaly to old to run ros v6
in general units support 2v updates and these boards are from around 2006
http://routerboard.com/pdf/rb133ugA.pdf
 
mperdue
Member Candidate
Member Candidate
Posts: 290
Joined: Wed Jun 30, 2004 8:18 pm

Re: v6.19 released

Wed Sep 24, 2014 6:06 pm

3 rb133c's (using mipsle code)
These units are probaly to old to run ros v6
in general units support 2v updates and these boards are from around 2006
http://routerboard.com/pdf/rb133ugA.pdf
Then why would they release 6.x code for them then?
 
Ljubo
just joined
Posts: 21
Joined: Thu Apr 24, 2014 10:57 am

Re: v6.19 released

Wed Sep 24, 2014 6:18 pm

Our system is running a mixture of 6.1 on the AP's and 5.6 on the clients.

I pulled copies of 6.9 and decided to first upgrade the miscellaneous units that I had here in the office.

Out of 13 units upgraded to 6.9, 6 units would not restart or respond after reboot.

3 rb133c's (using mipsle code)
1 rb 411 (using mipsbe code)
1 rb 750 (using mipsbe code)
1 rb 911 ((using mipsbe code)

I managed to recover the 411, 750 and 911 units using netinstall and did manage to get 6.9 on it.
The rb133c's won't take any version that I offer them. Though I am going to take them home this weekend and try using a an old win xp machine com ports due to the usb com port option I am trying to use in a Win 7 machine.

I simply can not take the chance of upgrading clients and not having there units upgrade as expected. I can not pay for service calls to go replace units when they fail to upgrade. And I have probibly 20% of my network still on rb133c's which I have had a 100% failure rate on.

Has anyone else's experience been this way?

Regards,
Michael Perdue
SmythNet, CEO
http://www.smyth.net
276-783-3333
You do not have the required permissions to view the files attached to this post.
 
Thalid
newbie
Posts: 38
Joined: Sun Mar 31, 2013 11:33 pm

Re: v6.19 released

Wed Sep 24, 2014 6:22 pm

3 rb133c's (using mipsle code)
These units are probaly to old to run ros v6
in general units support 2v updates and these boards are from around 2006
http://routerboard.com/pdf/rb133ugA.pdf
Then why would they release 6.x code for them then?
just refering to what i read in some older posts like this one
http://159.148.147.201/viewtopic.php?f= ... us#p161880
 
bazzer
Trainer
Trainer
Posts: 87
Joined: Sat Mar 07, 2009 11:51 pm
Contact:

Re: v6.19 released

Wed Sep 24, 2014 7:13 pm

3 rb133c's (using mipsle code)
These units are probaly to old to run ros v6
in general units support 2v updates and these boards are from around 2006
http://routerboard.com/pdf/rb133ugA.pdf
Then why would they release 6.x code for them then?
It states "RB111, RB112, RB133C, RB150 devices are not supported in v6, please use v5." on the download web page. http://www.mikrotik.com/download
 
mperdue
Member Candidate
Member Candidate
Posts: 290
Joined: Wed Jun 30, 2004 8:18 pm

Re: v6.19 released

Wed Sep 24, 2014 7:48 pm

Ok, thanks. At least now I know why 6.x bricks the units and that I'll be unable to upgrade further. - Michael
 
User avatar
SiB
Forum Guru
Forum Guru
Posts: 1888
Joined: Sun Jan 06, 2013 11:19 pm
Location: Poland

Re: v6.19 released

Sun Sep 28, 2014 4:20 am

21:41:30 ipsec,error phase1 negotiation failed due to time up. 01d4db047a60b9bc:0000000000000000
21:42:30 ipsec,error phase1 negotiation failed due to time up. 77ef7ebbe6072755:0000000000000000
21:43:30 ipsec,error phase1 negotiation failed due to time up. 84b2038687046a7f:0000000000000000
21:44:30 ipsec,error phase1 negotiation failed due to time up. 42deffb07e877772:0000000000000000
21:45:30 ipsec,error phase1 negotiation failed due to time up. 51399cc76d9cf438:0000000000000000
21:46:30 ipsec,error phase1 negotiation failed due to time up. 06bded99cac5be7f:0000000000000000
21:47:40 ipsec,error phase1 negotiation failed due to time up. 89a97510102ce77c:0000000000000000
21:48:40 ipsec,error phase1 negotiation failed due to time up. 3f89e001a721cbab:0000000000000000
21:49:50 ipsec,error phase1 negotiation failed due to time up. 218823fc05c11ed0:0000000000000000
21:50:50 ipsec,error phase1 negotiation failed due to time up. b6863d33d03abd58:0000000000000000
21:51:50 ipsec,error phase1 negotiation failed due to time up. 56afaac137289cf2:0000000000000000
21:52:50 ipsec,error phase1 negotiation failed due to time up. 3ba12327f25ba182:0000000000000000
21:53:50 ipsec,error phase1 negotiation failed due to time up. 9772820fef218c03:0000000000000000
21:54:50 ipsec,error phase1 negotiation failed due to time up. e0f9cea084fc72f2:0000000000000000
21:55:50 ipsec,error phase1 negotiation failed due to time up. f699872d6c861076:0000000000000000
21:56:50 ipsec,error phase1 negotiation failed due to time up. d14bf652f5792b1d:0000000000000000
21:57:50 ipsec,error phase1 negotiation failed due to time up. 29f50f1bcfb494ed:0000000000000000
21:58:50 ipsec,error phase1 negotiation failed due to time up. 0d818de75296c237:0000000000000000
+1
now 3th try to upgrade... v6.19 stable for 3h and wait for specific reason to do downgrade into v6.4, I hope this release is truly stable.
Support file was send to MikroTik Support Team (I before enable logging ipsec as debug to memory).
Image
 
Clauu
Member Candidate
Member Candidate
Posts: 217
Joined: Fri Mar 21, 2014 8:27 pm
Location: RO

Re: v6.19 released

Sun Sep 28, 2014 12:05 pm

Ipsec errors here too, rb2011uias+6.19
> ipsec,error failed to get valid proposal.
> ipsec,error failed to pre-process ph1 packet (side: 1, status 1).
> ipsec,error phase1 negotiation failed.
supout sent to mikrotik
 
miguelgoncalves
just joined
Posts: 11
Joined: Tue Jul 19, 2011 12:43 am

Re: v6.19 released

Mon Sep 29, 2014 12:54 am

I was about to deploy an RB450 as a router to an OOB management network where rock solid stability is a must. I will throw this RB450 in the trash and use another thing.

- Beta testing in a production environment is not for me.
- Reading a thread on a forum to determine if a stable version is really stable is not for me. It takes time. Time is money. With this development pattern MK is not that cheap.

Alternatives? I will be using pfSense on an ALIX board for this situation. For everything else: Cisco. It's expensive but it works! They publish firmware updates with small changes and they tell exactly what has been changed. The software version I am using in my ASAs is 8.4.7(22). They will stop providing corrections for the 8.4 line in March, 2016. This is 18 months away. This kind of information is required for a production environment. I don't understand MikroTik. I really don't.

Cheers,
Miguel
 
jarda
Forum Guru
Forum Guru
Posts: 7756
Joined: Mon Oct 22, 2012 4:46 pm

Re: v6.19 released

Mon Sep 29, 2014 10:37 am

I am willing to pay post fee if you would like to send it to me instead throwing it to trash.
 
vb101
just joined
Posts: 1
Joined: Tue Sep 30, 2014 10:13 am

Re: v6.19 released

Tue Sep 30, 2014 10:23 am

One effect that I experienced after upgrading from 5.25 to 6.19 on a RB951G and then restoring a backup file taken from another RB951G running 5.25 - routing & switching through the device was quite slow (5-7Mbit/sec), in the end the issue was resolved after reseting mac-address on master interface of the switch group, it seems that overriding mac address for the switch group interfaces was causing slow switching & routing.
 
steen
Member
Member
Posts: 475
Joined: Sat Oct 23, 2010 2:15 am
Location: Sweden
Contact:

Re: v6.19 released

Tue Sep 30, 2014 6:02 pm

I was about to deploy an RB450 as a router to an OOB management network where rock solid stability is a must. I will throw this RB450 in the trash and use another thing.

- Beta testing in a production environment is not for me.
- Reading a thread on a forum to determine if a stable version is really stable is not for me. It takes time. Time is money. With this development pattern MK is not that cheap.

Alternatives? I will be using pfSense on an ALIX board for this situation. For everything else: Cisco. It's expensive but it works! They publish firmware updates with small changes and they tell exactly what has been changed. The software version I am using in my ASAs is 8.4.7(22). They will stop providing corrections for the 8.4 line in March, 2016. This is 18 months away. This kind of information is required for a production environment. I don't understand MikroTik. I really don't.

Cheers,
Miguel
Hello Folks!
We had to give up on MT devices in some situations due to two things, policy based routing and l2tp tunnels could not pass more than some megabyte of data till they simply stopped passing traffic. The lt2p MT devices is stuck in RoS6.7, which in our case is very many devices at all customer and company side offices.

The policy based rotuing devices where replaced with ASA5510, which works like a charm since years back. We do not like to be stuck in low versions, neither do we like to use the very big power consuming ASA5510 and catalysts switches, which also is expensive to buy and keep, but they do work.

However we have a success story with all MT wireless devices, they saved our company wireless business. The same goes for CRS 125 switches, they have been successfully implemented on our datacenter and replacing older cisco switches, but they do lack one cruical function and that is spanning tree, which makes them impossible to build redundant layer 2 network. For that we still uses cisco and hp switches.

But who knows, in some future even MT will fix policy based routing and that l2tp tunnel bug and implement spanning tree in CRS 125 swiches.

Overall, without Mikrotik devices, our company had been out of business years ago!
 
User avatar
paoloaga
Member Candidate
Member Candidate
Posts: 227
Joined: Tue Mar 08, 2011 2:52 am
Location: Lugano - Switzerland
Contact:

Re: v6.19 released

Wed Oct 01, 2014 3:18 am

The same goes for CRS 125 switches, they have been successfully implemented on our datacenter and replacing older cisco switches, but they do lack one cruical function and that is spanning tree, which makes them impossible to build redundant layer 2 network.
One mandatory feature is Per VLAN Spanning Tree, which prevents us from switching old Cisco switches to CRS ones.
 
ste
Forum Guru
Forum Guru
Posts: 1924
Joined: Sun Feb 13, 2005 11:21 pm

Re: v6.19 released

Wed Oct 01, 2014 11:42 am

Now I run into a MPLS Problem with v6.19. After a connected bridge was updated/rebooted the bridged
network (even MPLS routers own address) is no longer reachable from our network. The route distributes
in ospf and LDP but packets do not get through. I cant repair it be disabling enabling the interface. Seems
I have to reboot the router and kick some hundred customers.

I am really pissed to debug all the time. Sent supout ...
 
aizhihuxiao
just joined
Posts: 8
Joined: Tue Jan 15, 2013 7:59 am

Re: v6.19 released

Wed Oct 01, 2014 12:18 pm

I found a bug when using routeros to be pptp client.
some problem cause pptp tunnel disconnected, but pptp client still hang in there. It will not reconnect automatic, I have to disable pptp client and enable again then it works.
 
zyzelis
Member Candidate
Member Candidate
Posts: 213
Joined: Sun Apr 08, 2012 9:25 pm

Re: v6.19 released

Wed Oct 01, 2014 1:25 pm

Now I run into a MPLS Problem with v6.19. After a connected bridge was updated/rebooted the bridged
network (even MPLS routers own address) is no longer reachable from our network. The route distributes
in ospf and LDP but packets do not get through. I cant repair it be disabling enabling the interface. Seems
I have to reboot the router and kick some hundred customers.

I am really pissed to debug all the time. Sent supout ...
Hello ste,
try to disable rstp on affected bridges. :)
 
ste
Forum Guru
Forum Guru
Posts: 1924
Joined: Sun Feb 13, 2005 11:21 pm

Re: v6.19 released

Wed Oct 01, 2014 2:25 pm

Now I run into a MPLS Problem with v6.19. After a connected bridge was updated/rebooted the bridged
network (even MPLS routers own address) is no longer reachable from our network. The route distributes
in ospf and LDP but packets do not get through. I cant repair it be disabling enabling the interface. Seems
I have to reboot the router and kick some hundred customers.

I am really pissed to debug all the time. Sent supout ...
Hello ste,
try to disable rstp on affected bridges. :)
There are bridges (physicaly) connected. The interface to this bridges is not bridged within ros.
So for sure no rstp problem.
 
ste
Forum Guru
Forum Guru
Posts: 1924
Joined: Sun Feb 13, 2005 11:21 pm

Re: v6.19 released

Thu Oct 02, 2014 10:34 am

Now I run into a MPLS Problem with v6.19. After a connected bridge was updated/rebooted the bridged
network (even MPLS routers own address) is no longer reachable from our network. The route distributes
in ospf and LDP but packets do not get through. I cant repair it be disabling enabling the interface. Seems
I have to reboot the router and kick some hundred customers.

I am really pissed to debug all the time. Sent supout ...
A nightly reboot solved the problem ... for a while.
So there is a bug in MPLS which might be in a place near you ... soon.
 
User avatar
sergejs
MikroTik Support
MikroTik Support
Posts: 6695
Joined: Thu Mar 31, 2005 3:33 pm
Location: Riga, Latvia
Contact:

Re: v6.19 released

Thu Oct 02, 2014 12:34 pm

Who is online

Users browsing this forum: DanMos79, Google [Bot], GoogleOther [Bot], NetTecture, RobertsN, sinisa and 77 guests