I want to communicate 192 to 172 with firewall rules
Please help

Firewall routing?

I want to communicate 192 to 172 with firewall rules
Please help

You tried hard to describe the problem,
We will make the same effort to answer you:
Firewall rules alone do not magically connect two networks.

Every question so poorly worded constructed and presented, should be handled by Mikrotik as they do not want to support better forum handling of new posters.

For the OP.
Please provide a diagram and export your config
/export file=anynameyouwish ( minus router serial number, any public WANIP information, keys etc. )

handled by Mikrotik

They've explicitly ruled out this category in point 6, here: "Technical support does not include training on TCP/IP."

I'll readily grant that this is a poor-quality question, but as the mod who approved it, I'll tell you why: rejecting it would not have helped the OP. However clueless this person may be, accepting his question and then giving a bare doc link as my reply above at least has a chance of them taking the hint and RTFMing, thereby either allowing them to a) solve their own problem; or b) post a better question. Either way, it's to the benefit of all concerned.

Everyone here was clueless once upon a time. The proper distinction to be made is between temporary and ongoing willful ignorance.

In any case, I don't agree that forcing all new questions through an artificial gauntlet of form-filling will make such people suddenly smarter. The best you can hope for is differential frustration, resulting in more clueless first-time posters being run off than clueful ones.

Lemme ask you this: when you call up tech support and the Level 1 "technician" runs you through the same canned script you found seven times with a web search before breaking down and calling support, how does that make you feel? Me, it irritates to the point of incandescence. This is not a good practice to be advocating here. I don't buy the proposition that there is any amount of form-filling you can put up at the entrance to the forum that will meaningfully cut down on clueless people being clueless.

handled by Mikrotik

They've explicitly ruled out this category in point 6, here: "Technical support does not include training on TCP/IP."

So the meaning is:
A) Purchase MikroTik products only if you are an expert in TCP/IP
either/or
B) You must ask for support from whoever you buy the hardware, not directly from MikroTik.

--> rextended è buono come il pane.
--> rextended non ha peli sulla lingua, dice quello che pensa.

I hope its not to hot where you are.
Take care.


.

A) Purchase MikroTik products only if you are an expert in TCP/IP

…or mean to become one through experience, which is why I so often lead with links to relevant docs.

If the poster shows evidence that they either won't read or won't attempt to understand and apply what they did read, then that falls under my "ongoing willful ignorance" category.

B) You must ask for support from whoever you buy the hardware, not directly from MikroTik.

Wishful thinking. Most retailers of computer products have zero staff for this.

This is why I spend so much time on self-help forums like this one, participate in chat rooms, write blog posts, etc: distributed knowledge transfer is the biggest bang-for-buck method of reducing the net global level of ignorance.

In fact, I appreciate, shareable speech.

But a question should make some kind of sense.

What does it even mean? "I want to communicate 192 to 172 with firewall rules"
What is 192? What is 172? Range? Netmask? Host? Number of clients? Of sites? Angels, dancing on the needle's head top?

Some kind of effort must be made to convey the problem. It's like saying "please help me" is a valid question.
No, it's not.

Saying "I need to access one server from this desktop. How do I do it?" is an incomplete question - but a valid one. There is a difference.