I agree, it is getting like children in a playground now.Why 99% of users just simple complain without simpliest help to developers?
1) make all config backup
2) update
3) if have some problems
- make supout.rif
- reset router
- restore config
- if (fail restore/or same problem) -> make second supout.rif
4) revert for working 5.xx 6.xx and restore config
5) Send supout.rif's to support@mikrotik.com and wait .......
This is more efficient then don't like/worse/disappointed/+1
+1+1+1Bug on this new interface.
Bridge filters with in/out interface simply "disappear" from winbox but still appears on console.
Normis, supout.rif is necessary to know this?
+1 No add static ARP entryIn my RB1100AHx2 with 500 pppoe connections, i´ve seen 2 times a big drop in the troughput in clients interface, after i reboot, everything back to normal.. some hours after when i changed a ARP entry, the same occours, reboot again.. back to normal.. i will downgrade to 6.7..
Bug tracking system is needed. 'nuff saif. E-mail with tickets is rather... old solution. Other users can't see my problem(s) and if they have it also, they could leave their observations on bug track. Atlassian Jira or something different and many problems could be gone.Why 99% of users just simple complain without simpliest help to developers?
1) make all config backup
2) update
3) if have some problems
- make supout.rif
- reset router
- restore config
- if (fail restore/or same problem) -> make second supout.rif
4) revert for working 5.xx 6.xx and restore config
5) Send supout.rif's to support@mikrotik.com and wait .......
This is more efficient then don't like/worse/disappointed/+1
+1Same problem here!I upgraded a rb2011uas-2HnD from 6.9 to 6.11 and now I can't connect my windows OVPN client to the ROS OVPN server anymore.
The log show: disconnected <TLS failed>
I've checked that the CA and intermediate CA have both a LT status, while the rb2011 cert has a KT status.
If I uncheck the 'require client certificate' in the OVPN server parameters the connection works, but that would defeat the purpose of having a cert authentication in the first place.
Ticket#2014031766000331
6.10 BUG: user-manager profile limitation can not add profile limitation on command line when default admin customer are renamed, because missing "owner=" parameter.
This bug is still present on last official 6.11.
the error are replicable:
install with netinstall 6.11 whit NO keep old configuration
routeros-mipsbe-6.11.npk
user-manager-6.11-mipsbe.npk
on a RB750UP with bios 3.13 [hardware no matter...]
onmissing the possibility to setCode: Select all/tool user-manager profile limitation add name=test2
parameterCode: Select allowner=notadmin
it suppose everytime the owner are "admin" only.
I paste the terminal output:[admin@MikroTik] > /tool user-manager profile limitation
[admin@MikroTik] /tool user-manager profile limitation> print
# NAME OWNER
[admin@MikroTik] /tool user-manager profile limitation> add name=test
[admin@MikroTik] /tool user-manager profile limitation> print
# NAME OWNER
0 test admin
[admin@MikroTik] /tool user-manager profile limitation> /tool user-manager customer
[admin@MikroTik] /tool user-manager customer> print
Flags: X - disabled
0 login="admin" password="" backup-allowed=yes time-zone=-00:00 permissions=owner signup-allowed=no paypal-allowed=no paypal-secure-response=no paypal-accept-pending=no
[admin@MikroTik] /tool user-manager customer> set 0 login=notadmin
[admin@MikroTik] /tool user-manager customer> print
Flags: X - disabled
0 login="notadmin" password="" backup-allowed=yes time-zone=-00:00 permissions=owner signup-allowed=no paypal-allowed=no paypal-secure-response=no paypal-accept-pending=no
[admin@MikroTik] /tool user-manager customer> /tool user-manager profile limitation
[admin@MikroTik] /tool user-manager profile limitation> print
# NAME OWNER
0 test notadmin
[admin@MikroTik] /tool user-manager profile limitation> add name=test2
failure: customer does not exist
[admin@MikroTik] /tool user-manager profile limitation>
[admin@MikroTik] /tool user-manager profile limitation>add name=test2 (!!!TAB key pressed!!!)
address-list comment copy-from download-limit group-name ip-pool rate-limit-... transfer-limit upload-limit uptime-limit
[admin@MikroTik] /tool user-manager profile limitation> add name=test2 owner=notadmin
expected end of command (line 1 column 16)
[admin@MikroTik] /tool user-manager profile limitation>
Good morning, after upgrade I see this - the select box is not full width in WinBox. It's normal or bug? I didn't see this in earlier versions.
+1OpenVPN server doesn't work. TLS failed appears in the log. Downgrade to 6.10
Great tip, thanks. But how is this preventing us from stumbling on regression bugs, which are the most often mentioned ones here? Too many of them. Which means MikroTik do not do any QA whatsoever and rely on the end-users to do the testing. I'm a SOHO user so it's fine with me but there are many who use MT in production and its not their duty to do MT's job.Why 99% of users just simple complain without simpliest help to developers?
1) make all config backup
2) update
3) if have some problems
- make supout.rif
- reset router
- restore config
- if (fail restore/or same problem) -> make second supout.rif
4) revert for working 5.xx 6.xx and restore config
5) Send supout.rif's to support@mikrotik.com and wait .......
This is more efficient then don't like/worse/disappointed/+1
Unfortunately 90% of issues posted here, are never reported to support, even if we ask for more info. Many issues are config problems and some issues are very specific to the config user has made in their device.I must admit it is difficult to know which Comments are actual Bugs confirmed by Mikrotik and which are not. Assuming users are reporting these things to Mikrotik in the proper way and not just posting here. Mikrotik have never posted an official Bug list. This feature would not only help us but stop a lot of negative posting which must be really be gut wrenching for the developers who work extremely hard and deserve a bit more credit for producing the worlds greatest routing OS. I will post a feature request for this. the more users that do the same the more chance Mikrotik will consider the idea
Ticket#2014031766000331Unfortunately 90% of issues posted here, are never reported to support, even if we ask for more info. Many issues are config problems and some issues are very specific to the config user has made in their device.I must admit it is difficult to know which Comments are actual Bugs confirmed by Mikrotik and which are not. Assuming users are reporting these things to Mikrotik in the proper way and not just posting here. Mikrotik have never posted an official Bug list. This feature would not only help us but stop a lot of negative posting which must be really be gut wrenching for the developers who work extremely hard and deserve a bit more credit for producing the worlds greatest routing OS. I will post a feature request for this. the more users that do the same the more chance Mikrotik will consider the idea
What problems do you have in v6.11?Seem to yes. And i think it will be good - skip all versions with a new PPP package and new features up to 6.18 at least. If You do not want be beta tester of Muikrotik, of course. We will have stable version in about a year with this style of development6.11 another version to skip?
This has been discussed. Most of the reports are not bugs. Bug tracker would quickly fill up with false reports and config problems, and cause panic among other users.E-mail with tickets is rather... old solution. Other users can't see my problem(s) and if they have it also, they could leave their observations on bug track. Atlassian Jira or something different and many problems could be gone.
SSTP problems were fixed in v6.9, it works fine in v6.11 also.What about the bug in SSTP (Mikrotik server, connecting from windows 7/8 client)? It simply stopped working in 6.8 and higher. I am still using 6.7.
http://forum.mikrotik.com/viewtopic.php?f=1&t=81644
Is the issue still there, or can somebody claim, it works again?
Thx
Some of the problems, with ticket already opened from 6.10:What problems do you have in v6.11?Seem to yes. And i think it will be good - skip all versions with a new PPP package and new features up to 6.18 at least. If You do not want be beta tester of Muikrotik, of course. We will have stable version in about a year with this style of development
Normis, and these are bugs?This has been discussed. Most of the reports are not bugs. Bug tracker would quickly fill up with false reports and config problems, and cause panic among other users.E-mail with tickets is rather... old solution. Other users can't see my problem(s) and if they have it also, they could leave their observations on bug track. Atlassian Jira or something different and many problems could be gone.
Cause more panic seeing old bug (with ticket) not solved, and continuosly discovering new, with new version.... cause panic among other users ...
This version was running on several hundred volunteer networks for more than a week, before we released it. The bugs that are found here only are apparent in very specific situations, and don't apply to everybody.MikroTik do not do any QA whatsoever and rely on the
Exactly, you have right, there is no problem in NTP packages, if you not put ntp client on CPE can obtain IP trough pppoe-client, tested on 6.8.....6.12... NTP package has not been changed (zero commits) for the last year at least. Please check if your NTP server is responding, or try a different NTP server. ...
How is possible this 6.8~6.10 bug (fixed from 6.11rc1 v4):This version was running on several hundred volunteer networks for more than a week, before we released it. The bugs that are found here only are apparent in very specific situations, and don't apply to everybody.MikroTik do not do any QA whatsoever and rely on the
There is a difference between running a software and testing the software. Testing implies focus on finding bugs and regressions in ALL subsystems. Running only slightly touches some of the subsystems. Your answer proves the point that MT is lacking in the QA dep. I hope this does not get deleted as wellThis version was running on several hundred volunteer networks for more than a week, before we released it. The bugs that are found here only are apparent in very specific situations, and don't apply to everybody.
I can assure you, all kinds of testing is done prior to release. You are still missing the point. Most of the posts here are not bugs.There is a difference between running a software and testing the software. Testing implies focus on finding bugs and regressions in ALL subsystems. Running only slightly touches some of the subsystems. Your answer proves the point that MT is lacking in the QA dep. I hope this does not get deleted as wellThis version was running on several hundred volunteer networks for more than a week, before we released it. The bugs that are found here only are apparent in very specific situations, and don't apply to everybody.
Best regards
PLEASE, now we must stop complain.There is a difference between running a software and testing the software. Testing implies focus on finding bugs and regressions in ALL subsystems. Running only slightly touches some of the subsystems. Your answer proves the point that MT is lacking in the QA dep. I hope this does not get deleted as wellThis version was running on several hundred volunteer networks for more than a week, before we released it. The bugs that are found here only are apparent in very specific situations, and don't apply to everybody.
Best regards
No, since I have not yet upgraded to 6.11. But OK, I will, so that I do not speak without facts. I can always revert to 6.10, right?Drank, do you have any issues in v6.11? Have you already emailed MikroTik support?
the problem is still present on 6.12 "alpha"
winbox on pc directly connected on ethernet on gateway
inside the gateway are a pppoe-server mppe encrypted with mrru 1614
remote cpe (over various other machine) are taking ip address from pppoe-client
the winbox link from pc to cpe freeze after some kb of traffic inbound from cpe to pc.
Must revert to 6.7 to disappear this bug.
(I hope your read my previous message for you)the problem is still present on 6.12 "alpha"
winbox on pc directly connected on ethernet on gateway
inside the gateway are a pppoe-server mppe encrypted with mrru 1614
remote cpe (over various other machine) are taking ip address from pppoe-client
the winbox link from pc to cpe freeze after some kb of traffic inbound from cpe to pc.
Must revert to 6.7 to disappear this bug.
Tell me your Support ticket number, I will check if there is any progress with your report
Normis, how can you do a supout of a router but omitting private information like password and keys? Not that I don't trust you, but it will go against our security policy. And I can't afford to have a spare unit of each single router to create a second config without sensitive info just to do a test for you and send a supout.
Unfortunately 90% of issues posted here, are never reported to support, even if we ask for more info. Many issues are config problems and some issues are very specific to the config user has made in their device.
passwords and keys are not included in these files. you can already check what the file contains if you log into your mikrotik.com account, and use the "supout.rif viewer" tool.Normis, how can you do a supout of a router but omitting private information like password and keys? Not that I don't trust you, but it will go against our security policy. And I can't afford to have a spare unit of each single router to create a second config without sensitive info just to do a test for you and send a supout.
Unfortunately 90% of issues posted here, are never reported to support, even if we ask for more info. Many issues are config problems and some issues are very specific to the config user has made in their device.
Disable encryption over pppoe-client (with no MRRU, MRRU=1600 or MRRU=1614 not matter) solve the problem.the problem is still present on 6.12 "alpha"
winbox on pc directly connected on ethernet on gateway
inside the gateway are a pppoe-server mppe encrypted with mrru 1614
remote cpe (over various other machine) are taking ip address from pppoe-client
the winbox link from pc to cpe freeze after some kb of traffic inbound from cpe to pc.
Must revert to 6.7 for make disappear this bug.
I get continuosly kernel failure and routerboard reboot with this configuration:"Winbox connection freeze after some kb received over mppe encrypted connection"
RouterOS version affected: all from 6.8, 6.9, 6.10, 6.11, 6.12 (2014/03/24)
From 6.10 the problem go worst.
/interface eoip add keepalive=10 local-address=192.168.3.1 mac-address=02:AE:6D:55:61:E2 name=eoip-tunnel1 remote-address=192.168.3.2 tunnel-id=666 /interface bridge settings set use-ip-firewall=yes /interface pppoe-server server add authentication=mschap2 default-profile=default-encryption disabled=no interface=eoip-tunnel1 mrru=1614 service-name=service1 /ip address add address=192.168.2.1/24 interface=ether13 network=192.168.2.0 add address=192.168.3.1/24 interface=ether2 network=192.168.3.0 /ip firewall connection tracking set enabled=yes /ppp secret add local-address=10.0.0.1 name=test password=test profile=default-encryption remote-address=10.0.0.2 /system identity set name="Test Gateway"paste this on RB951G-2HnD terminal
/interface eoip add keepalive=10 local-address=192.168.3.2 mac-address=02:08:2C:28:55:D6 name=eoip-tunnel1 remote-address=192.168.3.1 tunnel-id=666 /interface pppoe-client add ac-name="" add-default-route=yes allow=mschap2 default-route-distance=1 dial-on-demand=no disabled=no interface=eoip-tunnel1 keepalive-timeout=60 max-mru=1480 max-mtu=1480 mrru=1614 name=pppoe-out1 password=test profile=default-encryption \ service-name="" use-peer-dns=yes user=test /interface bridge settings set use-ip-firewall=yes /ip address add address=192.168.3.2/24 interface=ether2 network=192.168.3.0 /ip firewall connection tracking set enabled=yes /system identity set name="Test CPE"When you open with winbox 10.0.0.2 [after 1 hour, or 1 minutes are equal]
[admin@Test Gateway] /file> Oops: Exception in kernel mode, sig: 5 [#1]
SMP NR_CPUS=2 RB1120
NIP: 8021a730 LR: 8021a46c CTR: 00000000
REGS: dffefd30 TRAP: 0700 Not tainted (3.3.5-smp)
MSR: 00029000 <CE,EE,ME> CR: 42000028 XER: 20000000
TASK = 8036d3c0[0] 'swapper/0' THREAD: 80380000 CPU: 0
GPR00: 8021a46c dffefde0 8036d3c0 fffffff2 de6f58aa 00000001 de6f4e50 dc870cd2
GPR08: 120ff29a 0000001d 00000000 8021a400 42000022 00000001 dd9fc300 00000012
GPR16: 00000003 00000000 e1811a40 000005e2 de6dd414 e1811a2c e18119c8 e18119ec
GPR24: 00000012 e1811828 de6dd484 0000003b 000000fd dd9fc300 dd9fc300 de6dd3c0
NIP [8021a730] __pskb_pull_tail+0x330/0x340
LR [8021a46c] __pskb_pull_tail+0x6c/0x340
Call Trace:
[dffefde0] [8021a46c] __pskb_pull_tail+0x6c/0x340 (unreliable)
[dffefe00] [e180df30] ppp_register_channel+0xb20/0x1b4c [ppp_generic@0xe180c000]
[dffefe30] [e180f8d4] ppp_output_wakeup+0x978/0xa20 [ppp_generic@0xe180c000]
[dffefe90] [e180fb30] ppp_input+0xf0/0x12a4 [ppp_generic@0xe180c000]
[dffefeb0] [e18494d0] 0xe18494d0 [pppoe@0xe1849000]
[dffefed0] [80221f9c] __netif_receive_skb+0x220/0x400
[dffeff30] [802224a0] process_backlog+0xac/0x178
[dffeff60] [80223870] net_rx_action+0xc0/0x170
[dffeffa0] [80031a14] __do_softirq+0xf4/0x178
[dffefff0] [8000c054] call_do_softirq+0x14/0x24
[80381e80] [80003f5c] do_softirq+0x98/0xc4
[80381ea0] [80031d84] irq_exit+0xa0/0xd4
[80381eb0] [80003c44] do_IRQ+0x94/0x190
[80381ee0] [8000d71c] ret_from_except+0x0/0x18
--- Exception: 501 at cpu_idle+0x8c/0xe0
LR = cpu_idle+0x8c/0xe0
[80381fc0] [8034076c] start_kernel+0x2d4/0x2e8
[80381ff0] [800003f8] skpinv+0x2e4/0x320
Instruction dump:
7fdcf378 3b400000 4bffffa0 7fc3f378 7c84f850 4bfffced 2f830000 409eff9c
7f43d378 4bffe9c9 38600000 4bffff00 <0fe00000> 38c00001 7cc903a6 4bfffd90
---[ end trace 72421d3cf3d534d4 ]---
Kernel panic - not syncing: Fatal exception in interrupt
panicSaver: dumping panic to flash
flash: erase 10
flash: prg 10
flash: prg err 0
Rebooting in 1 seconds..
------------[ cut here ]------------
Kernel BUG at 800a3a70 [verbose debug info unavailable]
Oops: Exception in kernel mode, sig: 5 [#2]
SMP NR_CPUS=2 RB1120
NIP: 800a3a70 LR: 800113ec CTR: 00000000
REGS: dffefa60 TRAP: 0700 Tainted: G D (3.3.5-smp)
MSR: 00021000 <CE,ME> CR: 22000024 XER: 20000000
TASK = 8036d3c0[0] 'swapper/0' THREAD: 80380000 CPU: 0
GPR00: 800113ec dffefb10 8036d3c0 00001000 00000001 00000001 e1000000 edffc000
GPR08: 000000d0 80017554 00000300 fffffffd 22000024 00000001 dd9fc300 00000012
GPR16: 00000003 00000000 e1811a40 000005e2 de6dd414 e1811a2c e18119c8 e18119ec
GPR24: 80017554 80380000 e1000000 edffc000 000000d0 00000001 00000001 80017554
NIP [800a3a70] __get_vm_area_node.isra.31+0x34/0x180
LR [800113ec] __ioremap_caller+0x170/0x1a4
Call Trace:
[dffefb10] [e137c43c] flash_fixed_cmd+0x140/0x204 [flash@0xe137b000] (unreliable
)
[dffefb40] [800113ec] __ioremap_caller+0x170/0x1a4
[dffefb70] [80017554] rb1120_restart+0x68/0xa4
[dffefb90] [8000b35c] machine_restart+0x48/0x60
[dffefbb0] [802ad3b0] panic+0x198/0x1e8
[dffefc00] [800096b4] die+0x244/0x284
[dffefc30] [8000984c] _exception+0x100/0x114
[dffefd20] [8000d6d0] ret_from_except_full+0x0/0x4c
--- Exception: 700 at __pskb_pull_tail+0x330/0x340
LR = __pskb_pull_tail+0x6c/0x340
[dffefe00] [e180df30] ppp_register_channel+0xb20/0x1b4c [ppp_generic@0xe180c000]
[dffefe30] [e180f8d4] ppp_output_wakeup+0x978/0xa20 [ppp_generic@0xe180c000]
[dffefe90] [e180fb30] ppp_input+0xf0/0x12a4 [ppp_generic@0xe180c000]
[dffefeb0] [e18494d0] 0xe18494d0 [pppoe@0xe1849000]
[dffefed0] [80221f9c] __netif_receive_skb+0x220/0x400
[dffeff30] [802224a0] process_backlog+0xac/0x178
[dffeff60] [80223870] net_rx_action+0xc0/0x170
[dffeffa0] [80031a14] __do_softirq+0xf4/0x178
[dffefff0] [8000c054] call_do_softirq+0x14/0x24
[80381e80] [80003f5c] do_softirq+0x98/0xc4
[80381ea0] [80031d84] irq_exit+0xa0/0xd4
[80381eb0] [80003c44] do_IRQ+0x94/0x190
[80381ee0] [8000d71c] ret_from_except+0x0/0x18
--- Exception: 501 at cpu_idle+0x8c/0xe0
LR = cpu_idle+0x8c/0xe0
[80381fc0] [8034076c] start_kernel+0x2d4/0x2e8
[80381ff0] [800003f8] skpinv+0x2e4/0x320
Instruction dump:
9421ffd0 bf010010 542a0024 90010034 7c9d2378 7cbe2b78 7cda3378 814a000c
7cfb3b78 7d1c4378 7d384b78 554a016e <0f0a0000> 70a90001 41820018 7c690034
---[ end trace 72421d3cf3d534d5 ]---
http://forum.mikrotik.com/posting.php?mode=smilies&f=1#
Normis, Your upgrade version 6.11 Truly BIG PROBLEM with Hotspot Features
nOw back to 6.10
Please check it my support it
Tq
and also write (to support) what problem you have encountered, not limited to "nOw back to 6.10".http://forum.mikrotik.com/posting.php?mode=smilies&f=1#
Normis, Your upgrade version 6.11 Truly BIG PROBLEM with Hotspot Features
nOw back to 6.10
Please check it my support it
Tq
YOU MUST WRITE AND SEND AUTOSUPOUT TO support@mikrotik.com
For example - [Ticket#2014021466000802] - Permanent disconnections from Winbox via tunnels and non stable tunnels. This problem is actual for all versions newer than 6.7. My beautiful RB1100AHx2 works in far datacenter and i already afraid to install updates of ROS. I tried to update up to 6.9 and 6.10 - but every time was forced to downgrade to 6.7.What problems do you have in v6.11?
Seem to yes. And i think it will be good - skip all versions with a new PPP package and new features up to 6.18 at least. If You do not want be beta tester of Muikrotik, of course. We will have stable version in about a year with this style of development
Just for the records to stick to the topic: SSTP is broken again, no connection from 6.11/6.10 (client) to 6.11 (server); just getting "internal error (6)"SSTP problems were fixed in v6.9, it works fine in v6.11 also.
Do not bring back 2009 post, when the solution are already written inside.Please take a look to this http://forum.mikrotik.com/viewtopic.php ... 50#p417350
(original reply message adapted from 2009 to 2014)To get support for the card, you have to write e-mail to support, where you should send supout.rif file, where 6.11 version is installed and card is plugged in. Support e-mail is support@mikrotik.com
Is a new feature from 6.5 to report the traffic,I upgraded my RB2011UAS-2HnD from 6.0 to 6.11. All works ok, though I also see the Winbox formatting problem that everyone else reports.
I do observe one strange thing: I have some Ethernet switch ports that are slaves to other masters. In all cases after upgrading traffic is being shown on the slave ports rather than the master ports (unless there is active Ethernet activity on the master port). Is this a change? I thought that previously no traffic was reported on the slave ports. Can I be sure that even though traffic is being reported on the slave ports that LAN traffic between two switch ports is not going through the router's CPU?
remember to update also the firmware!!!*) ethernet interface stats that are behind switch chip
show real hw stats instead of just the traffic that goes through cpu;
Normis other tech companies I have dealt with professionally have bug tracking systems that are open to anyone (Cisco to name one). The bugs are not submitted by end users but by the development teams or other authorized individuals at the company. They are then referenced by tech support when looking for issues. Not all bugs are immediately publicly viewable. Once a bug has been fully confirmed and understood by the dev team the bug is opened up to the public. The bug record contains workaround instructions if available, version numbers affected, and versions that the bug is fixed in. I don't know that anyone is expecting user submitted bugs in a bug tracker like say an opensource project does. Typically those systems are also doubling as a issue tracker.This has been discussed. Most of the reports are not bugs. Bug tracker would quickly fill up with false reports and config problems, and cause panic among other users.E-mail with tickets is rather... old solution. Other users can't see my problem(s) and if they have it also, they could leave their observations on bug track. Atlassian Jira or something different and many problems could be gone.
+1Normis other tech companies I have dealt with professionally have bug tracking systems that are open to anyone (Cisco to name one). The bugs are not submitted by end users but by the development teams or other authorized individuals at the company. They are then referenced by tech support when looking for issues. Not all bugs are immediately publicly viewable. Once a bug has been fully confirmed and understood by the dev team the bug is opened up to the public. The bug record contains workaround instructions if available, version numbers affected, and versions that the bug is fixed in. I don't know that anyone is expecting user submitted bugs in a bug tracker like say an opensource project does. Typically those systems are also doubling as a issue tracker.
Folks just want straight forward answers about bugs that do exist so they can be worked around in their environment. When the limitations of the device or the software version that is being deployed are known it gives a lot more confidence in deploying it. If there are a lot of unknown issues or stigma attached to a version its hard to want to deploy it. A publicly viewable bug tracker is as much about managing expectations and rumors as it is about reducing support calls. It also builds trust in the company and their products.
+1+1Normis other tech companies I have dealt with professionally have bug tracking systems that are open to anyone (Cisco to name one). The bugs are not submitted by end users but by the development teams or other authorized individuals at the company. They are then referenced by tech support when looking for issues. Not all bugs are immediately publicly viewable. Once a bug has been fully confirmed and understood by the dev team the bug is opened up to the public. The bug record contains workaround instructions if available, version numbers affected, and versions that the bug is fixed in. I don't know that anyone is expecting user submitted bugs in a bug tracker like say an opensource project does. Typically those systems are also doubling as a issue tracker.
Folks just want straight forward answers about bugs that do exist so they can be worked around in their environment. When the limitations of the device or the software version that is being deployed are known it gives a lot more confidence in deploying it. If there are a lot of unknown issues or stigma attached to a version its hard to want to deploy it. A publicly viewable bug tracker is as much about managing expectations and rumors as it is about reducing support calls. It also builds trust in the company and their products.
All of our hardware support COA, but not RouterOS. No new features, only bugs with new versions.Yes.Still no COA in PPP...
Even new ppp package.
1) I confirm the bug, I must write how to replicate the problem and send to support@mikrotik.comAnyone can confirm this bug:
1. Not very important, upgrade to 6.11 Groove, SxLite, RB711, lost default LED indication for wireless signal strength. On RB411 try to add new LED, LED appears as unknown closing, open again new led windows in WinBox help to back to normal.
2. Before last couple version have problem with OpenVPN in bridge configuration, no problem with connection. Network is bridged connect to OpenVPN also bridge configuration have access to all device in bridge network but can't access device where is OpenVPN server, other device in network is accessible. But connect to other device in network can connect to MT where is OpenVPN server check bridge and OpenVPN client is in the bridge. This is on x86 tested again on RB433GL also 6.11 some thing happens.
Any one see this problem.
Of course send supout to support waiting answer.
+1Anyone can confirm this bug:
2. Before last couple version have problem with OpenVPN in bridge configuration, no problem with connection. Network is bridged connect to OpenVPN also bridge configuration have access to all device in bridge network but can't access device where is OpenVPN server, other device in network is accessible. But connect to other device in network can connect to MT where is OpenVPN server check bridge and OpenVPN client is in the bridge. This is on x86 tested again on RB433GL also 6.11 some thing happens.
Any one see this problem.
Of course send supout to support waiting answer.
In 6.10 openvpn dont work good, 6.11 work very good but only one day, now i have this error.What's new in 6.11 (2014-Mar-20 09:16):
*) ipsec - fix aes-cbc hardware acceleration on CCR with key sizes 192 and 256;
*) wireless - add auto frequency feature;
*) ovpn - fixed TLS renegotiation;
*) ovpn - make bridge mode work with big packets (do not leave extraneous padding);
*) ovpn - fixed require-client-certifcate;
*) ppp - revert RADIUS NAS-Port behaviour, report tunnel interface id;
*) ppp - mppe encryption together with mrru locked the router;
*) dhcp - added support for DHCP option 138 - list of CAPWAP IPv4 servers;
*) quickset - added Guest Network setup to Home AP mode;
*) console - no longer required to supply value of '/routing bgp instance vrf'
property 'instance' for 'add' command;
*) ethernet - added option to enable rx/tx flow control
(will be disabled by default);
*) ethernet - added ability to specify advertised modes for copper ports;
*) fixed 100% cpu usage on CCRs;
*) ssl - not finding CRL in local store for any certificate in trust chain will cause connection to fail;
*) lte - support for Huawei ME609 and ME909u-521;
+1Normis other tech companies I have dealt with professionally have bug tracking systems that are open to anyone (Cisco to name one). The bugs are not submitted by end users but by the development teams or other authorized individuals at the company. They are then referenced by tech support when looking for issues. Not all bugs are immediately publicly viewable. Once a bug has been fully confirmed and understood by the dev team the bug is opened up to the public. The bug record contains workaround instructions if available, version numbers affected, and versions that the bug is fixed in. I don't know that anyone is expecting user submitted bugs in a bug tracker like say an opensource project does. Typically those systems are also doubling as a issue tracker.This has been discussed. Most of the reports are not bugs. Bug tracker would quickly fill up with false reports and config problems, and cause panic among other users.E-mail with tickets is rather... old solution. Other users can't see my problem(s) and if they have it also, they could leave their observations on bug track. Atlassian Jira or something different and many problems could be gone.
Folks just want straight forward answers about bugs that do exist so they can be worked around in their environment. When the limitations of the device or the software version that is being deployed are known it gives a lot more confidence in deploying it. If there are a lot of unknown issues or stigma attached to a version its hard to want to deploy it. A publicly viewable bug tracker is as much about managing expectations and rumors as it is about reducing support calls. It also builds trust in the company and their products.
Same hereGood morning, after upgrade I see this - the select box is not full width in WinBox. It's normal or bug? I didn't see this in earlier versions.
Can you share more about " fixed 100% cpu usage on CCRs", what had been fixed, and what is the problem that related?If you are already running a RouterOS 6 install, Simply click “Check for updates” in QuickSet, Webfig or Winbox packages menu.
Available separately, is a new Wireless-FP package, which includes the new CAPsMAN feature. This is a beta package, so use only in controlled test networks. The package will replace your default Wireless package upon installation, which means it will also add wireless functionality changes and improvements, not only CAPsMAN. More information about the Wireless Controller (CAPsMAN) is here: http://wiki.mikrotik.com/wiki/Manual:CAPsMANWhat's new in 6.11 (2014-Mar-20 09:16):
*) ipsec - fix aes-cbc hardware acceleration on CCR with key sizes 192 and 256;
*) wireless - add auto frequency feature;
*) ovpn - fixed TLS renegotiation;
*) ovpn - make bridge mode work with big packets (do not leave extraneous padding);
*) ovpn - fixed require-client-certifcate;
*) ppp - revert RADIUS NAS-Port behaviour, report tunnel interface id;
*) ppp - mppe encryption together with mrru locked the router;
*) dhcp - added support for DHCP option 138 - list of CAPWAP IPv4 servers;
*) quickset - added Guest Network setup to Home AP mode;
*) console - no longer required to supply value of '/routing bgp instance vrf'
property 'instance' for 'add' command;
*) ethernet - added option to enable rx/tx flow control
(will be disabled by default);
*) ethernet - added ability to specify advertised modes for copper ports;
*) fixed 100% cpu usage on CCRs;
*) ssl - not finding CRL in local store for any certificate in trust chain will cause connection to fail;
*) lte - support for Huawei ME609 and ME909u-521;
I don't remember exactly what versions, but all experienced in 6.xCan you please name a few ?I have never seen MT release such bad firmware in the past. There are a LOT of unacceptable bugs in 6
Just a quick update on this...A SSTP tunnel that I have between two Mikrotik routers broke after the upgrade to 6.11.
It is configured so that the client verifies the server certificate and the server verifies the client certificate.
The certificate and server certificate derive from the same root. The root is one that I generated.
I suspect that it is this that has caused the issue somehow:
*) ssl - not finding CRL in local store for any certificate in trust chain will cause connection to fail.
If there is no CRL defined on a certificate in the trust chain, does this still cause connections to fail? If so, I assume this would be a new bug.
(Having disabled certificate validation at both ends, the tunnel is established successfully.)
voxframeSimple message - You guys need to improve your bug ticket handling, and spend more time testing before allowing firmware to be released. Perhaps a "pre-release" and "stable" branch with proper known issues being listed? This was different when you were "a small company" building small boards. Now you call yourselves "enterprise" and "carrier"... It's time to behave like it!
Well said!Simple message - You guys need to improve your bug ticket handling, and spend more time testing before allowing firmware to be released. Perhaps a "pre-release" and "stable" branch with proper known issues being listed? This was different when you were "a small company" building small boards. Now you call yourselves "enterprise" and "carrier"... It's time to behave like it!
Normis, if this is a bickering then this does not do you any good. If not then again, why ask? You must know all your bugs and not ask you customers to provide the list.Can you please name a few ?
+1Normis, if this is a bickering then this does not do you any good. If not then again, why ask? You must know all your bugs and not ask you customers to provide the list.Can you please name a few ?
It is obvious that you try to deny the existence of some bugs. It is also obvious that your customers are sure that there are bugs. Deploying a bug tracking system, with access to customers, will clear all this confusion. Continuing to deny that there are indeed bugs will not convince anybody here.
Think about it in this way - even if you're right and these are not bugs then MT failed to pass the message to the customers (obviously). This calls for some corrective actions from MT to fix the things. How do you intend to fix all this growing confusion and dissatisfaction with the quality of the releases and the QA process? Nobody says you're doing everything wrong. But that does not mean you're guaranteed you're doing it right. Sometimes it is better to admit, correct and continue.
Wish you all the best and thank you for trying to improve.
/interface wireless set 0 frequency=auto channel-width=20/40mhz-ht-below
interface wireless monitor 0
status: running-ap
band: 2ghz-n
frequency: 2412MHz
wireless-protocol: 802.11
I think I have similar problem! After half or few days router became not accessible from network and only hard reboot can help. How to view LOG at that moment I don't know... but after reboot I see string like "unexpected reboot" in the LOG.Upgraded RB951-2n from 6.10 to 6.11
Bridge network and wlan1 interface disappears.
reboot and it works normal. after a few minutes it disappears.
If you look at the download link to the current version, it provides a clue to the older versions.I think I have similar problem! After half or few days router became not accessible from network and only hard reboot can help. How to view LOG at that moment I don't know... but after reboot I see string like "unexpected reboot" in the LOG.Upgraded RB951-2n from 6.10 to 6.11
Bridge network and wlan1 interface disappears.
reboot and it works normal. after a few minutes it disappears.
Somebody tell me where to download v6.10 for downgrading?
http://download2.mikrotik.com/routeros/6.11/routeros-mipsbe-6.11.npk
There's the API protocol you know.I am writing a lot of software to automate various tasks, and I am getting crazy with lots of regexps to parse the "print terse" outputs.
Is it possible to implement a "print json" ?
Going to HTTP facebook will automatically redirect you to HTTPS facebook.Does anyone able to use the routing mark + the "Content" field working correctly ?
As soon as I add anything inside the field "Content", the connection will timeout . For example, if I type in "facebook" in the Content field, it supposed to mark the route if I go to http://www.facebook.com . And then eventually route to a VPN connection. However, the connection would time out as soon as I go to http://www.facebook.com.
However, if I take out the "Content" field and make it to mark the route unconditionally, when I go to http://www.facebook.com, it will route to the VPN correctly.
Therefore, it seems adding a condition will break the routing mark.
It doesn't matter what value you set in Content, it will time out. You can try to set "whatismyipaddress" to Content, and then try to go to whatismyipaddress.com. It will timeout.Going to HTTP facebook will automatically redirect you to HTTPS facebook.Does anyone able to use the routing mark + the "Content" field working correctly ?
As soon as I add anything inside the field "Content", the connection will timeout . For example, if I type in "facebook" in the Content field, it supposed to mark the route if I go to http://www.facebook.com . And then eventually route to a VPN connection. However, the connection would time out as soon as I go to http://www.facebook.com.
However, if I take out the "Content" field and make it to mark the route unconditionally, when I go to http://www.facebook.com, it will route to the VPN correctly.
Therefore, it seems adding a condition will break the routing mark.
Since its HTTPS, the router cant read the packet content (its encrypted), and therefore will NOT find "facebook" in the content, and not route the connection over the VPN.
I am trying accessing this using Ruby and OpenSSL. All connection methods fail, except for SSLv2 which just hangs and doesn't allow me to proceed. Should this be considered a bug?Added support for API over TLS (SSL) from 6.1:
see on IP / Services / api-ssl
I think the "Content" field is pretty reliable to reproduce even at v6.7 (the only known version work with routing mark). I just make a quick record here http://youtu.be/I5hLiX1sic8For those had issues with routing marks,
i ve seen the issue after upgrading from 6.7 to 6.9,i guess the same happened with 6.10 and 6.11
I was not able to reproduce and show to mikrotik,
Although a possible fix(not 100% if that fixed the issue) is to downgrade to 5.26 and upgrade back to latest version
Regarding eoip and bridge interfaces disappearing as somebody said above, it happened on 6.10,
i was able to fix it with same solution(downgrade to 5.26 and upgrade to latest)
hope it helps...
Caught a log output screenshot when it bombed. And yes, I sent the autosupout.rif as well as a supout.rif to mikrotik. I haven't heard anything back, yet, and I'm not sure I will.Posting here, so that others can know about it.
I just read through the entire thread, and I'm not certain if others are having the same problem I am. I have an RB800, and it's started crashing and rebooting for me at random times. Once while I was in the webUI, wondering why the CPU graph was spiking. The WebUI crawled to a halt, and I heard the watchdog beep as it rebooted the thing.
The HTTPS connection begins with server certificate transfer to the client. This phase is not encrypted so the router can see what is in the certificate body and there are server names:Going to HTTP facebook will automatically redirect you to HTTPS facebook.Does anyone able to use the routing mark + the "Content" field working correctly ?
As soon as I add anything inside the field "Content", the connection will timeout . For example, if I type in "facebook" in the Content field, it supposed to mark the route if I go to http://www.facebook.com . And then eventually route to a VPN connection. However, the connection would time out as soon as I go to http://www.facebook.com.
However, if I take out the "Content" field and make it to mark the route unconditionally, when I go to http://www.facebook.com, it will route to the VPN correctly.
Therefore, it seems adding a condition will break the routing mark.
Since its HTTPS, the router cant read the packet content (its encrypted), and therefore will NOT find "facebook" in the content, and not route the connection over the VPN.
0x0340: 3058 820e 2a2e 7879 2e66 6263 646e 2e6e 0X..*.xy.fbcdn.n
0x0350: 6574 820e 2a2e 7878 2e66 6263 646e 2e6e et..*.xx.fbcdn.n
0x0360: 6574 820b 2a2e 6662 7362 782e 636f 6d82 et..*.fbsbx.com.
0x0370: 0c66 6163 6562 6f6f 6b2e 636f 6d82 0b2a .facebook.com..*
0x0380: 2e66 6263 646e 2e6e 6574 820e 2a2e 6661 .fbcdn.net..*.fa
0x0390: 6365 626f 6f6b 2e63 6f6d 3009 0603 551d cebook.com0...U.
radius monitor numbers=0
pending: 0
requests: 0
accepts: 0
rejects: 0
resends: 0
timeouts: 0
bad-replies: 0
last-request-rtt: 0ms
I have a problem with high CPU usage too - but only when I am connected by WinBox. Profiler says non-senses - sometimes flash, sometimes spi process. It is happening on various routers (mipsbe and powerpc) like RB750G, RB493G, RB1200.Suddenly my cpu was up to 100%, latest actions used was 'ip-arp make static' and 'torch'. Also my logging usb flash was reseted do not know if this was before or after that high cpu usage.Profile was showing 'management' as eating the hole cpu, i was not able to generate any supout file due to this high cpu usage.. latest ros 6.11 mipsbe
Depends on what you use it for. For me I have 6.5, because 6.7 still has DHCP server on VLAN issue.What's the latest stable version for CCR? I need to move from 6.3 (pretty stable). It looks like 6.7 is the next stop?
With the new wireless-fp package the the driver will have that feature.Code: Select all/interface wireless set 0 frequency=auto channel-width=20/40mhz-ht-below interface wireless monitor 0 status: running-ap band: 2ghz-n frequency: 2412MHz wireless-protocol: 802.11
This puts the ht below and computers have issues connecting.
Can we get channel-width=20/40mhz-ht-auto?
http://forum.mikrotik.com/viewtopic.php ... 88#p416454Ticket#2014031766000331
6.10 BUG: user-manager profile limitation can not add profile limitation on command line when default admin customer are renamed, because missing "owner=" parameter.
This bug is still present on last official 6.11.
Am not sure if the problem was NV2. After changing the wireless protocol to 802.11, it started workingHas anyone tried the CAPsMan over wireless link. The CAP is connecting to the CAPsManager via NV2 radio using layer 3. The CAP get registered to the CAPsManager and 802.11b/g client are registered on the CAPsManager. The forwarding mode is enabled and datapath is a bridge with no physical interface on the bridge port and has a DHCP server. The 802.11b/g client is able to obtain an IP address after associating but cannot ping the IP on the bridge interface (Datapath).
However if the CAP is connected via wire to the CAPsManager it works flawlessly.
Thank's god.. I have unused RB450G with old ROS 5.26, on which I have set up DHCP for all VLAN's over single cable.server4 offering lease x.x.x.x for AA:BB:CC:DD:EE:FF without success
Thank's god.. I have unused RB450G with old ROS 5.26, on which I have set up DHCP for all VLAN's over single cable.server4 offering lease x.x.x.x for AA:BB:CC:DD:EE:FF without success
Its not NV2 because it stopped pinging after rebooting. I think the CAPsMan does not work over wireless link.Am not sure if the problem was NV2. After changing the wireless protocol to 802.11, it started workingHas anyone tried the CAPsMan over wireless link. The CAP is connecting to the CAPsManager via NV2 radio using layer 3. The CAP get registered to the CAPsManager and 802.11b/g client are registered on the CAPsManager. The forwarding mode is enabled and datapath is a bridge with no physical interface on the bridge port and has a DHCP server. The 802.11b/g client is able to obtain an IP address after associating but cannot ping the IP on the bridge interface (Datapath).
However if the CAP is connected via wire to the CAPsManager it works flawlessly.
What's the latest stable version for CCR? I need to move from 6.3 (pretty stable). It looks like 6.7 is the next stop?
Hi!
I have a problems after upgrade on v6.11 on my RB751U-2HnD (firmware: v3.13):
Device just freeze every 3-4 hours - it`s very bad for my work. I do power of and on. Later i set IP adress in "watchdog" tab, and device reboot automaticaly and works fine 3-4 hours and history repeat.
I aways updgrade new version in this device when new release at soon, and i never not have problem. Whats wrong?
...But another my device RB751U-2HnD, and more different models works fine, but hes is works with a most simple configuration
Of cause? I don`t imagine my work without MikroTik! Perfectly product line!
Sorry for my Eng..
Thanks!
Still exist on 6.12rc1 (2014-Apr-07 09:04):http://forum.mikrotik.com/viewtopic.php ... 88#p416454Ticket#2014031766000331
6.10 BUG: user-manager profile limitation can not add profile limitation on command line when default admin customer are renamed, because missing "owner=" parameter.
This bug is still present on last official 6.11.
Still exist on 6.12rc1 2014-04-02
I try the other 2 bug I have discovered later
/ping 217.67.x.y
HOST SIZE TTL TIME STATUS
105 (No buffer space...
105 (No buffer space...
105 (No buffer space...
105 (No buffer space...
sent=4 received=0 packet-loss=100%
/ping arp-ping=yes address=217.67.x.y interface=ether1
HOST SIZE TTL TIME STATUS
00:0C:CF:FC:58:1A 0ms
00:0C:CF:FC:58:1A 0ms
sent=7 received=7 packet-loss=0% min-rtt=0ms avg-rtt=0ms max-rtt=0ms
I've been sending supout files in relation to no buffer space errors. Unfortunatly I did not get a response to my e-mails. Could you please look at 2013050666000323 if my issues is the same issue?no buffer space is related to L2TP. If you have L2TP configured then this problem will be fixed in v6.12.
This was never supported on RB1100 due to specific file system on RB1100. It was not showing on previous versions toodocmarius, I confirm.
On my RB1100AHx2 after upgrade to 6.11:
Both Sector Writes Since Reboot and Total Sector Writes: 0
Thanks, I have sure now about that release have got fix on this problem. I plan upgrade to this v6.12rc1 asap.no buffer space is related to L2TP. If you have L2TP configured then this problem will be fixed in v6.12.
Same. So disgusted with MK right now! It's not like we can easily drive to our customer sites.im have troubles with bridges - bridge become unknown, reboot fix problem....
where download link 6.12 is already fixed????
try this pre-release issue (not final, some issues with tunnels not completely fixed):Same. So disgusted with MK right now! It's not like we can easily drive to our customer sites.im have troubles with bridges - bridge become unknown, reboot fix problem....
where download link 6.12 is already fixed????
What are the risks of downgrading while not having someone out onsite? I hate to say it Normunds, but were at the point of not knowing which versions are truly the stable ones... We've got about 20% of routers coming back because of this exact issue with 6.11. I think Mikrotik is taking on too much between CAPSman, wireless, new products, etc. I think its time to slow down and start focusing on what needs to be fixed rather than launching a continual of products with bugs.try this pre-release issue (not final, some issues with tunnels not completely fixed):Same. So disgusted with MK right now! It's not like we can easily drive to our customer sites.im have troubles with bridges - bridge become unknown, reboot fix problem....
where download link 6.12 is already fixed????
CCR http://www.mikrotik.com/download/share/ ... e-6.12.npk
PPC: http://www.mikrotik.com/download/share/ ... c-6.12.npk
MIPS BE: http://www.mikrotik.com/download/share/ ... e-6.12.npk
The entirety of V6 seems to be botched with no end in sight.After reading this lengthily tread several times I'll guess we can consider 6.10 to be the last stable version for now....
Glad I didn't use the auto upgrade function. My whole network (with almost every type of rb's, vlan's, dhcp servers (over vlan), bridged and static routes) runs .10 now, some since it came out. No issues so far.
I have one cpe running 6.11. I'll guess that's as far as I'll have it penetrate my network...
See what .12 might bring us....
For the impatience among us, don't bother if MT is not answering your support request or any answers on this tread. The amount of reported bugs/problems is at such a scale they are obviously working hard to find out what went where and why and how wrong to correct them asap in a new release... be patient and keep the good spirit!
In V5 everything was fixed in 5.26, so in V6 we are not even in half way....The entirety of V6 seems to be botched with no end in sight.
STILL EXIST ON 6.12 (2014-Apr-14)Still exist on 6.12rc1 (2014-Apr-07 09:04):Still exist on 6.12rc1 2014-04-02Ticket#2014031766000331
6.10 BUG: user-manager profile limitation can not add profile limitation on command line when default admin customer are renamed, because missing "owner=" parameter.
This bug is still present on last official 6.11.
I try the other 2 bug I have discovered later
sure?no buffer space is related to L2TP. If you have L2TP configured then this problem will be fixed in v6.12.
[Ticket#2014032566001217]
BUG 6.12: Replicable kernel crash when try to discover why winbox not working well from 6.8 over IP obtained from pppoe-client
Hi,
when I try to replicate this problem:
I get continuosly kernel failure and routerboard reboot with this configuration:"Winbox connection freeze after some kb received over mppe encrypted connection"
RouterOS version affected: all from 6.8, 6.9, 6.10, 6.11, 6.12 (2014/03/24)
From 6.10 the problem go worst.
For this example I use one RB1100AHx2 and one RB951G-2HnD,
netinstalled with ***NO*** Keep old configuration and routeros-powerpc-6.12.npk / routeros-mipsbe-6.12.npk
both have last 3.10 / 3.12 bios.
The connection maded with ethernet cable are:
PC -> PoE - > ether13 RB1100AHx2
RB1100AHx2 ether2 -> RB951G-2HnD ether2
power jack -> RB951G-2HnD
The PoE and the ethernet cable do not matter, also tried to change.
RB1100AHx2 and RB951G-2HnD:
after netinstall
disable all packages except for:
routeros-powerpc / routeros-mipsbe
ppp
system
and reboot
paste this on RB1100AHx2 terminal
ros code
/interface eoip add keepalive=10 local-address=192.168.3.1 mac-address=02:AE:6D:55:61:E2 name=eoip-tunnel1 remote-address=192.168.3.2 tunnel-id=666 /interface bridge settings set use-ip-firewall=yes /interface pppoe-server server add authentication=mschap2 default-profile=default-encryption disabled=no interface=eoip-tunnel1 mrru=1614 service-name=service1 /ip address add address=192.168.2.1/24 interface=ether13 network=192.168.2.0 add address=192.168.3.1/24 interface=ether2 network=192.168.3.0 /ip firewall connection tracking set enabled=yes /ppp secret add local-address=10.0.0.1 name=test password=test profile=default-encryption remote-address=10.0.0.2 /system identity set name="Test Gateway"paste this on RB951G-2HnD terminal
ros code
/interface eoip add keepalive=10 local-address=192.168.3.2 mac-address=02:08:2C:28:55:D6 name=eoip-tunnel1 remote-address=192.168.3.1 tunnel-id=666 /interface pppoe-client add ac-name="" add-default-route=yes allow=mschap2 default-route-distance=1 dial-on-demand=no disabled=no interface=eoip-tunnel1 keepalive-timeout=60 max-mru=1480 max-mtu=1480 mrru=1614 name=pppoe-out1 password=test profile=default-encryption \ service-name="" use-peer-dns=yes user=test /interface bridge settings set use-ip-firewall=yes /ip address add address=192.168.3.2/24 interface=ether2 network=192.168.3.0 /ip firewall connection tracking set enabled=yes /system identity set name="Test CPE"When you open with winbox 10.0.0.2 [after 1 hour, or 1 minutes are equal]
the RB1100AHx2 continuosly reboot / freeze without creating any autosupout.rif,
but with kernel failure on log and on terminal on serial port:
I hope that I've explained everything well and sufficently detailed all.Code: Select all[admin@Test Gateway] /file> Oops: Exception in kernel mode, sig: 5 [#1] SMP NR_CPUS=2 RB1120 NIP: 8021a730 LR: 8021a46c CTR: 00000000 REGS: dffefd30 TRAP: 0700 Not tainted (3.3.5-smp) MSR: 00029000 <CE,EE,ME> CR: 42000028 XER: 20000000 TASK = 8036d3c0[0] 'swapper/0' THREAD: 80380000 CPU: 0 GPR00: 8021a46c dffefde0 8036d3c0 fffffff2 de6f58aa 00000001 de6f4e50 dc870cd2 GPR08: 120ff29a 0000001d 00000000 8021a400 42000022 00000001 dd9fc300 00000012 GPR16: 00000003 00000000 e1811a40 000005e2 de6dd414 e1811a2c e18119c8 e18119ec GPR24: 00000012 e1811828 de6dd484 0000003b 000000fd dd9fc300 dd9fc300 de6dd3c0 NIP [8021a730] __pskb_pull_tail+0x330/0x340 LR [8021a46c] __pskb_pull_tail+0x6c/0x340 Call Trace: [dffefde0] [8021a46c] __pskb_pull_tail+0x6c/0x340 (unreliable) [dffefe00] [e180df30] ppp_register_channel+0xb20/0x1b4c [ppp_generic@0xe180c000] [dffefe30] [e180f8d4] ppp_output_wakeup+0x978/0xa20 [ppp_generic@0xe180c000] [dffefe90] [e180fb30] ppp_input+0xf0/0x12a4 [ppp_generic@0xe180c000] [dffefeb0] [e18494d0] 0xe18494d0 [pppoe@0xe1849000] [dffefed0] [80221f9c] __netif_receive_skb+0x220/0x400 [dffeff30] [802224a0] process_backlog+0xac/0x178 [dffeff60] [80223870] net_rx_action+0xc0/0x170 [dffeffa0] [80031a14] __do_softirq+0xf4/0x178 [dffefff0] [8000c054] call_do_softirq+0x14/0x24 [80381e80] [80003f5c] do_softirq+0x98/0xc4 [80381ea0] [80031d84] irq_exit+0xa0/0xd4 [80381eb0] [80003c44] do_IRQ+0x94/0x190 [80381ee0] [8000d71c] ret_from_except+0x0/0x18 --- Exception: 501 at cpu_idle+0x8c/0xe0 LR = cpu_idle+0x8c/0xe0 [80381fc0] [8034076c] start_kernel+0x2d4/0x2e8 [80381ff0] [800003f8] skpinv+0x2e4/0x320 Instruction dump: 7fdcf378 3b400000 4bffffa0 7fc3f378 7c84f850 4bfffced 2f830000 409eff9c 7f43d378 4bffe9c9 38600000 4bffff00 <0fe00000> 38c00001 7cc903a6 4bfffd90 ---[ end trace 72421d3cf3d534d4 ]--- Kernel panic - not syncing: Fatal exception in interrupt panicSaver: dumping panic to flash flash: erase 10 flash: prg 10 flash: prg err 0 Rebooting in 1 seconds.. ------------[ cut here ]------------ Kernel BUG at 800a3a70 [verbose debug info unavailable] Oops: Exception in kernel mode, sig: 5 [#2] SMP NR_CPUS=2 RB1120 NIP: 800a3a70 LR: 800113ec CTR: 00000000 REGS: dffefa60 TRAP: 0700 Tainted: G D (3.3.5-smp) MSR: 00021000 <CE,ME> CR: 22000024 XER: 20000000 TASK = 8036d3c0[0] 'swapper/0' THREAD: 80380000 CPU: 0 GPR00: 800113ec dffefb10 8036d3c0 00001000 00000001 00000001 e1000000 edffc000 GPR08: 000000d0 80017554 00000300 fffffffd 22000024 00000001 dd9fc300 00000012 GPR16: 00000003 00000000 e1811a40 000005e2 de6dd414 e1811a2c e18119c8 e18119ec GPR24: 80017554 80380000 e1000000 edffc000 000000d0 00000001 00000001 80017554 NIP [800a3a70] __get_vm_area_node.isra.31+0x34/0x180 LR [800113ec] __ioremap_caller+0x170/0x1a4 Call Trace: [dffefb10] [e137c43c] flash_fixed_cmd+0x140/0x204 [flash@0xe137b000] (unreliable ) [dffefb40] [800113ec] __ioremap_caller+0x170/0x1a4 [dffefb70] [80017554] rb1120_restart+0x68/0xa4 [dffefb90] [8000b35c] machine_restart+0x48/0x60 [dffefbb0] [802ad3b0] panic+0x198/0x1e8 [dffefc00] [800096b4] die+0x244/0x284 [dffefc30] [8000984c] _exception+0x100/0x114 [dffefd20] [8000d6d0] ret_from_except_full+0x0/0x4c --- Exception: 700 at __pskb_pull_tail+0x330/0x340 LR = __pskb_pull_tail+0x6c/0x340 [dffefe00] [e180df30] ppp_register_channel+0xb20/0x1b4c [ppp_generic@0xe180c000] [dffefe30] [e180f8d4] ppp_output_wakeup+0x978/0xa20 [ppp_generic@0xe180c000] [dffefe90] [e180fb30] ppp_input+0xf0/0x12a4 [ppp_generic@0xe180c000] [dffefeb0] [e18494d0] 0xe18494d0 [pppoe@0xe1849000] [dffefed0] [80221f9c] __netif_receive_skb+0x220/0x400 [dffeff30] [802224a0] process_backlog+0xac/0x178 [dffeff60] [80223870] net_rx_action+0xc0/0x170 [dffeffa0] [80031a14] __do_softirq+0xf4/0x178 [dffefff0] [8000c054] call_do_softirq+0x14/0x24 [80381e80] [80003f5c] do_softirq+0x98/0xc4 [80381ea0] [80031d84] irq_exit+0xa0/0xd4 [80381eb0] [80003c44] do_IRQ+0x94/0x190 [80381ee0] [8000d71c] ret_from_except+0x0/0x18 --- Exception: 501 at cpu_idle+0x8c/0xe0 LR = cpu_idle+0x8c/0xe0 [80381fc0] [8034076c] start_kernel+0x2d4/0x2e8 [80381ff0] [800003f8] skpinv+0x2e4/0x320 Instruction dump: 9421ffd0 bf010010 542a0024 90010034 7c9d2378 7cbe2b78 7cda3378 814a000c 7cfb3b78 7d1c4378 7d384b78 554a016e <0f0a0000> 70a90001 41820018 7c690034 ---[ end trace 72421d3cf3d534d5 ]---
Thanks to all.
I have all my machine on CED powered @ 24V* by PoE on ether13, 2 RB1100AH and 4 RB1100AHx2, no one single reboot, kernel panic / or kernel failure before 6.8.Do you power RB1100 over POE ?
I had a similiar problem when my main RB2011 (powered over classing DC adapter) got POE on ether2. One of my collegues attached test SXT wrong (POE went to RB2011 and LAN to SXT . In this setup my RB2011 rebooted sporadicly (15 min, then 1h, then 3 min then again 4h etc..). I tried to change ROS from 6.5 to 6.11.
Everytime it was kernel panic, and reboot. However router made autosupp.out which I sent to support@mikrotik. By the time they answered me I found the POE culprit (he called me saying my SXT is not working.. ) After correctly attached SXT no more reboots..
I answered the support team of my solution but you can try if it is the same problem..