Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: aruba on July 02, 2016, 09:15:39 AM
-
Hi,
Having recently moved over to Sky Fibre, I was wondering if anyone was currently using a VMG8324 to connect?
It looks possible as the all important 'Option 61' is available, but I'm not having any joy (currently using a guide meant for a 8800NL for reference).
Any pointers/screenshots of the settings to use on the ETHWAN would be much appreciated. :)
Thanks...
-
Certainly works in bridge mode as I am on sky fibre but using my router with merlin allowing the option 61 etc. Will have a look round but I dont believe it works in router mode with sky but will check if I can
-
Ah, I see!
So you have your Asus 'in front' of your ZyXel acting as a modem? Is there any reason you're not using the Asus alone?
I was just hoping to get down to one unit.
Thanks.
-
No the other way round. The zyxel is first acting as modem only (put it in bridge mode) then the asus is 'behind' connected using its WAN port to port 1 of the zyxel. The asus needs merlin so it can authenticate the dhcp properly for skys requirements.
The asus is a router only and has no modem
8324(bridge mode) > asus rt-ac87u (router only)
-
Thanks for that skyeci.
I've been digging around, and I'm thinking that it won't be possible to get away with just the ZyXel as the Option 61 part is only available via the Ethernet WAN, rather than the VDSL modem.
Might just replace my current setup with one of the new Billion routers.
-
Go for the Billion 8800NL. ;)
-
What encapsulation are you trying?
-
I would be cautious with the 8800nl if you are on an eci cabinet. I used to use one but due to high error rates I have found the zyxel performs much better
I personally favour seperate modem and routers purely due to if you need to make a change to your network settings etc on the router side you can reboot the router without causing a resync like you would with an all in one product.
If you want to upload stats then do check compatability with what you might buy to ensure it would work. I would get a good 5ghz wifi router that supports option60/61 to run alongside your 8324 in bridge mode 😆
-
Is this what you need?
VDSL WAN configuration with Encapsulation: IPoE.
-
Sky Fibre doesn't use PPPoE
-
Thanks for all your replies folks!
- Yep, a 8800NL would be one option - funnily enough I used to use one for ADSL, and I see there's a new R2 version now.
- I'm just trying to cut down from two units (SR102 & 8324) to one due to where the phone socket is located. Fortunately, I'm on a Huawei cabinet, but I'd rather just use the ZyXel instead of buying another router, and adding to my router collection. :wry:
- It looks like the encapsulation type is where I've been going wrong on the VDSL side.
I'll have another go in the morning (there would be household uproar if I kill the internet tonight!), and report back when I put the settings in the VDSL side rather than ethernet WAN. :-[
Thanks again...
-
It's very easy with a Billion 8800NL any changes on the Router side will not cause it to resync a change on the Modem side will, once the settings on the Modem are setup there is no need to change any parameters on that side.
-
Well, sadly not much joy in getting the ZyXel set up.
The main issue is the option 61 settings.
As seen in npr's screenshot, you need need hex values for both Option 61 IAID and DUID, so you can't just paste in the credentials as with other routers.
I have the hex version of my sky login as you can get it from Wireshark, but despite trying different combinations I can't seem to establish a connection with Sky.
Will have a ponder, but a Billion is looking an attractive option at the moment. :)
-
Try changing the ipv6/ipv4 mode to ipv4
-
Thanks for the suggestion Dray. Sadly, the options/requirements are just the same with IPv4. IPv6 is different, but option 61 disappears.
-
I did read somewhere else that the Option 61 data does not seem to be being checked any more so perhaps it depends on how you specify the data in the router gui. You may or may not have to prefix the hex data with '0x', have you tried it both ways?
Stuart
-
IPv6 is incorrect. What do you actually see when IPv4 is correctly selected? A screenshot would help ;)
-
Thanks for your replies...
I've had a go with the 0x prefix, but no joy.
The options when IPv4 are selected are the same as npr's screenshot. The IPv6 ones are removed, but they are further down.
The issue I guess is not knowing what's supposed to go in the IAID and DUID parts. The IAID wants just 8 hex digits and can't be left blank, so I've been using the first eight from the sky user name/password combination and then either omitting or repeating the digits in the DUID box.
I really appreciate everyone's help, but also don't want to waste people's time so I'll probably just go get a router that's proven to work on Sky, rather than trying to get this to work.
-
Have a look at post #218 here:
http://www.skyuser.co.uk/forum/technical-discussion/46464-skys-mer-why-does-not-work-other-routers-22.html
That give a link to a hex password generator
Also says the 61 option hex should start 0x3d:
-
Do you have any other option for encapsulation type, because I'm successfully using DHCP?
-
Thanks for the link. I ran the Sky credentials through the hex generator, and it appears Wireshark adds an equals sign at the beginning which I removed. I tried with and without the 0x3d beginning without success. I also tried various values in the IAID section, but again I'm not sure what it supposed to go in there and the 8324's manual is a tad vague.
The only type of encapsulation available for VDSL is IPoE or PPPoE.
I think overall, it's a no-can-do! ::)
-
Reading round it seems IPoE is the same as DHCP. The issue really is down to what goes into the DHCP client identifier and hostname and where are they?
My router sends the same data in both, which is the username and password concatenated by | like this:
xxxxxxxxxxxx@skydsl|yyyyyyyy
I've replaced my username and password with x and y ;)
-
Yes, it's a shame the 8324 doesn't make it simpler - the requirement for two set of hex digits seems to be only used on ZyXel and some TP-Link routers.
If I an opportunity, I might fire up Wireshark again and see if there's any clues during the router's boot up cycle to what the first hex digits should be.