Bananian

DHCP stopped working after upgrade to 16.04

0 1087
salty  
Edited by salty at Apr 29, 2016 09:43

Hi,

I'm having issues with Bananian after upgrading to 16.04. Everything was working just fine before upgrading, I have a DHCP server on my OpenWrt router and it is trying to offer the Banana Pi an ip but the Pi keeps on declining it. The Pi never successfully boots up if the ethernet cable is connected, it just stays in an endless loop where it tries to get an ip. This is what the endless loop looks like on the Pi;

DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPOFFER from 192.168.0.1
DHCPACK from 192.168.0.1
DHCPDECLINE on eth0 to 255.255.255.255 port 67

I have not changed anything on the OpenWrt router. This is what the problem looks like on the router (I have set up a static lease for the Pi but removing it does not solve the issue, the Pi still declines all ip's):

12:10:41 2016 daemon.info dnsmasq-dhcp[2206]: DHCPDISCOVER 192.168.0.109 02:54:xx:xx:xx:xx
12:10:41 2016 daemon.info dnsmasq-dhcp[2206]: DHCPOFFER 192.168.0.161 02:54:xx:xx:xx:xx
12:10:41 2016 daemon.info dnsmasq-dhcp[2206]: DHCPREQUEST 192.168.0.161 02:54:xx:xx:xx:xx
12:10:41 2016 daemon.info dnsmasq-dhcp[2206]: DHCPACK 192.168.0.161 02:54:xx:xx:xx:xx
12:10:41 2016 daemon.info dnsmasq-dhcp[2206]: DHCPDECLINE 192.168.0.161 02:54:xx:xx:xx:xx
12:10:41 2016 daemon.warn dnsmasq-dhcp[2206]: not using configured address 192.168.0.110 because it was previously declined
12:10:44 2016 daemon.info dnsmasq-dhcp[2206]: DHCPDISCOVER 192.168.0.109 02:54:xx:xx:xx:xx
12:10:44 2016 daemon.info dnsmasq-dhcp[2206]: DHCPOFFER 192.168.0.162 02:54:xx:xx:xx:xx
12:10:44 2016 daemon.info dnsmasq-dhcp[2206]: DHCPREQUEST 192.168.0.162 02:54:xx:xx:xx:xx
12:10:44 2016 daemon.info dnsmasq-dhcp[2206]: DHCPACK 192.168.0.162 02:54:xx:xx:xx:xx
12:10:44 2016 daemon.info dnsmasq-dhcp[2206]: DHCPDECLINE 192.168.0.162 02:54:xx:xx:xx:xx
12:10:44 2016 daemon.warn dnsmasq-dhcp[2206]: not using configured address 192.168.0.110 because it was previously declined

Thanks in advance for any suggestions!

You have to log in before you can reply Login | Sign Up

Points Rules