Sorry to put this again on the bench

RouterOS General
1

My theory sometimes is wrong, but MOST of the time is right.
The question is TO REMEMBER OR NOT TO REMEMBER interface settings. Quite sometime ago i questioned this and replies were 3-4 … Now i see more people are using this software in production environments and dont want to play around configuring something that was configured before. What is this feature anyway useful for? I cant think of anything…
HUGE PROBLEMS: image this case - mtik box sitting somewhere for like 1 year - something happends, ethernet dies or wireless…
1st case: i go there swap damaged card and everything works normal as it was (sometimes remember it should not be me or you but someone with little or no experience what is going on)
2nd case: i go there, swap damaged card, reconfigure the system with monitor and keyboard for like 10 minutes… and everything goes on. BUT imagine this is not in some nice place like home, office or building - climb up the tower and speak again. OR pay climber to do that for you and you are broke.

REMOVE THIS FOR GODS SAKE! :slight_smile:
we want this system run like linux does.

2

I’m still trying to figure out what your post is referencing… lol

And I have MT routers that have 9+months uptime..

3

Translation: Don’t force the admin to reconfigure all firewall rules, wireless configs, etc if the MAC address on a NIC is changed. Currently if you change a NIC then all references to that interface become unknown. So, if you are simply changing out a NIC you can’t simply plug a new one in start running.

I think changing the primary key for the NIC from a MAC address to the NAME (or a new field, ID?) would fix this, but then you couldn’t rename nics very easy… I’m sure they will figure out a way around it soon that makes sense for both sides.

Sam

4

oh yeah.. that is annoying.. I’ve had to do that with wireless interfaces. It sucks when you have to edit the 30+ client access list to change to the correct interface.