if you mean Intel cards and VLAN - yesvlan issue fixed?
I've downloaded this 3 times, with the auto-updater and also direct from the website and dragged it into winbox.
Every time, after rebooting, it does not upgrade. The log says "broken package routeros-mipsbe-6.1.npk"
Is this router running one of the last rc versions? In that case try netinstalling.I've downloaded this 3 times, with the auto-updater and also direct from the website and dragged it into winbox.
Every time, after rebooting, it does not upgrade. The log says "broken package routeros-mipsbe-6.1.npk"
Use all-rates-fixed instead of card-rates for AR9300 WLANs.RB2011UAS-2HnD-IN Tx Power Problem
ROS V6.1 and V6.0 (Firmware 3.08)
On wireless tab
Frequency Mode set: manual txpower
Country: no_country_set
Atenna Gain: 0
Tx Power tab
Tx Power Mode set: card rates
Tx Power set: 18 dBm
Current Tx Power tab show all rates = 30 dBm Total Tx Power
Why is it so? Or I before it didn't notice?
Is this router running one of the last rc versions? In that case try netinstalling.I've downloaded this 3 times, with the auto-updater and also direct from the website and dragged it into winbox.
Every time, after rebooting, it does not upgrade. The log says "broken package routeros-mipsbe-6.1.npk"
One of the pre-release build for rc15 had this problem with upgrading. Netinstall if you see "broken package routeros-mipsbe-6.1.npk" message.Yes, it is running 6.0 RC15
Does RC15 break upgrading?
Please update FAQ and Manual))Use all-rates-fixed instead of card-rates for AR9300 WLANs.
It pre-release version. From development pageAFAIK RC15 was never released so it never happened.
use at your own risk, it saysIt pre-release version. From development pageAFAIK RC15 was never released so it never happened.
you have newer one. so don't worry and leave it untouched.Hello MikroTik team..
What does that mean ? and why ???
Thanks,
they are not. and they won't be includedAre included Global-In & Out Simple Queues in this version ? If not im never upgrade ROS.
why?I really need them .
Does this fix issue where auto negotiate is disabled and still the port will not link up?*) fix 1G linking with some Cisco devices (affects RB7xx, RB9xx, RB1100, RB2011, CCR);
IGMP works perfectly in 6.0 and 6.1 versions.Is IGMP proxy fixed?
Anyone having trouble with routerboot upgrade? It shows I am out of date but upgrading does not change the current version. No error message, nothing in log.
I found a minor GUI bug in the DHCPv6 Server Bindings. IPv4 servers show up in Winbox and Webfig.All reported issues are fixed
The changelog is being read from the server. After upgrade, you no longer are connected to the download server. Better read before you click the buttonBefore upgrade changelog in Sysstem->Packages->Check for upgrade is show but after is gone why ?...I think the cnahgelog is show always before and dfter ugrades.
/tool graphing> export verbose
# jun/13/2013 12:10:44 by RouterOS 6.1
# software id = EFBE-4LMB
#
/tool graphing
set page-refresh=300 store-every=5min
/tool graphing interface
add allow-address=0.0.0.0/0 disabled=no interface=all store-on-disk=yes
/tool graphing resource
add allow-address=0.0.0.0/0 disabled=no store-on-disk=yes
---------------------------------------------------------
/system resource print
uptime: 12m2s
version: 6.1
build-time: Jun/12/2013 11:50:54
free-memory: 3203.1MiB
total-memory: 3969.0MiB
cpu: tilegx
cpu-count: 36
cpu-frequency: 1200MHz
cpu-load: 1%
free-hdd-space: 428.1MiB
total-hdd-space: 512.0MiB
architecture-name: tile
board-name: CCR1036-12G-4S
platform: MikroTik
# ADDRESS FROM-... INTERFACE ADV
3 DL fe80::d6ca:6dff:fe3b:ec5/64 (unknown) no
You're wrong! Since there's a IGMP proxy in mikrotik there are two big bugs. One of them is described in this topic:IGMP works perfectly in 6.0 and 6.1 versions.Is IGMP proxy fixed?
Tested on RB951G-2HnD
I find that mine shows this for the wireless interface (or at least that's what the MAC address in the link local address implies).IPv6 link local address for bridge interface seems to be somehow broken. It was also on 6.0.
Somehow it worked for the first reboot after upgrade, but the second reboot broke it.
The link local address now gets assigned to (unknown) interface.If I remove this address, it gets regenerated in next reboot.Code: Select all# ADDRESS FROM-... INTERFACE ADV 3 DL fe80::d6ca:6dff:fe3b:ec5/64 (unknown) no
I trust you rebooted the router after the upgrade - otherwise the change won't have appliedAnyone having trouble with routerboot upgrade? It shows I am out of date but upgrading does not change the current version. No error message, nothing in log.
Sorry if this is an obvious question, but I can't figure out how to upgrade my 951G-2HnD from 5.25 to 6.1 at all.Anyone having trouble with routerboot upgrade? It shows I am out of date but upgrading does not change the current version. No error message, nothing in log.
There are some automatic upgrade capabilities as well, but simplest is to download a proper arch image (.npk) and upload to your device. Then reboot and maybe your box will com up not a brick and all functionality intact as well.Sorry if this is an obvious question, but I can't figure out how to upgrade my 951G-2HnD from 5.25 to 6.1 at all.Anyone having trouble with routerboot upgrade? It shows I am out of date but upgrading does not change the current version. No error message, nothing in log.
Using WebFig, System > Packages > Check for updates says Current Version = Latest Version = 5.25, but the announcement at the top of this thread suggests that the RB9xx units should be able to find and perform this upgrade to 6.1.
For what it's worth, System > License shows Software ID = 9G0L-4HZF, Upgradable To = v7.x, Level = 4; and System > Routerboard shows Current Firmware = Upgrade Firmware = 3.07.
Can anyone point me in the right direction please?
Thanks in advance,
-H
Currently, the auto upgrade feature only shows minor revisions. If you have v5.xx it will only show v5.xx+1Using WebFig, System > Packages > Check for updates says Current Version = Latest Version = 5.25, but the announcement at the top of this thread suggests that the RB9xx units should be able to find and perform this upgrade to 6.1.
please send full details of your configuration to supportipsec (transport mode) between linux openswan and mikrotik stopped working after upgrade from 6.0 to 6.1 ... ipsec between mikrotik and mikrotik works OK ...
after downgrading to 6.0 everything works OK ...
There are things that are not easily fixable between minor revisions of software. It will be fixed when possible, but I can't make any specific promises.Hi Normis, I don't know why mikrotik stuff pretends to be deaf whenever someone mentions IGMP proxy, you don't know how to fix that bug or don't want to do that?
IPSec logs or debug?need more details, IPSec did not receive any changes that would brake that.
try to enable debug logs on RouterOS and see what is happening.
I find out this bug with logging:Logging doesn't work also!
[admin@ITSC_MKTK] > system logging print
Flags: X - disabled, I - invalid, * - default
# TOPICS ACTION PREFIX
0 * info disk
1 * error disk
2 * warning disk
3 * critical echo
4 firewall disk
5 ipsec disk IPSEC_
6 debug disk DEBUG_
No new records in the log...
debug ipsec logs.IPSec logs or debug?need more details, IPSec did not receive any changes that would brake that.
try to enable debug logs on RouterOS and see what is happening.
Why is it incorrect?debug ipsec logs.IPSec logs or debug?need more details, IPSec did not receive any changes that would brake that.
try to enable debug logs on RouterOS and see what is happening.
"ipsec,debug" is what you have to add. above shows incorrect configuration and is not supposed to work.
ipsec configuration of linux box, and export compact of two routerboards has been sent to support ... [Ticket#2013061466000753]please send full details of your configuration to supportipsec (transport mode) between linux openswan and mikrotik stopped working after upgrade from 6.0 to 6.1 ... ipsec between mikrotik and mikrotik works OK ...
after downgrading to 6.0 everything works OK ...
Thanks -- that did the trick!Currently, the auto upgrade feature only shows minor revisions. If you have v5.xx it will only show v5.xx+1
To upgrade to a major revision, like the v6, you must upload this package in the Files menu, and reboot: http://download2.mikrotik.com/routeros/ ... be-6.1.npk
Also have had IPSEC problems 6.0 <-> 6.1 - downgraded the 6.1 side, and its now working again. However it was intermittent - ie worked fine since about midday yesterday until first thing this morning, then stopped.need more details, IPSec did not receive any changes that would brake that.
try to enable debug logs on RouterOS and see what is happening.
I guess it's a confirmed bug then?I find that mine shows this for the wireless interface (or at least that's what the MAC address in the link local address implies).IPv6 link local address for bridge interface seems to be somehow broken. It was also on 6.0.
Somehow it worked for the first reboot after upgrade, but the second reboot broke it.
The link local address now gets assigned to (unknown) interface.If I remove this address, it gets regenerated in next reboot.Code: Select all# ADDRESS FROM-... INTERFACE ADV 3 DL fe80::d6ca:6dff:fe3b:ec5/64 (unknown) no
again: it's not the number of routes, it's the number of routing tables. why do you need so much of them?..Hello MikroTik team
Why do you limit the number of routes by 251?
Could you please increase the number of routes limits? Thanks a lot.
again: it's not the number of routes, it's the number of routing tables. why do you need so much of them?..Hello MikroTik team
Why do you limit the number of routes by 251?
Could you please increase the number of routes limits? Thanks a lot.
Same problem with RB7xx . Manual disconnect and reconnect PPPoE client solves problem for few hours .After upgrade from 5.25 to 6.0 PPPoE client disconected after 3 hours on x86. System reboot PPPoE client conect again. Back to 5.25 all is OK.
I have observed this with SSTP and PPTP links also, random disconnects after only a few minutes of uptime, stable link on both sides and no problems prior to upgrade to 6.1.Problems here with IPSEC between Draytek and Mikrotik 6.1 - worked fine in 6.0 but upgraded to 6.1 and found the VPN randomly disconnects and will not reconnect.
Workaround - copy the IPSEC proposal and the connection comes back up but the issue re-occurs.
No logs available at this time (production environment)
This is turning into a spectacular problem for us too, and we've advised against 6.1 too. MikroTik, could you please be more careful with changing your scripting API? Some people have constructed elaborate management systems around it and have to also try accommodate multiple ROS versions across hundreds of routers. Changes like these really hamper the stability of the ROS platform.Hi,
We have 2 problems with the Ros6.1 release.
importing rsc scripts has changed the calling structure and also the maximum characters per router script has been changed in Ros 6.1
The first problem is fixable with some work on rewriting the structure of the scripts, aka where we had to \\\ a " or $ it has to change to only 1x \.
The second problem we can also sort by breaking the scripts up into smaller scripts being called.
I do not see these changes in the change log, and wondered who else has experienced this problem?
We have advised our clients not to upgrade to Ros6.1 for the moment as we first need to rewrite our scripts and test it on the new version, as it currently breaks (fails) on importing the rsc script file.
Is this an error on Mikrotik's side or will things stay this way forward?
Any info welcome please.
Thanks
Thanks,you are right!I just duplicate the answer here:
Linux Kernel supports upto 252 additional routing tables, so MikroTik cannot break that limit
So it is clear now that v6.1 has issues with IPSEC that were not there in v6.0 and v5.25... has anyone received any feedback from Mikrotik about this problem?Hi,
Just to keep you informed...
Downgraded back to v6.0rc14.
Upgraded firmware to v3.07
Upgraded to v6.0
Keeping firmware at v3.07 (even if it asks to upgrade to v3.02 (not sure what kind of upgrade is this))
L2TP/IPSEC works fine now.
Best regards,
the_prism
Had the same problem, just clear your browser cache and it should start working.I have upgraded from 5.25 to 6.1.
After upgrade I cannot login using web interface using Chrome 27.0.1453.110(Linux).
I got the message "ERROR: Internal Server Error"
I can connect to web interface using firefox, and I can connect using ssh.
Have checked, dns showing from 90 to 40-30-20-0. what can be wrong with dns ?alexanders check what "tool profile" menu shows. you will see which process takes it.
Don't fix what ain't broken. If you are happy and nothing is missing, stay with what you have.On RC13, 60 days uptime in production. Do you recommend upgrading to 6.1?
That's one of the lessons you learn the hard wayDon't fix what ain't broken. If you are happy and nothing is missing, stay with what you have.
Thank youDon't fix what ain't broken. If you are happy and nothing is missing, stay with what you have.On RC13, 60 days uptime in production. Do you recommend upgrading to 6.1?
6.2 RC1 has not been released to the public yet, and there is no changelog at all for 6.2 yet. You should wait for 6.2 to be released and then they will have a changelog for it.Please give me a link to ROS 6.2 RC1. And also, the current list of changes.
Thanks
How can someone get access to the beta/RC builds for testing/feedback before they get released to the public?6.2 RC1 has not been released to the public yet, and there is no changelog at all for 6.2 yet. You should wait for 6.2 to be released and then they will have a changelog for it.Please give me a link to ROS 6.2 RC1. And also, the current list of changes.
Thanks
Write to support and ask for access to beta releases.I don't need it at the moment (unless it includes a fix for IPSec ). I was just curious if there is a process (register somewhere?) for users to try beta versions for feedback etc.
I am debugging a site with mutiple IPSEC tunnels on ROS 6.1 currently.need more details, IPSec did not receive any changes that would brake that.
try to enable debug logs on RouterOS and see what is happening.
Hi Alex,The best way to manage logs in Mikrotik - and frankly just about anything - is to export them via Syslog to a Dude server. You can then filter/sort/export them to your hearts content.
Go one step further an deploy SIEM if you wish to do correlation etc... http://communities.alienvault.com/
I havent seen what you describe about secrets though. We are running about 70 Ipsec tunnels on 5.25 and beginning to test with 6.1.
Hmmm, reading above is a bit worrying about ipsec. Has anybody tried mikrotik -> Cisco Ipsec? v6.1?
Alex
This is turning into a spectacular problem for us too, and we've advised against 6.1 too. MikroTik, could you please be more careful with changing your scripting API? Some people have constructed elaborate management systems around it and have to also try accommodate multiple ROS versions across hundreds of routers. Changes like these really hamper the stability of the ROS platform.Hi,
We have 2 problems with the Ros6.1 release.
importing rsc scripts has changed the calling structure and also the maximum characters per router script has been changed in Ros 6.1
The first problem is fixable with some work on rewriting the structure of the scripts, aka where we had to \\\ a " or $ it has to change to only 1x \.
The second problem we can also sort by breaking the scripts up into smaller scripts being called.
I do not see these changes in the change log, and wondered who else has experienced this problem?
We have advised our clients not to upgrade to Ros6.1 for the moment as we first need to rewrite our scripts and test it on the new version, as it currently breaks (fails) on importing the rsc script file.
Is this an error on Mikrotik's side or will things stay this way forward?
Any info welcome please.
Thanks
So my first question, why does /import have to print script lines by default? Can you rather add a "debug=yes" or "verbose=yes" option to the import command, please? Reason being, we have scripts that are already perfectly verbose ala :put, so having ROS automatically print line numbers and commands creates an utter mess of the terminal output.
Secondly, please could you (MikroTik) explain exactly what other limitations have been imposed now, that Russian has observed? Right now all I see is scripts failing all over the network, and researching a fix will be much easier with an in-depth understanding of the changes you've made.
Thanks.
invalid length of payload
We rolled the worst site back to RoS6.0 and it's IPSEC tunnels have been stable for 3-4 days now. I have not been game to try RoS 6.2RC1 as this is a live customer site......Hi Alex,The best way to manage logs in Mikrotik - and frankly just about anything - is to export them via Syslog to a Dude server. You can then filter/sort/export them to your hearts content.
Go one step further an deploy SIEM if you wish to do correlation etc... http://communities.alienvault.com/
I havent seen what you describe about secrets though. We are running about 70 Ipsec tunnels on 5.25 and beginning to test with 6.1.
Hmmm, reading above is a bit worrying about ipsec. Has anybody tried mikrotik -> Cisco Ipsec? v6.1?
Alex
Thanks for the syslog suggestion. I'll redirect these logs to The Dude and see if that helps.
IPSEC is troubling me on ROS6.x.
We have had several sites upgrade from working IPSEC VPN to ROS6.x and they have each experienced some disruption.
In one case we only had to change one tunnel's encryption algorithm to get it working to this latest site where we had to set every password the same **.
We suspect, but have not yet proven, that special characters may also be an issue if used in the secret. As it is a live site once we got it going we have had to leave it alone
These tunnels are a mix of Mikrotik to Mikrotik and Mikrotik to 3rd Party routers.
** Now confirmed issue on two sites using RoS 6.1. Change password on one peer so that it is different to the others and it breaks all tunnels. Change it back and all tunnels are again connected within a few minutes.
** Also, disabling one peer in the group also caused tunnels to start dropping. Re-enabling the disabled peer corrected the issue.
This is like the peers are somehow inter-connected ?
I haven't had this or any other problems running 6.1 in a dual-WAN configuration. I don't use IPSEC or VPN.There is more to this than just IPSec issues. The router, running 6.1, was very sluggish in response to commands, as if it was stuck in a loop, the terminal window taking upwards to 30 seconds to get to a command prompt in comparison to the normal 3-5 seconds.
We rolled the worst site back to RoS6.0 and it's IPSEC tunnels have been stable for 3-4 days now. I have not been game to try RoS 6.2RC1 as this is a live customer site......Hi Alex,The best way to manage logs in Mikrotik - and frankly just about anything - is to export them via Syslog to a Dude server. You can then filter/sort/export them to your hearts content.
Go one step further an deploy SIEM if you wish to do correlation etc... http://communities.alienvault.com/
I havent seen what you describe about secrets though. We are running about 70 Ipsec tunnels on 5.25 and beginning to test with 6.1.
Hmmm, reading above is a bit worrying about ipsec. Has anybody tried mikrotik -> Cisco Ipsec? v6.1?
Alex
Thanks for the syslog suggestion. I'll redirect these logs to The Dude and see if that helps.
IPSEC is troubling me on ROS6.x.
We have had several sites upgrade from working IPSEC VPN to ROS6.x and they have each experienced some disruption.
In one case we only had to change one tunnel's encryption algorithm to get it working to this latest site where we had to set every password the same **.
We suspect, but have not yet proven, that special characters may also be an issue if used in the secret. As it is a live site once we got it going we have had to leave it alone
These tunnels are a mix of Mikrotik to Mikrotik and Mikrotik to 3rd Party routers.
** Now confirmed issue on two sites using RoS 6.1. Change password on one peer so that it is different to the others and it breaks all tunnels. Change it back and all tunnels are again connected within a few minutes.
** Also, disabling one peer in the group also caused tunnels to start dropping. Re-enabling the disabled peer corrected the issue.
This is like the peers are somehow inter-connected ?
You obviously have either a firewall rule blocking you, or an "Allowed Address" set on your username preventing your from logging in from a non-local address.one issue i have encountered is that if you are not "local" to the MikroTik trying to log into the box fails on everything, winbox, ssh, telnet even the webfig!
i upgraded a box to it (v6.1), then found i couldn't get to it any more, same thing happened to my box at home, dad couldn't log into it from the outside the network
any clues?
Kev
I'm seeing the exact same problem trying to connect an IPSec connection from a recently upgraded AH1100 V6.1 to an AH1100 V5.24. Not an issue connection to antoher AH1200 with V6.0rc13.ipsec from 6.1 to 5.25 - no connection
ipsec from 5.25 to 6.1 - packet rejected
I don't recommend downloading files from unknown sources. Those are not MikroTik domains.Do we dare after the ordeal 6.1 put us through??
When will be available for download 6.2?I don't recommend downloading files from unknown sources. Those are not MikroTik domains.Do we dare after the ordeal 6.1 put us through??
When all known issues will be fixed.
issue with IGMP PROXY is "known issues"?When all known issues will be fixed.
+1It's pretty well understood that things are kinda rocky in transitioning to ROS 6. Can we all please submit as many tickets to Mikrotik so that successive versions can get better? It does us no good to just complain frivolously.
I think Mikrotik is trying to do what they do as best as they can. Lets give them as much ammunition as we can to fix all these problems and help them succeed.
We saw the same errors connecting to a Sophos/Aastaro UTM and to a Sonicwall TZ170. Downgraded to 6.0 and the problem went away. Did not matter what Phase 1 settings were, it simply would not complete Phase 1.On the V5.24 side I see errors such as "malformed cookie" and "invalid payload length".
I'm a bit weary of upgrading the V5.24 router as it is in our headoffice and always in use, and when upgrading the other two units to V6.0rc13 it didn't apply the IP settings to the correct ports or not at all and requiring me to do the configuraiton from scratch on both the other routers.
Two years for a reported bug that still has not been resolved is "working really hard"??+1It's pretty well understood that things are kinda rocky in transitioning to ROS 6. Can we all please submit as many tickets to Mikrotik so that successive versions can get better? It does us no good to just complain frivolously.
I think Mikrotik is trying to do what they do as best as they can. Lets give them as much ammunition as we can to fix all these problems and help them succeed.
Mikrotik are working really hard to resolve the reported issues.
Please tell me the ticket number of this issue, and I will check the progress.Two years for a reported bug that still has not been resolved is "working really hard"??
They're wasting time on nonsense and unnecessary things while serious bugs are still unresolved.
Wow, that IS old! What is the issue in that ticket?October 03, 2011 12:08 PM
Ticket#2011092966000591
2yrs minus 2 days and counting...CCR1036-12G-4S on v6.1
lost ping to CCR after winbox attempt. any help?
Reply from 192.168.10.252: bytes=32 time<1ms TTL=64
Reply from 192.168.10.252: bytes=32 time<1ms TTL=64
Reply from 192.168.10.252: bytes=32 time<1ms TTL=64
Reply from 192.168.10.252: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
http://forum.mikrotik.com/viewtopic.php ... hilit=igmpWow, that IS old! What is the issue in that ticket?October 03, 2011 12:08 PM
Ticket#2011092966000591
This is well known and documented. Backup is only for restoring on the same machine. Use Export/Import files to move config. This is not a bug.Hi All
in the 6.0 rc14 I have found that, exporting and importing backup on another hardware, backup also imports the mac address.
Once imported you can not change it in winbox and if change manualy in the .backup file don't effect.
I remeber this problem was present in versions 2.xx but solved in the next.
The problem has been fixed in 6.1? I have no way to test it at the moment.
thanks
Senzatempo
ok backup is for the same hardware, but in previous versions (5,x) worked well on different hardware.This is well known and documented. Backup is only for restoring on the same machine. Use Export/Import files to move config. This is not a bug.
Hello,MikroTik team!
It will be great,if you can fix problem with (3g/4g) ppp disconnection,and add ndis driver for popular 4g modems.
PPP disconnects after 1 minute or 40 minutes,and then try reconnects every second.
3G Network signal quality is from -74dbm to -83dbm.
I tested RoS version from 5.22 to 6.2rc1.
All versions have this problems.
My record was 1:40 minutes without disconnection.
(RoS 6.2rc1;RouterBoot 3.5)
Also I noticed that problem occurs frequently,if you didn't add NAT masquerade rule,or disable it.
This problem is very old.
Some forum themes about it:
http://forum.mikrotik.com/viewtopic.php?f=3&t=71031
http://forum.mikrotik.com/viewtopic.php?f=9&t=56463
Thanks.
Hi Normis, did you check progres of ticket #2011092966000591?Please tell me the ticket number of this issue, and I will check the progress.Two years for a reported bug that still has not been resolved is "working really hard"??
They're wasting time on nonsense and unnecessary things while serious bugs are still unresolved.
You can tell which bugs are fixed in version 6.2?We don't have any holidays now. Work work work and fixing bugs
See changelog.You can tell which bugs are fixed in version 6.2?We don't have any holidays now. Work work work and fixing bugs
Excuse me, but where to get a new list of changes. There is only 6.1.See changelog.You can tell which bugs are fixed in version 6.2?We don't have any holidays now. Work work work and fixing bugs
here: http://forum.mikrotik.com/viewtopic.php ... 34#p377724Excuse me, but where to get a new list of changes. There is only 6.1.
One known nssa problem was fixed several versions ago, so please be more specific on problem description.what about OSPF -nssa stability ? is that fixed?
connected network on nssa (redistribute connected on) become unreachable, default route on nssa present, translator always on but dont know where is nssa connected network, reboot tranlator fix this bug... to next timeOne known nssa problem was fixed several versions ago, so please be more specific on problem description.what about OSPF -nssa stability ? is that fixed?
ok backup is for the same hardware, but in previous versions (5,x) worked well on different hardware.This is well known and documented. Backup is only for restoring on the same machine. Use Export/Import files to move config. This is not a bug.
Please to want to consider how to implement inquiry, working with similar configurations on the same model of rb, it is very convenient to use it instead of having to use export / import
to be able to import a configuration with import takes several steps, with the backup function only 1 click.
THS all
Senzatempo
Did you contact support ? Let me know your ticket number, I will check statuswe are running 6.2 about JUL 08 and still experiencing random not active PPPoE interface.
attached there is a screen shot
NORMIS, when it will be fixed???
thanks
Did you contact support ? Let me know your ticket number, I will check statuswe are running 6.2 about JUL 08 and still experiencing random not active PPPoE interface.
attached there is a screen shot
NORMIS, when it will be fixed???
thanks
what should Normis see in a fresh ticket? wait for an answer from support first[Ticket#2013072566000383]
regards
Ros
In which RouterOS version did it work? What device is this ?Hi guys, my ethernet chip atheros AR8151 b not recognized with ros 6.1 ,any idea why this happen ?
In which RouterOS version did it work? What device is this ?Hi guys, my ethernet chip atheros AR8151 b not recognized with ros 6.1 ,any idea why this happen ?
thank youIf it never worked before, there is nothing we can do. Apparently linux kernel doesn't support it yet.
Same Problem here. Only one IPSEC connection can be established. It seems something is broken in 6.1 regarding IPSEC.Hi Folks,
Problem was that only on IPSec Peer would establish correct SAs, randomly, that means it doesn't matter if it was the netgear or a RB2011xx. Analysing the problem showed that one had to deactivate all but one peer, this peer would come up perfectly. Then activate the next peer, wait until it would come up after nearly one minute. And so on.
It's still broken for me in unreleased ROS6.2. Very strange issue (2x RB2011), ping and small packets are passing fine, but larger packets are not reaching it's destination. I'm checking what can cause this and there is a support ticket open, but I had no much luck until now.....
Yes, IPSEC is broken in 6.1. It should be fixed in 6.2, look back a few posts for the pre-release link to it.
Yeap, on 6.2 pre-release IPSec is still broken.It's still broken for me in unreleased ROS6.2. Very strange issue (2x RB2011), ping and small packets are passing fine, but larger packets are not reaching it's destination. I'm checking what can cause this and there is a support ticket open, but I had no much luck until now.....
Yes, IPSEC is broken in 6.1. It should be fixed in 6.2, look back a few posts for the pre-release link to it.
write to support@, they can give you access to pre-release builds with (sometimes) changelogs via your MikroTik.com accountMaybe they could form a beta testing community to allow to it access to night builds and have a larger set of installations to do tests before public releases.
Has anyone tested this in production using 6.2 final release? changelog says its fixed........Yeap, on 6.2 pre-release IPSec is still broken.
I second this. I was so stupid to upgrade a CCR router from beta "release candidate" to the "stable/release" version 6.2 and now it totally crashed after two weeks of uptime. It's a very very basic setup with 10 VLANs and a VPN (PPTP) access (and "no" traffic compared to what a CCR is supposed to handle!).Out of all the releases for CCR, RC13 looks like the most stable.
does anybody know about those issues? have you written to support@?I tried a few times to use 6.7, then 6.1 but both have issues using MLPPP which I almost exclusively use the Mikrotiks for. Normally on 750GL's or 493AH's depending on the number of lines in the bond.