This looks fantastic - thank you for this.Here is my version of auto-upgrade script, it has many features such as backup to your email before performing RouterOS upgrade process
https://github.com/beeyev/Mikrotik-Rout ... and-update
It would be a useful tool for remote network testing
I can do that I was just searching for the simple answer first .....Since it comes with a PS of 24V 1.5A that is the suggested.
Otherwise you should measure the current draw of the device unter full load and see how much current it draws.
Yes I'm just not sure what the manufacturer suggestsI would never use a Power supply of a lower rating than the manufacturer suggests.
Personally i would extend the cable if needed.
Thanks for this - unfortunately it did not work. It keeps updating.Update your winbox, clear its cache and test again.
Thank you - that is very helpful for me. No I just need to remember .For all named objects, you can actually replace [find name=xxx] by just xxx in the get (and other) commands.
Perfect - thank you.Doesnot work?Code: Select all
/ip dhcp-server alert add alert-timeout=10m disabled=no interface=bridge valid-server=[/interface bridge get [find name=bridge] mac-address]
This appears to fail for me.Nice Work!
I added FireHOL Level2 to the script as well, in case you're interested. Just added this line:
$update url=https://raw.githubusercontent.com/ktsao ... el2.netset description="FireHOL Level2" delimiter=("\n")
Thanks for the tip - very helpfulProbably not massively helpful for you but I successfully use the Cisco GLC-SX-MM SFP's in all of my MT devices. Dirt cheap on the second hand market as well.
m2mDNS server for Chromecast/Bonjour/ZeroConfig across VLANs.
WiFi networks are too big to have all the available devices all bridged to the LAN.
Would be nice to then firewall what devices are discoverable.
This makes a great deal of sense to me - thanks.Pre-empting the worst is probably the best summary.
If they're poking at certain ports when they shouldn't then you probably don't want them poking at anything.
@icsterm Thank you very much. I will give it a shot!Just filter out UDP broadcast packets with destination 255.255.255.255 & port 5678 on the devices you don't want taking part in MNDP.
This was very helpful - and perhaps the end game.Due to that, you can't consider blacklist as alternative to whitelists (which are useful only for incoming connections). It has different purpose and even with thousands of blocked IP's blacklist will not have significant impact on your CPU.
Yes in that case you can do it with the switch:
/interface ethernet switch port
set 5 default-vlan-id=172 vlan-header=always-strip vlan-mode=secure
This will make port 5 an untagged member of vlan 172.
Which one of the two hints?Thank you this was helpful and allowed me back in.