Maybe this might help
http://www.skyuser.co.uk/forum/sky-broadband-fibre-h... if you are still isimg the wr1043?

In reply to a post by choppersrock:

Well your wan port should be configured to automatic ip if you are using a 3rd party router.

I assume you are not using pfsense. Ipv6 needs to be enabled. Its not immediate far as I know. The only way to check is to see if sky q or sr102 shows a valid ip6 config then you can use your own. I would disable your ipv6 config for now then once you get the wan port connected properly re-enable it.
What are you using router wise now.

I've currently got the "Sky Q Hub" (ER110) plugged in, still no IPv6. I also rang Sky to get it enabled but they said it's a rollout and they can't enabled it manually.

Could it have actually been because I had IPv6 with no support stopping the IPv4 connection?

In reply to a post by choppersrock:

Maybe this might help
http://www.skyuser.co.uk/forum/sky-broadband-fibre-h... if you are still isimg the wr1043?

That guy puts information into some password generator from his router, but it's an older model than the one they sent me, so I'm not entirely sure it'd work.

I also a bit hesitant to go back to DD-WRT because of this: http://www.skyuser.co.uk/forum/sky-broadband-fibre-h...

It will just enable at some point. If this is a new service give it a day or 2. I think my sr102 updated overnight then it was enabled. If you are using the q hub with the modem then you could just reboot the router each morning to see if its gets enabled when it authenticates.

In reply to a post by choppersrock:

It will just enable at some point. If this is a new service give it a day or 2. I think my sr102 updated overnight then it was enabled. If you are using the q hub with the modem then you could just reboot the router each morning to see if its gets enabled when it authenticates.

Right, I'll have to wait for that to happen then with the ER110 plugged in. Quite annoying, can't connect the Sky box anymore as I don't have a spare switch.

I dont know your router etc if it can run as an access point connected to the sky hub that would give you some extra ports for now..

In reply to a post by choppersrock:

I dont know your router etc if it can run as an access point connected to the sky hub that would give you some extra ports for now..

Didn't cross my mind for some reason, of course it can, there's a Dumb AP guide on the OpenWRT Wiki!

I use LEDE (based on Openwrt) with Sky via an HG612 modem without issue, even with IPv6 and get a full /56 delegated to me to do as I see fit.

Possibly some of that trick is that the 'option 61' DHCPv4 request has to be entered as a HEX string, so user/pass combo of '7c4ca2d3a9b8@skydsl|d45f8a77' (made up but of the usual form) would be entered as '37633463613264336139623840736b7964736c7c6434356638613737'

Concentrate on getting IPv4 up first, then IPv6. A suitable extract (and slightly tweaked) from my own working /etc/config/network

config interface 'lan'
option force_link '1'
option type 'bridge'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '64'
option _orig_ifname 'eth1 wlan0 wlan1'
option _orig_bridge 'true'
option ifname 'eth1'
option ip6hint 'dd'

config interface 'wan'
option ifname 'eth0'
option proto 'dhcp'
option release '0'
option clientid '37633463613264336139623840736b7964736c7c6434356638613737'
option peerdns '0'
option dns '8.8.8.8 8.8.4.4'

config interface 'wan6'
option _orig_ifname 'eth0'
option _orig_bridge 'false'
option proto 'dhcpv6'
option ifname 'eth0'
option reqprefix '56'
option peerdns '0'
option norelease '1'
option dns '2001:4860:4860::8888 2001:4860:4860::8844'
option reqaddress 'none'

Note that on my device eth0 is connected to the WAN and eth1 forms part of the internal LAN bridge, often routers use eth0 for LAN and eth1 for WAN.

In reply to a post by kevindb:

I use LEDE (based on Openwrt) with Sky via an HG612 modem without issue, even with IPv6 and get a full /56 delegated to me to do as I see fit.

Possibly some of that trick is that the 'option 61' DHCPv4 request has to be entered as a HEX string, so user/pass combo of '7c4ca2d3a9b8@skydsl|d45f8a77' (made up but of the usual form) would be entered as '37633463613264336139623840736b7964736c7c6434356638613737'

Concentrate on getting IPv4 up first, then IPv6. A suitable extract (and slightly tweaked) from my own working /etc/config/network

config interface 'lan'
option force_link '1'
option type 'bridge'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '64'
option _orig_ifname 'eth1 wlan0 wlan1'
option _orig_bridge 'true'
option ifname 'eth1'
option ip6hint 'dd'

config interface 'wan'
option ifname 'eth0'
option proto 'dhcp'
option release '0'
option clientid '37633463613264336139623840736b7964736c7c6434356638613737'
option peerdns '0'
option dns '8.8.8.8 8.8.4.4'

config interface 'wan6'
option _orig_ifname 'eth0'
option _orig_bridge 'false'
option proto 'dhcpv6'
option ifname 'eth0'
option reqprefix '56'
option peerdns '0'
option norelease '1'
option dns '2001:4860:4860::8888 2001:4860:4860::8844'
option reqaddress 'none'

Note that on my device eth0 is connected to the WAN and eth1 forms part of the internal LAN bridge, often routers use eth0 for LAN and eth1 for WAN.

Thanks for that, I will try again tomorrow with your config.

I see your client ID is hex, mine wasn't like that.

EDIT: So the numbers you have converted into hex, "7c4ca2d3a9b8@skydsl|d45f8a77", did you get them from a Sky router or are they random?

Edited by deleted (Thu 27-Oct-16 23:30:13)

In reply to a post by choppersrock:

It will just enable at some point. If this is a new service give it a day or 2. I think my sr102 updated overnight then it was enabled. If you are using the q hub with the modem then you could just reboot the router each morning to see if its gets enabled when it authenticates.

Just a quick update, the Q hub is now showing a 'Global IPv6 Address'. Interestingly, just like BT, Sky appear to have no IPv6 DNS servers, and the Q hub has no options to change DNS.

When I get back later I will retry the OpenWRT box