You poor thing. Do you feel left out now?
Nobody cares about the “reduced resell value” because of the sector writes count. Who advertises de sector writes count when selling their hardware? Is that a thing? realy?
Selling a cheap MikroTik, cheaper? how much “resell value” loss are we talking about? If you decided to ditch that device you must have some other reasons.
You’re not reselling gold.
It has any meaning from an administrative point of view when you monitor that value and you notice it increasing without any explanation and you start to dig for the cause, nothing else.
OH, and if you have some device for sale, why do you still keep updating and using it with the latest and greatest release? Leave it somewhere offline without installing some release as soon it gets out.
Any comment about this should be considered offtopic and deleted. Including my current comment.
Cheers.
I think this might be about :resolve command with server parameter specified.
E.g.:
:put [:resolve google.com server=8.8.8.8]
:put [:resolve example.com server=10.10.10.10]
I have two hEX-s bought in short sequence and one has 300K on the clock and the other one 1600K. The last one, ran ROS 6.47 with the crazy counter. Gold has a market price so you can’t compare that with a router. I don’t think a router will increase it price during years of usage.
Resell value is something different than collectors value and I don’t keep my routers in the original unopened box.
have you seen the issues?
you got 6.8MiB free memory, and the new version itself has 11.4MiB
What have you got in file? it seems like you have to remove something from there.
Make sure you got enough free memory.
Is the issue with SFP interfaces fixed in this release? Changelog suggests so but can anyone confirm?
6.47.1 seems to work fine on 3011 and 2011…
(other RBs are still on “long-term”)
Still missing the “antenna gain” setting though (removed in 6.47), since I’m running the 2011 with non-standard (not build-in) antenna’s, and now the gain cannot be set correctly against regulatory-domain.
Also, I know that in 6.44.3 the sfp-led is removed from the configs, but this was very useful. So why???
It was, space-wise, also totally unnecessary to remove, since 2011 has more that enough storage to run 8 (!) Mipsbe-partitions if one would choose to…
Searched through the forums and the net, and all I could find was people asking why it was removed, but never an answer by MT.
So please Mikrotik, be a sport, and re-instate the sfp-led (as user-led setting) and the antenna-gain field.
Ozone
must be very annoying to our fellow Mikrotikls, that every new release anouncement is turning into a whining-zone : )
.
so many fashionable new features … no party :
… but that’s your life jacky brown : |
.
so hopefully my vendor id dhcpd inconvience is handled first : )
You may be right davis! I tested it just now with 6.47 (not working) vs 6.47.1 (working). So it was just misunderstanding of the changelog.
Dude is having frequent disconnects with operation failed: 10054:connection reset by peer. System log is not showing anything related to that…
For now reboot seemed to cure that problem.
I’ve upgraded an LtAP mini (RB912R-2nD), and it would not boot after updating.
I did a netinstall with 6.47.1 and it started. I kept the config, seems to work fine now.
Not sure if a problem with my device or a bug.
hAP ac, hAP ac 2, and crs112 updated with no problem.
Updated RBM33G, LtAP LTE kit, BaseBox 2, BaseBox 5 and PowerBox Pro without issues.
R11e-LTE-US works well on both devices.
Regards.
Updated 3xHapAC 6.47 → 6.47.1 - So far no issues.
Updated 3xHap Lite 6.47 → 6.47.1 - No issues.
Regards.
Hi
i dont believe that i will be able to upgrade my hex3.
Only 4.9MiB free but nothing on the flash.
Anybody an idea ? Im about 50km away from this box.
[admin@MikroTik] /file> /system resource print
uptime: 20w5d4h35m31s
version: 6.46.3 (stable)
build-time: Jan/28/2020 10:46:05
factory-software: 6.40
free-memory: 207.1MiB
total-memory: 256.0MiB
cpu: MIPS 1004Kc V2.15
cpu-count: 4
cpu-frequency: 880MHz
cpu-load: 0%
free-hdd-space: 4.9MiB
total-hdd-space: 16.3MiB
write-sect-since-reboot: 207005
write-sect-total: 470237
bad-blocks: 0%
architecture-name: mmips
board-name: hEX
platform: MikroTik
[admin@MikroTik] /file> print
[admin@MikroTik] /file> print
# NAME TYPE SIZE CREATION-TIME
0 mikrotik_config_2020032... script 8.4KiB mar/26/2020 15:20:53
1 hex3_20200711.rsc script 8.9KiB jul/11/2020 12:59:24
2 flash disk jan/01/1970 02:00:07
3 flash/skins directory jan/01/1970 02:00:08
4 flash/pub directory sep/07/2019 11:30:53
[admin@MikroTik] /file>
That turned out to be premature assumption - problem is back. It occures only when trying to open property window of Dude server device itself in Devices menu - Device properties window stays open for a second and then disconnection occures - every time. System log shows only “logged in” and logged out" messages…
Stable - do these products contain francium?
Not updated - 2xHex Stable
Not updated- 2xCapac Stable
Not updated-1ccr1009 Stable
As for hex resale value, still waiting for HW offload on the hex chipset. 
PS. This Danish custom of drinking in the early morning is not that bad!
Mmmh.
it worked on
hex3 with only 5 M free hdd space
crs326 with only 2.5 M free hdd space
hap lite with 7.9 M frre space (but here i only have the following packages: advanced,dhcp,routing,security,system,wireless)
I had the same problem. Was able to trace it to the fact that I renamed the device that had some disabled services: graph data sources for these services retained the old device name and that was causing client to crash on mouse over.
After I removed these disabled services the crashes stopped.
I would downgrade to an older, much smaller version then upgrade to latest, but in your case that may give problem if you loose some function so that you can not reach it any more.
I think this is broken in 6.47 (and also here still in 6.47.1). It works fine on 6.46.6.
I did send some support files for 6.47 regarding this issue but I think it’s still not fixed here. Can anyone else confirm? Or maybe even better still suggest a fix? It’s stopping me from upgrading as I need to use this feature..