Settings to configure alternative router to work with Sky Fibre / DHCP Option 61

[BrianGJSteer]

1. Plug in your TP-Link to a power supply and connect the grey DSL cable to the corresponding port on the back of your router. 2. Connect the other end of your DSL cable to the micro-filter that comes with the router and connect it to your phone socket. If you already have a micro-filter, replace it with the new one. 3. Connect the network cable to port 1 on the router, then connect the other end to your laptop. 4. Open a browser window and navigate to http://192.168.1.1. 5. The TP-Link will ask you to set an admin password – make sure you use something secure, as Password123 ain’t gonna cut it! 6. Once in, the TP-Link setup wizard will start: Input your location and time zone. Click Next. Select Sky(MER)_VDSL from the ISP list. Make sure it’s this one, as this is Sky fibre. The other Sky option in the list is for Sky Broadband and will not work for fibre connections. Internet connection type In the username field, enter abcdefgh@skydsl In the password field, enter 1234567890abcdef Click Next, then set up your wireless network how you see fit. SSID Password   The TP-Link will then test the Internet connection and you should see a success message. If you do not, wait for the DSL light to stop flashing and try again – it should work just fine. 7. That’s it! You’re now connected to Sky fibre via your new TP-Link router.

[G404]

Watson+-+PC

how did you manage to connect TP Link Archer 2100 to Sky Q box and Q minis? could you please post the steps taken for the same? I can connect to Sky broadband with TP Links 2100 withno problems but so far unable to connect Q box and minis through Wifi to TP Links 2100. Thanks

[BrianGJSteer]

I can see the VR2100 when I search for the network on the Sky Q box, so I just add the password and it connects. I did buy a TP-Link Mesh M9 tripple pack and one is directly connected to the VR2100, and I actually use that network to connect to the Sky Q, but either works fine. In my case there is just one wall between the router and mesh to the TV which I connect via Wi-Fi. I have no problem connecting.

[Cheezy2015]

Hi Matt

Did you ever get any joy setting up the Dream Machine Pro working?

Cheers

Chris

[Matt1408]

It's working but behind another Router that is handling Option 61 - I don't seem to be able to get it to work directly connected to either a BT Openreach Modem or a Vigor 130

I have not looked at it for a while as I do not want to start playing with settings when I don't have a few hours to spare in case something goes pear-shaped...

[Cheezy2015]

Hi Matt @Matt1408 

in the Network setting page for the Wan connected to the sky modem(in my case WAN1), I've set the following

IPV4 to "Using DHCP"

IPV6 to "Using DCHPv6

prefix Delegation size to 64

DNS servers are set to the two sky ones

90.207.238.97 and 90.207.238.99

I clicked on add a DHCP option, then DHCP Client Options selected  "Option 61"

with a value to "True"

Hit the save button and stared at the Draytek for a bit then the Wan1 on Unify went green.

Hope this helps as there was a lot of trail and error to get it up and running

[stevieb3]

Hi Matt, I have my UDM Pro working directly connected to my ONT box, you can enable option 61 in the settings if you have it set to classic view instead of the new user interface, once you choose option 61, a username and password box should appear, I think there's a generic username/password combo that has been posted previously.

[Matt1408]

Hi Stevie,

I have tried that and I just does not seem to want to work, got nothing from the UDM pro, keeps saying no internet!!

[Matt1408]

Hi @Cheezy2015 

I have not used the sky router for years now, only used it to wireshark the connection details back before option 61 was allowed...

[Hx768vx]

I have a guide for creating the password/username combo... will post shortly.. have had many a Cisco router as the primary VDSL router configured over the years.... *walks to laptop*.... you just need the password/username bit (no wireshark needed) or anyone using Cisco kit that could do with a full config?

[Hx768vx]

This was an thread I did for somone else (so ignore where I ramble on,  its a straight copy paste job from my email), but it should make sense, even if you just use the first bit for the username & password.

You need to do a few things first

1.        MAC address of your sky router (they say you can use anything, I used my real one - you need to use this format), so basically: a1b1.c1d1.e1f1

1.        You need the dhcp hostname, basically macaddress@skydsl|password (some say you can use random again, but I used my true mac and random password of the right format), so basically: a1b1c1d1e1f1@skydsl|12345abcde – note the | (pipe symbol) between skydsl & password - that’s important!

1.        You need your client ID as hex – I used http://www.unit-conversion.info/texttools/hexadecimal/#data – drop in macaddress@skydsl then grab the hex value: 61316231633164316531663140736b7964736c

For Cisco VDSL, you need to use a .1q interface, NOT a dialer. But once you have the user/ pass you should be pretty much set to set up the physical interface and the dot1q virtual, this is the VDSL bit on my router; obviously your interfaces may be numbered differently, but this is the crux of it - once they go in you should start seeing everything go up.

interface Ethernet0/2/0

description Sky VDSL WAN Physical Interface ET0/2/0

mac-address a1b1.c1d1.e1f1

no ip address

no ip unreachables

no negotiation auto

!

interface Ethernet0/2/0.101

description Sky VDSL WAN Virtual Interface ET0/2/0.101

encapsulation dot1Q 101

ip dhcp client client-id hex 61316231633164316531663140736b7964736c

ip dhcp client hostname a1b1c1d1e1f1@skydsl|12345abcde

ip address dhcp

no ip redirects

no ip unreachables

no ip proxy-arp

ip nat outside

ip virtual-reassembly

!

Here’s my full config from my 4321 ISR (with some bits removed obviously), so hopefully you’ll be able to make a bit of sense of it when it’s all together… I’ve removed some of my zone based rules, so don’t forget you’ll need to secure it with some ACL’s/ZBF’s depending on what your IOS version uses… If you don’t have any joy, give me a nudge and I’ll dig out the old 1900 series config which may be more in-line with the 867 IOS version….ps you may have to check your interface refrences depending on your model, especially on the VDSL controller.

Oh and sometimes they come up as shutdown on the interface, don’t for get to issue a “no shut” command on both the physical and virtual interface… I always forget and spend 10 mins shouting at it before remembering!!

!

! Last configuration change at 18:56:40 UTC Sat Oct 23 2020

!

version 16.9

service timestamps debug datetime msec

service timestamps log datetime msec

platform qfp utilization monitor load 80

no platform punt-keepalive disable-kernel-core

platform hardware throughput level 1OOOOO

!

hostname XXX

!

boot-start-marker

boot-end-marker

!

!

vrf definition Mgmt-intf

!

address-family ipv4

exit-address-family

!

address-family ipv6

exit-address-family

!

!

no aaa new-model

!

!

!

!

!

!

!

ip name-server 90.207.238.97 90.207.238.99 8.8.8.8 8.8.4.4

ip domain name XXX

ip dhcp excluded-address XXXX XXXX

!

ip dhcp pool XXX_VLAN1-INTERNAL

network 10.0.0.0 255.255.255.0

default-router 10.0.0.1

dns-server 90.207.238.97 90.207.238.99 8.8.8.8 8.8.4.4

domain-name XXX

lease 7

!

!

!

login on-success log

!

!

!

!

!

!

!

subscriber templating

!

!

!

!

!

multilink bundle-name authenticated

!

!

!

!

!

!

license udi pid ISR4321-B/K9 sn XXXXXXXXXX

license accept end user agreement

license boot level appxk9

license boot level uck9

license boot level securityk9

no license smart enable

diagnostic bootup level minimal

!

spanning-tree extend system-id

!

!

!

username xxxxxxxx privilege 15 secret 5 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

!

redundancy

mode none

!

!

!

!

controller VDSL 0/2/0

!

!

vlan internal allocation policy ascending

!

!

interface GigabitEthernet0/0/0

no ip address

shutdown

negotiation auto

!

interface GigabitEthernet0/0/1

no ip address

shutdown

negotiation auto

!

interface GigabitEthernet0/1/0

power inline auto

!

interface GigabitEthernet0/1/1

power inline auto

!

interface GigabitEthernet0/1/2

power inline auto

!

interface GigabitEthernet0/1/3

power inline auto

!

interface GigabitEthernet0/1/4

power inline auto

!

interface GigabitEthernet0/1/5

power inline auto

!

interface GigabitEthernet0/1/6

power inline auto

!

interface GigabitEthernet0/1/7

power inline auto

!

interface ATM0/2/0

no ip address

atm oversubscribe factor 2

no atm enable-ilmi-trap

!

interface Ethernet0/2/0

description Sky VDSL WAN Physical Interface ET0/2/0

mac-address xxxx.xxxx.xxxx

no ip address

no ip unreachables

no negotiation auto

!

interface Ethernet0/2/0.101

description Sky VDSL WAN Virtual Interface ET0/2/0.101

encapsulation dot1Q 101

ip dhcp client client-id hex xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

ip dhcp client hostname xxxxxxxxxxxx@skydsl|xxxxxxxxxx

ip address dhcp

no ip redirects

no ip unreachables

no ip proxy-arp

ip nat outside

ip virtual-reassembly

!

interface GigabitEthernet0

vrf forwarding Mgmt-intf

no ip address

shutdown

negotiation auto

!

interface Vlan1

description VLAN1 default INTERNAL

ip address 10.0.0.1 255.255.255.0

ip nat inside

ip virtual-reassembly

!

ip forward-protocol nd

ip tftp source-interface GigabitEthernet0

ip nat inside source list 1 interface Ethernet0/2/0.101 overload

ip route 0.0.0.0 0.0.0.0 Ethernet0/2/0.101 dhcp

!

!

!

access-list 1 permit 10.0.0.0 0.0.0.255

!

!

!

!

control-plane

!

[stevieb3]

Yeah I had a bit off an issue with it at first, i was struggling with it, so I rang sky, spoke to their technical department and they said they don't support 3rd party routers. I reminded them that it was now illegal to block 3rd party equipment, which he checked and agreed, then magically everything is been trying all of a sudden worked! So I'm not sure if they removed some sort of block! I'll take a picture of my configuration when I'm next home and post, just in case that helps anyone.

[Hx768vx]

I think my 'long full guide' is stuck in moderation 😂 maybe it's too helpful... if it doesn't post soon I'll re-do just the 'important' bit lol

[Hx768vx]

As they didn't seem to like my last post as has dissapeared into the ether with "the whole shebang" in... but this should be what you need for the creds... lets see if this gets through....

You need to do a few things first

1.        MAC address of your sky router (they say you can use anything, I used my real one - you need to use this format), so basically: a1b1.c1d1.e1f1

1.        You need the dhcp hostname, basically macaddress@skydsl|password (some say you can use random again, but I used my true mac and a random PW of the same format), so basically: a1b1c1d1e1f1@skydsl|12345abcde – note the | (pipe symbol) between skydsl & password - that’s important!

1.        You need your client ID as hex – I used http://www.unit-conversion.info/texttools/hexadecimal/#data – drop in macaddress@skydsl then grab the hex value: 61316231633164316531663140736b7964736c

Once you have them, you should be pretty much set to set up the physical interface and the dot1q virtual, this is the VDSL bit on my router; obviously your interfaces may be numbered differently, but this is the crux of it for the credentials - once they go in you should start seeing everything go up.

interface Ethernet0/2/0

description Sky VDSL WAN Physical Interface ET0/2/0

mac-address a1b1.c1d1.e1f1

no ip address

no ip unreachables

no negotiation auto

!

interface Ethernet0/2/0.101

description Sky VDSL WAN Virtual Interface ET0/2/0.101

encapsulation dot1Q 101

ip dhcp client client-id hex 61316231633164316531663140736b7964736c

ip dhcp client hostname a1b1c1d1e1f1@skydsl|12345abcde

ip address dhcp

no ip redirects

no ip unreachables

no ip proxy-arp

ip nat outside

ip virtual-reassembly

!

[Cheezy2015]

@Matt1408 

Im using a Draytek Vigor 166 from Germany now. Seems to work fine as long as vlan101  is set in the modem for the outgoing connection and DHCP for the rest. Used to use a Vigor 130 but had a few issues with dropped connection on Sky. I've tried the same dream machine pro settings with the BT Openworld modem and it's working through that also.