No, Not at all. I am much faster in understanding his point an have no need in ycrolling up and reading the last messages to understand.Don't you think it is unneeded a waste of time?
What is the problem? It is just efficient and the forum Software shortens the text anyway. Instead of hist post, your post actually has nothing to add to the thread.Do you think that people are unable to follow the thread?
netwatch too, just changing the comment should not update the uptimeIn fact this should be done for every possible item in the config. Don't know what is the exact status now, but I have seen many things go down-up when changing only a comment.
Really? Nobody ever asked me for this...Good that the false reporting of sector writes is finally fixed. This did reduce the resell value of the Mikrotik device you own greatly.
Because you dont need it. You dont need access to Kernel, you dont need access to Filesystem. I hope mikrotik will never Listen to guys like you. This will Not improve the OS.[
Can you please tell us:
What is the reason for hiding the files?
I have 2 carriers with 2 different SIMs. One works, one seems to block it!/ interface lte firmware-upgrade lte1 upgrade=yes
.... lost connection.... reboot.... same version on modem
And where is the version specific part of this? As I see it it's nothing new to this beta.... So please stay in the other thread.
When watchdog is on, it reboots.
Please work with us in this issue.
Is 008 still the current firmware?the recent betas [ eg 6.44beta20 ] allow for upgrade of the lte card's firmware in RBwAPR-2nD&R11e-LTE,
What is the Capsman-part of this?*) wireless - added option to disable PMKID for WPA2;
Scripts can read the log! See https://wiki.mikrotik.com/wiki/Manual:S ... _log_entryBut this is not available to scripts, no? Perhaps you should add a read-only property "pending-upgrade". A scheduled script could look like this:
Will you please also release a fix for 6.36.4 as it is the only version which works with my wireless-devices?v6.38.5 has just been released, with vulnerabilities closed. Everyone please upgrade.
OK, sorry... this one i missed ...!notToNew - This is from 6.37 changelog:
"check-for-updates - with two or more standalone wireless packages, will result in no wireless packages installed, uninstall extra packages first;"
Not good that you stopped supporting 6.36.x and replaced it with 6.37.4!! Not at all!Stay at 6.36.4 or disable encryption in newer releases as workaroundwireless still broken. my old phone Lenovo A660 can't connect to AP after 6.37 migration anymore.
Stay at 6.36.4 or disable encryption in newer releases as workaroundwireless still broken. my old phone Lenovo A660 can't connect to AP after 6.37 migration anymore.
How? Ist it now allowed again?Version 6.38rc49 has been released.
*) wireless - fixed upgrade from older wireless packages when AP interface had empty SSID;
I ssee the same on 6.36.4, so i wonder why 6.37.3 is working... didn' test this version.On the AP 951G-2HnD, it would report a management protection error, but after disabling management protection the connection would still brief disconnects.
This is a known problem with new wireless-package. only old wireless-cm2 works with some legacy-devices.Old (2.3.6) android smart cannot connect via wifi, connect\disconnect in one second.
Does this version exist? I know 6.36.3. I would be interested in this aswell, as i cann't upgrade to 6.37 because of wireless-issues.However, I managed to downgrade to 6.36.4 ...
As i mentioned, I have this checked(activated) but still cannot see the comments in this window, other windows show the comments just as expected!notToNew:
Winbox SETTINGS / INLINE COMMENTS (above Safe Mode on your screen)
+1. This would allow me to sync it to several desktopsplease make windows winbox version working folder to be the same where winbox.exe exists. why we have to mess with "user\appdata\roaming" folder?
Hm, that's quiet annoying. It was stable before... Is there any workaround?benesm1 - Winbox disconnects will be fixed in upcoming Winbox versions.
And just because of this you think you can not run your devices?
Hi, I think, this ist the better place for dude-postings: http://forum.mikrotik.com/viewtopic.php?f=8&t=110424Hello,
I've some features requests (don't know if this is the right place to post them):
See the new http://wiki.mikrotik.com/wiki/Manual:Packet_Flow_v6.can anyone tell me that how to use RAW tab in firewall.
Same here... router was not accessible after upgrade because of this. I had to write a script to manually add all interface-lists from a rc38 backup-file again.After the update: add action=accept chain=input in-interface-list="" log-prefix=""
Nice!!!Version 6.36rc16 has been released.
*) firewall - allow to add domain name to address-lists (dynamic entries for resolved addresses will be added to specified list);
I have one as welljondavy - Please provide an example of export which you are not being able to import afterwards
#line 1407 + 1408 set cpu-frequency=650MHz init-delay=0s memory-frequency=300MHz \ expected end of command (line 1 column 26)
simply didn't understand this function! Thanks a lot for pointing me there, i will try it!!!Why not use the existing wireless "connect list" feature ?
Right! Current RC-Branch should go to "development"...Then they are not RC. Similar naming problem as "Current".
Can reproduce this with 6.35rc31 on Basebox2. Switched back to WIRELESS-CM2 as well.I use 6.35rc26 wireless-rep (AP mode), my laptop (WIN7 INTEL wireless 5300AGN) had a lot of PING loss, when I changed to WIRELESS-CM2, everything is normal.