Hello.
It is long, but necessary.
Test settings:
--------------
RouterBoard 153 version 2.9.34
ARP: ENABLED - on all interfaces
NOTE: ARP_PROXY IS NOT ACTIVATED ON ANY INTERFACE
ether1 00-0c-42-0d-1d-6a
ether2 00-0c-42-0d-1d-6b
ether3 00-0c-42-0d-1d-6c
ether4 00-0c-42-0d-1d-6d
ether5 00-0c-42-0d-1d-6e
ether1 192.168.101.12/24
ether2 192.168.102.12/24
ether3 192.168.103.12/24
ether4 192.168.104.12/24
ether5 192.168.105.12/24
Windows adapter list:
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-00-00-B0-0D-EE
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.105.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.104.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.103.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.102.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Test results:
-------------
Arp table is always discarded before test (arp -d).
Connected to physical ether1
Arp list after
ping 192.168.102.12 ping 192.168.103.12 ping 192.168.104.12 ping 192.168.105.12
Internet Address Physical Address Type
192.168.102.12 00-0c-42-0d-1d-6a dynamic - bad record
192.168.103.12 00-0c-42-0d-1d-6a dynamic - bad record
192.168.104.12 00-0c-42-0d-1d-6a dynamic - bad record
192.168.105.12 00-0c-42-0d-1d-6a dynamic - bad record
NO RECORD SHOULD BE HERE
Connected to physical ether2
Arp list after
ping 192.168.102.12 ping 192.168.103.12 ping 192.168.104.12 ping 192.168.105.12
Internet Address Physical Address Type
192.168.102.12 00-0c-42-0d-1d-6b dynamic - only correct record
192.168.103.12 00-0c-42-0d-1d-6b dynamic - bad record
192.168.104.12 00-0c-42-0d-1d-6b dynamic - bad record
192.168.105.12 00-0c-42-0d-1d-6b dynamic - bad record
Connected to physical ether3
Arp list after
ping 192.168.102.12 ping 192.168.103.12 ping 192.168.104.12 ping 192.168.105.12
Internet Address Physical Address Type
192.168.102.12 00-0c-42-0d-1d-6c dynamic - bad record
192.168.103.12 00-0c-42-0d-1d-6c dynamic - only correct record
192.168.104.12 00-0c-42-0d-1d-6c dynamic - bad record
192.168.105.12 00-0c-42-0d-1d-6c dynamic - bad record
Connected to physical ether4
Arp list after
ping 192.168.102.12 ping 192.168.103.12 ping 192.168.104.12 ping 192.168.105.12
Internet Address Physical Address Type
192.168.102.12 00-0c-42-0d-1d-6d dynamic - bad record
192.168.103.12 00-0c-42-0d-1d-6d dynamic - bad record
192.168.104.12 00-0c-42-0d-1d-6d dynamic - only correct record
192.168.105.12 00-0c-42-0d-1d-6d dynamic - bad record
Connected to physical ether5
Arp list after
ping 192.168.102.12 ping 192.168.103.12 ping 192.168.104.12 ping 192.168.105.12
Internet Address Physical Address Type
192.168.102.12 00-0c-42-0d-1d-6e dynamic - bad record
192.168.103.12 00-0c-42-0d-1d-6e dynamic - bad record
192.168.104.12 00-0c-42-0d-1d-6e dynamic - bad record
192.168.105.12 00-0c-42-0d-1d-6e dynamic - only correct record
Test conclusion:
----------------
Mikrotik's ARP is not working properly.
Only IP assigned to ether interface should answer.
I tried other routerboards and all have broken ARP subsystem.
RouterOS PC version 2.9.38 does not work correctly too.
I understand it is linux but there are some problems:
1) I am windows programmer and not much into the linux.
2) I do not see any interesting configuration files in terminal or ftp.
3) I did not even find what Linux version it is.
Questions:
----------
1) Does anybody knows how to repair Mikrotik with configuration or any other way ?
2) Does anybody know if it is global Linux problem or Mikrotik's fault ?
3) If it is Linux problem, can be Mikrotik patched in some way ?
4) Maybe it is well known problem, but why nobody knows then ?
Thank You.