The simple one?: Connect 2 subnets (separate on 2 ports in 2 different switch groups) - "I tried everything?!"

Hey there,

I thought I am a little bit advanced in configuring RouterOS .. doesn’t seem this way.

This is my issue:

  • Subnet 10.1.1.0/24 with DHCP server on Port eth2 (Master Port for eth3-eth5) @ Switch group 1
  • Subnet 192.168.1.0/24 no DHCP server on Port eth9 (no master/slave) @ Switch group 2

I CAN ping + access via telnet my device attached to eth9 (192.168.1.1) from RouterOS
I CANNOT ping or access this device from any other network (e.g. my base network 10.1.1.0/24)

I already tried:

  • bridging two ports of switch group 1+2 together
  • defining static routes (although it seems to be done correctly in dynamic/auto mode)
  • played around with some firewall/nat rules
  • and all variants of this ..
    = none if this worked

What can I try next?
The device itself is a MikroTik RB3011UIAS-RM

Please let me know if you need any output of

You can tell us more about those two networks. Do devices in both of them have this router as default gateway?

Hey,

thanks for your reply.

The subnet 10.1.1.0/24 is used for general purpose (Internet connectivity), so personal devices like PC or Smartphone via WiFi are connecting to this one.

My use case: I want to configure a new DSL modem (Draytek Vigor 130), which I currently attached to eth9 (later on, this will function as bridged MPoA @ eth1/WAN for the MikroTik router)

The Vigor 130 does come with a factory default static network configuration, the device has the IP address 192.168.1.1, so no - I don’t think the router is set as gateway.
So what I’m trying to achieve is, that I can access the 192.168.1.1 Web interface - connecting to the Vigor 130 does already work from the router itself (e.g. via telnet) - but not from any other device.

Thanks!

PROBLEM SOLVED:

I defined a Firewall NAT rule (dstnat) with action “dst-nat” to the specific address.

Nat is ok if you want to nat. Otherwise you need to route between subnets.

I tried to define a static route for the specific network 192.168.1.0/24 on the specific port .. but the DSL modem can’t be reached from any other client - except the directly attached router itself.

Maybe it is a speciality of the Vigor 130 ?!

  • Since I don’t have to re-configure the device everyday (just using it as a DSL modem / MPoA bridge / PPPoE pass-through), the connectivity isn’t really an issue after the setup (which I did for now).