huh, is that to fix those annoying errors?..*) l2tp, pptp, pppoe - fixed possible packet corruption when encryption was enabled;
jul/15/2014 22:46:10 ppp,error,critical 25585: Encryption got out of sync - disabling
jul/16/2014 13:56:11 ppp,error,critical 45075: Encryption got out of sync - disabling
any details?*) latency improvements on CCR devices;
I can confirm that. Igmp proxy stops to forward multicast traffic after upstream interface goes down/up. RB2011, ROS 6.16. Upstream inteface on RB2011 is on port 1...IGMP proxy is still broken!
yes, wireless-fp replaces the regular package, this is why regular gets disabledShoould i use wireless or wirless-fp package on RB2011UiAS-2Hnd?
Once I enable wireless-fp and reboot wireless goes to disable state.
Is that OK ?
BTW: I tried to upgrade also the CCR1016-12G (connected on the other end of the cable). This one works correctly (the 1016), but the ports on the 1009 keep flapping. I already tried to reset and re-apply configuration, I tried net-install and I tried it on another 1009, the results are the same. Need to revert back to 6.15.It happens on ports 5 and 7, routed ports, with a straight configuration: one ip address and ospf configured (so yes, the router makes some traffic when the cable is connected). On the other side there is a CCR1016-12G.are they switched? did you send an traffic, or just connect the cable to somewhere (where)?
Simply because on same user used to access webfig, by winbox, you can be able to create script with full right.Clarify why is this important?
It is not a bug, but lack of feature due to security.
Why would you need these permissions in the GUI editor?
HomeVPN is only in HomeAP mode of the Quickset.Where is 6.17, not on downloads page, also can not find VPN wizard in 6.16 as claimed in newsletter
Yes, we have added "Use IPsec" option to L2TP server, so basically you will be able to do the same. IPsec will now become simple, and your tunnels — much more secure.Nice feature with this "fast vpn" setup. Is it possible to enable fast and easy from either command prompt or winbox regardless of quickset?
I use this for enabling L2TP+IPSEC and it works. If IPSEC fails for some reason, it still connects the l2tp tunnel, so you running an unencrypted VPN and maybe didnt't notice it. Other implementation for example Softether, deny L2TP connection if IPSEC fails, so you notice that something is wrong.Yes, we have added "Use IPsec" option to L2TP server, so basically you will be able to do the same. IPsec will now become simple, and your tunnels — much more secure.Nice feature with this "fast vpn" setup. Is it possible to enable fast and easy from either command prompt or winbox regardless of quickset?
thanks for suggestion, we will think of somethingIf IPSEC fails for some reason, it still connects the l2tp tunnel, so you running an unencrypted VPN and maybe didnt't notice it.
I can confirm that the issue with CCR1009 routers is fixed on 6.17.We just published v6.17, which includes CCR1009 fix for port issues that caused crash. No other changes included, thanks everybody for quick reports that allowed us to immediately release a fix!
Release Notes RouterBOOT Do not update?What´s new in routerboot 3.18 ?
I know --> support for new AC products.
But another changes?
Please update old changelog on wiki - http://wiki.mikrotik.com/wiki/RouterBOOT_changelog
It fixes the problem when router could not come back after upgrade from v5 to v6Release Notes RouterBOOT Do not update?What´s new in routerboot 3.18 ?
I know --> support for new AC products.
But another changes?
Please update old changelog on wiki - http://wiki.mikrotik.com/wiki/RouterBOOT_changelog
I want to know what's changed for the time being.
Have you made a support ticket with support@mikrotik.com?I've been sticking with 6.7 because of issues with SSTP and Windows clients - can anyone confirm if these problems are fixed? I know that both reliability and performance issues were noted by other users with SSTP + Windows.
This means Changelog was not readable, the version will install just fine. You probably clicked the button when I was updating the Changelog. Try again, it should work.Hello,
Just FYI:
Maybe there is problem with installing update directly from winbox (system > packages > check for updates) = Err: File not found
Thank you
There's still problem with updating from Winbox.This means Changelog was not readable, the version will install just fine. You probably clicked the button when I was updating the Changelog. Try again, it should work.
Should be fixed nowThere's still problem with updating from Winbox.This means Changelog was not readable, the version will install just fine. You probably clicked the button when I was updating the Changelog. Try again, it should work.
Tested it on CRS125-24G-1S-2HnD and 2011UiAS - both report ERROR: file not found, when trying to Check for updates.
This issue is still there, i switched everything to l2tp+ipsec because of this issue.I've been sticking with 6.7 because of issues with SSTP and Windows clients - can anyone confirm if these problems are fixed? I know that both reliability and performance issues were noted by other users with SSTP + Windows.
You are kidding?Where are the instructions for 802.11ac? I installed this on some rb711's and some rb911gs and I dont see an option for it. Do these boards not support this?
If not for anything else, at the very least for consistency's sake. Is that not enough of a reason?Clarify why is this important? It is not a bug, but lack of feature due to security. Why would you need these permissions in the GUI editor ?THIS BUG ALREADY SIGNALED ON 6.12 STILL PRESENT AND NOT SOLVED:
Primary BUG: Webfig created script or schedule do not have ftp, winbox, api rights and are impossible to set that rights on Webfig
Secondary BUG: Winbox do not have the possibility to change ftp, winbox, api rights on script or schedule
VERSION AFFECTED: ALL VERSION OF ROUTEROS where webfig are present.
When one script are created on Winbox or on CLI, the default right applied are:
ftp,reboot,read,write,policy,test,winbox,password,sniff,sensitive,api
But when the script are created by webfig, the only right can be applied are:
reboot,read,write,policy,test,password,sniff,sensitive
MISSING ftp,winbox,api
Without ftp right some command like "/export file=filename;" are not doable on script / schedule created with WebFig.
Walkthrought: obviously using the CLI you can set the missing rights.
Is clear what is the problem, without any other investigation.
You are kidding?Where are the instructions for 802.11ac? I installed this on some rb711's and some rb911gs and I dont see an option for it. Do these boards not support this?
Are you using SSTP between RouterOS or do you have Windows/other Clients/Servers?Our sstp vpn is extremely stable on 6.15...
Its better to always backup the current configuration and download it in case the update fails and a downgrade or reinstallation in needed.I upgraded one of my core routers (x86 type) to 6.17 yesterday and this morning I had no routes to anything plugged into that router. Evidently OSPF was not redistributing static & connected. Once I rebooted it was working. However I did revert back to 6.15 as that I have had no issues with that version for my applications. Now for the biggest irritation, When I downgraded if deleted everything and I mean everything in IPsec. I have no peers, profiles nothing. So use caution if you downgrade and you are using IPsec.
The routers I upgraded are used for testing various things out. This post was made to enlighten other Mikrotik users or support staff about possible issues or bugs regarding 6.17 and in no way am I whining about blindly upgrading and then experiencing issues doing so. With over 1000 Mikrotik routers in the field I can assure you we upgrade any critical routers prior to upgrading.Its better to always backup the current configuration and download it in case the update fails and a downgrade or reinstallation in needed.I upgraded one of my core routers (x86 type) to 6.17 yesterday and this morning I had no routes to anything plugged into that router. Evidently OSPF was not redistributing static & connected. Once I rebooted it was working. However I did revert back to 6.15 as that I have had no issues with that version for my applications. Now for the biggest irritation, When I downgraded if deleted everything and I mean everything in IPsec. I have no peers, profiles nothing. So use caution if you downgrade and you are using IPsec.
The routers I upgraded are used for testing various things out. This post was made to enlighten other Mikrotik users or support staff about possible issues or bugs regarding 6.17 and in no way am I whining about blindly upgrading and then experiencing issues doing so. With over 1000 Mikrotik routers in the field I can assure you we upgrade any critical routers prior to upgrading.Its better to always backup the current configuration and download it in case the update fails and a downgrade or reinstallation in needed.I upgraded one of my core routers (x86 type) to 6.17 yesterday and this morning I had no routes to anything plugged into that router. Evidently OSPF was not redistributing static & connected. Once I rebooted it was working. However I did revert back to 6.15 as that I have had no issues with that version for my applications. Now for the biggest irritation, When I downgraded if deleted everything and I mean everything in IPsec. I have no peers, profiles nothing. So use caution if you downgrade and you are using IPsec.
To: AndriysTo sdugoten:
The content you're matching against is a part of a URL you're connecting to, and thus is included in only a single packet withing the whole connection. You need to mark a connection with your content-matching rule first, then mark routing based on the connection mark you assigned previously.
As far as I understand, only the articles listed here can be considered an official Mikrotik documentation. The rest of the wiki is, generally, user-driven. Anyone can get a write-enabled account by writing to support@. The document you're referring to is not written by a Mikrotik employee, but rather someone who claims to be a Mikrotik certified trainer/consultant (see document history here).I am just following the official document here. http://wiki.mikrotik.com/wiki/Policy_Base_Routing.
Hmm...it seems only the people within the administrator group can grant people edit right on the wiki. So, I would assume people who get the access grant by the administrator would write something that is at least "correct" and cross check by Mikrotik support in order to put it on wiki. If not, why the administrator granting the access in the first place if those information is wrong on a "mikrotik.com" domain. If the information is not meant to be cross checked by Mikrotik, then they would have open the account creation for everyone else without Administrator granting access.As far as I understand, only the articles listed here can be considered an official Mikrotik documentation. The rest of the wiki is, generally, user-driven. Anyone can get a write-enabled account by writing to support@. The document you're referring to is not written by a Mikrotik employee, but rather someone who claims to be a Mikrotik certified trainer/consultant (see document history here).I am just following the official document here. http://wiki.mikrotik.com/wiki/Policy_Base_Routing.
Anyways, I think the article you're referring to is wrong. Connection marking is mandatory in your case.
Please use Netinstall to reinstall RouterOS, this should fix it.Hello, I upgraded one CCR1036 6.2 to 6.17 for just last night. Now, the router does not keep the password anymore. After a short period of time to set the new password, it is in default (blank).
same problem, solve this urgent
Please clarify, what is wrong in your image?The same thing shed reported little earlier (http://forum.mikrotik.com//viewtopic.ph ... ff#p437480) occuring on different HW.
Any ideas why?
Multiple "ipsec,warning,critical" "phase 1 negotiation failed due to time up." log entries.Please clarify, what is wrong in your image?The same thing shed reported little earlier (http://forum.mikrotik.com//viewtopic.ph ... 7d#p437480) occuring on different HW.
Any ideas why?
this is already solved in 6.16 without reinstall. my suggestion was for this person specifically, as it seems he has some sort of other issueCan people with OSPF issues please send in support files?
We use OSPF and now with 2 reports of the same symptoms, I'm not touching the new version.
Also normis, netinstall is not an option for the majority of our units, how do we fix the problem with passwords going blank? Will this be solved on the next revision?
A while back I had a similar issue, turned out that clearing the browser cache fixed it. Guessing it had cached some older javascript that was invoking the login API in a deprecated fashion.Upgraded from 6.4 to 6.17 and Winbox and Webfig (http and https on nonstandard ports) both hang on connect. Logs say I have logged in successfully. I can SSH fine.
[admin@master] > /system routerboard print
routerboard: yes
model: CCR1016-12G
serial-number: 42D502D13F33
current-firmware: 3.09
upgrade-firmware: 3.18
yeah don't upgrade. I too am in this boat and downgrading is a real pain in the a$$ with 6.17 as IPsec wont downgrade right below 6.17 and you have to do a dance to get things back to normal. Think of it like this: Mikrotik lives on the bleeding edge. version 5 is considered the stable 6.4 is beta and 6.5+ is alphaMy log is flooded with "negotiation failed due to time up" and my IPSec site-to-site VPN's are unstable now.
Anything that I can do to help this?
regular Winbox is included in RouterOS. open IP address in your browser, and click on "WInbox"Anyone noticing copy and paste issues with the new winbox? And why in the hell is not there a choice between the stable winbox and the beta in the download area?
Thanks Normis.regular Winbox is included in RouterOS. open IP address in your browser, and click on "WInbox"Anyone noticing copy and paste issues with the new winbox? And why in the hell is not there a choice between the stable winbox and the beta in the download area?
+1yeah don't upgrade. I too am in this boat and downgrading is a real pain in the a$$ with 6.17 as IPsec wont downgrade right below 6.17 and you have to do a dance to get things back to normal. Think of it like this: Mikrotik lives on the bleeding edge. version 5 is considered the stable 6.4 is beta and 6.5+ is alphaMy log is flooded with "negotiation failed due to time up" and my IPSec site-to-site VPN's are unstable now.
Anything that I can do to help this?
>ip proxy cache-contents print
I'm requesting.We already made some IPsec fixes in v6.18rc3 which is available for testing upon request.
14:06:18 interface,info ether1 link down
14:06:20 interface,info ether1 link up (speed 100M, full duplex)
14:08:40 interface,info ether1 link down
14:08:41 interface,info ether1 link up (speed 100M, full duplex)
14:08:44 interface,info ether1 link down
14:08:48 interface,info ether1 link up (speed 100M, full duplex)
14:09:17 interface,info ether1 link down
14:09:18 interface,info ether1 link up (speed 100M, full duplex)
16:09:54 interface,info ether1 link down
16:10:00 interface,info ether1 link up (speed 100M, full duplex)
16:10:24 interface,info ether1 link down
16:10:25 interface,info ether1 link up (speed 100M, full duplex)
16:10:26 interface,info ether1 link down
16:10:31 interface,info ether1 link up (speed 100M, full duplex)
16:23:37 interface,info ether1 link down
16:23:42 interface,info ether1 link up (speed 100M, full duplex)
20:46:39 interface,info ether1 link down
20:46:40 interface,info ether1 link up (speed 100M, full duplex)
20:47:29 interface,info ether1 link down
20:47:30 interface,info ether1 link up (speed 100M, full duplex)
20:48:15 interface,info ether1 link down
20:48:17 interface,info ether1 link up (speed 100M, full duplex)
20:51:28 interface,info ether1 link down
20:51:30 interface,info ether1 link up (speed 100M, full duplex)
20:57:31 interface,info ether1 link down
20:57:33 interface,info ether1 link up (speed 100M, full duplex)
21:09:17 interface,info ether1 link down
21:09:19 interface,info ether1 link up (speed 100M, full duplex)
21:09:29 interface,info ether1 link down
21:09:31 interface,info ether1 link up (speed 100M, full duplex)
22:17:12 interface,info ether1 link down
22:17:13 interface,info ether1 link up (speed 100M, full duplex)
tryd whitout auto negotiation?I upgraded one Omnitik from ROSv6.12, firmware 3.10, to ROSv6.17, firmware 3.17, wireless-fp enabled. I'm noticing port flapping. Omnitik is through ether1 connected to RB493G, which has ROSv5.26, firmware 3.07.
Auto Negotiation is enabled. Tx/RX Flow Control is off. In Advertise (10M half, 10M full, 100M half, 100M full,...) everything is checked. These are the default Mikrotik settings.
Are there some problems in the communication between these ROS versions?
I am interested, since we have major issues with reproducible issues and what seems to be random issues with IPsec.We already made some IPsec fixes in v6.18rc3 which is available for testing upon request.
We have now added it to the regular download page:I am interested, since we have major issues with reproducible issues and what seems to be random issues with IPsec.We already made some IPsec fixes in v6.18rc3 which is available for testing upon request.
the link routeros-mipsbe-6.18rc.npk point to file routeros-x86-6.18rc.npkWe have now added it to the regular download page:I am interested, since we have major issues with reproducible issues and what seems to be random issues with IPsec.We already made some IPsec fixes in v6.18rc3 which is available for testing upon request.
http://www.mikrotik.com/download
see the signal i am getting in V1.7 how can i read the bars????
[admin@AI5926CX] /system routerboard> print
routerboard: yes
model: 411U
serial-number: 28DB012DC0E8
current-firmware: 3.18
upgrade-firmware: 3.18
[admin@AI5926CX] > /system watchdog print
watch-address: 8.8.8.8
watchdog-timer: no
no-ping-delay: 10m
automatic-supout: yes
auto-send-supout: no
[admin@AI5926CX] > /system clock print
time: 18:22:01
date: jul/25/2014
time-zone-name: Europe/Kiev
gmt-offset: +03:00
dst-active: yes
[admin@AI5926CX] > /log print follow where topics~"watchdog" or topics~"ppp"
18:22:50 async,ppp,info ppp-outIT: terminating... - hungup
18:22:50 async,ppp,info ppp-outIT: disconnected
18:23:00 async,ppp,info ppp-outIT: initializing...
18:23:00 async,ppp,info ppp-outIT: reseting link...
18:23:00 async,ppp,info ppp-outIT: reseting link... - could not acquire serial port
18:23:00 async,ppp,info ppp-outIT: disconnected
18:23:10 async,ppp,info ppp-outIT: initializing...
18:23:10 async,ppp,info ppp-outIT: reseting link...
18:23:10 async,ppp,info ppp-outIT: reseting link... - could not acquire serial port
18:23:10 async,ppp,info ppp-outIT: disconnected
18:23:20 async,ppp,info ppp-outIT: initializing...
18:23:20 async,ppp,info ppp-outIT: reseting link...
18:23:20 async,ppp,info ppp-outIT: reseting link... - could not acquire serial port
18:23:20 async,ppp,info ppp-outIT: disconnected
18:23:30 async,ppp,info ppp-outIT: initializing...
18:23:30 async,ppp,info ppp-outIT: reseting link...
18:23:30 async,ppp,info ppp-outIT: reseting link... - could not acquire serial port
18:23:30 async,ppp,info ppp-outIT: disconnected
18:23:40 async,ppp,info ppp-outIT: initializing...
18:23:40 async,ppp,info ppp-outIT: reseting link...
18:23:40 async,ppp,info ppp-outIT: reseting link... - could not acquire serial port
18:23:40 async,ppp,info ppp-outIT: disconnected
18:23:46 watchdog,error,critical watchdog cannot ping address 8.8.8.8, rebooting
18:23:50 async,ppp,info ppp-outIT: initializing...
18:23:50 async,ppp,info ppp-outIT: reseting link...
18:23:50 async,ppp,info ppp-outIT: reseting link... - could not acquire serial port
18:23:50 async,ppp,info ppp-outIT: disconnected
-- Ctrl-C to quit. Space prints separator. New entries will appear at bottom.
echo: watchdog,error,critical watchdog cannot ping address 8.8.8.8, rebooting
/system routerboard upgrade skip-confirmation=yes;
/tool user-manager database clear skip-confirmation=yes;
/tool user-manager database clear-log skip-confirmation=yes;
/tool user-manager database rebuild skip-confirmation=yes;
/system reboot skip-confirmation=yes;
/system reset-configuration run-after-reset=myfile.rsc skip-confirmation=yes;
/ip proxy reset-html skip-confirmation=yes;
/interface wireless reset-configuration;
please make an example where 'reboot' command is pasted from clipboard (not executed from script, where it asks nothing) and is not the last command that's what I meanIf you paste something from clipboard, the "y" sometime is unexpected and broken the rest of the pasted commands.
<...>
One simple example: on my maintenance script at the boot, if new bios version are available are updated and system rebooted before script go further, at reboot script continue (because are scheduled at the boot and the bios is already updated).
Then just describe basically what is that script of yours supposed to do (no specifics or actual code), and why would you (realistically) want to not have the reset be the last thing in there.I do not want reply because if i do that I show my script, and I do not want disclose it to any.
*** Check what version of initialization script used to first time program the CPE and accordingly what version are found, reset configuration with running new .rsc script OR if are more recent version simply change some value on configuration. If the bios on RouterOS are more recent than the bios onboard, first of all upgrade and then reboot, after reboot continue the script (run again) ***Then just describe basically what is that script of yours supposed to do (no specifics or actual code), and why would you (realistically) want to not have the reset be the last thing in there.I do not want reply because if i do that I show my script, and I do not want disclose it to any.
I think the Chupaka questions derail the sense of the request.One simple example: on my maintenance script at the boot, if new bios version are available are updated and system rebooted before script go further, at reboot script continue (because are scheduled at the boot and the bios is already updated).
/system scheduler add name="SETTER" interval=1s on-event={
/system scheduler remove "SETTER"
/system reboot
}
/system scheduler add name="SETTER" interval=1s on-event={
/system scheduler remove "SETTER"
#Your script here
}
Why must be find everytime one walktrought instead obtaining one simpe solution from mikrotik?Reboot, reset... whatever...
You can easily wrap your copy&paste script into a scheduler even that is 1s away, and the first thing it does is to remove itself. That way, you're executing everything, and not even leaving a trail. This includes reboots, and I'm pretty sure it would work for a reset as well.
e.g.or more generallyCode: Select all/system scheduler add name="SETTER" interval=1s on-event={ /system scheduler remove "SETTER" /system reboot }
Technically, there's also the "execute" command, which doesn't involve adding a self removing item, but it requires the script as a string, meaning it's less convenient for the most part.Code: Select all/system scheduler add name="SETTER" interval=1s on-event={ /system scheduler remove "SETTER" #Your script here }
It really depends on how easy and generic the supposed workaround is, and ideally, that should dictate the priority of feature additions and fixes.Another example is "toip" for convert one "1.2.3.4/32" as string toip not work, and toipprefix not exist,
must be used again another fantasious method instead to have toip working as expected:
http://forum.mikrotik.com/viewtopic.php ... 85#p438947
The language used for Scripting are mikrotik proprietary and I'm not expecting anything more what I can do, but I ask just for fix ALREADY existent functions, not add new, like decimal numbers or read more than 4096 characters on file.
Are present static leases or only dynamic?While upgrading from v6.15 to v6.17.
IP / DHCP Server - Leases list is all gone .. (Leases list is removed)
RB2011UAS / RB2011UiAS / RB750GL / RB450G was all the same problem
For me it is a serious problem.
Monday tomorrow, we hope not only no problems at suppliers.
I read again and once more. And I can't find why.You keep on this type of statistic?
Is like you do not read the change log, or better, you do not understand the change log.
Read again and you find why.
Have the same problem on 435G. Additionally, the list disappeared after accidental power failure. And when I try to make a backup:While upgrading from v6.15 to v6.17.
IP / DHCP Server - Leases list is all gone .. (Leases list is removed)
RB2011UAS / RB2011UiAS / RB750GL / RB450G was all the same problem
error creating backup file: could not read all configuration files
Only a dynamic leases.Are present static leases or only dynamic?While upgrading from v6.15 to v6.17.
IP / DHCP Server - Leases list is all gone .. (Leases list is removed)
RB2011UAS / RB2011UiAS / RB750GL / RB450G was all the same problem
For me it is a serious problem.
Monday tomorrow, we hope not only no problems at suppliers.
Simply put back from backup. Yu have backup, right?
perfect!Technically, there's also the "execute" command
execute "/system reboot"
Saving time each 10 min (?) on boardI read again and once more. And I can't find why.You keep on this type of statistic?
Is like you do not read the change log, or better, you do not understand the change log.
Read again and you find why.
May be, can you specify the reason?
Thanks for the info!perfect!Technically, there's also the "execute" commanddoes not ask for confirmation! so, to skip confirmation, one should replace '$command' with 'execute "$command"'Code: Select allexecute "/system reboot"
Apply (restore) previous backup over the existing configuration, then try to make a new backup.Have the same problem on 435G. Additionally, the list disappeared after accidental power failure. And when I try to make a backup:Code: Select allerror creating backup file: could not read all configuration files
I went back to v. 6.15 on this device. In addition to downgrade ROS I had to downgrade RouterBoard firmware too, because the problem persists. I'll wait for a better version.Apply (restore) previous backup over the existing configuration, then try to make a new backup.
Or reset the configuration first, and then apply previous backup.
That worked in my case.
what exactly doesn't work? what do you check, what do you expect to see and what results do you actually see?But still now transparent web proxy doesn't work in both 6.15 & 6.17
Watchdog address is not the same as Watchdog timer. What you see is a reboot because of kernel crash. This is also done by watchdog, and can't be disabled.New feature?
Watchdog timer is disabled, but the router still reboots on watchdog timer.
In version 6.15 I was not able to configure transparent web-proxy to show this login page: http://www.samplecomponents.com/scripts ... ll?hittitewhat exactly doesn't work? what do you check, what do you expect to see and what results do you actually see?But still now transparent web proxy doesn't work in both 6.15 & 6.17
what were your steps to do that? we're not telepathists. what do you mean saying 'to show this page'? all pages were opening normally, and that only page didn't work?In version 6.15 I was not able to configure transparent web-proxy to show this login page: http://www.samplecomponents.com/scripts ... ll?hittite
24 hours. On all devices. Always.Saving time each 10 min (?) on boardI read again and once more. And I can't find why.You keep on this type of statistic?
Is like you do not read the change log, or better, you do not understand the change log.
Read again and you find why.
May be, can you specify the reason?
So what? It is a bug or a feature?New feature?
Watchdog timer is disabled, but the router still reboots on watchdog timer.
And it does not wait for 10 minutes, and may restart in 30 seconds.
I already answered a few posts aboveSo what? It is a bug or a feature?New feature?
Watchdog timer is disabled, but the router still reboots on watchdog timer.
And it does not wait for 10 minutes, and may restart in 30 seconds.
what were your steps to do that? we're not telepathists. what do you mean saying 'to show this page'? all pages were opening normally, and that only page didn't work?In version 6.15 I was not able to configure transparent web-proxy to show this login page: http://www.samplecomponents.com/scripts ... ll?hittite
/ip proxy
set cache-administrator=it@test.com cache-on-disk=yes enabled=\
yes max-cache-size=none max-fresh-time=1w
/ip proxy access
add action=deny comment="block telnet & spam e-mail relaying" disabled=yes \
dst-port=23-25
add action=deny comment=\
"allow CONNECT only to SSL ports 443 [https] and 563 [snews]" dst-port=\
!443,563 method=CONNECT
what exactly doesn't work? what do you check, what do you expect to see and what results do you actually see?But still now transparent web proxy doesn't work in both 6.15 & 6.17
It's not count any packet.and what about your Mangle rule? does it count packets?
I read your answer, but later than the written message.I already answered a few posts above
With this, I understood everything. Thank you.ping watchdog is enabled by setting an IP address. remove IP address - ping watchdog will be disabled. watchdog-timer is about hardware watchdog
I've now updated some 150 units. Most from 6.15 to 6.17, some from 6.13 or even 6.10. Out of these 150 some 5-7 lost their config.Cool, on some routers disapeared configuration after update. Firmwares more and more worse from version to version.
Well, let's see. But for the 'dead' units it will be too late. They have to be send back I'm afraid. There is no way I can login to these. Winbox nor Telnet 'sees' the units anymore. (I'm referring 2 grooves now. They both worked and only passed away after the remote upgrade fm 6.15 toward 6.17).We have found some issue in mips-be that could fix your issue, Rudy. Please wait until tomorrow until we have something to test.
Netinstall should be able to revive them. If not, maybe you have some other issue with themWell, let's see. But for the 'dead' units it will be too late. They have to be send back I'm afraid. There is no way I can login to these. Winbox nor Telnet 'sees' the units anymore. (I'm referring 2 grooves now. They both worked and only passed away after the remote upgrade fm 6.15 toward 6.17).We have found some issue in mips-be that could fix your issue, Rudy. Please wait until tomorrow until we have something to test.
I still have to test 2 SXT's I believe, they are on their way to me..
Both the 2 Groove's I had the issue were actually running fine and delivering internet to the client.Netinstall should be able to revive them. If not, maybe you have some other issue with themWell, let's see. But for the 'dead' units it will be too late. They have to be send back I'm afraid. There is no way I can login to these. Winbox nor Telnet 'sees' the units anymore. (I'm referring 2 grooves now. They both worked and only passed away after the remote upgrade fm 6.15 toward 6.17).We have found some issue in mips-be that could fix your issue, Rudy. Please wait until tomorrow until we have something to test.
I still have to test 2 SXT's I believe, they are on their way to me..
hmm, strange. But yeah, I also started it when it came out. It is only the last days we find some units are giving the problems. Doesn't mean the problem wasn't there before. It just didn't surface yet. I am not monitoring all clients. Some units might not be seen because they are down but I only react when the client calls. Many client switch their stuff off so If I can see or not see the CPE is not always a proof it is down.I still upgrade all my devices with last 3.17/3.18 BIOS and RouterOS 6.17,
I'm doing that from the day is out,
NO ONE SINGLE PROBLEM,
I'm a WISP and I have updated/upgraded almost 400 mipsbe devices and 10 ppc (RB1xxx) without any problem.
I have near all models on production environment, from RB411 to QRT-5,
the only devices I do not have are mipsle and tilera models.
Yes, I can. Or; yes I have. Watchdog is enabled but without IP for test.When you update/upgrade the board, can you add watchdog?
I tried from AP side; mac-ping... no reply, ping.... no reply, mac telnet... disconnected, telnet ... no reply,>>>...It is just not able to reach by any telnet or winbox session...<<<
And by MAC telnet on winbox -> AP -> ip/neighbors list?
We have lost 2 devices out of 50 after upgrading to 6.15. Then we stopped upgrading to 6.15. May be this problem persist for a while now. The devices are completely inaccessible. They have ethernet link but no neighbor discovery packets arive and mac-telnet do not work either. Not sure it was 6.15 or the firmware. One Omnitik and one RB411AH.I tried from AP side; mac-ping... no reply, ping.... no reply, mac telnet... disconnected, telnet ... no reply,>>>...It is just not able to reach by any telnet or winbox session...<<<
And by MAC telnet on winbox -> AP -> ip/neighbors list?
Then we tried with laptop from ethernet end. (By technician that doesn't know as much as me...) But winbox doesn't even 'see' it. We tried to contact it to its default ethernet IP address (after setting laptop to manual IP in same network) but no reply neither.
Laptop was also not getting IP address from CPE dhcp-server on the lan.
But symbols and lights on devices do notice the connection.
Later on my desk tried all the same from the ethernet end, no way.... just no response whatsoever, even not after 20 mins. (sometimes we have troubled units that only come up after long, long time..)
I didn't try via neighbor list from AP's end when unit was still 'visible' in the reg list but not responding. Since a power cycle mostly helps with 'stalled' radios, the standard is to do a power cycle first. Usually it solves the issue, but now it just stayed completely inaccessible. Off course it was too late than for the neighbor method.
I have confirmed this on Safari and FireFox after I upgraded two SXT-AC units. Has this been confirmed as a bug?Changing profiles in quickset you get a warning that you could loose connectivity, no matter what i answer it just pops back to my original quickset profile.
Running Chromes and windows 7.