Which boards have this problem? Only mipsbe?Issue with sector writes rising will be fixed in version 6.29. If you want to test it, then fix for it will be included in RouterOS starting from 6.29rc13 version when it comes out.
I have set to only N mode however if the radio is and AC radio the problem persists.Have yet to test, does this apply also if set in N mode?I am well aware of the increased self-interference . We plan sites very carefully to avoid this as much as possible. I also agree Nstream is allot better for PTP however it has proven to be almost useless when it comes to the new AC radios.
If you have 6to4 with 2002::/16 address derived from IPv4, unspecified remote address for 6to4 interface and 192.88.99.1 as default gateway, you're running into "my" 6to4 bug (broken since 6.20, in current state since 6.24). The problem is that default gateway specified as ::192.88.99.1%6to4 does not work at all. So you can only access 2002::/16 and that's it. And if someone tries to connect to you from production (non-2002::/16) range, packets get to your router, but replies don't get out.3. i added and configured 6to4 interface through 192.88.99.1 but cant get good score on tests because MT blocks ICMPv6 to local bridge, ...
/interface 6to4
add local-address=<your IPv4 address> mtu=1480 name=6to4
add local-address=<your IPv4 address> mtu=1480 name=6to4gw remote-address=192.88.99.1
/ipv6 address
add address=2002:<your IPv4 address>::1/16 advertise=no interface=6to4
/ipv6 route
add distance=1 gateway=6to4gwI did as suggested, and now http://www.ipv6-test.com/ tells me there is no ipv6Current workaround recommended by MikroTik support is to use two 6to4 interfaces:
Ok, that does not sound like improvement. I'd suggest to create new topic and post more details, config export, etc..I did as suggested, and now http://www.ipv6-test.com/ tells me there is no ipv6
I do not have this problem, on production I do not have any mipsbe devices.... and the excessive flash writings?
And this provocative phrase that means?So just because -you- are not affected by the bug, does not mean that 6.28 was all colors and rainbows.
It means that Mikrotik 6.28 (or any other 6.x version) is FAR from stable.And this provocative phrase that means?So just because -you- are not affected by the bug, does not mean that 6.28 was all colors and rainbows.
I may have been a bit offensive to you but that was not my intention.
1) Update the bios (/sys rou up)Since upgrading my home box seems very unstable, lots of spontaneous reboots and enough bad connections that I have power cycled it a few times.
[admin@catbus_home] /system> /system routerboard print
routerboard: yes
model: 751G-2HnD
serial-number: 2F8701252CD1
current-firmware: 3.17
upgrade-firmware: 3.22
[admin@catbus_home] /system> /system resource print
uptime: 58m57s
version: 6.28
build-time: Apr/15/2015 15:18:31
free-memory: 26.1MiB
total-memory: 64.0MiB
cpu: MIPS 24Kc V7.4
cpu-count: 1
cpu-frequency: 250MHz
cpu-load: 4%
free-hdd-space: 21.4MiB
total-hdd-space: 64.0MiB
write-sect-since-reboot: 3132
write-sect-total: 12762707
bad-blocks: 0%
architecture-name: mipsbe
board-name: RB751G-2HnD
platform: MikroTik
[admin@catbus_home] /system>
From the log
may/18 23:14:53 system,error,critical System rebooted because of kernel failure
may/18 23:14:54 system,error,critical Out of memory condition was detected
may/18 23:14:54 system,error,critical router was rebooted without proper shutdown
What method you use for install 6.7 (or the previous and what method use to go to 6.7)?After upgrade from 6.7 to 6.28 we now get spontaneous hangs every few days on CCR1036-12G-4S.
What package you have installed and what date and time have the packages?routerboard: yes
model: CCR1036-12G-4S
serial-number: ...
current-firmware: 3.10
upgrade-firmware: 3.22
nmaton,
please contact MikroTik support (support@mikrotik.com) with attached support output files from one of your routers.
We will try to find out what is the reason for your issues. We are sorry for any inconvenience.
