Hello, I'm having a problem with my MikroTik. I don't know what's wrong, but I've connected my internet router to the MikroTik, then to the Mercusys router, where there are many CCTV cameras connected. The problem is when I want to connect to the device on the internet router because my server is located there. How can I connect to it when my IP address print looks like this?
[admin@MikroTik] /ip address> print
Flags: X - disabled, I - invalid, D - dynamic
Please show full config and draw the network diagram + info about used IPs for interfaces..
It's hard to understand the expected flow of packets without them.
Please remove serial Number, as a precautionary move.
Since you have masquerade appropriately applied, any traffic leaving your Routers WAN interface ( LAN interface of ISP router), it will get the IP address of 192.168.1.30 and thus be on the SAME LAN as the rest of the devices hanging off the ISP router. Any responses by the server should head back to your MT router and then the router should properly distribute the traffic back to any user on the MT router.
What cannot be done easily is for users on the ISP router to originate traffic to users/devices on non-local subnets ( aka the 192.168.88.0 subnet ). The ISP router would need a static route sending traffic for 192.168.88.0/24 to 192.168.1.30
If the request is from tripleNAT, the mercury router, depends........... if the mercury router is on the LAN subnet of the MT router ( as thus the WANIP of the mercury router is 192.168.88.XY ), some things need to be know.
a. what is the subnet LAN of the mercury router
b. do you masquerade its traffic out the WAN of the mercury router aka everything coming from it would have an IP of 192.168.88.XY?
Assuming it does........... and subnet of mercury is 10.10.10.0./24
Then to reach the server on the ISP router first you would simply initiate traffic to reach the server.
the traffic would leave the device with
src-address=10.10.10.5 dst-address=192.168.1.20
The traffic would go out the WAN of the mercury router (src address getting masqueraded) and hit the MT router with something like
src-address=192.168.88.XY dst-address= 192.168.1.20
The MT router would be quite aware of the 192.168.1.0 subnet and would send the traffic out the WAN of the MT upstream masqueraded with the wanip of the MT router.
The traffic would hit the ISP router with
Src-address=192.168.1.30 dst-address=192.168.1.20
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Response back from the server would leave the server with
src-address=192.168.1.20 dst-address=192.168.1.30
The MT Router would receive this traffic and unsrcnat the information such that the traffic is:
src-address=192.168.1.20 to to 192.168.88.XY. and would sent the traffic to the WAN port of the Mercury Router.
Response would then reach the mercury router and then be unsrcnatted there so that the traffic now reads
src-address=192.168.1.20 dst-address=10.10.10.5 and the traffic would be sent directly to that device.
Random values? Random YouTube guide? Artificial Deficence?
Lack of understanding what L2 and L3 are?
Is bigger better? (This doesn't apply everywhere...)
If MTU is 9214, L2MTU must be at least(...) 9228, the same is for 2290, must be at least 2304...
From the description it is not clear where the devices are connected,
it would be better if you made a diagram that also specifies the IPs.
It's best you start from scratch and leave it alone,
then ask for help on the forum.
If you don't use VLAN or MPLS etc... then you can set MTU = L2MTU without problem. Also if you add a VLAN interface on top of an ethernet or bridge interface, the L2MTU of the VLAN interface is automatically reduced from the L2MTU of the parent interface, so for that VLAN interface you can set MTU = L2MTU (of the VLAN interface) too.
.
