Serious Problem:

Entire network is being routed by a PC x86 platform AMD 1.2Ghz, 256MB and RouterOS 3.10. Due to untidy growing and upgrading, network is conformed by VLANs over ether2 interface but also, a plain network (no vlan) is placed over this interface (it is a sort of lan coupled to a trunking).

ETH2 ---- 40.0.10.X
|___VLAN110-- 192.168.110.X
|___VLAN120-- 192.168.120.X

A file server is conected on vlan110 with 192.168.110.144 ip address.
People from vlan120 and from 40.0.10.X can access file server perfectly


The big problem arose when we wanted to migrate from PC to RB1000!. When host from 40.0.10.X try to access file server, they are not able to do it because router does not route between vlan and no-vlan networks (over the same interface). However, it has been working without any kind of problem over the PC.

NOTE: we have performed all kind of tests with many RouterOS versions and the same happen all the time over RB1000, we know this network arquitecture is not suittable at all, but we need to mantain this configuration until we can manage our network in a diferent and correct way.

Ivan Perino

RB1000 does not have any differences for routing over VLAN and non-VLAN interface.
It works in the same way like x86 works, RB100, RB200, RB300, RB400, RB500, RB600; there is no difference.
Please, check your configuration !

I have done 5 tests and believe me, configuration is OK.

3 tests have been performed on x86, RB600 and RB532 with ROS 3.10v with the same configuration and all of them worked properly.
2 tests have been performed on diferents RB1000 with ROS 3.3 and another with 3.10 with the same configuration and they didnt work.

- Bench tests performed on RB1000 diplayed NO routing capability between VLANs and LAN conected to the same interface even though they are DAC (directly connected) (you dont need to configure anything)

** after conecting LAN to another Eth port (eth3) and leaving Eth2 just for VLANs...

eth2 --- VLAN110
|______VLAN120
|______VLAN130

eth3 --- 40.0.10.X
((((( please, remember that 40.0.10.X is blended in the trunking, then both ports [eth2, eth3] were connected to the trunking available on our switch))))

this happened...
- We had more than 50% packets lost (ping test) between LAN and VLANs and in many cases, Router doesnt route!.
- The router stops sending Neighbor broadcast (MDP) becoming inaccesible (trying unused eth ports). hence, it becomes inaccessible through IP address. It seems to hang up!

The curious thing is none of these things happen using RB600 or 532 or x86 moreover, these routers work VERY FAST and WELL!

I will realy appreciate your help. I am disposed to send you any test I did just for contributing (humbly) to mokrotik.

PS: Power Supply was wrong connected from factory, I mean, positive to negative and viceversa hence I had to swap terminals to get the RB1000 switched on

Mindfully, Eng. Ivan Perino

I suggest you to contact support (support@mikrotik.com) and provide configurations [support output files] from RB1000 with 3.10 version.
and describe the same problems and add more detailed description and attach simple network diagram.

- We had more than 50% packets lost (ping test) between LAN and VLANs and in many cases, Router doesnt route!.
- The router stops sending Neighbor broadcast (MDP) becoming inaccesible (trying unused eth ports). hence, it becomes inaccessible through IP address. It seems to hang up!