I leave this other script (module-continer) as an example, it creates a global function "registerContainer", the function works perfectly, the problem is that after 5-10 minutes the global function disappears from the environment.
One thing you can tell is a ROS bug is that the script's run-count read-only variable returns to 0 when it should indicate it has > 1 runs.
/system/script> :put [get hello-world run-count]
4-Run the script.
5-Verify that the global variable “helloWorld” exists in the environment and the run-count property of the script is > 0.
6-Close the script repository window.
7-Wait 5-10min.
8-Go to the system/script menu, verify the variable “helloWorld” does NOT exist in the environment and the run-count property of the script is 0.
Absolutely confirmed and indefinitely repeatable: The global variables is deleted and the run script counter go to 0
You’re right,
thank you for the report by all those who use the scripts and see the interrupted work and do not explain why.
I did it too by simply closing and reopening winbox without waiting a minute… (test on RB911G-5HPnD / RouterOS mipsbe 7.4rc2 / WinBox 3.36 x64)
[admin@MikroTik] > export
# jan/02/1999 00:07:18 by RouterOS 7.4rc2
# software id = 3NSC-9L2V
#
# model = 911G-5HPnD
# serial number = 57680402EB8C
/interface wireless
set [ find default-name=wlan1 ] ssid=MikroTik
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/system routerboard settings
set init-delay=2s reformat-hold-button-max=2m
/system script
add dont-require-permissions=no name=hello-word owner=admin policy=\
ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon source=\
":global helloWorld;\r\
\n:set helloWorld do={:put \"Hello World.\";}"
Just bought a mAP lite to connect a remote site. Naturally, first thing I did after unpacking it was to upgrade to 7.4rc2. Technically, I upgraded to latest version of 6 (whatever that was), then to 7.3.1, then to 7.4. Actually, the first problem was having plugged the mAP lite into my primary router (hAP AC2) I couldn’t see the device via Winbox. I turned on Wifi on my PC and connected to the mAP directly - that let me begin configuration. I don’t know if the problem was the pre-loaded Quickset or if was something else - and since I’m still fighting…
I don’t know if this is a mAP lite thing, a 7.4rc2 thing, or just me - but I’m having problems I haven’t had before. Again, I couldn’t see the device via local ethernet. Even though the DHCP client obtained a address from my primary router - while I could ping it I couldn’t access it via Winbox. I’ve now de-activated the built-in IP 192.168.88.1 - and now it’s advertising itself on my 192.168.5.x network. I’ve re-activated the IP now and it’s still working - but I swear it didn’t respond to the 192.168.5.x address until I turned off the 88 address.
The whole point of this exercise is to get Wireguard functional on this device. I’ve configured a Wireguard interface - just like the other devices I’ve done before. I’ve added a peer - and copied the public key to the peer. I also added a srcnat accept line for the Wireguard port. And…nothing. I’ve enabled wireguard-debug logging and…nothing. This device never tries to connect to the remotes (I’ve added two different peers to see if there was a remote issue - and there isn’t).
At the moment, I’m on quickset “CPE”. I toggled over to “Router” instead of “Bridge” to see if that would help. Nope. I also noticed the Wireless interface shows disabled - which I don’t understand as in the QuckSet it’s showing available wireless networks to join.
Am I just being more brain-dead than usual or is there something wrong either with this install or this particular device?
First, map lite needs to be configured initially via Wifi. Eth port is blocked (as it is considered WAN side).
Second, I also have map lite with 7.4rc2 (already from very first ROS7 version) ánd wireguard (that’s why I wanted ROS7 on the little bugger).
Must be some config thing (so yes, you’re brain dead :lol: ). Normally srcnat is not needed (at least not in my setup).
Best to start new thread, post your config so we can have a look.
I am glad that VRF support is starting to be added to these services. One thing that I noticed is even with a VRF assigned in the NTP Client it still doesn’t work. I believe this to be due to not having the ability to specify a source address. In my case these are P routers utilizing mpBGP/MPLS. I have found when utilizing Ping function I have to specify a source address rather than just the VRF and destination address.
Additionally I’d love to see VRF support for DHCP-Relay, TFTP Client and DNS Client as well as the update service
This version has still problem with WiFiWave2 package (RBD53iG-5HacD2HnD) for mobile devices → you can connect to network but no Internet access (guest network in a bridge in a separate VLAN). The same with version 7.3.1. Downgrade to 7.1.5 eliminates the WiFI transmission problem. Had no time to investigate deeper.
could be very usefull to have for each connection a counter that count the estabilished sessions.
So it will be usefull for me that use 1 connection/1 sessions and for other that uses multiple sessions for each connection.
see it at zero is useful a lot!!!
in a list of 500 connections and 495 sessions estabilished and no sessions not esteblished how do you find the connections those have issue???
That is not actually true. This discussion should hint to you that the monitoring and logging of BGP in v7 leaves a lot to be desired.
So hopefully in the next v7.4rc release notes the word bgp will once again appear.
the bug with the bgp ‘default information originate’ is still not fixed in 7.4rc2.
that means, when you advertise a default route via ros7 bgp to a ros6 bgp neighbour, the bgp session starts to flap endless.
with ros6 to ros6 same configuration works fine.
this got confirmed by support already very long ago and was suposed to be fixed already, but still happens.
as long as this isn’t fixed, bgp is anything else than stable nor ros7 usable for serious bgp setups.
