@bluetomgold
If that is a British Telecomms hub have you tried restarting it ? (with the Daphile connected and powere up 🙂)
If that is a British Telecomms hub have you tried restarting it ? (with the Daphile connected and powere up 🙂)
Rather than take the Daphile machine home I brought the second machine into work to see if matters improved - behaviour is the same, neither device recognises each other.
Fairly sure these are Wi-Fi connections - but to clarify I have also been able to connect my windows laptop via Ethernet.
Plugged into the same ethernet wall/router socket as the non-working machines?
Just tried turning the router firewall off to see if that made any difference. It did not,
Correct.
Thought I'd give this a little bump. Any ideas? I could see if I can get it to work wirelessly I suppose.
I'll toss a couple things into the mix. First I'd check to see if the lights come on when you plug in the daphile box into the hub. Both the hub and the daphile should have lights. Could be the cable is an X cable and the daphile/hub do not have auto-switching. The lights will indicate of the hardware has made a connection. Next up is the DHCP. It is possible the daphile was configured with a fixed IP address. I'm assuming the daphile is linux here, but do a /sbin/ifconfig -a on the command line of the daphile after it is connected.it should show the IP address of the eth0 connection. If static, it may not match up with the addresses available for static in your hub. I think it must be between 192.168.1.2 and 192.168.1.63 for your case. Everything 64 and above is reserved for DHCP. You can also do a netstat -nr where you should get something like
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlp2s0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp2s0
My guess is the daphile is configured static and your hub is dynamic. If your home network used 192.168.0.1-255 then the daphile will not see anything on the network. The ifconfig should look something like
wlp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.98 netmask 255.255.255.0 broadcast 216.30.52.255
inet6 fe80::b38c:a7f0:8f85:7d5e prefixlen 64 scopeid 0x20<link>
ether d8:9c:67:95:b6:79 txqueuelen 1000 (Ethernet)
RX packets 233322171 bytes 179006217718 (179.0 GB)
RX errors 0 dropped 13971841 overruns 0 frame 0
TX packets 137090368 bytes 32377727123 (32.3 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Note the flags field has UP and RUNNING included. Of course yours is going to have a different name than wlp2s0, that is my machines wifi adapter address.
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlp2s0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp2s0
My guess is the daphile is configured static and your hub is dynamic. If your home network used 192.168.0.1-255 then the daphile will not see anything on the network. The ifconfig should look something like
wlp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.98 netmask 255.255.255.0 broadcast 216.30.52.255
inet6 fe80::b38c:a7f0:8f85:7d5e prefixlen 64 scopeid 0x20<link>
ether d8:9c:67:95:b6:79 txqueuelen 1000 (Ethernet)
RX packets 233322171 bytes 179006217718 (179.0 GB)
RX errors 0 dropped 13971841 overruns 0 frame 0
TX packets 137090368 bytes 32377727123 (32.3 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Note the flags field has UP and RUNNING included. Of course yours is going to have a different name than wlp2s0, that is my machines wifi adapter address.
Thank you for your ideas!
No lights. Have tried 3 cables, all of which should be standard, one of which I had used previously to connect the machine to my home network.
Given that the Daphile won't get past the "waiting for network connection" screen I'm not sure whether I can get to a command line...
...in any case, I think how the machines are configured is moot - when booting from the Daphile live boot/install USB (default configuration for setting up - would assume IP address assigned dynamically?) router and machines still fail to recognise each other.
When accessing the 2 Daphile boxes on my home network I used
http://192.168.1.195/
http://192.168.1.128/
not sure whether that helps at all!
OK, not what I expected. No lights on most hubs/machines means no link. No link means no communication. Was not expecting dead physical comms, was expecting configuration problem. I'll toss another wild idea out there. At home could the daphile box had been connected via wifi? I googled a bit to discover daphile is a derivative O/S and not linux based. It did walk thru the install though. Did the box you put it on have a video out/keyboard option? It looked like you do some initial setup locally and then the rest is done via http. I'm afraid you may have to take it home again and examine how it is configured unless you have a way to connect a monitor to the box at work if that is even possible.
Neither box has Wi-Fi onboard, so no.
Yes, there's no problem connecting a monitor or keyboard at work. There are some manual configuration options, although previously I didn't need to engage with these.
I'm still inclined to think that the issue is more likely to be related to settings on the router/hub than settings on the Daphile - as this is the element that has changed, it's a very recent installation from BT.
I might just try booting Daphile from USB on my regular work laptop to see if that works...
OK, I just tried a live boot of Daphile on my work laptop. Running Windows this machine happily connects to the hub via wifi or ethernet.
Booting Daphile the machine would not connect to the hub via ethernet. Lights were blinking on the laptop but not the hub. In this case as the machine has wifi Daphile would have enabled me to control it via web console via wifi hotspot. No help for getting the other boxes working.
It seems that there is a particular issue between the ethernet connections on my hub and Daphile. Have had a quick look at initial settings (F1 option in live boot) - it looks like these enable you to set up a static IP address. Not sure whether this is likely to be helpful?
Booting Daphile the machine would not connect to the hub via ethernet. Lights were blinking on the laptop but not the hub. In this case as the machine has wifi Daphile would have enabled me to control it via web console via wifi hotspot. No help for getting the other boxes working.
It seems that there is a particular issue between the ethernet connections on my hub and Daphile. Have had a quick look at initial settings (F1 option in live boot) - it looks like these enable you to set up a static IP address. Not sure whether this is likely to be helpful?
I need to apologise. I have just double checked and I was wrong in my previous post - the ethernet lights on the Daphile machine do illuminate/blink. There are no lights visible on the hub though.
Can't edit my previous post, probably because you have quoted me...
Perhaps one of the devices insists on some fixed speed (it's unlikely, but technically possible) which the other side cannot provide (e.g. the hub talking only at gigabit and daphile having only 100Mbps)?
Daphile is linux gentoo with squashfs:
Code:
pavel@precision:/tmp$ unsquashfs rootfs
created 24192 files
created 3535 directories
created 3306 symlinks
created 0 devices
created 2 fifos
pavel@precision:/tmp$ cat squashfs-root/etc/gentoo-release
Daphile 24.06-x86_64Looking at BT hubs specs https://www.bt.com/help/broadband/learn-about-broadband/different-types-of-bt-hub , the new hubs are gigabit, while the older were only 100Mbps. I can imagine the daphile device tries to connect at gigabit but fails somehow.
Maybe there is a setting on the BT hub for the hardwired ethernet. I think I've got some stuff with giga ports and I thought some connected to 100M but may be wrong. I know giga uses all 8 wires while 10/100 use only 4. It is possible the hub has turned off lights though, so it may be linked but not turning on the light for darkness. The daphile link lights on are some indication that the link is active. So perhaps it is connecting and because the dhcp starts at 64, the hub may not be allowing your 128 and 195 addresses. I'm pretty sure you have setup static IP's. So one more idea to toss out. Either reconfigure the daphiles to dhcp via the monitor/keyboard direct interface or set them to a static Ip of less than 64.
The hub at home is a Smart Hub 2 - at work it's a BT Business Smart Hub 3. Both gigabit.
You're correct that once set up the boxes are on a static IP (the address enables you to access them via web console). However, on a reset (or booting from USB) they default to DHCP. As stated I've tried running the OS as a live boot from the USB - which would be DHCP - but with no success.
If you have old switches lying around like me, try plugging the daphile into the switch and then on another port on the switch plug into the BT hub. Then you can see if lights come on for both ports on the switch and with luck the switch has activity lights and you can at least see who is sending packets. This is one weird problem.
No switches lying about.
FWIW I took one home and have been using it again without issue on my home network.
I had a quick look at the settings last night, it is set to DHCP.
I’ve pretty much given up hope of getting this working via Ethernet, wasted too much time already… but I plan to try one or two Wi-Fi adapters this week to see if that route is more successful.
FWIW I took one home and have been using it again without issue on my home network.
I had a quick look at the settings last night, it is set to DHCP.
I’ve pretty much given up hope of getting this working via Ethernet, wasted too much time already… but I plan to try one or two Wi-Fi adapters this week to see if that route is more successful.
The only thing I can think of is the daphile will not connect to the 1G ethernet port of the hub at work and the 1G hub will not negotiate down to the 100MB daphile port. Weird. I thought all modern equip would go down to even 10MB if the counter-party wanted it. Because I think we know.
Hub works, you connected a laptop to it successfully. Maybe check the laptop to see if its ether is 1G or 100M after connecting.
Daphile works at home
No lights on ether with daphile indicating a hardware issue
Simplest solution might be to get a cheap 4 port switch that does 1G and 100M. Probably around 25 bucks. Connect one port to the BT hub and one to the Daphile. Let the cheap switch handle the 1G/100M conversion.
Hub works, you connected a laptop to it successfully. Maybe check the laptop to see if its ether is 1G or 100M after connecting.
Daphile works at home
No lights on ether with daphile indicating a hardware issue
Simplest solution might be to get a cheap 4 port switch that does 1G and 100M. Probably around 25 bucks. Connect one port to the BT hub and one to the Daphile. Let the cheap switch handle the 1G/100M conversion.