Tried all your suggestions before I posted before I posted, different lease periods had same consequences, moved device to different Vlan same. I just gave it a static.You could try adjusting the lease to a short time - five minutes for example and disconnect or switch off all the other devices, to see then if the lease renews - this will demonstrate if another device is conflicting for some reason.
It is also a good idea to make sure that the dhcp pool isn't giving leases that actually exist on the network as statics. Go round, check every device if it has a static write it down. Where possible try to make sure all your static addresses are within a certain range 192.168.88.50 - 100 for example. And then edit the DHCP pool to provide addresses in a different range. Most people setup huge dhcp pools, like 200 addresses when there is on 20 devices possible - so of course a pool of 40 addresses is more than sufficient.
Next, make sure the name of the device is different from your other fire tv - they cannot be the same, but sometimes the manufacturers make the device name the same, because they never expect somebody to have two of them.
Failing that you could try removing that switch port from the master port and setup a seperate subnet with its own dhcp server and pool.
Or lastly give up and assign a static address.
Just out of interest, have you enabled uPNP on your routerboard. I had problems with my Playstation and Android TV until I did.
I indeed set the lease time to only 3m for debugging purpose. With "short lease time" from MikroTik I meant that the ACK is sent with the remaining lease time and not the full 3m. So on the client (the FireTV) the lease runs out because it is never extended.Of course the lease time from the MikroTik is very short, but I think you have set that yourself to debug it.
(i.e. you could set it higher in the DHCP server but then you have to wait longer to reproduce the same issue)
I will try that and report my results.You could try adding the two options manually to the MikroTik DHCP server (a somewhat laborious task, but
it is made simpler because you have the packet from the ZyWall where you can see these options) and check
if that solves it.
The ICMP message was also there on the ZyWall. It seems that packets has no effect in that matter.When you did this test, did you still see the related ICMP message and was it present on the ZyWall as well?
Yes, it may be that the DHCP client is listening on a raw socket and sees the reply, while there is a firewallThe ICMP message was also there on the ZyWall. It seems that packets has no effect in that matter.
I modified the dhcp-server so that it sends those two options as well. I used the following dhcp-server config for that.You could try adding the two options manually to the MikroTik DHCP server (a somewhat laborious task, but it is made simpler because you have the packet from the ZyWall where you can see these options) and check
if that solves it.
/ip dhcp-server add address-pool=pool1 disabled=no interface=ether2 lease-time=3m name=server1 /ip dhcp-server option add code=58 name=RenewalTimeValue value="'90'" add code=59 name=RebindingTimeValue value="'157'" /ip dhcp-server network add address=10.0.0.0/24 dhcp-option=RenewalTimeValue,RebindingTimeValue dns-server=10.0.0.1 gateway=10.0.0.1
I checked with three other devices as dhcp clients (a Windows 10 laptop, a RPi and another MikroTik router). The main difference is, that all those three devices send a unicast to the dhcp server to renew the lease. The FireTV however sends a broadcast.However, the fact that the router does not reply with a new full-length lease when it is re-requested after
half the lease period is also a bit strange. Maybe that is a bug, but then it should be possible to find
the conditions when it occurs because the DHCP server normally works OK for PC and other clients.
(in my experience, at least)
I can absolutely confirm thatAlways nice to learn something!
Yes, the software is "Fire OS 220.127.116.11 (550144920)" and the menu said that there where not updates available.Is the software on that device uptodate?
The Amazon customer support was quite helpful. They told me they can forward my bug report to the development team if I send it in by email (so I did).You could try filing a software bug, but it will probably be very difficult...
The issue has already been debugged and identified, please read back above.You could try setting up a relay for the DHCP server.
Same issue. Just cross graded from my UBNT EdgeRouter to the Mikrotik. First issue was the 10 minute Amazon Fire TV stream issue due to base config setting at 10min lease. Extended to 24 hours. Did not fix. Came upon this thread. Topic push. I have really been impressed with the Mikrotik, but this simple issue is plain stupid, one I never encountered on my Ubiquiti Edge Router.Replying to my own thread... I've bought a Fire TV as I was getting so many customer complaints and wanted to replicate the problem for myself.
Yes this does seem to be DHCP related; the problem goes away if you set a static IP.
From what I can see, the DHCP lease expires and the Fire TV renews it a few seconds later. All should be fine, except that this break in connectivity causes the box decide that there is no internet connectivity. Video will stop playing after any buffer has been used up. Even though the device has a new lease with the same IP address it still refuses to reconnect. Only a reboot of the Fire TV gets it back.
I am going to report to Amazon myself, but in the mean time has anyone else got anywhere?
DHCP server set to authoritative=yesThis doesn't look related to mikrotik DHCP server implementation, but actually poor implementation on the Fire.
Try setting authoritative=yes in the DHCP server config and see if it makes a difference.
That is not how IT and standards work. When you check above, it has been identified as a problem in the Fire. The fact that others have worked around it does not mean that everyone has to.So I'm really going to point the finger at Mikrotik on needing to address this issue.