Community discussions

 
rememberme
just joined
Posts: 19
Joined: Fri Nov 13, 2015 10:13 pm
Location: Chicago, USA

Re: v6.42.5 [current]

Fri Jun 29, 2018 4:34 pm

Thank you very much for the reports about issues with space, next RouterOS version will fix the issue.
Meanwhile this package can be used to clear space on your router,
https://www.mikrotik.com/download/share/fix_space.npk
- upload package to your router;
- run /system reboot

It works on every board and does not depend on version.
Guys, be careful with this patch!!!

I uploaded it to a test CCR1016 and it doesn't come up after reboot!

Test it first!
 
sindy
Forum Guru
Forum Guru
Posts: 3765
Joined: Mon Dec 04, 2017 9:19 pm

Re: v6.42.5 [current]

Fri Jun 29, 2018 4:40 pm

Thanks, but I'm getting values like 4294967228 from the OID above.
That's a matter of interpretation, if you interpret it as a signed 32-bit integer, this value means -68 which looks like a plausible one for RSSI. You seem to be interpreting it as a 32-bit unsigned integer so you get this.
Instead of writing novels, post /export hide-sensitive. Use find&replace in your favourite text editor to systematically replace all occurrences of each public IP address potentially identifying you by a distinctive pattern such as my.public.ip.1.
 
User avatar
Cha0s
Forum Veteran
Forum Veteran
Posts: 882
Joined: Tue Oct 11, 2005 4:53 pm

Re: v6.42.5 [current]

Fri Jun 29, 2018 4:41 pm

Cha0s - Is it possible that you added EoIP tunnels from old Winbox version?
I created the tunnels via CLI. Upgrading or rebooting the router loses the hostname in the remote address field and leaves an old/previously resolved IP.
Never mind. It was my mistake. :oops:
A combination of a forgotten custom dyndns script with a wrong/outdated dyndns configured that resolved to the wrong IP.
The "issue" appeared only during reboot/upgrade because only then the public IP actually changed causing the script to run and overwrite the EoIP remote addresses.

Lesson learned: When installing new routerboards (as replacements to old ones) I shouldn't blindly copy/paste the export from the old device that has ancient scripts that are no longer needed :P
 
rememberme
just joined
Posts: 19
Joined: Fri Nov 13, 2015 10:13 pm
Location: Chicago, USA

Re: v6.42.5 [current]

Fri Jun 29, 2018 4:42 pm

Thanks, but I'm getting values like 4294967228 from the OID above.
That's a matter of interpretation, if you interpret it as a signed 32-bit integer, this value means -68 which looks like a plausible one for RSSI. You seem to be interpreting it as a 32-bit unsigned integer so you get this.
Fair enough :)
Thanks!
 
User avatar
Cha0s
Forum Veteran
Forum Veteran
Posts: 882
Joined: Tue Oct 11, 2005 4:53 pm

Re: v6.42.5 [current]

Fri Jun 29, 2018 4:52 pm

Guys, be careful with this patch!!!

I uploaded it to a test CCR1016 and it doesn't come up after reboot!

Test it first!
I tested it on a Groove and worked. I haven't tried it on any other device.

@Mikrotik: will this patch be included automatically on next ROS updates so we can avoid the extra reboots?
 
User avatar
sergejs
MikroTik Support
MikroTik Support
Posts: 6615
Joined: Thu Mar 31, 2005 3:33 pm
Location: Riga, Latvia
Contact:

Re: v6.42.5 [current]

Fri Jun 29, 2018 4:53 pm

Yes, patch will be included into the next RouterOS versions.
 
rememberme
just joined
Posts: 19
Joined: Fri Nov 13, 2015 10:13 pm
Location: Chicago, USA

Re: v6.42.5 [current]

Fri Jun 29, 2018 6:19 pm

Tested on 2 CCRs in the lab, both go into kernel panic.
Seems that this script is killing devices that don't have the space issue, ones that have only one boot image.

  • CCR1016-12S-1S+
  • CCR1009-8G-1S-1S+
RouterBOOT booter 3.33

CCR1016-12S-1S+

CPU frequency: 1200 MHz
Memory size: 2048 MiB
NAND size: 128 MiB

Press any key within 2 seconds to enter setup..

loading kernel... OK
setting up elf image... OK
jumping to kernel code

Pid: 1, comm: init, CPU: 15
r0 : 0xfffffe403e535c00 r1 : 0xfffffe0004940e40 r2 : 0xfffffe003c397500
r3 : 0xfffffe403feffb20 r4 : 0xfffffe403feffb68 r5 : 0x0000000000000060
r6 : 0x0000000000000001 r7 : 0x0000000000000000 r8 : 0x0000000000000000
r9 : 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000001
r12: 0xfffffff5001f21c0 r13: 0xfffffffcffffffff r14: 0x0000000000000001
r15: 0x000000000000013e r16: 0xfffffe003c020420 r17: 0xfffffff5001e0100
r18: 0x0000000000000000 r19: 0x000000000000013d r20: 0xfffffe003c397700
r21: 0xfffffe003c397528 r22: 0x0002000000000000 r23: 0xfffffe003c397520
r24: 0xfffffe403feff950 r25: 0xfffffe403feffb90 r26: 0xfffffe403feffbc0
r27: 0xfffffe403feffbc8 r28: 0xfffffe403feffbb8 r29: 0xfffffe403feffbd0
r30: 0xfffffe403e535ea8 r31: 0xfffffe403e535c00 r32: 0x0000000000000001
r33: 0xfffffff70023df48 r34: 0xfffffe003caa39c0 r35: 0x0000000000000000
r36: 0x0000000000000001 r37: 0x0000000000000000 r38: 0xfffffe003caa3980
r39: 0x0000000000000003 r40: 0x0000000007fc0000 r41: 0x00000000000f3f38
r42: 0x00000000000f4170 r43: 0x00000000000f4370 r44: 0x00000000000f3f10
r45: 0x000000007ffbfb10 r46: 0x000000000014a0b4 r47: 0x00000000000f4768
r48: 0x000000007ffbfb10 r49: 0x000000000014a09c r50: 0x000000000014a0b4
r51: 0x000000000014a0b4 r52: 0xfffffe403feffcc0 tp : 0x000001f4ffc70000
sp : 0xfffffe403feffbb0 lr : 0xfffffff70015bb10
pc : 0xfffffff70023dd38 ex1: 2 faultnum: 18
Instruction dump:
c6e886cd05c18d9b defe400055bbf01f 2862f340102a801e 9e56400035ec3000
<9e06400034ac3000> 23ff1ce051483000 23ff1d9fd107f7c0 8600c6ce05e20d9d

Starting stack dump of tid 1, pid 1 (init) on cpu 15 at cycle 22038278009
frame 0: 0xfffffff70023dd38 squashfs_kill_sb+0x30/0x70 (sp 0xfffffe403feffbb0)
frame 1: 0xfffffff70015bb10 deactivate_locked_super+0x70/0xd8 (sp 0xfffffe403feffbd0)
frame 2: 0xfffffff70015cfb0 mount_nodev+0x90/0x158 (sp 0xfffffe403feffbf0)
frame 3: 0xfffffff70015e690 mount_fs+0x48/0x1e0 (sp 0xfffffe403feffc28)
frame 4: 0xfffffff70018ac60 vfs_kern_mount+0xa8/0x1a0 (sp 0xfffffe403feffc58)
frame 5: 0xfffffff70018baa8 do_kern_mount+0x70/0x1c0 (sp 0xfffffe403feffc98)
frame 6: 0xfffffff70018ead8 do_mount+0x898/0xac0 (sp 0xfffffe403feffcd0)
frame 7: 0xfffffff7001cbb98 compat_sys_mount+0x2c8/0x370 (sp 0xfffffe403feffd60)
frame 8: 0xfffffff700520198 handle_syscall+0x210/0x2d0 (sp 0xfffffe403feffdc0)
<syscall while in user mode>
frame 9: 0x94618 0x94618 (sp 0x7ffbf9e0)
frame 10: 0x13810 0x13810 (sp 0x7ffbf9e0)
frame 11: 0x12338 0x12338 (sp 0x7ffbfa88)
frame 12: 0x4fd30 0x4fd30 (sp 0x7ffbfd30)
frame 13: 0x12670 0x12670 (sp 0x7ffbfe80)
Stack dump complete
---[ end trace a26cf30f1b6cd5ff ]---
Kernel panic - not syncing: Kernel page fault running init!

Starting stack dump of tid 1, pid 1 (init) on cpu 15 at cycle 22173885595
frame 0: 0xfffffff70051f448 dump_stack+0x0/0x20 (sp 0xfffffe403feff808)
frame 1: 0xfffffff7005183e0 panic+0x168/0x398 (sp 0xfffffe403feff808)
frame 2: 0xfffffff7000394f0 do_page_fault+0xa60/0xc48 (sp 0xfffffe403feff8b0)
frame 3: 0xfffffff70051f7a8 handle_interrupt+0x288/0x2a0 (sp 0xfffffe403feff940)
<interrupt 18 while in kernel mode>
frame 4: 0xfffffff70023dd38 squashfs_kill_sb+0x30/0x70 (sp 0xfffffe403feffbb0)
frame 5: 0xfffffff70015bb10 deactivate_locked_super+0x70/0xd8 (sp 0xfffffe403feffbd0)
frame 6: 0xfffffff70015cfb0 mount_nodev+0x90/0x158 (sp 0xfffffe403feffbf0)
frame 7: 0xfffffff70015e690 mount_fs+0x48/0x1e0 (sp 0xfffffe403feffc28)
frame 8: 0xfffffff70018ac60 vfs_kern_mount+0xa8/0x1a0 (sp 0xfffffe403feffc58)
frame 9: 0xfffffff70018baa8 do_kern_mount+0x70/0x1c0 (sp 0xfffffe403feffc98)
frame 10: 0xfffffff70018ead8 do_mount+0x898/0xac0 (sp 0xfffffe403feffcd0)
frame 11: 0xfffffff7001cbb98 compat_sys_mount+0x2c8/0x370 (sp 0xfffffe403feffd60)
frame 12: 0xfffffff700520198 handle_syscall+0x210/0x2d0 (sp 0xfffffe403feffdc0)
<syscall while in user mode>
frame 13: 0x94618 0x94618 (sp 0x7ffbf9e0)
frame 14: 0x13810 0x13810 (sp 0x7ffbf9e0)
frame 15: 0x12338 0x12338 (sp 0x7ffbfa88)
frame 16: 0x4fd30 0x4fd30 (sp 0x7ffbfd30)
frame 17: 0x12670 0x12670 (sp 0x7ffbfe80)
Stack dump complete
Rebooting in 1 seconds..Resetting chip and restarting.

RouterBOOT booter 3.33

CCR1009-8G-1S-1S+

CPU frequency: 1200 MHz
Memory size: 2048 MiB
NAND size: 128 MiB

Press any key within 2 seconds to enter setup..

loading kernel... OK
setting up elf image... OK
jumping to kernel code

Pid: 1, comm: init, CPU: 8
r0 : 0xfffffe007dea5c00 r1 : 0xfffffe0004a35640 r2 : 0xfffffe007d597680
r3 : 0xfffffe007eedfb20 r4 : 0xfffffe007eedfb68 r5 : 0x0000000000000060
r6 : 0x0000000000000001 r7 : 0x0000000000000000 r8 : 0x0000000000000000
r9 : 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000001
r12: 0xfffffff5001121c0 r13: 0xfffffffcffffffff r14: 0x0000000000000001
r15: 0x000000000000013a r16: 0xfffffe007d020420 r17: 0xfffffff500100100
r18: 0x0000000000000000 r19: 0x0000000000000139 r20: 0xfffffe007d597880
r21: 0xfffffe007d5976a8 r22: 0x0002000000000000 r23: 0xfffffe007d5976a0
r24: 0xfffffe007eedf950 r25: 0xfffffe007eedfb90 r26: 0xfffffe007eedfbc0
r27: 0xfffffe007eedfbc8 r28: 0xfffffe007eedfbb8 r29: 0xfffffe007eedfbd0
r30: 0xfffffe007dea5ea8 r31: 0xfffffe007dea5c00 r32: 0x0000000000000001
r33: 0xfffffff70023df48 r34: 0xfffffe007de62580 r35: 0x0000000000000000
r36: 0x0000000000000001 r37: 0x0000000000000000 r38: 0xfffffe007de62540
r39: 0x0000000000000003 r40: 0x0000000007fc0000 r41: 0x00000000000f3f38
r42: 0x00000000000f4170 r43: 0x00000000000f4370 r44: 0x00000000000f3f10
r45: 0x000000007fe2fb10 r46: 0x000000000014a0b4 r47: 0x00000000000f4768
r48: 0x000000007fe2fb10 r49: 0x000000000014a09c r50: 0x000000000014a0b4
r51: 0x000000000014a0b4 r52: 0xfffffe007eedfcc0 tp : 0x000001f4ffb90000
sp : 0xfffffe007eedfbb0 lr : 0xfffffff70015bb10
pc : 0xfffffff70023dd38 ex1: 2 faultnum: 18
Instruction dump:
c6e886cd05c18d9b defe400055bbf01f 2862f340102a801e 9e56400035ec3000
<9e06400034ac3000> 23ff1ce051483000 23ff1d9fd107f7c0 8600c6ce05e20d9d

Starting stack dump of tid 1, pid 1 (init) on cpu 8 at cycle 21745015076
frame 0: 0xfffffff70023dd38 squashfs_kill_sb+0x30/0x70 (sp 0xfffffe007eedfbb0)
frame 1: 0xfffffff70015bb10 deactivate_locked_super+0x70/0xd8 (sp 0xfffffe007eedfbd0)
frame 2: 0xfffffff70015cfb0 mount_nodev+0x90/0x158 (sp 0xfffffe007eedfbf0)
frame 3: 0xfffffff70015e690 mount_fs+0x48/0x1e0 (sp 0xfffffe007eedfc28)
frame 4: 0xfffffff70018ac60 vfs_kern_mount+0xa8/0x1a0 (sp 0xfffffe007eedfc58)
frame 5: 0xfffffff70018baa8 do_kern_mount+0x70/0x1c0 (sp 0xfffffe007eedfc98)
frame 6: 0xfffffff70018ead8 do_mount+0x898/0xac0 (sp 0xfffffe007eedfcd0)
frame 7: 0xfffffff7001cbb98 compat_sys_mount+0x2c8/0x370 (sp 0xfffffe007eedfd60)
frame 8: 0xfffffff700520198 handle_syscall+0x210/0x2d0 (sp 0xfffffe007eedfdc0)
<syscall while in user mode>
frame 9: 0x94618 0x94618 (sp 0x7fe2f9e0)
frame 10: 0x13810 0x13810 (sp 0x7fe2f9e0)
frame 11: 0x12338 0x12338 (sp 0x7fe2fa88)
frame 12: 0x4fd30 0x4fd30 (sp 0x7fe2fd30)
frame 13: 0x12670 0x12670 (sp 0x7fe2fe80)
Stack dump complete
---[ end trace 9b1a353c28c3b544 ]---
Kernel panic - not syncing: Kernel page fault running init!

Starting stack dump of tid 1, pid 1 (init) on cpu 8 at cycle 21880507611
frame 0: 0xfffffff70051f448 dump_stack+0x0/0x20 (sp 0xfffffe007eedf808)
frame 1: 0xfffffff7005183e0 panic+0x168/0x398 (sp 0xfffffe007eedf808)
frame 2: 0xfffffff7000394f0 do_page_fault+0xa60/0xc48 (sp 0xfffffe007eedf8b0)
frame 3: 0xfffffff70051f7a8 handle_interrupt+0x288/0x2a0 (sp 0xfffffe007eedf940)
<interrupt 18 while in kernel mode>
frame 4: 0xfffffff70023dd38 squashfs_kill_sb+0x30/0x70 (sp 0xfffffe007eedfbb0)
frame 5: 0xfffffff70015bb10 deactivate_locked_super+0x70/0xd8 (sp 0xfffffe007eedfbd0)
frame 6: 0xfffffff70015cfb0 mount_nodev+0x90/0x158 (sp 0xfffffe007eedfbf0)
frame 7: 0xfffffff70015e690 mount_fs+0x48/0x1e0 (sp 0xfffffe007eedfc28)
frame 8: 0xfffffff70018ac60 vfs_kern_mount+0xa8/0x1a0 (sp 0xfffffe007eedfc58)
frame 9: 0xfffffff70018baa8 do_kern_mount+0x70/0x1c0 (sp 0xfffffe007eedfc98)
frame 10: 0xfffffff70018ead8 do_mount+0x898/0xac0 (sp 0xfffffe007eedfcd0)
frame 11: 0xfffffff7001cbb98 compat_sys_mount+0x2c8/0x370 (sp 0xfffffe007eedfd60)
frame 12: 0xfffffff700520198 handle_syscall+0x210/0x2d0 (sp 0xfffffe007eedfdc0)
<syscall while in user mode>
frame 13: 0x94618 0x94618 (sp 0x7fe2f9e0)
frame 14: 0x13810 0x13810 (sp 0x7fe2f9e0)
frame 15: 0x12338 0x12338 (sp 0x7fe2fa88)
frame 16: 0x4fd30 0x4fd30 (sp 0x7fe2fd30)
frame 17: 0x12670 0x12670 (sp 0x7fe2fe80)
Stack dump complete
Rebooting in 1 seconds..Resetting chip and restarting.
 
ac6529
just joined
Posts: 4
Joined: Sun Apr 30, 2017 9:22 am

Re: v6.42.5 [current]

Fri Jun 29, 2018 6:46 pm

Tested on 2 CCRs in the lab, both go into kernel panic.
Seems that this script is killing devices that don't have the space issue, ones that have only one boot image.

  • CCR1016-12S-1S+
  • CCR1009-8G-1S-1S+

can confirm, killed a CCR1009 here.
how does one recover from this? i was able to do a netinstall, router boots up but for some reason I can't connect to 192.168.88.1 on eth1 per the default configuration.

EDIT: got access, it put the default IP on the combo interface and not ETH1
 
pe1chl
Forum Guru
Forum Guru
Posts: 5559
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42.5 [current]

Fri Jun 29, 2018 7:49 pm

Indeed the patch does not work!
I tried it on a 2-partition CCR1009 (before reading other remarks).
First copied partition containing 6.42.1, updated it to 6.42.5 which resulted in lost space issue as usual,
then uploaded patch and rebooted, router came back but it has switched active partition back to the 6.42.1 copy!

That explains why routers with only one partition fail completely. They don't have the second partition to fall back to.
 
telepro
Frequent Visitor
Frequent Visitor
Posts: 63
Joined: Sun Apr 03, 2011 7:50 pm

Re: v6.42.5 [current]

Fri Jun 29, 2018 9:42 pm

Fix_Space.npk script did not work successfully on a RB750r2 after executing the following procedure:
Device operational running ROS 6.42.5
Placed update procedure on flash partition using winbox
Use winbox to execute reboot to run the Fix_Space.npk script.
Device did reboot but not come up successfully.
Waited about 10 minutes, but device never became accessible.
Cycled power.
After power cycle, device did start up and respond to winbox, but entire configuration was lost and all files previously on flash disk were gone.
 
Sob
Forum Guru
Forum Guru
Posts: 4410
Joined: Mon Apr 20, 2009 9:11 pm

Re: v6.42.5 [current]

Fri Jun 29, 2018 11:10 pm

For the record, fix_space.npk did work well with my testing CHR. It did survive and successfully reclaimed missing space.
People who quote full posts should be spanked with ethernet cable. Some exceptions for multi-topic threads may apply.
 
LeftyTs
Frequent Visitor
Frequent Visitor
Posts: 67
Joined: Thu Nov 03, 2016 2:39 am
Location: Athens, Greece
Contact:

Re: v6.42.5 [current]

Sat Jun 30, 2018 2:32 am

As for the HDD problem - we are currently trying to find out how to reproduce this problem. If anyone can share such information (step-by-step), then please send in an e-mail to support@mikrotik.com. Is it possible that all of the affected devices had partitions?
No, I am very certain partitioning has nothing to do with it. Actually I have send MT info as well as supout. Most devices I upgraded from bugfix release to the current one had this issue as backup stopped from working right after the upgrade. None of them had partitioning. I will repost the steps I did.

1) Upgraded from v5.26 to bugfix.
2) Right after bugfix I upgraded again to current

Almost all devices I upgraded could not get a valid backup right after the above two steps (system backup save). The backup file that was created was extremely large in size and ROS was always reporting an error.
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1406
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42.5 [current]

Sat Jun 30, 2018 1:25 pm

We are very sorry for any inconvenience caused. Fix package for missing storage space has been temporary removed and will soon be updated to patched version.
 
User avatar
Cha0s
Forum Veteran
Forum Veteran
Posts: 882
Joined: Tue Oct 11, 2005 4:53 pm

Re: v6.42.5 [current]

Sat Jun 30, 2018 3:55 pm

Indeed the patch does not work!
I tried it on a 2-partition CCR1009 (before reading other remarks).
First copied partition containing 6.42.1, updated it to 6.42.5 which resulted in lost space issue as usual,
then uploaded patch and rebooted, router came back but it has switched active partition back to the 6.42.1 copy!

That explains why routers with only one partition fail completely. They don't have the second partition to fall back to.
I only tried it on one (non-critical) device (an old Groove) that has two partitions to test if it works.
It worked ok without breaking the first partition so I thought it's ok in general.
I guess I was just lucky with this one (and more lucky I didn't start running it on more critical equipment).
 
pe1chl
Forum Guru
Forum Guru
Posts: 5559
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42.5 [current]

Sat Jun 30, 2018 5:51 pm

I only tried it on one (non-critical) device (an old Groove) that has two partitions to test if it works.
It worked ok without breaking the first partition so I thought it's ok in general.
Did that Groove have the lost space issue?
The patch does this:

#!/bin/bash
if [ "$bootimage" != "1" ]; then rm -f /flash/bootimage; fi
mv /var/pdb/fix-space/image /tmp
rm -rf /var/pdb/fix-space

I think it is a bit confusing, I would expect to see a mv to /flash/bootimage. Or the ln -f method I
posted before.
It looks like after the above the bootimage might be gone. But I have no knowledge of the RouterOS
filesystem and boot code, only general Linux experience.
 
User avatar
Cha0s
Forum Veteran
Forum Veteran
Posts: 882
Joined: Tue Oct 11, 2005 4:53 pm

Re: v6.42.5 [current]

Sat Jun 30, 2018 6:03 pm

Did that Groove have the lost space issue?
Obviously. Why would I try it on a device that has no problem?
 
Redmor
Member Candidate
Member Candidate
Posts: 248
Joined: Wed May 31, 2017 7:40 pm
Location: Italy

Re: v6.42.5 [current]

Sat Jun 30, 2018 6:12 pm

I have to admit that Nv2 has been improved, but are you going to implement a madder TDMA protocol?
I have co-workers that say "If you have 100Mbps on an AP and 100 clients connected, with TDMA you can give 100Mbps to them all simultaneously, slowing latency", I know that this is pure theory, but in some cases I don't see any difference between Nv2 and 802.11 even with 20 clients and 500Mbps on AP.
ImageImage
 
User avatar
Cha0s
Forum Veteran
Forum Veteran
Posts: 882
Joined: Tue Oct 11, 2005 4:53 pm

Re: v6.42.5 [current]

Sat Jun 30, 2018 6:37 pm

I have to admit that Nv2 has been improved, but are you going to implement a madder TDMA protocol?
I have co-workers that say "If you have 100Mbps on an AP and 100 clients connected, with TDMA you can give 100Mbps to them all simultaneously, slowing latency", I know that this is pure theory, but in some cases I don't see any difference between Nv2 and 802.11 even with 20 clients and 500Mbps on AP.
NV2 is a TDMA implemenation of MikroTik's.

I don't see how you can give 100Mbps * 100 times (clients) at the same time when your physical interface cannot do 10gbit (that's how much 100*100 is!). Not even in theory. Your co-workers don't seem to know what they are talking about.

TDMA divides the signal into different time slots. That does not multiply the available traffic times the connected clients. That doesn't make any sense whatsoever.
TDMA allows for multiple clients to use the AP without any client overtaking any other (for example due to the hidden node problem).
Each client has its own time slot on when to talk to the AP, so no two clients can talk at the same time (which would be pretty much noise as far as the AP is concerned).
https://en.wikipedia.org/wiki/Time-divi ... ple_access
 
benoga
just joined
Posts: 13
Joined: Wed Mar 09, 2016 7:50 am

Re: v6.42.5 [current]

Sat Jun 30, 2018 9:01 pm

This Package on the first Page kill my CCR Router....

Edit 06.29.2018
To fix storage issue on your router, use package from the link,
https://www.mikrotik.com/download/share/fix_space.npk
- upload package to your router;
- run /system reboot
[/quote]
 
marekm
Member Candidate
Member Candidate
Posts: 196
Joined: Tue Feb 01, 2011 11:27 pm

Re: v6.42.5 [current]

Sat Jun 30, 2018 9:53 pm

*) w60g - general stability and performance improvements;
Ticket#2018062622003837
For me, 6.42.5 made w60g less stable (6.43rc34 has the same issues too) than 6.42.4. Wireless Wire Dish kit, 208 m PtP link, testing with UDP 300Mbps/600Mbps btest for many hours, new versions randomly disconnect about 100 times in 24 hours, 6.42.4 - not a single disconnect and only about 0.07% packet loss (probably not all of it in that link, I have a few switches passing a lot of other traffic in between). Support gives various recommendations that don't help (change alignment, reduce Tx power, change channel). Only downgrade helps, the issue is easy to reproduce reliably (the disconnects happen even with no traffic, and take long enough for winbox to close), so I'm a bit surprised the changes were rushed from RC to current without more internal testing. I'm fine with running 6.42.4 for now, but it's missing one important thing (channel 4 support - BTW, why CLI only and winbox shows "auto" instead of 64800?).
 
User avatar
Xymox
Member
Member
Posts: 387
Joined: Thu Jan 21, 2010 5:04 pm
Location: Phoenix, Arizona US
Contact:

Re: v6.42.5 [current]

Sun Jul 01, 2018 6:01 am

Thank you very much for the reports about issues with space, next RouterOS version will fix the issue.
Meanwhile this package can be used to clear space on your router,
UPDATE: (package removed, will be updated very soon)
- upload package to your router;
- run /system reboot

It works on every board and does not depend on version.
AWESOME !!!!!
 
User avatar
Xymox
Member
Member
Posts: 387
Joined: Thu Jan 21, 2010 5:04 pm
Location: Phoenix, Arizona US
Contact:

Re: v6.42.5 [current]

Sun Jul 01, 2018 6:15 am

Thank you Mikrotik for addressing the space bug. Thank you for also working up a way to recover a router.

A bit late for me as I flew to 4 sites to recover devices :( As I was the first to report this issue and I suffered a lot of expenses related, I think I deserve a Mikrotik T-Shirt, hahaha...
 
antonsb
MikroTik Support
MikroTik Support
Posts: 194
Joined: Sun Jul 24, 2016 3:12 pm
Location: Riga, Latvia

Re: v6.42.5 [current]

Sun Jul 01, 2018 11:10 pm

*) w60g - general stability and performance improvements;
Ticket#2018062622003837
For me, 6.42.5 made w60g less stable (6.43rc34 has the same issues too) than 6.42.4. Wireless Wire Dish kit, 208 m PtP link, testing with UDP 300Mbps/600Mbps btest for many hours, new versions randomly disconnect about 100 times in 24 hours, 6.42.4 - not a single disconnect and only about 0.07% packet loss (probably not all of it in that link, I have a few switches passing a lot of other traffic in between). Support gives various recommendations that don't help (change alignment, reduce Tx power, change channel). Only downgrade helps, the issue is easy to reproduce reliably (the disconnects happen even with no traffic, and take long enough for winbox to close), so I'm a bit surprised the changes were rushed from RC to current without more internal testing. I'm fine with running 6.42.4 for now, but it's missing one important thing (channel 4 support - BTW, why CLI only and winbox shows "auto" instead of 64800?).
At what power output are you right now?
You will need to lower power output even more to something in range from 1 to 5 should be fine for such close distance
 
bda
Member Candidate
Member Candidate
Posts: 124
Joined: Fri Sep 03, 2010 11:07 am
Location: Russia,Moscow

Re: v6.42.5 [current]

Mon Jul 02, 2018 9:21 am

We are very sorry for any inconvenience caused. Fix package for missing storage space has been temporary removed and will soon be updated to patched version.
Sorry for disturbing.
When we can download fix for missing storage space?
God bless UNIX!
 
Babujnik
just joined
Posts: 9
Joined: Fri May 05, 2017 2:15 pm

Re: v6.42.5 [current]

Mon Jul 02, 2018 11:34 am

is it only me, or wireless performance on 6.42.5 is really bad ?
today I couldn't even work from home, was disconnected every few minutes. speed between workstation and NAS (laptop--WIFI->RB--LAN->NAS) was runing around 800kbs (5Ghz Network !).
when downgraded to 6.42.4 - works like a charm

(RouterBOARD 962UiGS-5HacT2HnT)
 
User avatar
sergejs
MikroTik Support
MikroTik Support
Posts: 6615
Joined: Thu Mar 31, 2005 3:33 pm
Location: Riga, Latvia
Contact:

Re: v6.42.5 [current]

Mon Jul 02, 2018 1:56 pm

We are sorry for any issues caused by the previous package, we uploaded new packages, that will work fine on any router.

Package updated 07/02/2018
To fix storage issue on your router, use package from the link,
https://www.mikrotik.com/download/share/fix_space.npk
- upload package to your router;
- run /system reboot
 
User avatar
vecernik87
Long time Member
Long time Member
Posts: 642
Joined: Fri Nov 10, 2017 8:19 am

Re: v6.42.5 [current]

Mon Jul 02, 2018 2:07 pm

is it only me, or wireless performance on 6.42.5 is really bad ? (RouterBOARD 962UiGS-5HacT2HnT)
Maybe it is device specific? No disconnection or slow network with RBD52G-5HacD2HnD running 6.42.5
 
lesnikov
just joined
Posts: 17
Joined: Tue Jul 15, 2014 9:33 pm
Location: Slovenia

Re: v6.42.5 [current]

Mon Jul 02, 2018 2:23 pm

We are sorry for any issues caused by the previous package, we uploaded new packages, that will work fine on any router.

Package updated 07.02.2018
To fix storage issue on your router, use package from the link,
https://www.mikrotik.com/download/share/fix_space.npk
- upload package to your router;
- run /system reboot
we updated to 6.42.5 about 20 hours ago and when we do check for updates it says up to date. so new patched version is not getting fetched. should we manually upgrade?
 
Babujnik
just joined
Posts: 9
Joined: Fri May 05, 2017 2:15 pm

Re: v6.42.5 [current]

Mon Jul 02, 2018 2:33 pm

is it only me, or wireless performance on 6.42.5 is really bad ? (RouterBOARD 962UiGS-5HacT2HnT)
Maybe it is device specific? No disconnection or slow network with RBD52G-5HacD2HnD running 6.42.5
maybe it is as you mentioned. haven't changed anything else in environment, except update to 6.42.5. got few other devices, but didn't go with that version there yet. one problematic device is enough ;)
 
User avatar
eworm
Member
Member
Posts: 358
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.42.5 [current]

Mon Jul 02, 2018 2:40 pm

We are sorry for any issues caused by the previous package, we uploaded new packages, that will work fine on any router.

Package updated 07.02.2018
To fix storage issue on your router, use package from the link,
https://www.mikrotik.com/download/share/fix_space.npk
- upload package to your router;
- run /system reboot
we updated to 6.42.5 about 20 hours ago and when we do check for updates it says up to date. so new patched version is not getting fetched. should we manually upgrade?
This is not an update but just a fix. You are up-to-date, no action required.
Manage RouterOS scripts and extend your devices' functionality: RouterOS Scripts
 
sindy
Forum Guru
Forum Guru
Posts: 3765
Joined: Mon Dec 04, 2017 9:19 pm

Re: v6.42.5 [current]

Mon Jul 02, 2018 2:41 pm

we updated to 6.42.5 about 20 hours ago and when we do check for updates it says up to date. so new patched version is not getting fetched. should we manually upgrade?
fix_space.npk is a standalone package used to resolve the missing space issue, not related to any particular release. So the "check for updates" function is not relevant to it.
Instead of writing novels, post /export hide-sensitive. Use find&replace in your favourite text editor to systematically replace all occurrences of each public IP address potentially identifying you by a distinctive pattern such as my.public.ip.1.
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 1239
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v6.42.5 [current]

Mon Jul 02, 2018 3:00 pm

We are sorry for any issues caused by the previous package, we uploaded new packages, that will work fine on any router.

Package updated 07.02.2018
To fix storage issue on your router, use package from the link,
https://www.mikrotik.com/download/share/fix_space.npk
- upload package to your router;
- run /system reboot
7 February 2018??

Use correct format on date please.
02.07.2018
or us format
07/02/2018
 
How to use Splunk to monitor your MikroTik Router

MikroTik->Splunk
 
 
marekm
Member Candidate
Member Candidate
Posts: 196
Joined: Tue Feb 01, 2011 11:27 pm

Re: v6.42.5 [current]

Mon Jul 02, 2018 6:13 pm

At what power output are you right now?
You will need to lower power output even more to something in range from 1 to 5 should be fine for such close distance
Default, which is stable in 6.42.4. I have already tried different tx-power values (as suggested by support), there was no link at all with power 1 or 2, RSSI was about -67 at power 3, -60 at power 4, -54 at power 5, little change at higher settings or default. So it seems tx-power is in ~6dB units, but reducing it didn't make it more stable. If acceptable RSSI range is so narrow, it would be nice to adjust tx-power automatically (especially in PtMP where stations can be at very different distances).
 
anuser
Member
Member
Posts: 369
Joined: Sat Nov 29, 2014 7:27 pm

Re: v6.42.5 [current]

Mon Jul 02, 2018 6:15 pm

is it only me, or wireless performance on 6.42.5 is really bad ? (RouterBOARD 962UiGS-5HacT2HnT)
Is ANI enabled?
/interface wireless set adaptive-noise-immunity=ap-and-client-mode wlan2
/interface wireless set adaptive-noise-immunity=ap-and-client-mode wlan1 
 
bda
Member Candidate
Member Candidate
Posts: 124
Joined: Fri Sep 03, 2010 11:07 am
Location: Russia,Moscow

Re: v6.42.5 [current]

Mon Jul 02, 2018 10:25 pm

We are sorry for any issues caused by the previous package, we uploaded new packages, that will work fine on any router.

Package updated 07/02/2018
To fix storage issue on your router, use package from the link,
https://www.mikrotik.com/download/share/fix_space.npk
- upload package to your router;
- run /system reboot
Script do nothing on hEX PoE:

[bda@hme16-08ra] > system resource print
uptime: 1m58s
version: 6.42.4 (stable)
build-time: Jun/15/2018 14:14:17
factory-software: 6.36
free-memory: 106.0MiB
total-memory: 128.0MiB
cpu: MIPS 74Kc V5.0
cpu-count: 1
cpu-frequency: 800MHz
cpu-load: 12%
free-hdd-space: 4.8MiB
total-hdd-space: 16.0MiB
write-sect-since-reboot: 67
write-sect-total: 9870
bad-blocks: 0%
architecture-name: mipsbe
board-name: hEX PoE
platform: MikroTik

Why?
God bless UNIX!
 
pe1chl
Forum Guru
Forum Guru
Posts: 5559
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42.5 [current]

Mon Jul 02, 2018 10:32 pm

Script do nothing on hEX PoE:
Why?
Of course not!
It is for devices with 128MB flash. They have to store the updates in the same partition as the running firmware.
You have a 16MB flash device which puts updates in the RAM disk. And thus the error that is being fixed here cannot occur
on those devices.
 
bda
Member Candidate
Member Candidate
Posts: 124
Joined: Fri Sep 03, 2010 11:07 am
Location: Russia,Moscow

Re: v6.42.5 [current]

Mon Jul 02, 2018 10:39 pm

Script do nothing on hEX PoE:
Why?
Of course not!
It is for devices with 128MB flash. They have to store the updates in the same partition as the running firmware.
You have a 16MB flash device which puts updates in the RAM disk. And thus the error that is being fixed here cannot occur
on those devices.
But why this device have only free-hdd-space: 4.8MiB ?!
God bless UNIX!
 
Sob
Forum Guru
Forum Guru
Posts: 4410
Joined: Mon Apr 20, 2009 9:11 pm

Re: v6.42.5 [current]

Mon Jul 02, 2018 10:58 pm

How much would you expect? It the total space is only 16MB and it has to take whole system, there can be hardly anything left.
People who quote full posts should be spanked with ethernet cable. Some exceptions for multi-topic threads may apply.
 
pe1chl
Forum Guru
Forum Guru
Posts: 5559
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42.5 [current]

Mon Jul 02, 2018 10:59 pm

Because it has only 16MB total and 10-11 MB is required.
The problem we are discussing is on the higher end devices (or better: old devices) that had 128MB.
You could partition this in 2 partitions of 64MB of which some 40MB is used.
you need the remaining 24MB to upload a new version.
In the 16MB devices the new version is loaded into RAM.
 
bda
Member Candidate
Member Candidate
Posts: 124
Joined: Fri Sep 03, 2010 11:07 am
Location: Russia,Moscow

Re: v6.42.5 [current]

Mon Jul 02, 2018 11:07 pm

Script do nothing on hEX PoE:
Why?
Of course not!
It is for devices with 128MB flash. They have to store the updates in the same partition as the running firmware.
You have a 16MB flash device which puts updates in the RAM disk. And thus the error that is being fixed here cannot occur
on those devices.
But why this device have only free-hdd-space: 4.8MiB ?!
Understood about 16 mb devices.. How about CRS ? After 6.42.1-4 - they have low space too...
In a few hours I will test on one of CRS...

And how about old RB800/RB850Gx2/RB493G on so on. Does this patch applicable?
God bless UNIX!
 
bda
Member Candidate
Member Candidate
Posts: 124
Joined: Fri Sep 03, 2010 11:07 am
Location: Russia,Moscow

Re: v6.42.5 [current]

Mon Jul 02, 2018 11:08 pm

And at last.... Before 6.42.1-4, any of hEX has more than 4mb... anyway
God bless UNIX!
 
Babujnik
just joined
Posts: 9
Joined: Fri May 05, 2017 2:15 pm

Re: v6.42.5 [current]

Tue Jul 03, 2018 12:34 am

is it only me, or wireless performance on 6.42.5 is really bad ? (RouterBOARD 962UiGS-5HacT2HnT)
Is ANI enabled?
/interface wireless set adaptive-noise-immunity=ap-and-client-mode wlan2
/interface wireless set adaptive-noise-immunity=ap-and-client-mode wlan1
No, i haven't set this function. I can run upgrade once more and try with ANI functionality
As much as network on it's own I understand, the Wi-Fi settings are a little mistery for me
 
User avatar
Xymox
Member
Member
Posts: 387
Joined: Thu Jan 21, 2010 5:04 pm
Location: Phoenix, Arizona US
Contact:

Re: v6.42.5 [current]

Tue Jul 03, 2018 2:31 am

We are sorry for any issues caused by the previous package, we uploaded new packages, that will work fine on any router.

Package updated 07/02/2018
To fix storage issue on your router, use package from the link,
https://www.mikrotik.com/download/share/fix_space.npk
- upload package to your router;
- run /system reboot
Awesome.. I will test this shortly..

Thanks again..
 
krzysztof
just joined
Posts: 24
Joined: Sat Apr 25, 2015 7:46 pm

Re: v6.42.5 [current]

Tue Jul 03, 2018 3:08 am

IGMP still has problems with overloading.
PIM for IGMP continues to add multicast streams incorrectly!

I want to show an error in my laboratory
I am writing please and nothing.
I giving my phone number to Poland and nothing
Why do you treat your clients like that?

I like this equipment

And I'm forced to buy huawei, cisco etc.

krzysztof@pawluk.org

Certificate:
Cisco:
CCNA
CCNP
Mikrotik:
MTCNA
MTCWE
MTCRE
MTCTCE
 
pe1chl
Forum Guru
Forum Guru
Posts: 5559
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42.5 [current]

Tue Jul 03, 2018 10:47 am

We are sorry for any issues caused by the previous package, we uploaded new packages, that will work fine on any router.

Package updated 07/02/2018
To fix storage issue on your router, use package from the link,
https://www.mikrotik.com/download/share/fix_space.npk
- upload package to your router;
- run /system reboot
Did someone already test the new version of the fix on a CCR? I have become a bit more reluctant since the previous version could
have killed out router when we were not saved by the automatic partition fallback...
 
petertosh
newbie
Posts: 25
Joined: Wed Mar 21, 2018 9:42 am

Re: v6.42.5 [current]

Tue Jul 03, 2018 11:56 am

We are sorry for any issues caused by the previous package, we uploaded new packages, that will work fine on any router.

Package updated 07/02/2018
To fix storage issue on your router, use package from the link,
https://www.mikrotik.com/download/share/fix_space.npk
- upload package to your router;
- run /system reboot
Did someone already test the new version of the fix on a CCR? I have become a bit more reluctant since the previous version could
have killed out router when we were not saved by the automatic partition fallback...
Used on CCR1009 yesterday, went smooth. Now with hotspot the system uses about 38 MBs. Was able to repartition again. Previously, because of the lost space I repartitioned from 2 to 1 partitions. For all asking if this erases the config: no. You can repartition from two to one partition and at least in my case the router was up and running normally after that. Thanks for the fix.
 
disik
just joined
Posts: 4
Joined: Fri May 23, 2014 11:30 pm

Re: v6.42.5 [current]

Tue Jul 03, 2018 1:55 pm

Kid-control should apply to IPv6 too
 
User avatar
Cha0s
Forum Veteran
Forum Veteran
Posts: 882
Joined: Tue Oct 11, 2005 4:53 pm

Re: v6.42.5 [current]

Tue Jul 03, 2018 2:46 pm

And at last.... Before 6.42.1-4, any of hEX has more than 4mb... anyway
I agree. On my devices that have 16MB flash, they have ~7.5MiB free, not 4.8MiB.
 
105547111
Member Candidate
Member Candidate
Posts: 131
Joined: Fri Jun 22, 2012 9:46 pm

Re: v6.42.5 [current]

Tue Jul 03, 2018 6:21 pm

Kid-control should apply to IPv6 too
I agree totally - so much is missing from ipv6 in general like routing-marks, etc, etc :-(
 
Beone
Member Candidate
Member Candidate
Posts: 243
Joined: Fri Feb 11, 2011 1:11 pm

Re: v6.42.5 [current]

Tue Jul 03, 2018 7:51 pm

Thank you very much for the reports about issues with space, next RouterOS version will fix the issue.
Meanwhile this package can be used to clear space on your router,
https://www.mikrotik.com/download/share/fix_space.npk
- upload package to your router;
- run /system reboot

It works on every board and does not depend on version.
18:50:39 system,error can not install fix-space-6.0: system-6.41 is not installed, but is required

Who is online

Users browsing this forum: No registered users and 9 guests