Hi, may be that I didn’t fully understand this feature but in my case this setting didn’t add meta refresh into html code.
http://forum.mikrotik.com/t/mikrotik-auto-refresh-page/29150/1
Also… I now have a graph showing the increased CPU usage on 6.2. This is from a box running minimal stuff. If you look at mid monday you can see a distinct drop from an average of 8% to an average of 3% or so. This was when the box was downgraded to 6.1. There is basically no load on this box and it is just idle. Not really sure why the CPU usage is higher in 6.2… anyone else seen this?
Normis?
Thanks for the scripting fixes since 6.1, but unfortunately we’re hitting a new scripting bug.
:local q
:local msg
:set msg "hello world"
:set q [:parse ("/put message=\"the message is: " . $msg . "\"")]
$q
:put $q
On 6.2:
[admin@dev] /system script> run test
(eval /putmessage=the message is: hello world)
On 5.24:
[aragon@rb1.kush] /system script> run test
the message is: hello world
the message is: hello world
Reported to support@ - #2013081166000228
I have several omnitiks and a few sextants on 6.1 and my phone customers are not complaining.. I put 6.1 on a couple of months ago to cure some ospf irregularities in that part of the network.
I didn’t “uncheck” any service settings and all my Voip ATA’s, registration and quality are good!
Simple suggestion for ROS6 which might have huge impact.
Very nice to see from-dscp-high-3-bits and from-priority-to-high-3-bits.
Thank you for that! I will make a big difference.
Now what about the other 3+2 bits in that little Byte.
I think I would be usefull if ROS would be able to set filter/mangle rule on condition dscp-low-3-bits and have actions set-dscp-high-3-bits and set-dscp-low-3-bits
This would mean, I can use high 3 bits for QoS and low 3 bits for e.g. differentiating capped and uncapped users, or to give QoS sub-classes/queues, or to classify routing info (we have different gateways on large network, so ‘cheap’ clients can be routed differently, etc. etc. etc.)
The point is I think DSCP is fantastic as it is the only way to transmit information between routers on a packet by packet bases.
It would be great if MT can let us harness the untapped great potential of these few bits.
I think if it is available, it would inspire people to think differently about their networks and it can save lots of CPU power downstream as some info can be transmitted like a simple network-wide connection mark, and certain processes can be centralized & transmitted.
If you really want to go full out, in Winbox you can perhaps (in mangle condition), choose to test between DSCP (6 bits) or high-3 or low-3 bits and/or have the last 2 EC bits there maybe? (or some other way?)
Then in action, choose to set dscp-6-bits, dscp-high-3-bits or dscp-high-3-bits. When setting dscp-high-3-bits, the lower 3 must be unchanged, and vice versa.
Am I just looking at it wrong, or does someone agree?
Regards
Ekkas
Hi
seems that proxy arp with sstp tunnels is not working
any other got that problem? I’ve seen that problem since ros 6.0rc14
kind regards
Please email to support@mikrotik.com with these problems so if we could check and fix them.
How are you reading the voltage - from snmp?
Are you talking about this? What is so faulty about it?
Hm.. he said he had four meta entries and the faulty is the last but your screenie only shows three. Maybe he could paste / screenshot his version.
Please try to use ‘tool profile’ and check what process eats so much CPU and report back with the results.
So probably he has custom html and introduced the mistake himself, because this is default header from latest RouterOS.
Hi Normis,
Any news on when a prebuild of 6.3 with the ip proxy access is fixed? 
/Frank
when we will fix it, pre-release will be made available
Normis,
I did not create a login page myself.
I’ve attached a screenshot of the page.
I’ve also seen that there are two different login pages, one in the root, and one in the lv directory.
The last one does not show the line which seems to be faulty in the other one.
Ok, looks like ours after all, thanks for report
There’s a slash missing, but it will get parsed without problems in any browser. It’s more of cosmetic thing and not 100% valid according to the doctype (xhtml requires correct nesting and opening / closing of tags), but then again - which website is?
I alerady did (nr. 2013080466000205 - about loosing graphs). Today I received advice to netinstall v6.2. I am not sure that it will help, but I will try to.
Regarding the voltage I use this script:
# Define global variables
:global TempLast
:global VoltLast
# Define and fill actual values
:local TempAct [/system health get temperature]
:local VoltRAW [/system health get voltage]
# Divide voltage by 10 as it is 10 times multiplicated
:local VoltAct [ ($VoltRAW / 10) ]
# Calculate differences between last and actual values
:local TempDiff [ ($TempAct - $TempLast) ]
:local VoltDiff [ ($VoltAct - $VoltLast) ]
:tonum TempDiff
:tonum VoltDiff
# Calculate absolute values of differences
:if ( $TempDiff < 0 ) do={ :set TempDiff [ ( 0 - $TempDiff ) ] }
:if ( $VoltDiff < 0 ) do={ :set VoltDiff [ ( 0 - $VoltDiff ) ] }
# Do the reporting
:if ( $TempDiff >= 2 ) do={ :log info ("Environment: Last Temperature was $TempLast C. Actual Temperature is $TempAct C.") }
:if ( $VoltDiff >= 2 ) do={ :log info ("Environment: Last Voltage was $VoltLast V. Actual Voltage is $VoltAct V.") }
:if ( $TempDiff >= 2 ) do={ :set TempLast $TempAct }
:if ( $VoltDiff >= 2 ) do={ :set VoltLast $VoltAct }
# Debugging info below....
#:log info $TempAct
#:log info $VoltAct
#:log info $TempDiff
#:log info $VoltDiff
#:log info ("Environment: Actual Temperature is $TempAct C. Voltage is $VoltAct V.")
It gets voltage and temperature, compares it with last values and if vlaues change, it makes the info log entry.
This script works in v5.25 but does not work in v6.2. In v6.2 also DnsExit script does not work (do not know why):
# Set needed variables
:local username "some-name"
:local password "some-pass"
:local hostname "some-url.linkpc.net"
:global dyndnsForce
:global previousIP
#:global currentIP
# print some debug info
#:log info ("UpdateDnsExit: username = $username")
#:log info ("UpdateDnsExit: password = $password")
#:log info ("UpdateDnsExit: hostname = $hostname")
#:log info ("UpdateDnsExit: previousIP = $previousIP")
# get the current IP address from the internet (in case of double-nat)
/tool fetch mode=http address="ip.dnsexit.com" src-path="/" dst-path="usb1/dnsexit.tmp" port=80 host=ip.dnsexit.com
:local result [/file get [/file find name=usb1/dnsexit.tmp] contents]
# parse the current IP result
:local resultLen [:len $result]
:local currentIP [:pick $result 0 ($resultLen-1)]
#:log info "UpdateDnsExit: 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 DnsExit!
#:set dyndnsForce true
# Determine if dyndns update is needed
# more dyndns updater request details on DnsExit.com
:if (($currentIP != $previousIP) || ($dyndnsForce = true)) do={
:set dyndnsForce false
:log info "UpdateDnsExit: Current IP $currentIP"
:log info "UpdateDnsExit: Previous IP $previousIP"
:set previousIP $currentIP
/tool fetch mode=http address="www.dnsexit.com" \
src-path="RemoteUpdate.sv?login=$username&password=$password&host=$hostname&myip=$currentIP" \
dst-path="usb1/dnsexit.txt" port=80 host=www.dnsexit.com
:local result [/file get usb1/dnsexit.txt contents]
#:log info "UpdateDnsExit: previousIP = $previousIP"
:log info ("DnsExit: DnsExit update needed")
:log info ("UpdateDnsExit: DnsExit Update Result: ".$result)
:log info ("DnsExit Update Result: ".$result)
} else={
:log info ("UpdateDnsExit: No DnsExit update needed")
}
jarda, please contact support@mikrotik.com we will provide you with test release of v6.3 which will have a fix for this problem.
No it is not the slash.
It is a different double quote char. Look closely and you will see difference between the start and end of the line.
Ah! You’re right, thanks for pointing it out. It’s something that’s easily overlooked.
P.S.:
But the slash is missing, nevertheless 