What's New in 6.23rc1 ?
CHANGELOG is empty
Re: 6.22 released!
Confirmed, address display for /tool torch is somehow messy (src-address is 192.168.230.1, dst-address not shown). The display within Winbox is ok.
Code: Select all
[admin@MikroTik] > /tool torch interface=WAN dst-address=0.0.0.0/0
MAC-PROTOCOL SRC-ADDRESS TX RX TX-PACKETS RX-PACKETS
ip 2.4kbps 1840bps 2 2
2.4kbps 1840bps 2 2
[admin@MikroTik] > /tool torch interface=WAN src-address=0.0.0.0/0
MAC-PROTOCOL TX RX TX-PACKETS RX-PACKETS
ip 4.2kbps 920bps 2 1
4.2kbps 920bps 2 1
[admin@MikroTik] > /tool torch interface=WAN src-address=0.0.0.0/0 dst-address=0.0.0.0/0
MAC-PROTOCOL SRC-ADDRESS TX RX TX-PACKETS RX-PACKETS
ip 192.168.230.1 4.6kbps 920bps 2 1
4.6kbps 920bps 2 1
Re: 6.22 released!
In the interests of making Mikrotik aware of what is happening, with 6.22 I'm seeing the following issues with an RB450G:
MicroSD card has completely disappeared from system, no longer showing under disks or stores. This last appeared correctly in version 6.18
Ethernet stats are zero for all slave ports configured as hardware switchports (ether5-trunk is the master port) and extended information is missing:
Similarly on the Ethernet interfaces directly:
MicroSD card has completely disappeared from system, no longer showing under disks or stores. This last appeared correctly in version 6.18
Ethernet stats are zero for all slave ports configured as hardware switchports (ether5-trunk is the master port) and extended information is missing:
Code: Select all
/interface ethernet switch port> print stats
name: ether2-skybox ether3-tv ether4-ap ether5-trunk switch1-cpu
driver-rx-byte: 0 0 0 1 359 887 146
driver-rx-packet: 0 0 0 6 157 431
driver-tx-byte: 0 0 0 7 683 300 763
driver-tx-packet: 0 0 0 8 133 653
rx-bytes: 0 0 0 0
rx-too-short: 0 0 0 0
rx-64: 0 0 0 0
rx-65-127: 0 0 0 0
rx-128-255: 0 0 0 0
rx-256-511: 0 0 0 0
rx-512-1023: 0 0 0 0
rx-1024-1518: 0 0 0 0
rx-1519-max: 0 0 0 0
rx-too-long: 0 0 0 0
rx-broadcast: 0 0 0 0
rx-pause: 0 0 0 0
rx-multicast: 0 0 0 0
rx-fcs-error: 0 0 0 0
rx-align-error: 0 0 0 0
rx-fragment: 0 0 0 0
rx-overflow: 0 0 0 0
tx-bytes: 0 0 0 0
tx-64: 0 0 0 0
tx-65-127: 0 0 0 0
tx-128-255: 0 0 0 0
tx-256-511: 0 0 0 0
tx-512-1023: 0 0 0 0
tx-1024-1518: 0 0 0 0
tx-1519-max: 0 0 0 0
tx-too-long: 0 0 0 0
tx-broadcast: 0 0 0 0
tx-pause: 0 0 0 0
tx-multicast: 0 0 0 0
tx-underrun: 0 0 0 0
tx-collision: 0 0 0 0
tx-excessive-collision: 0 0 0 0
tx-multiple-collision: 0 0 0 0
tx-single-collision: 0 0 0 0
tx-excessive-deferred: 0 0 0 0
tx-deferred: 0 0 0 0
tx-late-collision: 0 0 0 0
Code: Select all
/interface ethernet> print stats
name: ether1-gateway ether2-skybox ether3-tv ether4-ap ether5-trunk
driver-rx-byte: 7 288 415 796 0 0 0 1 361 018 164
driver-rx-packet: 8 072 759 0 0 0 6 165 323
driver-tx-byte: 831 390 476 0 0 0 7 692 641 941
driver-tx-packet: 5 676 361 0 0 0 8 143 470
rx-bytes: 0 0 0 0
rx-too-short: 0 0 0 0
rx-64: 0 0 0 0
rx-65-127: 0 0 0 0
rx-128-255: 0 0 0 0
rx-256-511: 0 0 0 0
rx-512-1023: 0 0 0 0
rx-1024-1518: 0 0 0 0
rx-1519-max: 0 0 0 0
rx-too-long: 0 0 0 0
rx-broadcast: 0 0 0 0
rx-pause: 0 0 0 0
rx-multicast: 0 0 0 0
rx-fcs-error: 0 0 0 0
rx-align-error: 0 0 0 0
rx-fragment: 0 0 0 0
rx-overflow: 0 0 0 0
tx-bytes: 0 0 0 0
tx-64: 0 0 0 0
tx-65-127: 0 0 0 0
tx-128-255: 0 0 0 0
tx-256-511: 0 0 0 0
tx-512-1023: 0 0 0 0
tx-1024-1518: 0 0 0 0
tx-1519-max: 0 0 0 0
tx-too-long: 0 0 0 0
tx-broadcast: 0 0 0 0
tx-pause: 0 0 0 0
tx-multicast: 0 0 0 0
tx-underrun: 0 0 0 0
tx-collision: 0 0 0 0
tx-excessive-collision: 0 0 0 0
tx-multiple-collision: 0 0 0 0
tx-single-collision: 0 0 0 0
tx-excessive-deferred: 0 0 0 0
tx-deferred: 0 0 0 0
tx-late-collision: 0 0 0 0
-
-
oscar198810
just joined
- Posts: 3
- Joined:
Re: 6.22 released!
Currently I have a problem with a CCR1009 + S1S1 with version 6.22, the simple queues dynamic and Static do not have a good performance.
I have configured PPPoE + EOIP + OSPF.
Previously had a RB1000AHX2 With 6.5v and all was well .
try installing the v6.5 version but change the CCR1009 iD Software and lost the license for which I had to return to the probe and the 6.22 but 6.17 to 6.21.1 .
I have configured PPPoE + EOIP + OSPF.
Previously had a RB1000AHX2 With 6.5v and all was well .
try installing the v6.5 version but change the CCR1009 iD Software and lost the license for which I had to return to the probe and the 6.22 but 6.17 to 6.21.1 .
-
-
oscar198810
just joined
- Posts: 3
- Joined:
Re: 6.22 released!
Currently I have a problem with a CCR1009 + S1S1 with version 6.22, the simplest dynamic queues do not have a good performance.
I have configured PPPoE + EOIP + OSPF.
Previously had a RB1000AHX2 With 6.5vy all was well .
try installing the v6.5 version but change the CCR1009 iD Software and lost the license for which I had to return to the probe and the 6.22 but 6.17 to 6.21.1 .
I have configured PPPoE + EOIP + OSPF.
Previously had a RB1000AHX2 With 6.5vy all was well .
try installing the v6.5 version but change the CCR1009 iD Software and lost the license for which I had to return to the probe and the 6.22 but 6.17 to 6.21.1 .
Re: 6.22 released!
Have 2SHPn as well.
All the sudden the past two versions and even RC23 are all causing SSID not to be broadcasted or allow attaching UNTIL REBOOT...
This is happening now very very very often... Had to ROLL BACK TO LAST V.5 to gain stability of SSID/RADIO broadcasting..
2SHPn IS NOT FIXED, STILL LOOSING SSID/RADIO (I do not have CPU 50/100 issue.., Clients just cannot connect and do not see SSID)
All the sudden the past two versions and even RC23 are all causing SSID not to be broadcasted or allow attaching UNTIL REBOOT...
This is happening now very very very often... Had to ROLL BACK TO LAST V.5 to gain stability of SSID/RADIO broadcasting..
2SHPn IS NOT FIXED, STILL LOOSING SSID/RADIO (I do not have CPU 50/100 issue.., Clients just cannot connect and do not see SSID)
Re: 6.22 released!
OK, that's it. I am quiting with this upgrade quick fix trash. Whole RouterOS is just pile of error after errors.
I just try 6.22 for a few minutes and now I am back on 6.18 and I will never try any new version again or buy a new MikroTik.
I bought 951G-2HnD in the spring. I want some really good WiFi AP for my IT workroom.
With original 5.26 (I think) USB 2,5" 250 GB HDD (small handy home made NAS) doesn't work on Android smartphone or tablet. Only some errors with lots of nonsence number.
With 6.xx it's start to work on Android, but on the Windows 7 (all my systems are Win7) it was really painfull, because it work only if you logged in Winbox and change some SMB file sharing settings (number of user etc). After clean star it was working for a while, but after Win7 hibernation, no way without login to Winbox.
FINALLY versin 6.17 fix that. but it was buggy and router died after couple shutoff (I disconned all electricity in all devices for the night).
So I managed to fix that through PXE boot.
With version 6.18 USB HDD was working almost fine like a NAS from computers and android devices.
But sometimes, it's show wrong amount of space left on HDD, but only sometimes. And manytimes all folders (except for web-proxy2 and lost+found) are suddenly gone and you have to wait for sometimes couple of minutes or log to the WInbox to get access for your folders and files back
I try 6.20 and it was working, little less folder disappearence, but show everytime only 9 MB space left, wchich was nonsence. But I was using 6.20 for the last two monthor something like that.
Today I try 6.22 and even 6.23 RC afterwards, but my HDD was gone, nothing worked, It didn't even show any HDD connected.
Seriously, do you think, that's normal? Why do you keep changing or corrupting something that worked OK?
You fix couple of error and make dozens new one. A milion versions but nothing stable and usable without problems.
Exacly the same think like Asus motherboards BIOS back in 2005-2007. Since 2008 I am using Gigabyte motherboars only and my
constant problems with BIOS (HW compatibility, unstability, error etc. etc.) are gone forever. No more Asus for me.
So no more MikroTik for me?
SMB and USB HDD NAS functionallity should work like a charm without any problems. Do it something wit it FINALLY!!! Thanks.
I just try 6.22 for a few minutes and now I am back on 6.18 and I will never try any new version again or buy a new MikroTik.
I bought 951G-2HnD in the spring. I want some really good WiFi AP for my IT workroom.
With original 5.26 (I think) USB 2,5" 250 GB HDD (small handy home made NAS) doesn't work on Android smartphone or tablet. Only some errors with lots of nonsence number.
With 6.xx it's start to work on Android, but on the Windows 7 (all my systems are Win7) it was really painfull, because it work only if you logged in Winbox and change some SMB file sharing settings (number of user etc). After clean star it was working for a while, but after Win7 hibernation, no way without login to Winbox.
FINALLY versin 6.17 fix that. but it was buggy and router died after couple shutoff (I disconned all electricity in all devices for the night).
So I managed to fix that through PXE boot.
With version 6.18 USB HDD was working almost fine like a NAS from computers and android devices.
But sometimes, it's show wrong amount of space left on HDD, but only sometimes. And manytimes all folders (except for web-proxy2 and lost+found) are suddenly gone and you have to wait for sometimes couple of minutes or log to the WInbox to get access for your folders and files back
I try 6.20 and it was working, little less folder disappearence, but show everytime only 9 MB space left, wchich was nonsence. But I was using 6.20 for the last two monthor something like that.
Today I try 6.22 and even 6.23 RC afterwards, but my HDD was gone, nothing worked, It didn't even show any HDD connected.
Seriously, do you think, that's normal? Why do you keep changing or corrupting something that worked OK?
You fix couple of error and make dozens new one. A milion versions but nothing stable and usable without problems.
Exacly the same think like Asus motherboards BIOS back in 2005-2007. Since 2008 I am using Gigabyte motherboars only and my
constant problems with BIOS (HW compatibility, unstability, error etc. etc.) are gone forever. No more Asus for me.
So no more MikroTik for me?
SMB and USB HDD NAS functionallity should work like a charm without any problems. Do it something wit it FINALLY!!! Thanks.
Re: 6.22 released!
I am sorry that you had to experience this, yes, you are right, we are working on some changes for the HDD mounting software in RouterOS, and it seems, that all your issues are related to that.
We are aware of the remaining problems, and are attempting to fix them.
We are aware of the remaining problems, and are attempting to fix them.
Re: 6.22 released!
"Normis",
It's not you... it's me...
And all the other problems and things that broke during all the other updates or that never really worked well...
CCR performance, multi threading, Memory Leaks, IPSEC issues, downgrade issues, upgrade issues, stability issues, queues, routing, firewalling, watchdog issues, kernel panics... i could definitely stay here for hours
I know that there are circumstances for all in life, but for me that work with more than 1K of your equipment's it's all getting to that point that i have to admit... I like Mikrotik very much and all the wireless paraphernalia is quite nice.
But i miss my other friends, those that have R&D and don't use the customer as a department (good move by the way less employees)
Those that are more expensive, but really have asics, application specific integrated circuits you know?
MKT is really cheap compared to my friends, but i'm tired of processed food.
Well all that and what will break on 6.23...
I know that the answer will be that all your are hardly working for a "better OS"
and you know what I'll probably do... flash them with something nice... something different... I'll think of something... don't worry..
It's not you... it's me...
And all the other problems and things that broke during all the other updates or that never really worked well...
CCR performance, multi threading, Memory Leaks, IPSEC issues, downgrade issues, upgrade issues, stability issues, queues, routing, firewalling, watchdog issues, kernel panics... i could definitely stay here for hours
I know that there are circumstances for all in life, but for me that work with more than 1K of your equipment's it's all getting to that point that i have to admit... I like Mikrotik very much and all the wireless paraphernalia is quite nice.
But i miss my other friends, those that have R&D and don't use the customer as a department (good move by the way less employees)
Those that are more expensive, but really have asics, application specific integrated circuits you know?
MKT is really cheap compared to my friends, but i'm tired of processed food.
Well all that and what will break on 6.23...
I know that the answer will be that all your are hardly working for a "better OS"
and you know what I'll probably do... flash them with something nice... something different... I'll think of something... don't worry..
Re: 6.22 released!
Hello Folks!
60% of our devices successfully updated to RoS6.22, rock solid for a week: rb333, rb411,rb433,rb600,rb750,crs and ccr. Remaining will be taken upcoming weekend.
60% of our devices successfully updated to RoS6.22, rock solid for a week: rb333, rb411,rb433,rb600,rb750,crs and ccr. Remaining will be taken upcoming weekend.
Re: 6.22 released!
Very clever, but you really think that I didn't test new version before I upgrade a critical router?Why upgrade that critical router before testing by yourself on other non critical place ?
I first upgrade my home MT router everything working then update non critical part of network and after that update critical part of network. I know people using today 2.9.27 or 3.30 or 4.17 or 5.26 or 6.22 and there are happy with that version.
Don't upgrade before testing on other non critical place.
RouterBoard have option to make partition make two partition one for testing other with working system tested before is something wrong happens just switch back to tested working system.
http://wiki.mikrotik.com/wiki/Manual:Partitions
If is something very very important upgrade must me planed, tested, prepared with replaced device ready to replace.... upgrading critical part of network without precise planing is crazy. It is nice button upgrade just to trysorry but on some places I can afford that luxury.
I have tested it on 3 other Routerboards... there is all ok, but on this very important router it ***** everything.
So next time please try to think before post some stupidity
-
-
jaykay2342
Member
- Posts: 336
- Joined:
- Location: /Vigor/LocalGroup/Milky Way/Earth/Europe/Germany
Re: 6.22 released!
Why do you the update of a critical router not during a maintenance windows? Even a tiny configuration change to a critical router i would only do during a maintenance windows having an implementation- and a rollback-plan. So if it is not working i roll back. For systems that are critical i have spare hardware. Those hardware is also be used for tests in the lab.
Very clever, but you really think that I didn't test new version before I upgrade a critical router?
I have tested it on 3 other Routerboards... there is all ok, but on this very important router it ***** everything.
So next time please try to think before post some stupidity
If i'm afraid something breaks i do a real test:
1. Export the config from the live system.
2. Replace the IPs with the ones from the test range. Just a search/replace with a text editor.
3. Import the new config into the test/spare device.
4. Do the planned change/upgrade on the test device.
Over all i agree that MT can improve the testing before they release a version. Some bugs are visible without a special config and should be found by doing basic tests.
Re: 6.22 released!
Steen, you are a partner of Mikrotik?Hello Folks!
60% of our devices successfully updated to RoS6.22, rock solid for a week: rb333, rb411,rb433,rb600,rb750,crs and ccr. Remaining will be taken upcoming weekend.
Or you're a lucky guy.
Re: 6.22 released!
+1Very clever, but you really think that I didn't test new version before I upgrade a critical router?Why upgrade that critical router before testing by yourself on other non critical place ?
I first upgrade my home MT router everything working then update non critical part of network and after that update critical part of network. I know people using today 2.9.27 or 3.30 or 4.17 or 5.26 or 6.22 and there are happy with that version.
Don't upgrade before testing on other non critical place.
RouterBoard have option to make partition make two partition one for testing other with working system tested before is something wrong happens just switch back to tested working system.
http://wiki.mikrotik.com/wiki/Manual:Partitions
If is something very very important upgrade must me planed, tested, prepared with replaced device ready to replace.... upgrading critical part of network without precise planing is crazy. It is nice button upgrade just to try
I have tested it on 3 other Routerboards... there is all ok, but on this very important router it ***** everything.
So next time please try to think before post some stupidity
Re: 6.22 released!
Very clever, but you really think that I didn't test new version before I upgrade a critical router?
I have tested it on 3 other Routerboards... there is all ok, but on this very important router it ***** everything.
So next time please try to think before post some stupidity
kubik256 and visalink maybe I am stupid but for now update dozen of router on 6.22 and all my routers working maybe because I am stupid and try to help you.
Also nice answer for anyone try to help you with this answer you can expect someone to help you
.Also next time thing before write something like this for people on forum try to solve your problem.
Good lucky to kubik256 and visalink
Re: 6.22 released!
Please upgrade the RouerBoard firmware to v3.19 and check if the situation gets better.Have 2SHPn as well.
All the sudden the past two versions and even RC23 are all causing SSID not to be broadcasted or allow attaching UNTIL REBOOT...
This is happening now very very very often... Had to ROLL BACK TO LAST V.5 to gain stability of SSID/RADIO broadcasting..
2SHPn IS NOT FIXED, STILL LOOSING SSID/RADIO (I do not have CPU 50/100 issue.., Clients just cannot connect and do not see SSID)
Re: 6.22 released!
I have the RB2011UiAS-2HnD, just bought it. I upgraded to v6.22 RouterOS, and now using the WebFig on Google Chrome, OSX Yosemite, initial configuration goes correctly but then in quick after configuring my wireless access point I'm seeing "no_country_set" and am unable to configure anything related to wireless. Winbox on my virtual machine works perfectly aside from crashing sometimes, shows all the configuration.
Re: 6.22 released!
Hello Folks!
All out devices are now successfully upgraded to RoS6.22 and latest firmware for each device, thats say:
RB333,
RB411,
RB433,
RB600,
RB750,
RB751U-2HnD,
RN2011 UAS-2HnD,
SXT-5D,
SXT G-5HnD,
SEXTANT(RB711G-5HnD, RB711-5HnD),
CCR1016-12G,
CRS125-24G-1S.
All systems working normally as far we can see.
Patching/Upgrading was made in two rollouts, two different cities using "The Dude", on first a few, and then many at time, going back to them and upgrade firmware and so on.
All out devices are now successfully upgraded to RoS6.22 and latest firmware for each device, thats say:
RB333,
RB411,
RB433,
RB600,
RB750,
RB751U-2HnD,
RN2011 UAS-2HnD,
SXT-5D,
SXT G-5HnD,
SEXTANT(RB711G-5HnD, RB711-5HnD),
CCR1016-12G,
CRS125-24G-1S.
All systems working normally as far we can see.
Patching/Upgrading was made in two rollouts, two different cities using "The Dude", on first a few, and then many at time, going back to them and upgrade firmware and so on.
Re: 6.22 released!
guyz,
my 951Ui-2HnD, updated to 6.22 from 6.20
start lose and high ping on wired connections.
also i can't update firmware to 6.19 from 6.18. router just accidentally rebooted right after i press update in inbox.
downgraded to 6.20. all fine.
whats wrong?
my 951Ui-2HnD, updated to 6.22 from 6.20
start lose and high ping on wired connections.
also i can't update firmware to 6.19 from 6.18. router just accidentally rebooted right after i press update in inbox.
downgraded to 6.20. all fine.
whats wrong?
Re: 6.22 released!
I have a problem after the update to 6.20 and 6.22
The problem in the PPPoE
Any Script Related Abute PPPoE Monitor IP change Not Work after the update to 6.20 and 6.22 as the connection Disconnected or downlink
this script working before the update to 6.20 and 6.22
this code send mail thin PPPoE Disconnected by another ISP by PCC Service
Code :
/system script add name="PPPoEmonitorIPchange" source={
:global currentIP1;
:global newIP1 [/ip address get [find interface="pppoe-ISP1"] address];
:if ($newIP1 != $currentIP1) do={
:put "ip address $currentIP1 changed to $newIP1";
:set currentIP1 $newIP1;
:if ([:pick $newIP1 0 8] = "192.168.") do={
/tool e-mail send to="mypersonalemail@gmail.com" subject=("Disconnected - ISP1") body=("$currentIP1")
} else={
/tool e-mail send to="mypersonalemail@gmail.com subject=([/ip address get [find where interface="pppoe-ISP1"] address] . " - ISP1") body=("$currentIP1")
}
}
/system scheduler add name=IPcheck interval=1m on-event=PPPoEmonitorIPchange
The problem in the PPPoE
Any Script Related Abute PPPoE Monitor IP change Not Work after the update to 6.20 and 6.22 as the connection Disconnected or downlink
this script working before the update to 6.20 and 6.22
this code send mail thin PPPoE Disconnected by another ISP by PCC Service
Code :
/system script add name="PPPoEmonitorIPchange" source={
:global currentIP1;
:global newIP1 [/ip address get [find interface="pppoe-ISP1"] address];
:if ($newIP1 != $currentIP1) do={
:put "ip address $currentIP1 changed to $newIP1";
:set currentIP1 $newIP1;
:if ([:pick $newIP1 0 8] = "192.168.") do={
/tool e-mail send to="mypersonalemail@gmail.com" subject=("Disconnected - ISP1") body=("$currentIP1")
} else={
/tool e-mail send to="mypersonalemail@gmail.com subject=([/ip address get [find where interface="pppoe-ISP1"] address] . " - ISP1") body=("$currentIP1")
}
}
/system scheduler add name=IPcheck interval=1m on-event=PPPoEmonitorIPchange
Re: 6.22 released!
Pretty much this. You need to duplicate the device. As much as a pain in the ass that is to do. We don't even make changes to our core routers during business hours, let alone any upgrade.Why do you the update of a critical router not during a maintenance windows? Even a tiny configuration change to a critical router i would only do during a maintenance windows having an implementation- and a rollback-plan. So if it is not working i roll back. For systems that are critical i have spare hardware. Those hardware is also be used for tests in the lab.
Very clever, but you really think that I didn't test new version before I upgrade a critical router?
I have tested it on 3 other Routerboards... there is all ok, but on this very important router it ***** everything.
So next time please try to think before post some stupidity
If i'm afraid something breaks i do a real test:
1. Export the config from the live system.
2. Replace the IPs with the ones from the test range. Just a search/replace with a text editor.
3. Import the new config into the test/spare device.
4. Do the planned change/upgrade on the test device.
Over all i agree that MT can improve the testing before they release a version. Some bugs are visible without a special config and should be found by doing basic tests.
-
-
napismizpravu
Member Candidate
- Posts: 135
- Joined:
- Location: czech
Re: 6.22 released!
Work is underway to correct the errors of work with discs that have arisen since version 6.20?
latest functionality works with disks was in version 6.19
discovered another bug,
smb deleted files ... USB Flash 8GB free space 144 MB samba info > delete 1,2 GB dat > smb info free space 144 MB / info free space winbox disk list 1,3 GB free space
disk format table ext3 print RouterOS / Windows NTFS
http://forum.mikrotik.com/viewtopic.php ... vu#p449879
+ deleted error message in thread
<Google Translator>
latest functionality works with disks was in version 6.19
discovered another bug,
smb deleted files ... USB Flash 8GB free space 144 MB samba info > delete 1,2 GB dat > smb info free space 144 MB / info free space winbox disk list 1,3 GB free space
disk format table ext3 print RouterOS / Windows NTFS
http://forum.mikrotik.com/viewtopic.php ... vu#p449879
+ deleted error message in thread
<Google Translator>
You do not have the required permissions to view the files attached to this post.
Re: 6.22 released!
I also just upgrade from 6.19 to 6.22 and now my 6to4 tunnels are broken (SIXXS) the are running / not running 
And the both have a IPv6 static route to keep the ping going bacause i don`t always use them since my provider sometimes gives me Native IPv6 when it is not broken
And the both have a IPv6 static route to keep the ping going bacause i don`t always use them since my provider sometimes gives me Native IPv6 when it is not broken
Re: 6.22 released!
I have problem with Intel Corporation 82576 Gigabit Network card after upgrade to: 6.15, 6.19, 6.22 MT lost 2-5% packet on this interface. 5.26 works fineNo, we have packet loss only on version 6.8-6.22.Versions 6.5-6.7 works stable. After 20-30 minutes MT start drops packet on all interfaces. In log file we see next message "105 (no buffer space available)". We try start VM on next servers:What about this problem?
http://forum.mikrotik.com/viewtopic.php?f=2&t=86119If you have packet loss in all versions, maybe there is some sort of hardware problem? if you have the chance, try another machine or at least other NIC
1. Supermicro X8DTT 12CPUs x 2.4 GHz Processor Type Inter(R) Xeon(R) CPU E5645 @ 2.40GHZ
Intel Corporation 82576 Gigabit Network Connection
Re: 6.22 released!
Hi to All!
Please, give a torrent file for RoS6.20
Please, give a torrent file for RoS6.20
-
-
napismizpravu
Member Candidate
- Posts: 135
- Joined:
- Location: czech
Re: 6.23rc7 disk error
RB433UAHWhat's new in 6.23rc7 (2014-Nov-25 08:26):
*) files - allow to move files between different disks in winbox;
*) dhcpv4 server - fix adding address lists;
*) dhcpv4 server - make radius classless static route tag as dhcp vendor specific;
*) smb - fixed HDD used/free space reporting
*) made powerpc metarouters work again (were broken in v6.22);
*) disks - fixed fat32 formatting where some bogus files with strange names were created
(to delete existing files reformatting is needed);
*) disks - fixed problem where some of USB disks were not recognized;
*) fetch - allow checking certificate trust without crl checking;
*) userman - fix more web session problems when user uses
customer and administrator interfaces at the same time;
*) snmp - fix external storage info reporting;
*) snmp - fix bulk walk problem introduced in v6.20;
*) fix tunnels - keep keepalive disabled for existing tunnels when upgrading;
*) fix tunnels - mtu for eoip tunnels was not allowed
to be set less than 1280 since 6.20;
*) using routing-marks could lead to tunnel loop detection to turn off tunnels;
6.20rcX -6.23rc7 persistent problem with USB Flash = not working proxy cache + free space 0 B + samba error (FTP access via FTP to disk is okay)
upgrade RouterOS ... correction error disk:
write name disk1 (default no name) > format USB FLASH - ext3 > disable proxy > enable proxy > reboot (if it fails, then repeat the process)
Version 6.19 errors with working with disks are not
You do not have the required permissions to view the files attached to this post.
Re: 6.22 released!
local tx, rx limits during bandwitch test dont limit test...
-
-
lunchboxrts
Member Candidate
- Posts: 143
- Joined:
- Location: United States
Re: 6.22 released!
Wireless clients randomly stop transmitting when connected to R11e-5HacD. Only fix is to disconnect and reconnect. Tested Yoga 3 Pro, iPad mini, Macbook pro, Apple tv, Netgear PTV3000, and Droid turbo. Also tried all the latest betas with the same results.
(the card is in a 912UAG-2HPnD)
(the card is in a 912UAG-2HPnD)
Re: 6.22 released!
I upgraded to 6.22 also firmware, but problem of Metal 2Shpn has not solved yet. I can't connect from 30 meters distance.
Re: 6.22 released!
Upgrading Omnitik from 5.24 to 6.13 works fine.
But after that, upgrade from 6.13 to 6.22 delete all my wlan1 configuration, exactly in the same way that 5.26 to 6.14.....
But after that, upgrade from 6.13 to 6.22 delete all my wlan1 configuration, exactly in the same way that 5.26 to 6.14.....
Re: 6.22 released!
What kind of configuration was deleted? Give a few examples what was lostUpgrading Omnitik from 5.24 to 6.13 works fine.
But after that, upgrade from 6.13 to 6.22 delete all my wlan1 configuration, exactly in the same way that 5.26 to 6.14.....
Re: 6.22 released!
6to4 tunnel NO fixed !!!
Router OS 6.22 Router OS 6.19 (6to 4 work OK)
Hi miszak,
I have same problems; you can post the ipv6 configuration?
for me, working only with version 6.15; have some problems with 6.20.
Thanks.
Re: 6.22 released!
**Metal 2Shpn is not working in 2GHz-B/G/N mode . it works only in B/G mode.
**Smart Phones , wifi usb Dongles & ip cameras are not connected with Metal 2Shpn @ short or long distance.
**Smart Phones , wifi usb Dongles & ip cameras are not connected with Metal 2Shpn @ short or long distance.
Re: 6.22 released!
6to4 tunnel NO fixed !!!
Router OS 6.22 Router OS 6.19 (6to 4 work OK)
Hi miszak,
I have same problems; you can post the ipv6 configuration?
for me, working only with version 6.15; have some problems with 6.20.
Thanks.
Please contact our support department. Send your supout.rif file/s from latest version. We have tested 6to4 and it works with correct configuration.
If there is something specific in your configuration what does not allow to create connection, then we would definitely like to fix it.
http://www.mikrotik.com/support.html
Re: 6.22 released!
contrary to v6.19 much lower wirelles throughoutput (2 times less sometimes), bad wireless stability, bandwitch test not working correctly....
Quick and easy way to reproduce 6to4 bug
Upload 6to4bug.rsc with following content (change the addresses of course) to router:
ros code
/ip address add address=AA.BB.CC.DD/24 interface=ether1 /ip route add gateway=AA.BB.CC.GG /interface 6to4 add local-address=AA.BB.CC.DD mtu=1480 name=6to4 /ipv6 address add address=2002:AABB:CCDD::1/16 advertise=no interface=6to4 /ipv6 route add distance=1 dst-address=2000::/3 gateway=::192.88.99.1%6to4Reset config:
ros code
/system reset-configuration run-after-reset=6to4bug.rscAnd then try to ping some IPv6 address:
ros code
[admin@MikroTik] > /ping address=2002:ca0c:1dea::1 count=1
HOST SIZE TTL TIME STATUS
2002:59b9:e186::1 104 64 0ms hop limit exceeded
sent=1 received=0 packet-loss=100%
[admin@MikroTik] > /ping address=2a02:610:7501:1000::2 count=1
HOST SIZE TTL TIME STATUS
no route to host
sent=1 received=0 packet-loss=100%
This is how it looks on 6.22, pinging other 6to4 address fails with "hop limit exceeded", native one fails with "no route to host". It works fine on 6.19 and lower.Re: 6.22 released!
Same problem i have, sometimes ....Upgrading Omnitik from 5.24 to 6.13 works fine.
But after that, upgrade from 6.13 to 6.22 delete all my wlan1 configuration, exactly in the same way that 5.26 to 6.14.....
it looks like it has found a new wlan adapter ... and lost the ols one
Re: 6.22 released!
My thoughts exactly.Steen, you are a partner of Mikrotik?Hello Folks!
60% of our devices successfully updated to RoS6.22, rock solid for a week: rb333, rb411,rb433,rb600,rb750,crs and ccr. Remaining will be taken upcoming weekend.
Or you're a lucky guy.
Re: 6.22 released!
kubik256, visalink
Are you able to provide us with support output file or remote access, when problem is present?
Are you able to provide us with support output file or remote access, when problem is present?
Re: 6.22 released!
Any details on this one?
*) dhcpv4 server - fix adding address lists from radius;
Last edited by santa on Tue Dec 02, 2014 4:25 pm, edited 1 time in total.
Re: 6.22 released!
Please try to install RouterOS v6.23rc10 and test if the issue is fixed as we have fixed only issue regarding 802.11ac driver.Wireless clients randomly stop transmitting when connected to R11e-5HacD. Only fix is to disconnect and reconnect. Tested Yoga 3 Pro, iPad mini, Macbook pro, Apple tv, Netgear PTV3000, and Droid turbo. Also tried all the latest betas with the same results.
(the card is in a 912UAG-2HPnD)
Re: 6.22 released! / OSPF issues on 750UP...
I deployed 2 new 750UP's on our network with v6.22. They are configured with OSPF between the two, then on one OSPF to another router. For some reason, the last leg in that chain never got a full OSPF route. I ended up downgrading both to 6.19 and they work fine now.
Configuration:
Router A: a 750UP v6.22 OSPF connected to:
Router B: a 750UP v6.22 OSPF connected to:
Router C: a 2011UiAS v6.12
OSPF between B and C worked as all routes were being shared from C to B. It failed between A and B as they would neighbor up just fine, but the only routes shared was the /29 shared between them. No other routes would get pushed to A. I tried rebooting both and even tried bridging them together, but nothing would work and I was short on time. Downgrading did the trick w/ the exact same configuration. :S Luckily these were new routers and had no users on them.
EDIT: I have 2 more 750UPs I could setup in a lab environment and see if I couldn't reproduce the issue. Anyone interested?
Configuration:
Router A: a 750UP v6.22 OSPF connected to:
Router B: a 750UP v6.22 OSPF connected to:
Router C: a 2011UiAS v6.12
OSPF between B and C worked as all routes were being shared from C to B. It failed between A and B as they would neighbor up just fine, but the only routes shared was the /29 shared between them. No other routes would get pushed to A. I tried rebooting both and even tried bridging them together, but nothing would work and I was short on time. Downgrading did the trick w/ the exact same configuration. :S Luckily these were new routers and had no users on them.
EDIT: I have 2 more 750UPs I could setup in a lab environment and see if I couldn't reproduce the issue. Anyone interested?
Re: 6.22 released!
Try, test and report back! LOLPlease try to install RouterOS v6.23rc10 and test if the issue is fixed as we have fixed only issue regarding 802.11ac driver.Wireless clients randomly stop transmitting when connected to R11e-5HacD. Only fix is to disconnect and reconnect. Tested Yoga 3 Pro, iPad mini, Macbook pro, Apple tv, Netgear PTV3000, and Droid turbo. Also tried all the latest betas with the same results.
(the card is in a 912UAG-2HPnD)
Re: 6.22 released! / OSPF issues on 750UP...
Everyone, I believeEDIT: I have 2 more 750UPs I could setup in a lab environment and see if I couldn't reproduce the issue. Anyone interested?
.Re: 6.22 released!
Hi.
When I update link to 6.22 witch wirelessfp my link loss packet randomly downgrade to 6.12 no problem.
When I update link to 6.22 witch wirelessfp my link loss packet randomly downgrade to 6.12 no problem.
Re: 6.22 released!
Please provide more detailed info on this problem to support@mikrotik.com and include a support output file.Hi.
When I update link to 6.22 witch wirelessfp my link loss packet randomly downgrade to 6.12 no problem.
-
-
lunchboxrts
Member Candidate
- Posts: 143
- Joined:
- Location: United States
Re: 6.22 released!
So far so good. No interface lockups but still to early to call it.Please try to install RouterOS v6.23rc10 and test if the issue is fixed as we have fixed only issue regarding 802.11ac driver.Wireless clients randomly stop transmitting when connected to R11e-5HacD. Only fix is to disconnect and reconnect. Tested Yoga 3 Pro, iPad mini, Macbook pro, Apple tv, Netgear PTV3000, and Droid turbo. Also tried all the latest betas with the same results.
(the card is in a 912UAG-2HPnD)
Re: 6.22 released!
Hi
I Have a small problem to configure queues for large quantity of IP's!
for 10 ore 20 ore 50 adreses it's ok to use simple queue, but if need to configure about 500 IP's (all of them is reserved to mac:) who i need to configure in different DHCP adress pools and download speeds + I need a time limits
I tell you- it's nightmare!
Try to use time shedule, but have a problem in weekends + i need about 8 shedules each working day. I have idea and hope it's will bee introduced.
Solution:
Maybe it's possible define adresses in ''Target'' ore ''Dst" from-to example: 192.168.7.48-192.168.7.254 in single queue?
Thanks!
I Have a small problem to configure queues for large quantity of IP's!
for 10 ore 20 ore 50 adreses it's ok to use simple queue, but if need to configure about 500 IP's (all of them is reserved to mac:) who i need to configure in different DHCP adress pools and download speeds + I need a time limits
I tell you- it's nightmare!
Try to use time shedule, but have a problem in weekends + i need about 8 shedules each working day. I have idea and hope it's will bee introduced.
Solution:
Maybe it's possible define adresses in ''Target'' ore ''Dst" from-to example: 192.168.7.48-192.168.7.254 in single queue?
Thanks!
Re: 6.22 released!
Hello!After upgrading to 6.22 I am getting warnings for "transmit loop detected, downing interface for 60 seconds" just as described in the logs. This is with a GRE tunnel that between two mikrotiks that was working before.
The tunnel is from one location with 2 internet providers to another location with a single internet provider. The first location has 2 tunnels setup with difference source addresses but the same destination address and the second location with the same source address but 2 different destination address. One of the tunnels works fine but the second is now useless. It was setup with a route to prefer our favored internet provider and to failover to the second if the primary's link failed.
What exactly is the loop detection supposed to do?
I had the same problem, and found reason of problem. In my case transmit loop detection was triggered because i used route-mark for making routing decision. After i've made static routes for my gre destinations - problem disappeared.
Re: 6.22 released!
Hello!After upgrading to 6.22 I am getting warnings for "transmit loop detected, downing interface for 60 seconds" just as described in the logs. This is with a GRE tunnel that between two mikrotiks that was working before.
The tunnel is from one location with 2 internet providers to another location with a single internet provider. The first location has 2 tunnels setup with difference source addresses but the same destination address and the second location with the same source address but 2 different destination address. One of the tunnels works fine but the second is now useless. It was setup with a route to prefer our favored internet provider and to failover to the second if the primary's link failed.
What exactly is the loop detection supposed to do?
I had the same problem, and found reason of problem. In my case transmit loop detection was triggered because i used route-mark for making routing decision. After i've made static routes for my gre destinations - problem disappeared.
This problem should be fixed in version 6.23.
Re: 6.22 released!
Sorry for the delay; This is the configuration as it has always worked up to version 6:15; then the new version no longer worked ...
This is my configuration:
Manual Route:
Version 6.15:
- working
Versione 6.19:
- (reset all, and restore rsc) - Working
Version 6.20:
- bridge-local and ether2-master-local -> no route to host
- sit1 -> echo reply
- Clients -> get IPv6 but not working
Version 6.22:
- on IPv6 Address the ether2-master-local is always Invalid, the ether5-slave-local is valid
- sit1 working; others interfaces not.
Versione 6.23:
- same problems of 6.22
Solutions? I have sended always supout.rif.
Thanks.
This is my configuration:
Code: Select all
/interface 6to4
add clamp-tcp-mss=no comment="Hurricane Electric IPv6" \
local-address=<Static Public IPv4 Address> mtu=1280 name=sit1 remote-address=\
<Server IPv4 Address>
/ip neighbor discovery
set sit1 comment="Hurricane Electric IPv6"
/ipv6 address
add address=<Client IPv6 Address> comment="IPv6 Gateway" interface=sit1
add address=<Routed /64> comment="IPv6 Network 1" interface=\
ether2-master-local
add address=<Routed /64>1 comment="IPv6 Network 2" interface=\
ether5-slave-local
/ipv6 firewall filter
add chain=input comment="Allow established connections" connection-state=\
established
add chain=input comment="Allow related connections" connection-state=related
add chain=input comment="Router Allow IPv6 ICMP" protocol=icmpv6
add chain=forward comment="Router Allow IPv6 ICMP" protocol=icmpv6
add chain=input comment="Allow UDP" protocol=udp
add chain=forward comment="Allow HTTP" dst-address=\
<server web>/128 dst-port=80 protocol=tcp
add action=log chain=input disabled=yes in-interface=sit1
add action=drop chain=input comment="Drop everything else"
add chain=forward comment="Allow any to internet" out-interface=sit1
add chain=forward comment="Allow established connections" connection-state=\
established
add chain=forward comment="Allow related connections" connection-state=\
related
add action=drop chain=forward
add action=log chain=output disabled=yes log-prefix="[DROP IPv6] " \
out-interface=sit1
/ipv6 firewall mangle
add action=change-mss chain=forward in-interface=sit1 new-mss=1220 protocol=\
tcp tcp-flags=syn tcp-mss=1221-65535
add action=change-mss chain=forward new-mss=1220 out-interface=sit1 protocol=\
tcp tcp-flags=syn tcp-mss=1221-65535
/ipv6 nd
set [ find default=yes ] advertise-dns=yes hop-limit=64
/ipv6 route
add distance=1 gateway=<Server IPv6 Address>Code: Select all
/ipv6 route
add dst-address=::/0 gateway=<Server IPv6 Address>- working
Versione 6.19:
- (reset all, and restore rsc) - Working
Version 6.20:
- bridge-local and ether2-master-local -> no route to host
- sit1 -> echo reply
- Clients -> get IPv6 but not working
Version 6.22:
- on IPv6 Address the ether2-master-local is always Invalid, the ether5-slave-local is valid
- sit1 working; others interfaces not.
Versione 6.23:
- same problems of 6.22
Solutions? I have sended always supout.rif.
Thanks.
Re: 6.22 released!
Thank you very much for your reports and help!
6.23 version is released!
viewtopic.php?f=2&t=91901
6.23 version is released!
viewtopic.php?f=2&t=91901
Who is online
Users browsing this forum: akakua, Bing [Bot], Google [Bot], GoogleOther [Bot], shahzaddj1 and 183 guests