jvkassar,
You have Point to Point or Point to Multi Point links using v6.23?
What speed you are getting with v6.20 and v6.23?
Could you provide support output files from both versions and send to support@mikrotik.com

Uldis,

When looking at the Ethernet ports, the right hand side. It was hot enough that I had to let it go. it was as hot or hotter then a cup of coffee. The Temp on the system/health after letting it sit for a bit was 55Deg, this was after I let it cool for a bit when I powered it off.

Its been on for hours now and the temp is 32 Deg so its normal.

Just looking through the vent holes, I would say the hottest part of the case was on the right side when looking at the Ethernet ports. Inside there is a heatsink cose to the LCD screen, I'm guessing this is the CPU? To put it in perspective better, the HOTTEST part was the right side of the case, but the other side (Left) was also hot but I could hold it from that side.

I do recall that I tested a speedtest from this device to another MikroTik CRS 24 port just to see the max speeds I could get over the Ethernet. The speedtest said at one point " Could not continue, no such test"

This test was from a CRS125-24G-1S-2HnD. The test stopped on the RB2011, and the data rate showed a few K of data, where as on the CRS it showedsome number, 400+ Mbit or something. I then relized that the RB2011 was assigning IP's so I had to unplug the network cable from the CRS, but I left the RB2011 powered on, just sitting on the desk. I left it probably for 30-45 minutes when I started to smell the "fried electronics" smell, that's hen I picked it up and I actually dropped it because it was that hot, and said a few profanities.... something like " holy F___ that's hot" I relized pretty quick that this wasn't normal, that's why I unplugged it.

Just thinking about it now, I cannot recall if I had the Ethernet cable unplugged for that 45 minutes or if it was plugged in, on ether 2 on the RB2011. I checked the graph for the port that it was connected to on my CRS125-24G-1S-2HnD and that port only has a very short duration on the graph no higher then 50 Mbit, not any where near 30 - 40 minutes, so I can rule out that the speedtest was running that whole time, even if it was, the temp should not of got that hot.

I also just remembered that I seen that port 10 had POE out, so I plugged in a UBNT Rocket M5 with a short 3 foot cable, and had it plugged in for a couple minutes, and just looked at the POE stuff on that interface, it said powered on, and didn't show any current draw level in winbox for the port 10 POE. I did a power cycle from within winbox for 5 seconds which is the default. But the RM5 wasn't hooked up longer then 2 minutes.

Seems ok now, not hot, just a warm 32 Deg


** EDIT, While posting the above, I did the exact same things as when I first did them, other then the upgrade from 6.5 to 6.23, and the board temp has maintained the 32 or 33 deg. Well for at least 10 minutes while typing the above.

I should also point out, this RB2011 is NEW, I just got it and upgraded from 6.5 to 6.23 right away, so I do not know if the overheat would of happened on ver 6.5....

jvkassar,
You have Point to Point or Point to Multi Point links using v6.23?
What speed you are getting with v6.20 and v6.23?
Could you provide support output files from both versions and send to support@mikrotik.com

Uldis, I sent the email as requested.
Tested in Point To Point ...
Thank you.

After 6.23 update I have port flapping on SXT lite 5.

I am running 3.19 Firmware and 6.23OS...

SSID will stop broadcasting. RB will respond, what debugging can be done to track this down?

I do not see resources that would explain it, I do not see anything in debugging that sticks out... It will stop SSID until a reboot. I can soft reboot and will work for a few minutes, takes a hard reboot to operate for a while. There is NOTHING other than bridged traffic.

Just to update the community on my CCR Port Flapping issue reported here.

According to Mikrotik any changes to the L2MTU of any interface on a CCR (they didn't explicitly talk about normal MTU so I will do some testing on this) requires the system to allocate "new space for certain interface in the internal buffer" and they report this is a hardware specific requirement for the CCR and they do not consider it a bug.

So a warning for permanent record.

Any change to L2MTU on any interface of a CCR will result in all interfaces flapping to implement buffer changes.

travisnj,
what board you are using?
Please make a support output file when the problem is happening and send it to support@mikrotik.com

After 6.23 update I have port flapping on SXT lite 5.

Please send the supout.rif file to MikroTIk support for inspection.

After 6.23 update I have port flapping on SXT lite 5.

Please send the supout.rif file to MikroTIk support for inspection.

Supout just sent.

hello everyone,
does anyone know of any issues related to IPSEC VPN tunneling using this release.
i upgrade my RB450 to the latest firmware and OS but i cannot connect via IPSEC now .
it works using pptp .
I am new in here, so if anyone can direct me to right place or send me the info on how i can fix it it would be great.

thanx for reading.

Depends from which version you upgraded. Could be that previously you had disabled default policy template or maybe default policy group is not set in peer settngs.
Enable ipsec debug logs for more output.

Any change to L2MTU on any interface of a CCR will result in all interfaces flapping to implement buffer changes.

Not necessarily taking sides here, but realistically, how often do you change the L2MTU on an interface?? Shouldn't that mostly be a set-it-and-forget-it setting? (Of course, if you ever do need to change it, it is good to be aware of this, though IMO you shouldn't be making changes to settings like that outside of a scheduled maintenance window anyway.)

-- Nathan

When I bring in a new ethernet service from a provider I configure the MTU and L2MTU on that port for the new service (we have providers who provide a range of MTU's to us so one standard doesn't protect everything.

This normally is not an issue as there will be no customer traffic on that link yet (its just being prepared for configuration).

However unlike boxes like the 1100's etc the CCR will flap all ports (not just the port that is being changed) and therefore any building of a new port requires an outage window because services will flap and if this box happens to also be our primary NNI box with another provider (thus dropping hundreds of customer connections) or is a device that provides a critical service we can no longer make these changes without that window.

Just to be clear, I expect the port I change to flap, however a change to one port that causes flapping on every active port on the box (especially when each port supposedly is independent (not switch chip etc)) then I would be expecting to be able to change an inactive port without having to open up a maintenance window.

Also I wanted to but down in writing this behaviour as its not on the MTU page in the wiki.

Regards
Alexander

Hello! I update to this FW, and have a problem!
apple (iphone, macbook) device then pptp disconnects after precisely 2 minutes and 30 seconds. on the previous version , this problem was not.

Hello! I update to this FW, and have a problem!
apple (iphone, macbook) device then pptp disconnects after precisely 2 minutes and 30 seconds. on the previous version , this problem was not.

I am connected for a long time now, from an iPhone to RouterOS v6.24 PPTP server, no disconnections. Have you tried looking in the Log? What is the stated reason for disconnection?

Hello All!
Does anyone know of any issues related to IPSEC VPN tunneling using this release.
i upgrade my RB2011UiAS from 6.21 to the latest firmware and OS but i cannot connect via IPSEC now . :-\
Everything worked before the upgrade.

Hello All!
Does anyone know of any issues related to IPSEC VPN tunneling using this release.
i upgrade my RB2011UiAS from 6.21 to the latest firmware and OS but i cannot connect via IPSEC now . :-\
Everything worked before the upgrade.

Have you tried looking in the Log? What is the stated reason for disconnection?

Hello All!
Does anyone know of any issues related to IPSEC VPN tunneling using this release.
i upgrade my RB2011UiAS from 6.21 to the latest firmware and OS but i cannot connect via IPSEC now . :-\
Everything worked before the upgrade.

Have you tried looking in the Log? What is the stated reason for disconnection?

Normis in your other post you said "from an iPhone to RouterOS v6.24 PPTP server".
Are you talking about the RC version?
I think that in 6.23 there are some issue with the security package because in one SXT I have CPU always at 100% after upgrade and disabling security it returned to 5-6%.

Hello All!
Does anyone know of any issues related to IPSEC VPN tunneling using this release.
i upgrade my RB2011UiAS from 6.21 to the latest firmware and OS but i cannot connect via IPSEC now . :-\
Everything worked before the upgrade.

Have you tried looking in the Log? What is the stated reason for disconnection?

Normis in your other post you said "from an iPhone to RouterOS v6.24 PPTP server".
Are you talking about the RC version?
I think that in 6.23 there are some issue with the security package because in one SXT I have CPU always at 100% after upgrade and disabling security it returned to 5-6%.

Try the RC, it is on our regular download page

Have you tried looking in the Log? What is the stated reason for disconnection?

Attached log.

Try the RC, it is on our regular download page

I can't because I want to wait for a stable version, I downgraded all the SXT to 6.19 because I have also port flapping (I sent the supout for this problem) but between the 4 am and 4.30 am the ether 1 now flap also with 6.19 and 3.18 firmware. Before upgrade I have no port flapping and no problem with security package (this happen only on 1 of 3 SXT upgraded and continue on that SXT despite downgrade).

Have you tried looking in the Log? What is the stated reason for disconnection?

Attached log

ntp client CCR not working anymore on 6.23. Anybody has the same issue? Both ntp packages (system standard or ntp) same result. One CCR worked for a year with previous versions but since 6.23 no more.
Other, new CCR without any firewall rules, only srce-nat masquerade connected to new provider wont get its clock updated. But have internet access....

Anybody with the same issue?

src nat an attached PC's IP to a public IP (have some set on WAN connected interface, gateway is on other side of cable=provider)
when I use 'masquerade' all works fine. change the rule in src-nat to, and give it any IP residing on the WAN port, no traffic.

I can set any public IP (class C range) on the WAN interface and masquerade works, But not a single src-nat to seems to work... traffic is not passing.....

All other firewall rules are empty (yet)

Any ideas/same experiences?

In relation with previous 2 posts;

Can't downgrade a CCR1016 to a previous version..... how's that!

We were hoping by a downgrade to restore the ntp issue and make srce-nat work but now I can't downgrade! (to 6.19 that worked stable)


How do I downgrade? Upload the previous version packages in the file folder. select "downgrade" and router ask confirmation with the reboot warning and I press 'enter'.
Router reboots, but still comes up in 6.23 and the files are still in the folder.....

Anybody with same experiences?

I used to keep all of our equipment on the same version but for the past year I stopped after having several unit failures or issues after upgrading. Several times I have had to try to downgrade and have the unit 'brick' on us and I have to send someone to the tower to replace a unit. That got very frustrating and expensive.

I would really like to see mikrotik work out the bugs and release a 'stable' version for those of us that do not wish to beta test / debug software. Most linux distro's have a release that should be pretty stable and is supported long term.

I just pulled the latest versions and was about to start upgrading some units then had second thoughts and decided to read through the 6.23 release topic, and now I'm very nervious about upgrading anything. I have versions 5.6 to 6.19 deployed and it would be nice to get everyting on a stable version.

Ealier this year I upgraded some older rb112's to 6.19 and had them brick on me and was told those no longer are supported in 6.x. But stragely I have a single unit that I upgraded this morning that seems stable on 6.23. So is it or is it not supported?

Regards,
Michael Perdue

Just found a differnt topic about the rb112 etc etc. http://forum.mikrotik.com/viewtopic.php ... 12#p454958 so guess that answers my question about that.

Design Skin problems on 6.23 and 6.22 (6.20 and 6.19 not affected)

http://forum.mikrotik.com/viewtopic.php?f=2&t=92305

Port flapping on SXT that began after upgrade to 6.23 this night from midnight to 3 AM several time.
Despite downgrade from 6.23 to 6.19 the situation is very very very annoying.

Hello.
There is no MetaROUTER config in WebFig after upgrade from 6.22 to 6.23, though WinBox still has it.
RB2011UiAS, firmware 3.19.

Any chance that winbox can be enhanced to allow one to see and change the ntp client server-dns-names field?

This field is actually quite useful if you put something like us.pool.ntp.org in it.

You can also try to use the Server-DNS-Names setting to specify the dns name of the ntp server:
/system ntp client set server-dns-names=us.pool.ntp.org

or (resolution errors catch):

مساءالخير ممكن مساعده انا اريد ان ادخل الى السيفر من مكان بعيد

مساءالخير ممكن مساعده انا ان ادخل الى السيفر من مكان بعيد

I didnt have much time for testing, but I think there is some problem:
Android phones and Planshets can't connect to VirtualAP. There wasn't such a problem in 6.19 and 6.22
Maybe anyone can confirm and give a solution?

I just tested this in my lab. I can connect to RB493G with RoS 6.23 installed with wlan1 as physical port and wlan2 as virtual ap. I connected with my Samsung S2 running Androrid, no problems detected. I don't think this is a general issue.

Thanks! I'll try to test again further.

Remote CAP upgrade does not work.
In this case, the update manually, is operating normally.

Remote CAP upgrade does not work.
In this case, the update manually, is operating normally.

As you can see in the log, security package is missing.

As you can see in the log, security package is missing.

Sorry, and thank you Normis.

new day not stamp in log. only hour

OK I am TIRED OF THIS!!!!

I have been trying to track down a problem with routing.. SIMPLE STATIC ROUTES.

I have wasted 3 days on this. You will be surprised to find out what it is.... its version 6.23. And every time I reboot the CRS125-24G-1S-2HnD I get a different result.

From a WIRED PC I cannot ping some devices, other MT products, NetMEtal5 also running 6.23. Yet from a tablet on wifi I can ping that same device.
Ironically, I could not ping the other end of that ptp link, which is in WDS bridge. I also could not ping the IP assigned to the Ethernet port on the RB 2011 that connects to another Netmetal5 ( The far end of the link )

This RB1100 is used at another location on a different subnet, it has the dynamic route vreated for the subnet that is assigned to the ether 2 interface, which is the subnet for the network at my place.

The messed up part is, that I cannot ping the two Netmetal 5's, and not that Ethernet interface at the far end, BUT I can ping the Bridge - lan interface for the LAN on the far side. I can also ping any other device.

From the far side, I cannot ping some of the devices over here at my local side, either from a desktop pc or from the RB 2011. reports unreachable.

What I am PISSED about is that I did nothing different, this set up has been the same for about.. I cant remember...
What pisses me off more, is that all I do is reboot the CRS that is at my place and it works, even pinging the NAS at my place from the desktop at the other end of this link on the other subnet.

I bet, if I reboot it again, something else will not be reachable.

Further more, after upgrading the RB2011 on the far end I cannot get more then 25-30 Mbit TCP data across the wireless link, where normally I was getting 60 - 100 mbit TCP data. Yet, the bandwidth test I run from one router to the other across the wireless link I still get that 60 - 100 Mbit tcp data. But for some reason the same server that does nightly back ups can no longer get that higher data rate.
I will test with direct Ethernet, bypassing the RB 2011 and see if I get the speeds back to what they are supposed to be.

So 6.23 SUCKS!

I should point out that I could use winbox to MAC address, or telnet to MAC address for the two Netmetal 5's from the desktop that was wired to the CRS 24 port. I also looked to see that there was an ARP entry, ip/arp for the IP addresses of the Netmetal5's and they were present, so WHY cant it work with IP connectivity?

What's new in 6.23 (2014-Dec-04 14:46):

...
*) userman - fix more web session problems when user uses
...

Dear MikroTik support team,really userman problem not solves.
after upgrade even database is not accessable!
please solve this problem.

Hello Folks!

NTP problems has arrived.
We syncronize all RB against two NTP servers, that has been working for years.
Suddeny some time ago, RB backups started to arrive at different days and so on, hmmm..
Investigating that, we found that the clock was very much off in them and even they were days behind.

Looking at the SNTP Client, they got som strange Lat bad package from: <ip address of ntp server> and last bad package 00:00:17 ago, Last bad packet reason: kod-\0a\1e\00\06

Majority of the RB devices do no thave this issue, only a few has, the affected sit in different places in the network among with other RB devices in same LAN that do not have the problem.

Anyone who knows what this is about and how to fix/mitigate it ?

Upgraded a CCR1009 to 6.23 with a not so good result...

loading kernel from nand partition 0... OK
setting up elf image... OK
jumping to kernel code
Starting...
failed to open /dev/flash: No such file or directory
Generating SSH DSA key...
Starting services...

Demo license expired!
Please reinstall the router.

connect failed (errno=2)
connect failed (errno=2)
connect failed (errno=2)
connect failed (errno=2)
Client requested halt.

Is this related to 6.23 or is it a hardware failure, uptime before upgrade was aprox. 70 days. Tried netinstall 6.23 with no luck.

Best regards
Thomas