Weird routing behavior with another CIDR

RouterOS Beginner Basics
1

Hi !

I have a RB5009UPr+S+IN running routerOS 7.11.2.
It runs a DHCP server for the CIDR 192.168.50.0/27.
I have a computer (Client A) and a server which receive their IP from the DHCP server.
Connected to the RB5009UPr I also have a computer ( Client B) with IP address 192.168.10.1 ( which is static and not managed by the RB5009UPr )

On the server, I’m running a simple web service which listen on 192.168.50.5:443

When I try to access it from Client A ( 192.168.50.10 ) all is working fine.
But when I try to access it from Client B ( 192.168.10.1 ), I have initial delay of 60 seconds to be able to access the server, then about 2 minutes of normal behavior and 20 seconds where the server is not reachable( an it restart with 2 minutes/20 seconds cycle )

I run a small script to test that behavior

while true;do 
date| tr "\n" " "
/usr/bin/time -a curl -ks https://192.168.50.5:443 -I
sleep 1
done




Wed Nov  8 17:24:49 +08 2023        75.06 real         0.03 user         0.02 sys
Wed Nov  8 17:26:05 +08 2023 HTTP/2 200 0.15 real         0.04 user         0.02 sys
Wed Nov  8 17:27:58 +08 2023 HTTP/2 200 0.15 real         0.05 user         0.00 sys
Wed Nov  8 17:27:59 +08 2023        75.04 real         0.04 user         0.01 sys
Wed Nov  8 17:29:15 +08 2023 HTTP/2 200 0.15 real         0.04 user         0.01 sys
Wed Nov  8 17:31:06 +08 2023 HTTP/2 200 0.15 real         0.04 user         0.00 sys
Wed Nov  8 17:31:07 +08 2023        75.03 real         0.03 user         0.00 sys
Wed Nov  8 17:32:23 +08 2023 HTTP/2 200 0.15 real         0.03 user         0.02 sys
Wed Nov  8 17:34:14 +08 2023 HTTP/2 200 0.14 real         0.05 user         0.00 sys
Wed Nov  8 17:34:15 +08 2023        75.06 real         0.03 user         0.00 sys
Wed Nov  8 17:35:31 +08 2023 HTTP/2 200 0.16 real         0.04 user         0.01 sys
Wed Nov  8 17:37:23 +08 2023 HTTP/2 200 0.14 real         0.03 user         0.01 sys
Wed Nov  8 17:37:25 +08 2023        75.03 real         0.03 user         0.00 sys
Wed Nov  8 17:38:41 +08 2023 HTTP/2 200 0.15 real         0.04 user         0.01 sys
Wed Nov  8 17:40:31 +08 2023 HTTP/2 200 0.15 real         0.05 user         0.00 sys
Wed Nov  8 17:40:33 +08 2023        75.07 real         0.03 user         0.02 sys
Wed Nov  8 17:41:49 +08 2023 HTTP/2 200 0.14 real         0.03 user         0.01 sys
Wed Nov  8 17:43:39 +08 2023 HTTP/2 200 0.16 real         0.05 user         0.00 sys
Wed Nov  8 17:43:40 +08 2023        75.03 real         0.02 user         0.02 sys

Any idea what could cause that ?
network.png
config-20231108.rsc (4.63 KB)

2

A few errors in your config:

  1. you configure VLAN interface vlan100 on ether3 … which is later enslaved as bridge port. You should never do that … if ether3 is supposed to carry non-vlan traffic which is of interest of other bridge ports, then you should properly configure bridge with vlan filtering.
  2. you’re configuring IP address 192.168.10.2/30 on ether1 which is at the same time enslaved as bridge port. Since that ‘special’ host seems to be the only host, connected to ether1, it would be best if you removed ether1 from the bridge and use it in a stand-alone manner.

There are other things which are not entirely clear to me, but these two are outstanding …

3

Thanks for pointing these misconfigurations !!

Yet, not only it didn’t fix my problem, it made it worse :laughing:

Before we had a cycle of not avail/avail of 20seconds/2 minutes, not it’s more like 1minute10/2minutes :open_mouth:

Wed Nov  8 22:42:22 +08 2023        75.04 real         0.03 user         0.01 sys
Wed Nov  8 22:43:38 +08 2023 HTTP/2 200 0.15 real         0.02 user         0.01 sys
Wed Nov  8 22:43:58 +08 2023 HTTP/2 200 0.14 real         0.02 user         0.02 sys
Wed Nov  8 22:43:59 +08 2023 HTTP/2 200 0.14 real         0.04 user         0.00 sys
Wed Nov  8 22:44:00 +08 2023        75.10 real         0.03 user         0.01 sys
Wed Nov  8 22:45:17 +08 2023 HTTP/2 200 0.16 real         0.05 user         0.00 sys
Wed Nov  8 22:45:43 +08 2023 HTTP/2 200 0.15 real         0.05 user         0.00 sys
Wed Nov  8 22:45:44 +08 2023        75.03 real         0.02 user         0.02 sys
Wed Nov  8 22:47:00 +08 2023 HTTP/2 200 0.16 real         0.06 user         0.00 sys
Wed Nov  8 22:48:50 +08 2023 HTTP/2 200 0.15 real         0.05 user         0.00 sys
Wed Nov  8 22:48:51 +08 2023        75.03 real         0.01 user         0.02 sys
Wed Nov  8 22:50:08 +08 2023 HTTP/2 200 0.15 real         0.05 user         0.00 sys
Wed Nov  8 22:52:00 +08 2023 HTTP/2 200 0.16 real         0.03 user         0.03 sys
Wed Nov  8 22:52:01 +08 2023        75.12 real         0.02 user         0.02 sys
Wed Nov  8 22:53:17 +08 2023 HTTP/2 200 0.15 real         0.05 user         0.00 sys
Wed Nov  8 22:55:07 +08 2023 HTTP/2 200 0.14 real         0.01 user         0.03 sys
Wed Nov  8 22:55:08 +08 2023        75.03 real         0.03 user         0.01 sys
Wed Nov  8 22:56:24 +08 2023 HTTP/2 200 0.15 real         0.04 user         0.00 sys
Wed Nov  8 22:58:16 +08 2023 HTTP/2 200 0.15 real         0.05 user         0.00 sys
Wed Nov  8 22:58:18 +08 2023        75.03 real         0.03 user         0.01 sys
Wed Nov  8 22:59:34 +08 2023 HTTP/2 200 0.14 real         0.04 user         0.00 sys
Wed Nov  8 23:01:24 +08 2023 HTTP/2 200 0.14 real         0.04 user         0.00 sys
Wed Nov  8 23:01:25 +08 2023

the mystery is getting thicker ( new config attached) …

I’m open to suggestions !!
config-20231108v2.rsc (4.4 KB)

4

Does the Client 2 computer know that 192.168.10.2 is it’s gateway?

5

Yes, Client B ( or your client 2 ) does know this route ( I’m not sure it would even work at all without it ).

Like always , not working at all is easier to debug than working intermittently