I swear to all that is unholy, I can SMELL so called network engineers who learned base concepts on RouterOS at this point.
-
@nuintari I've never used Juniper before. Yes, I could learn, but I'm busy learning new openzfs stuff.
My last day gig was mikrotik, so I already know that.
@mwl You are a smart cookie, you'd pick it up in a few days, tops.
Not trying to be pushy, but seriously, once you go JunOS..... you never wanna go back.
I am honestly shocked that no one has come even close to cloning their environment. Or even their basic escape hatch system.
-
I swear to all that is unholy, I can SMELL so called network engineers who learned base concepts on RouterOS at this point. The arguments they make, their base understandings of concepts, you can just tell.
Is my blanket, blatant hatred of @mikrotik completely deserved? Probably not. They do make cheap 10gigE ports with decent capabilities. I still won't touch them, and I actively refuse jobs that involve Mikrotik work anymore. Simply because as much as I enjoy a good challenge, I do not like tilting at windmills. Fixing your average Mikrotik network is about as much fun as autoappendectomy. See also: Fuck you, Chris.
But is RouterOS a good learning platform? FUCK NO. RouterOS is to networking as Pascal is to programming. You may learn some base concepts, but you will bring along some terrible baggage. You will learn some great for Mikrotik, terrible everywhere else techniques that make you the bane of your IT department.
After nearly 30 years in this field, there are certain..... quirks..... that only a foundational knowledge of Mikrotik will tell you are a good idea.
Seas of routers on sticks, endless EoIP tunnels, ridiculous overuse of NAT.... you can learn all these bad ideas somewhere else, but I see them EVERYWHERE on Mikrotik networks.
This is _why_ I loathe Mikrotik so much. Well, all that, and because that dude named Butch on AFMUG was a pretentious hogfucker.
-
I swear to all that is unholy, I can SMELL so called network engineers who learned base concepts on RouterOS at this point. The arguments they make, their base understandings of concepts, you can just tell.
Is my blanket, blatant hatred of @mikrotik completely deserved? Probably not. They do make cheap 10gigE ports with decent capabilities. I still won't touch them, and I actively refuse jobs that involve Mikrotik work anymore. Simply because as much as I enjoy a good challenge, I do not like tilting at windmills. Fixing your average Mikrotik network is about as much fun as autoappendectomy. See also: Fuck you, Chris.
But is RouterOS a good learning platform? FUCK NO. RouterOS is to networking as Pascal is to programming. You may learn some base concepts, but you will bring along some terrible baggage. You will learn some great for Mikrotik, terrible everywhere else techniques that make you the bane of your IT department.
After nearly 30 years in this field, there are certain..... quirks..... that only a foundational knowledge of Mikrotik will tell you are a good idea.
Seas of routers on sticks, endless EoIP tunnels, ridiculous overuse of NAT.... you can learn all these bad ideas somewhere else, but I see them EVERYWHERE on Mikrotik networks.
This is _why_ I loathe Mikrotik so much. Well, all that, and because that dude named Butch on AFMUG was a pretentious hogfucker.
@nuintari
Damn, what's with the Pascal hate? -
@haakon Yes, ^^^this^^^
This is so absolutely, perfectly accurate.
-
@mwl Ya know, you can get an SRX300 for like, $110 on eBay now, right?
-
-
@mwl You are a smart cookie, you'd pick it up in a few days, tops.
Not trying to be pushy, but seriously, once you go JunOS..... you never wanna go back.
I am honestly shocked that no one has come even close to cloning their environment. Or even their basic escape hatch system.
-
the commands are simple
commit check - basic test, "yes, I can technically load this command into main memory." - doesn't keep you from locking yourself out, but does make sure the config is valid.
commit confirmed <X> - take config live for X minutes, default is 10. if you don't commit within that time interval, the configuration rolls back to the previous configuration - this is your safety net
commit - take the config live, for sure, permanently
rollback <X> Take the configuration back X commits, default is 1.
show | compare rollback <X> - compare the current configuration vs the state X commits ago. There is no default.
Other vendors have tried to imitate this behavior, they always seem to come up lacking. I have NEVER had to drive or dispatch to rescue a Juniper device in the field.
So I guess trying googling, "JunOS commit" - this is one of those things I do not remember how I learned it beyond, "I read the Juniper documents."
-
@mwl You are a smart cookie, you'd pick it up in a few days, tops.
Not trying to be pushy, but seriously, once you go JunOS..... you never wanna go back.
I am honestly shocked that no one has come even close to cloning their environment. Or even their basic escape hatch system.
@mwl can confirm what @nuintari says. The config is structured in a logical way and aligns well with how protocols and certain technologies actually work. If you understand the protocols and technologies picking up JunOS is easy and quick.
Beware: once you’ve done JunOS you’ll *hate* every other config scheme and you’ll have a floating „w-t-f“ whenever you’ll have to touch anything else.
-
the commands are simple
commit check - basic test, "yes, I can technically load this command into main memory." - doesn't keep you from locking yourself out, but does make sure the config is valid.
commit confirmed <X> - take config live for X minutes, default is 10. if you don't commit within that time interval, the configuration rolls back to the previous configuration - this is your safety net
commit - take the config live, for sure, permanently
rollback <X> Take the configuration back X commits, default is 1.
show | compare rollback <X> - compare the current configuration vs the state X commits ago. There is no default.
Other vendors have tried to imitate this behavior, they always seem to come up lacking. I have NEVER had to drive or dispatch to rescue a Juniper device in the field.
So I guess trying googling, "JunOS commit" - this is one of those things I do not remember how I learned it beyond, "I read the Juniper documents."
-
R relay@relay.infosec.exchange shared this topic
