Hi,
I've been using Mikrotik products for many years. Now I connected with the problem.
Datacenter offered me switch port to HP-5308xl-switch, and I saw that ProCurve doesn't like Routerboard's ethernet link signals.
Firstly I connected Routerboard's first ethernet interface to switch via patch link. Set up host (IP/mask/gate) as host only router. The problem begins that I'couldn't connect to it from it's real IP address. With many tries I get connected. I mentioned also, that there's a big packet loss.
I asked to datacenter technical stuff to discover the problem, they said that "my device" has double and tripple MAC addresses seen on network.
Firstly they though that I am using a switch not router, with disabled STP protocol on bridge interface
I tried to change MAC adressess, switch ports to another - no results, then I changed Routerboards ethernet interface ports from ether1 to ether5, then performance was better (less packet loss), I also unchecked (disabled) auto-negotioation option under ethernet device.
I tried to ping real network address from mikrotik's console, then there haven't any packet loss.
But the problem connecting to router's real IP address from outside networks - still active.
I also tried to put my configuration on RB433 to ensure that there's no router problem, but also the same.
Both devices uses the same IC+ switch chip, and I think this IC+ conflicts with HP ProCurve switch. Tomorrow I'll ask to prepare me another port on Cisco switch, then I try again.
Has anybody connected with the same problem?
##############################################
Pings looks like:
Pinging xxx.yyy.zzz with 32 bytes of dat
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Ping statistics for xxx.yyy.zzz:
Packets: Sent = 80, Received = 62, Lost = 18 (22% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
##############################################
There's 30-50% packet loss, it's abnormal.
Routerboard 450
OS: latest - RouterOS 5.14.
firmware: latest - 2.39