This post has sorta morphed (in a good way) from the RouterOS manual ideas.
Naturally. The only people who could agree to your request to clone the manual into WinBox for offline use are MikroTik themselves, but this is a user-to-user forum. The direct user-to-MikroTik feature request channel is
elsewhere.
Personally, I think they should export it all to Markdown, then republish it via
Fossil so that I can clone it locally. That would not only let me open it in a web browser while offline, it would let me keep it updated with the sync protocol. I don't see that happening, though.
Alas, the learning curve is steep
Yes, but not maliciously so. Keep in mind, network engineering is a
career for some. This is a deep, deep pool you've plunged into. Your immediate project is nearly trivial when put up against the scale of what is possible, but at the same time, you can't expect free private consultation from working professionals every time you have a question. If they were to bill you at their hourly rate, you'd "nope" right on out of that deal for the same reason you're rejecting in-person training.
As a retired Joe Shmuck I can't justify or afford a 4 day out of state trip for a 3 day class on a $60 router
How about a
$13 class that you can do from your place of retirement, then?
The one I've linked is overkill for your purposes, but it's the closest match I can find to your immediate needs. I got my own start in RouterOS from Maher Haddad. If you can get past the strong accent, he knows what he's talking about. After a time, I found the quirks of his approach to English becoming somewhat charming.
On the course price, do realize that nearly everything at Udemy is on sale all the time. Don't believe them when they say it's normally a $60 course or whatever. If it is currently full-price when you visit, wait a day or two, and it'll be back down into the $9-15 range again.
You forum gurus hold the keys.
That implies that we're jealously withholding our knowledge. The fact is, our time on this planet is finite, and a good many of us have found someone who will pay us enough that we could buy multiple hEX routers every day. The expensive bit isn't the hardware, it's
human working time. Places like Udemy amortize that cost across thousands of people, asynchronously, so that we do not have to pay full-rate for training.
Tangent-- thank-you for the explanation of safemode. I will be able use it, if this thing can ever work the first time.
I gave you rather more than that. I spent roughly 6 hours writing
that article for you, in direct response to this thread. Where's my check for 6×$RATE for personal training?
I'm not being literal, but I do want you to value what you're getting here. It wasn't "free." Someone (me, in this case) spent a lot of time trying to help you several moves up the learning cliff, and now you're exhibiting signs that you didn't do more than skim it, if that.
What I want from you in return is effort. If you show us that you're trying to learn, and progressing, you'll increase the chances of getting more of this "free" training. If not, then why would any of us expend more of our finite time on this away mission to Planet Earth?
I don't care if the networks route or bridge.
Why not put them all onto your "192net," then? That would be the simplest solution; it would have allowed the default bridge to do everything you asked for above.
Mind you, I'm not advising that; I'm asking you to give us your justification for having the split in the first place.
By putting the two sides of the networks on different IP ranges, you
require routing. Bridging isn't even an option now.
(Not a
clean option, anyway. You could multi-home everything that needs to see both sides over a single bridge, but ick.)
So far, ChatGPT has been very helpful with me learning
Please stop saying that; you're making people here cringe. ChatGPT can, at best, regurgitate other humans' knowledge for you on demand. At worst, it makes up utter horse hockey that merely
sounds correct. Your ability to distinguish the two cases is minimal at this point, putting you at serious risk of being misled.
I bought this through Amazon, there is a notation that configuration help is a feature they can provide - yeah right, try it! I tried going the MikoTik support route and was summarily blown off, (albeit nicely).
They told you that right up front. Point 6,
here: "Technical support does not include training on TCP/IP." That's what you're asking for here: for someone to train you in basic networking. That's what the manual is for, and failing that, professional trainers like Mr. Haddad.
/ip route
add distance=1 gateway=ether5
add distance=1 gateway=ether2
add distance=1 dst-address=192.168.1.2/32 gateway=ether5
I told you above that I believe you can do this with a pair of static routes. You've got three here, one of which shadows the third.
The first static route you've defined tells the router that the default route is toward the camera network. This is simply wrong. The only traffic that should be going that direction is that which needs to get to your "10net".
The second rule corrects this, telling the router the truth, that the default route is toward ether2, which presumably connects to your Internet router.
But then your third rule goes and tells the router that the direction to your "192net" is toward the camera network again! No wonder it doesn't work.
I haven't tried this here, but what I believe you want is something more like this:
/ip route
add distance=1 gateway=ether2
add distance=1 dst-address=10.1.1.1/24 gateway=ether5
Atop that, everything in the "10net" needs to be told that their gateway is 10.1.1.1, the "10net" side of the router that knows how to get traffic onto the "192net" and from there out to the Internet.
I gave both routes for the purposes of explanation, but in fact, the second static route should be implicit from the "/ip/address/add 10…" rule above. Check it with "/ip/route print", and if I'm right, you only need the first rule. Presumably you had it in that configuration at one point, but you were doubtless missing the "10net" gateway on all the "10net" devices, explaining why it didn't work with the single default route configuration.
It is quite possible I've missed something in all this. I'm no routing expert, and if I had to do something like what you're proposing, I'd set it up with VLANs instead. I'm not recommending that to you, however; the
requirements for doing that would blow your mind at this stage. Get something basic working, rebuild your confidence, and
only then decide if you want to do this the fancy way professional network engineers prefer.