This is all very weird.
I've connected my first disc and it doesn't request an IP address via DHCP. I've confirmed I've got the correct MAC address in my DHCP table but the disc just doesn't seem to be requesting on the network (nothing appears in my logs from the disc's MAC address).
Tried a second disk from the same pack (slightly different MAC address) and it does the same thing; no DHCP requests sent.
So I assigned a static IP from the Whole Home App on my phone and now I can log on to the disk's web page from any machine on my network so the Ethernet's obviously working.
However, the disc's status page is saying "Ethernet No Connection" (even though there obviously is one as I'm using it to access the disk and read the message!) and the Whole Home App says "Your Wi-Fi is offline" at the top of the page; which is also bonkers as my phone is connected to it, got an IP from my DHCP server and can access the web fine.... until..... the disc turns off the WIFI which it does after a few minutes.
Looking at the discs' log file (using the ethernet with no connection! 🙂 I can see entries like so:
01.11.2016 00:02:10 OWL-RE work fine, but no uplink, turn off user Wi-Fi SSID. 01.11.2016 00:01:50 OWL-Backhaul Ethernet being used for downlink mode. 01.11.2016 00:01:45 Ethernet Port Link Up. 01.11.2016 00:01:36 OWL-start 01.11.2016 00:01:25 Current firmware version is v1.02.01 build24 and boot flag is 1. 01.11.2016 00:01:25 HTTP-start ...
Watching on the WIFI analyser on my phone I can indeed see that the WIFI SSID is going away when the disc's LED goes red. A few minutes later the LED flashes blue for a bit and the WIFI SSID reappears on my analyser, then it goes red with no WIFI again. At no point does the disc stop responding on the Ethernet side.
Does anyone have a clue what's going on here? I know it's not my 'broadband' as that's FTTP and solid.
Solved! Go to Solution.
I've tried connecting to various switches around the building and even on the end of a Devolo power line adaptor - the discs behave the same wherever they're connected.
I've been playing with it more today and had no success whatsoever. It still insists that there's no Ethernet connection even when it's own sys log shows me logging in from devices connected only to my wired network.
Connecting directly to my router isn't an option as it's a FTTP Gigaclear Genexis in bridging mode (only one IP address). That connects to a pfsense firewall and my internal 192.168.1.0/24 network lives behind that.
There's a linux box on the internal network running a DHCP server with specific IPs allocated to MAC addresses (no IP pool). This has been in place for decades and I've never had problems with any of the, probably hundreds, of devices I've connected over the years.
The disc doesn't seem to be generating DHCP requests for it's own Ethernet MAC (48:8D:36:87:1B:21) but I am seeing requests from d0:05:2a:22:22:22 when the disc is powered up. I've allocated an IP to that as well and my DHCP server is sending replies but the disc just keeps requesting every few seconds. Here's a sample from the DHCP log:
Dec 3 11:56:07 lls dhcpd: DHCPDISCOVER from d0:05:2a:22:22:22 via eth2 Dec 3 11:56:07 lls dhcpd: DHCPOFFER on 192.168.1.183 to d0:05:2a:22:22:22 via eth2 Dec 3 11:56:12 lls dhcpd: DHCPDISCOVER from d0:05:2a:22:22:22 via eth2 Dec 3 11:56:12 lls dhcpd: DHCPOFFER on 192.168.1.183 to d0:05:2a:22:22:22 via eth2 Dec 3 11:56:17 lls dhcpd: DHCPDISCOVER from d0:05:2a:22:22:22 via eth2 Dec 3 11:56:17 lls dhcpd: DHCPOFFER on 192.168.1.183 to d0:05:2a:22:22:22 via eth2 Dec 3 11:56:22 lls dhcpd: DHCPDISCOVER from d0:05:2a:22:22:22 via eth2 Dec 3 11:56:22 lls dhcpd: DHCPOFFER on 192.168.1.183 to d0:05:2a:22:22:22 via eth2 Dec 3 11:56:27 lls dhcpd: DHCPDISCOVER from d0:05:2a:22:22:22 via eth2 Dec 3 11:56:27 lls dhcpd: DHCPOFFER on 192.168.1.183 to d0:05:2a:22:22:22 via eth2 Dec 3 11:56:32 lls dhcpd: DHCPDISCOVER from d0:05:2a:22:22:22 via eth2 Dec 3 11:56:32 lls dhcpd: DHCPOFFER on 192.168.1.183 to d0:05:2a:22:22:22 via eth2
A bit of googling tells me that d0:05:2a:22:22:22 is a Arcadyan Corporation MAC and more Googling suggests that's what the BT Whole Home WIFI kit is based on.
I've reset to defaults a whole bunch of times and the disc just won't pickup an IP via DHCP (and annoyingly it seems to default to 192.168.1.1 which clashes with a machine on my network so I have to set a static IP via the http://mybtdevice.home page each time). It has it's WIFI on for a couple of minutes after a power cycle and then flashes the light blue for a bit, then goes red and the WIFI is turned off.
I guess the disc is looking for something before it decides that the Ethernet is working but I can't fathom what. I've got forward and reverse DNS for the IP(s) I'm allocating so it can't be that. What else could it need?
I do see it sending occasional multicasts (to Igmp.mcast.net: 220.127.116.11) and before it goes into a strop and turns the led red, devices connected to it's WIFI can access the internal network and the wider Internet fine.
This really is disappointing. I'm trying to get rid of a whole bunch of APs and this system (if it worked) would seem ideal.
I guess I'm going to have to try the BT helpline on Monday - Oh Joy :smileysad:
I played around with this some more last night and I've now got it working.
Two things made the difference.
1. Realising that the disc sends DHCP requests for the 2.4GHz MAC and not the Ethernet MAC.
2. Upgrading my DHCP server to ISC Version 4.3.6 from 2.something (No changes made to dhcpd.conf).
Having seen the disc get it's IP via DHCP I now see it using my NTP server to update its time which it presumably what it wanted to satisfy itself that the Ethernet was connected.
Quite why the disc is sending the WIFI MAC and not the Ethernet one I don't understand (anyone from BT care to comment as this seems wrong?) but for now I'll mark this as solved.