Why would the master local have a link of 10M HD, and the slave have a link of 1G FD? I never changed any of these settings when I set up the MT, and it seems to me that if the master local has only a 10M link, it’s going to create a huge bottleneck.
What might cause the IP to be assigned and immediately deassigned?
What might be some reasons for the disconnect due to extensive data loss?
i have the same problem in package 6.37 to 6.38 ???
I’m sure that at least one person, out of all those that have view this thread, has some insight into this.
Nobody? The screenshot has been viewed 113 times and not a single person has any insight into this? Why doesn’t MikroTik have techs perusing their own forums to provide assistance?
The device that is connected to ether2: is in sleep mode, is really old, has a bad ether port, or has a bad cable or it is too long. Only traffic destined to the device on ether2 would be slower. Other device on the other ports will connect at their connection speed.
The IP address in your log was actually deassigned then reassigned. This is due to the DHCP lease time. The shorter the lease time, the more logs like that you will see.
Disconnected, extensive data loss is literal. The device: moved out of range, received outside interference, or has a bad wireless port.
These are all common and expected log entries.
Thanks for the info, everything makes sense. The lease time is set to 3 hours, that’s why it was odd that it deassigned so quickly.