I could see the same thing on a "startup" script. It didn't work as well.scheduler is not working.
Yes. Let us choose to turn it on or off.Please, add a checkbox for turning off these dummy statistic rules for FastTrack. I don't understand, why do we need them, since we have this counter on IP - Settings.
I find them very useful. Imagine situation when you need to connect to some unknown router and configure mangle and queue tree, you start mangling, but rules doesn't see the traffic, you have no idea why, cause you can see traffic on interface ....Why even those dummy rules? Put the values to the real rules correctly !
I also saw issues with scheduled scripts not running and Netwatch scripts not executing on down/up. Has anyone else had this problem? I'm using rc23rc23 should fix scheduler, it is in the download page already
did you wrote an email to support like i suggested in othre topic?What about broken Simple Queues in Bridge configuration? 6.30rc22 (from 6.29, 6.30rc19,...)
http://forum.mikrotik.com/viewtopic.php ... 00#p488000
http://forum.mikrotik.com/viewtopic.php ... 90#p487990
It seems completely NO firewall, but IP Firewall box in Bridge Settings checked (screenshots).
All features worked OK until 6.27 .
It's not. I saw this error until rc23. The test client is a macbook pro with gigabit wired connection to pptp server. On debian server there is no problem.MikroTik RouterOS 6.30rc22 (c) 1999-2015 http://www.mikrotik.com/
jun/30/2015 11:49:08 ppp,error,critical pptp-vypervpn: Encryption got out of sync - disabling
jun/30/2015 11:58:38 ppp,error,critical pptp-vypervpn: Encryption got out of sync - disabling
jun/30/2015 13:58:10 ppp,error,critical pptp-vypervpn: Encryption got out of sync - disabling
jun/30/2015 15:35:52 ppp,error,critical pptp-vypervpn: Encryption got out of sync - disabling
Not sure if the Encryption out of sync is fixed yet...
Jul 1 11:07:11 router.domain.com dns,packet <1.2.3.4.in-addr.arpa:PTR:2981=host1234*.omkc.ru>
Jul 1 11:07:11 router.domain.com dns,packet --- got query from 192.168.1.11:33391:
Jul 1 11:07:11 router.domain.com dns,packet id:5e68 rd:1 tc:0 aa:0 qr:0 ra:0 QUERY 'no error'
v6.30rc24 is available now.@emils
Thank you for your update but ...
When should we expect the newest version rc24?
Does this mean that 6.29 has a known bug with leap second? That might explain why both our CCR crashed tonight.Of course, 6.30 will not be released until NTP package problem with Leap Second on CCR will be fixed.
yes, all RouterOS versions are affected if you use NTP package and CCR.Does this mean that 6.29 has a known bug with leap second? That might explain why both our CCR crashed tonight.Of course, 6.30 will not be released until NTP package problem with Leap Second on CCR will be fixed.
+1Trafficflow fix? 6.29 broke it, no egress + ingress netflows.
What exactly did you improve?"wireless - improve ac radio coexistence with other wireless clients" - what does it mean exactly?
maybe post your script in a new topic, 400 bad request is server telling your that the request is malformed.Hi,
I updated my RB951G to 6.30rc26 and now my DynDNS script fails,...I'm a beginner with Mikrotik, but debugging the script I saw that the /tool fetch command always return "Error 400 bad request".
I downgraded to 6.29.1 and works fine with the same script.
Regards!
May be developers trying to fix my [Ticket#2015063066000237] Fetch error on IPv6 url.maybe post your script in a new topic, 400 bad request is server telling your that the request is malformed.Hi, I updated my RB951G to 6.30rc26 and now my DynDNS script fails,...I'm a beginner with Mikrotik, but debugging the script I saw that the /tool fetch command always return "Error 400 bad request". I downgraded to 6.29.1 and works fine with the same script. Regards!
It is not made by MikroTik, so I can't say if it should work or not. The article is made by one of the forum users. I suggest to make a new thread, and maybe some Dyn user could help improve the script to be more compatibleMy script is the same that are in the Wiki:DynDns for RouterOS 6.x section.
Now come on Normis....It is not made by MikroTik, so I can't say if it should work or not. The article is made by one of the forum users. I suggest to make a new thread, and maybe some Dyn user could help improve the script to be more compatibleMy script is the same that are in the Wiki:DynDns for RouterOS 6.x section.
Yeah, in 6.30RCs scripts do not work.Now come on Normis....It is not made by MikroTik, so I can't say if it should work or not. The article is made by one of the forum users. I suggest to make a new thread, and maybe some Dyn user could help improve the script to be more compatibleMy script is the same that are in the Wiki:DynDns for RouterOS 6.x section.
it always is the users fault, isn´t it?
We too had problems with scripts.
Updating about 15 RB2011 from 6.29 (buggy as hell), to 6.30rc20, rc24 and later to rc26 (still buggy as hell), on all of them, the scripts stopped working.
On earlier versions, those ran without a problem for years.
Something clearly has changed.
saludos
Bernardo
/tool fetch address=members.dyndns.org src-path=$str mode=http user=$ddnsuser \
password=$ddnspass dst-path=("/DynDNS.".$ddnshost)
/tool fetch url=("http://members.dyndns.org".$str) user=$ddnsuser mode=http \
password=$ddnspass dst-path=("/DynDNS.".$ddnshost)
Normis any info about this changelog??What exactly did you improve?"wireless - improve ac radio coexistence with other wireless clients" - what does it mean exactly?
Improve performance or latency when both N and AC clients are connected?
It also improves with Nstreme and NV2 protocol?
How much?
+1Normis any info about this changelog??What exactly did you improve?"wireless - improve ac radio coexistence with other wireless clients" - what does it mean exactly?
Improve performance or latency when both N and AC clients are connected?
It also improves with Nstreme and NV2 protocol?
How much?
Neither!Normis any info about this changelog??What exactly did you improve?
Improve performance or latency when both N and AC clients are connected?
It also improves with Nstreme and NV2 protocol?
How much?
one post above yours shows how you can already do thisleave IP check and update URLs strings as variables
+Trafficflow fix? 6.29 broke it, no egress + ingress netflows.
we have released RC versions every day for a few weeks already.I would say, please release an RC-Final candidate file.
If people do not have any issues with it, then rename it and re-release it as 6.30.0 with no change other than the name.
That way whatever bugs are found are squashed before 6.30.0, and said backlash doesn't hit Mikrotik nearly as badly.
Other than that, what's the current changelog?
Just wondering... When RC is removed from version string... Is there any way to see it is not the final build? Perhaps adding a package property with incrementing build id would be of help.New build every few hours, RC is now removed, nearly ready to release. Any comments?
build time can be compared in "system packages". but yes, for the RC releases, currently we are not showing the build time, we will implement it for the download pageJust wondering... When RC is removed from version string... Is there any way to see it is not the final build? Perhaps adding a package property with incrementing build id would be of help.New build every few hours, RC is now removed, nearly ready to release. Any comments?
Probably it is there. But server gives "403 Forbidden", so looks file permissions are borked.where is wireless cm2 package for 6.30?
normis ..just a note: extra packages for x86 are missinghold on please, release procedure script went crazy
ERROR: missing wireless-cm2-6.30-mipsbe.npk
Dmitry, please read above posts before posting something.Where:
We had MPLS/LDP-Problems with 6.29.1. /32 Routes did not work.New build every few hours, RC is now removed, nearly ready to release. Any comments?
We have several customers who have working MPLS/LDP and it works for us too. My colleagues are at a loss, since we are unable to repeat any problems, and you have not provided us with any clear information, at least the supout.rif file would help.We had MPLS/LDP-Problems with 6.29.1. /32 Routes did not work.
:local i 0;
:if ([/ip firewall mangle get [find comment="wan0"] disabled]=false) do {
:set i 0; {:do {:set i ($i + 1)} while (($i < 5) && ([/ping 209.244.0.5 interval=500ms interface=ether1 count=1]=0))};
:if ($i=5 && [/ip firewall mangle get [find comment="wan0"] disabled]=false) do={:log info "wan0 down";
/ip firewall mangle set [find comment="wan0"] disabled=yes;
execute beeperdown}}
:if ([/ip firewall mangle get [find comment="wan0"] disabled]=true) do={
:set i 0; {:do {:set i ($i + 1)} while (($i < 5) && ([/ping 209.244.0.5 interval=500ms interface=ether1 count=1]=1))};
:if ($i=5 && [/ip firewall mangle get [find comment="wan0"] disabled]=true) do={:log info "wan0 up";
/ip firewall mangle set [find comment="wan0"] disabled=no;
execute beeperup}}
On 6.29 it disables/enables rule in mangle(where i do load balancing) and gives sound+log message when uplink stops working/starts working again.What exactly is not working in that script?
Maris informed me now. Thanks. I sent supout.rifs of the working routers after downgrading. I cant risk to upgrade again to provide supout of the problematic state. May be the problem is with mixed 6.15/6.29.1 routers. Dont know. But for sure there is a problem. The downgrade to 6.15 solved the problem and disabling LDP solved the problem, too.We have several customers who have working MPLS/LDP and it works for us too. My colleagues are at a loss, since we are unable to repeat any problems, and you have not provided us with any clear information, at least the supout.rif file would help.We had MPLS/LDP-Problems with 6.29.1. /32 Routes did not work.
But what exactly is not working in the code? You have to debug your script to find an error.
I added your script on my router and it shows syntax error at execute beeperdown. What exactly is beeperdown?
beeperdown
beeperup
:for i from=4000 to=2000 step=-500 do={
:beep frequency=$i length=50ms;
:delay 50ms;
}
:for i from=2000 to=4000 step=500 do={
:beep frequency=$i length=50ms;
:delay 50ms;
}
I replacedis that beeperdown script loaded as variable?
Otherwise :execute beeperdown is a syntax error and then of course the whole script is not going to run at all.
:execute command accepts "script" parameter which should be script source code not an unknown name.
execute
/system script run
Now official topic exists ..6.30 is out ..but Extra Packages for x86 item is not on download page.I know, see above Sorry about that. This is why official topic doesn't exist yet.
Okay, I think that I found the "bug" with "/tool fetch" command. In my initial script working on 6.29.1 I have the following command:
The above command doesn't works on 6.30rc28... then, I changed it for:Code: Select all/tool fetch address=members.dyndns.org src-path=$str mode=http user=$ddnsuser \ password=$ddnspass dst-path=("/DynDNS.".$ddnshost)
...and now it seems works on 6.30rc28Code: Select all/tool fetch url=("http://members.dyndns.org".$str) user=$ddnsuser mode=http \ password=$ddnspass dst-path=("/DynDNS.".$ddnshost)
I don't know if there are any problem with the "address" and "src-path" parameters on 6.30rcX...
Regards!
# Set needed variables
:local username yyyy
:local password xxxxx
:local hostname xxxx.dyndns.tv
:global dyndnsForce
:global previousIP
# print some debug info
:log info ("UpdateDynDNS: username = $username")
:log info ("UpdateDynDNS: password = $password")
:log info ("UpdateDynDNS: hostname = $hostname")
:log info ("UpdateDynDNS: previousIP = $previousIP")
# get the current IP address from the internet (in case of double-nat)
/tool fetch mode=http address="checkip.dyndns.org" src-path="/" dst-path="/dyndns.checkip.html"
:delay 1
:local result [/file get dyndns.checkip.html contents]
# parse the current IP result
:local resultLen [:len $result]
:local startLoc [:find $result ": " -1]
:set startLoc ($startLoc + 2)
:local endLoc [:find $result "</body>" -1]
:local currentIP [:pick $result $startLoc $endLoc]
:log info "UpdateDynDNS: currentIP = $currentIP"
# Remove the # on next line to force an update every single time - useful for debugging,
# but you could end up getting blacklisted by DynDNS!
#:set dyndnsForce true
# Determine if dyndns update is needed
# more dyndns updater request details http://www.dyndns.com/developers/specs/syntax.html
:if (($currentIP != $previousIP) || ($dyndnsForce = true)) do={
:set dyndnsForce false
:set previousIP $currentIP
:log info "$currentIP or $previousIP"
/tool fetch user=$username password=$password mode=http address="members.dyndns.org" \
src-path="nic/update?system=dyndns&hostname=$hostname&myip=$currentIP&wildcard=no" \
dst-path="/dyndns.txt"
:delay 1
:local result [/file get dyndns.txt contents]
:log info ("UpdateDynDNS: Dyndns update needed")
:log info ("UpdateDynDNS: Dyndns Update Result: ".$result)
:put ("Dyndns Update Result: ".$result)
} else={
:log info ("UpdateDynDNS: No dyndns update needed")
}
Any news? Anyone experiencing the issues that were in 6.29 and 6.29.1?+Trafficflow fix? 6.29 broke it, no egress + ingress netflows.
Hi,Okay, I think that I found the "bug" with "/tool fetch" command. In my initial script working on 6.29.1 I have the following command:
The above command doesn't works on 6.30rc28... then, I changed it for:Code: Select all/tool fetch address=members.dyndns.org src-path=$str mode=http user=$ddnsuser \ password=$ddnspass dst-path=("/DynDNS.".$ddnshost)
...and now it seems works on 6.30rc28Code: Select all/tool fetch url=("http://members.dyndns.org".$str) user=$ddnsuser mode=http \ password=$ddnspass dst-path=("/DynDNS.".$ddnshost)
I don't know if there are any problem with the "address" and "src-path" parameters on 6.30rcX...
Regards!
can you post full script ?
i try find and replace code but not working
that script i useCode: Select all# Set needed variables :local username yyyy :local password xxxxx :local hostname xxxx.dyndns.tv :global dyndnsForce :global previousIP # print some debug info :log info ("UpdateDynDNS: username = $username") :log info ("UpdateDynDNS: password = $password") :log info ("UpdateDynDNS: hostname = $hostname") :log info ("UpdateDynDNS: previousIP = $previousIP") # get the current IP address from the internet (in case of double-nat) /tool fetch mode=http address="checkip.dyndns.org" src-path="/" dst-path="/dyndns.checkip.html" :delay 1 :local result [/file get dyndns.checkip.html contents] # parse the current IP result :local resultLen [:len $result] :local startLoc [:find $result ": " -1] :set startLoc ($startLoc + 2) :local endLoc [:find $result "</body>" -1] :local currentIP [:pick $result $startLoc $endLoc] :log info "UpdateDynDNS: currentIP = $currentIP" # Remove the # on next line to force an update every single time - useful for debugging, # but you could end up getting blacklisted by DynDNS! #:set dyndnsForce true # Determine if dyndns update is needed # more dyndns updater request details http://www.dyndns.com/developers/specs/syntax.html :if (($currentIP != $previousIP) || ($dyndnsForce = true)) do={ :set dyndnsForce false :set previousIP $currentIP :log info "$currentIP or $previousIP" /tool fetch user=$username password=$password mode=http address="members.dyndns.org" \ src-path="nic/update?system=dyndns&hostname=$hostname&myip=$currentIP&wildcard=no" \ dst-path="/dyndns.txt" :delay 1 :local result [/file get dyndns.txt contents] :log info ("UpdateDynDNS: Dyndns update needed") :log info ("UpdateDynDNS: Dyndns Update Result: ".$result) :put ("Dyndns Update Result: ".$result) } else={ :log info ("UpdateDynDNS: No dyndns update needed") }
:global ddnsuser "theddnsusername"
:global ddnspass "theddnspassword"
:global theinterface "interfacename"
:global ddnshost blabla.dyndns.org
:global ipddns [:resolve $ddnshost];
:global ipfresh [ /ip address get [/ip address find interface=$theinterface ] address ]
:if ([ :typeof $ipfresh ] = nil ) do={
:log info ("DynDNS: No ip address on $theinterface .")
} else={
:for i from=( [:len $ipfresh] - 1) to=0 do={
:if ( [:pick $ipfresh $i] = "/") do={
:set ipfresh [:pick $ipfresh 0 $i];
}
}
:if ($ipddns != $ipfresh) do={
:log info ("DynDNS: IP-DynDNS = $ipddns")
:log info ("DynDNS: IP-Fresh = $ipfresh")
:log info "DynDNS: Update IP needed, Sending UPDATE...!"
:global str "/nic/update\?hostname=$ddnshost&myip=$ipfresh&wildcard=NOCHG&mx=NOCHG&backmx=NOCHG"
/tool fetch url=("http://members.dyndns.org".$str) user=$ddnsuser mode=http \
password=$ddnspass dst-path=("/DynDNS.".$ddnshost)
:delay 1
:log info "DynDNS: Data sent!"
:global str [/file find name="DynDNS.$ddnshost"];
/file remove $str
:global ipddns $ipfresh
:log info "DynDNS: IP updated to $ipfresh!"
} else={
:log info "DynDNS: dont need changes";
}
}
2 reasons.gotsprings - one post above yours is a working script. why not use that one ?