I have been using Tomato Shibby for a while now, but I was running an older version and didn't upgrade until the Heartbleed fix, then I updated. I'm now on v120. Pre-upgrading the router had been running without issues for a year.
Since upgrading to the Heartbleed fix, I'm running into an issue with DHCP leases, where it looks like something else is assigning an IP address but I honestly don't know what it could be.
I'm now at work and my phone is with me, so it is definitely not on the network. Here is a current screenshot of the device list:
s14. postimg .org /k3ojyn435/Screen_Shot_2014_06_17_at_11_36_53.png ^^ Please join the URL as it won't let me paste links, sorry for the inconvenience!
As you can see it is in the device list, even though it shouldn't be. The lease time is set to 20 minutes for now while I'm trying to work this out.
My setup is very small (isolated to just 2 bedrooms).
There is a 'master' modem which is connected into the WAN port on my N66U, which provides a direct external IP addresses. We also have 4 IPTV's plugged into the 'master' modem as well as one other router which services another area of the apartment out of range.
On the LAN side, the only physical connections are my Xbox One and Xbox 360, which rarely get switched on.
Wireless is pretty much limited to my laptop, phone and iPad.
Router LAN IP: 192.168.157.1
DHCP range is 192.168.157.100-199
I have static DHCP leases for my own devices, 192.168.157.10-15.
The symptoms will be when I get home, I cannot connect to the internet on my phone as it won't receive an IP address from the router. It is sometimes my phone, sometimes my laptop… Either way the same case, they won't get an IP address.
Has anyone come across this or have any idea? My only thought is that the DHCP may be coming from the modem or the other router, but technically the other router will be on another subnet as it also receives a direct external IP address and they are both connected to the WAN port anyway, so shouldn't interfere with my LAN.