Aura Ethernet connection left me totally confused

Forum Forums Freeview HD Aura UHD Aura Ethernet connection left me totally confused

Viewing 15 posts - 31 through 45 (of 60 total)
  • Author
    Posts
  • #102705
    Anonymous
    Inactive

    Faust – 36 mins ago  » 

    I believe I’m finally getting more of a handle on what’s been happening with the errant Ethernet connection on my new Aura. I appear to have a more stable Ethernet connection (no dropped connection for 4 days) providing I use normal standby. If I use low power standby then I get the dropped Ethernet connection.

    This is what I have observed. If I go into settings then Network and Internet when the Aura is connected the status information shows “not connected” whilst underneath shows not only the Aura IP address but iPV6 addresses.

    When I try using low power standby that status info changes to “connected” (it’s not) again with the Aura IP address plus the iPV6 addresses. The Aura somehow appears to think it’s connecting to iPV6. However, when I look at the connection info on the BT Smarthub for the Aura’s entry it states – The Smart Hub is currently not enabled for IPv6 addressing.

    Now how I get around this issue I’ve no idea and I’m not minded to splash out on a new router on the off chance it could solve the issue. I think I will just have to stick to normal standby.

    I have IPv6 disabled in my router, yet the Aura, my phone, my tablet, my computer, my printer, etc. all have IPv6 addresses. You are barking up the wrong tree again!

    #102706
    Anonymous
    Inactive

    Mars – 48 mins ago  » 

    Faust – 36 mins ago  » 

    I believe I’m finally getting more of a handle on what’s been happening with the errant Ethernet connection on my new Aura. I appear to have a more stable Ethernet connection (no dropped connection for 4 days) providing I use normal standby. If I use low power standby then I get the dropped Ethernet connection.

    This is what I have observed. If I go into settings then Network and Internet when the Aura is connected the status information shows “not connected” whilst underneath shows not only the Aura IP address but iPV6 addresses.

    When I try using low power standby that status info changes to “connected” (it’s not) again with the Aura IP address plus the iPV6 addresses. The Aura somehow appears to think it’s connecting to iPV6. However, when I look at the connection info on the BT Smarthub for the Aura’s entry it states – The Smart Hub is currently not enabled for IPv6 addressing.

    Now how I get around this issue I’ve no idea and I’m not minded to splash out on a new router on the off chance it could solve the issue. I think I will just have to stick to normal standby.

    I have IPv6 disabled in my router, yet the Aura, my phone, my tablet, my computer, my printer, etc. all have IPv6 addresses. You are barking up the wrong tree again!

    I can only report what I am seeing plus it’s now working. I cannot disable iPV6 on my router. It’s also the only device that has an iPv6 address, no other devices in the hub list anything other than iPv4.

    Can you shed any light on the connected/not connected message, what does your Aura report when it’s connected?

    #102707
    Anonymous
    Inactive

    Although I have now found out why the Aura will not stay connected via an Ethernet connection thanks to a long shot suggestion by a Humax technician, the problem isn’t solvable for my setup. The good news however is the Aura works brilliantly via my Mesh WiFi.

    #102708
    Martin Liddle
    Participant

    Faust – 41 mins ago  » 

    Although I have now found out why the Aura will not stay connected via an Ethernet connection thanks to a long shot suggestion by a Humax technician, the problem isn’t solvable for my setup.

    What was the long shot suggestion?

    #102709
    Anonymous
    Inactive

    Faust – 4 weeks ago  » 

    My replacement Aura arrived yesterday as the original just couldn’t for whatever reason maintain an Ethernet connection. There was clearly a fault possibly the Ethernet port or a fault on the Logic board as the replacement is working just fine. However there is still a quirk with the replacement which I simply can’t get my head around.

    When I go into settings and click on Network and Internet it states not connected then underneath is a long string of letters and symbols like a MAC adress plus the Aura’s IP address. However, I can’t work out what the long string is as it’s not the WLAN, LAN, or Bluetooth Mac address of the machine. Anyone got any ideas?

    fdaa:bbcc:ddee:0:e95:283f:cb:19c2<br

    This is the IP6 address.

    #102710
    Anonymous
    Inactive

    Faust – 5 hours ago  » 

    Although I have now found out why the Aura will not stay connected via an Ethernet connection thanks to a long shot suggestion by a Humax technician, the problem isn’t solvable for my setup. The good news however is the Aura works brilliantly via my Mesh WiFi.

    I changed my setup so the Aura connects directly into my BT Home hub. Previously it was connected via a 4 port hub. Since connecting directly, I haven’t had any ethernet connection issues.

    Not sure why, as everything else connected to the 4 port hub works fine and doesn’t have any issues.

    #102711
    Anonymous
    Inactive

    Martin Liddle – 1 day ago  » 

    Faust – 41 mins ago  » 

    Although I have now found out why the Aura will not stay connected via an Ethernet connection thanks to a long shot suggestion by a Humax technician, the problem isn’t solvable for my setup.

    What was the long shot suggestion?

    I have mesh WiFi which connects directly into the BT Homehub and effectively replaces the HH as the router for all WiFi traffic. The HH then simply becomes a gateway device for DCHP and Ethernet connected traffic. The technician suggested disconnecting the Mesh disk to see if it had any effect on the Ethernet connection. As soon as I disconnected the mesh disk the Aura connected by Ethernet and would stay connected even with repeated shutdowns into low power standby. As soon as I reconnected the mesh disk the Aura dropped the Ethernet connection again. As I need the Mesh WiFi I’m now using the Aura on WiFi via the Mesh and the connection is rock solid.

    #102712
    Martin Liddle
    Participant

    Faust – 38 mins ago  » 

    I have mesh WiFi which connects directly into the BT Homehub and effectively replaces the HH as the router for all WiFi traffic. The HH then simply becomes a gateway device for DCHP and Ethernet connected traffic. The technician suggested disconnecting the Mesh disk to see if it had any effect on the Ethernet connection. As soon as I disconnected the mesh disk the Aura connected by Ethernet and would stay connected even with repeated shutdowns into low power standby. As soon as I reconnected the mesh disk the Aura dropped the Ethernet connection again. As I need the Mesh WiFi I’m now using the Aura on WiFi via the Mesh and the connection is rock solid.

    Can I check I understand the topology of your network: you have a BT Home Hub which is the modem and the router for the WiFi; you then have a separate router supplying ethernet. Is that correct? What advantage does the separate router give you?

    #102713
    Anonymous
    Inactive

    Martin Liddle – 15 mins ago  » 

    Faust – 38 mins ago  » 

    I have mesh WiFi which connects directly into the BT Homehub and effectively replaces the HH as the router for all WiFi traffic. The HH then simply becomes a gateway device for DCHP and Ethernet connected traffic. The technician suggested disconnecting the Mesh disk to see if it had any effect on the Ethernet connection. As soon as I disconnected the mesh disk the Aura connected by Ethernet and would stay connected even with repeated shutdowns into low power standby. As soon as I reconnected the mesh disk the Aura dropped the Ethernet connection again. As I need the Mesh WiFi I’m now using the Aura on WiFi via the Mesh and the connection is rock solid.

    Can I check I understand the topology of your network: you have a BT Home Hub which is the modem and the router for the WiFi; you then have a separate router supplying ethernet. Is that correct? What advantage does the separate router give you?

    No, I have a BT smart hub which now has WiFi disabled because I’m using BT WholeHome Wifi Mesh disks which replaces the HH WiFi and provides far superior WiFi to all parts of my property. The Mesh WiFi comprises three disks (you can add more) one of the disks becomes the “master disk” (the one connected to the router) and also becomes your router for WiFi traffic. The other disks (strategically placed in other rooms) mesh with the main disk and as you move around the property seamlessly hand off your devices e.g. smartphone from one disk to another. That way you always get the maximum signal.

    #102714
    Anonymous
    Inactive

    Faust – 2 hours ago  » 

    No, I have a BT smart hub which now has WiFi disabled because I’m using BT WholeHome Wifi Mesh disks which replaces the HH WiFi and provides far superior WiFi to all parts of my property. The Mesh WiFi comprises three disks (you can add more) one of the disks becomes the “master disk” (the one connected to the router) and also becomes your router for WiFi traffic. The other disks (strategically placed in other rooms) mesh with the main disk and as you move around the property seamlessly hand off your devices e.g. smartphone from one disk to another. That way you always get the maximum signal.

    With this setup, does the BT Wholehome Wifi provide it’s only internal DHCP and subnet to anything that connects to the new Wifi?

    I had a TP-LINK Deco M4 Whole Home WiFi System, which I did some testing with. With this I found it used it’s own DHCP and subnets. This meant that anything connected on the Tp-Link mesh network couldn’t see anything connected on the Ethernet network. So when I had the Aura connected to the ethernet port and my mobile phone connected to the TP-Link mesh network, then the Aura app wouldn’t work, as it couldn’t see the Aura.

    Could it be a clash of IP addresses somewhere? The DHCP on the BT Home hub and the BT WholeHome Wifi are trying to use the same range?

    #102715
    Anonymous
    Inactive

    MattB1 – 2 hours ago  » 

    Faust – 2 hours ago  » 

    No, I have a BT smart hub which now has WiFi disabled because I’m using BT WholeHome Wifi Mesh disks which replaces the HH WiFi and provides far superior WiFi to all parts of my property. The Mesh WiFi comprises three disks (you can add more) one of the disks becomes the “master disk” (the one connected to the router) and also becomes your router for WiFi traffic. The other disks (strategically placed in other rooms) mesh with the main disk and as you move around the property seamlessly hand off your devices e.g. smartphone from one disk to another. That way you always get the maximum signal.

    With this setup, does the BT Wholehome Wifi provide it’s only internal DHCP and subnet to anything that connects to the new Wifi?

    I had a TP-LINK Deco M4 Whole Home WiFi System, which I did some testing with. With this I found it used it’s own DHCP and subnets. This meant that anything connected on the Tp-Link mesh network couldn’t see anything connected on the Ethernet network. So when I had the Aura connected to the ethernet port and my mobile phone connected to the TP-Link mesh network, then the Aura app wouldn’t work, as it couldn’t see the Aura.

    Could it be a clash of IP addresses somewhere? The DHCP on the BT Home hub and the BT WholeHome Wifi are trying to use the same range?

    I don’t really know what the issue is but I can confirm that the Aura over mesh WiFi has a different IP address to that of the Aura using Ethernet though only by one digit.

    #102716
    Anonymous
    Inactive

    That does sound like a DHCP issue; you shouldn’t have DHCP on the Home Hub AND the Whole Home wifi, it should be on one or the other only.

    I’ve not got anything connected via ethernet, but I’ve also got a mesh wifi network (Deco M4, using a Huawei fibre modem). I’ve got other routers connected to the mesh but all have to have their DHCP servers disabled to allow the M4’s “master” unit to act as the router.

    I may be wrong, but in terms of the server which is dishing out DHCP addresses I believe it is correct that for a single network there should be only a single DHCP server, which would result in all devices being allocated IP addresses within the same network.

    It sounds to me in the BT setup that you’ve got two devices trying to act as routers – the Home Hub and the “master” wifi disc. Surely only one should take that role, even if the “master” wifi disc is the only device which is creating a Wifi SSID?


    #102717
    Anonymous
    Inactive
    Quote:

    larkim – 41 mins ago  » 

    That does sound like a DHCP issue; you shouldn’t have DHCP on the Home Hub AND the Whole Home wifi, it should be on one or the other only.

    I’ve not got anything connected via ethernet, but I’ve also got a mesh wifi network (Deco M4, using a Huawei fibre modem). I’ve got other routers connected to the mesh but all have to have their DHCP servers disabled to allow the M4’s “master” unit to act as the router.

    I may be wrong, but in terms of the server which is dishing out DHCP addresses I believe it is correct that for a single network there should be only a single DHCP server, which would result in all devices being allocated IP addresses within the same network.

    It sounds to me in the BT setup that you’ve got two devices trying to act as routers – the Home Hub and the “master” wifi disc. Surely only one should take that role, even if the “master” wifi disc is the only device which is creating a Wifi SSID?

    What is supposed to happen is that once you connect the first disk to your router that then becomes the de facto router for all the WiFi devices. Hence why you should disable the routers WiFi. The original router continues its function as a gateway for hardwired devices. I can see no evidence of dual DCHP allocation but will investigate this further.

    #102718
    Anonymous
    Inactive

    If the devices are on different subnets then something non-standard seems to be going on. It could all be “as designed” by BT of course, but if my Deco setup used my EE Hub instead of a dedicated modem of still expect all devices, wired or wireless, to be on the same 192.168.1.xxx, rather than wired on 192.168.1.xxx and wireless on 192.168.2.xxx for example.

    #102719
    Anonymous
    Inactive

    larkim – 12 hours ago  » 

    If the devices are on different subnets then something non-standard seems to be going on. It could all be “as designed” by BT of course, but if my Deco setup used my EE Hub instead of a dedicated modem of still expect all devices, wired or wireless, to be on the same 192.168.1.xxx, rather than wired on 192.168.1.xxx and wireless on 192.168.2.xxx for example.

    I have spoken to BT about this issue and it’s perfectly normal behaviour. There is only one router handling DCHP and that’s the Smarthub. A device using WiFi via the Mesh network will always have a different IP address than if it was using Ethernet via the Smarthub. Ethernet and WiFi will have a different MAC address with this setup, so a different IP address will follow.

Viewing 15 posts - 31 through 45 (of 60 total)
  • You must be logged in to reply to this topic.

The inner genius!