Does Firewalla purple support Option 60/61
Hi.
I currently have a Firewalla Blue and im looking to purchase the Firewalla Purple and use this in Router mode to replace my Sky Broadband hub. Ill then add a new Mesh system which will be running in bridge mode.
My query is does the Purple support DHCP options 60 and 61 on the WAN port? SKY use MER for authentication which not all Routers support.
Thanks in advanced.
-
Thanks for the replies.
The issue with using skys router in modem mode is you still end up with a double NATing which can cause other issues. What i am wanting to do is do away with the sky router and use the firewalla with a 3rd party modem like a Draytek or and old BT modem. This is how i currently have everything setup with the Asus Router.
I have spoken with support and they plan on adding the ability to set these DHCP options on the next firmware update.
Thanks All
-
Another Sky customer here looking for DHCP Option 61 (client-identifier) support. Just received my Purple and was disappointed to find that I can't enter the required info for this option to use my Firewalla as a router in DHCP mode.
I'm currently using an ASUS RT-AX86U router connected to my Sky fibre ONT with WAN set to DHCP and only option 61 set to 'sky@skydsl|sky' which has worked without fault for over a year now.
Looking forward to the v1.50 release if this does indeed add DHCP Option 61 support. Happy to provide logs and further details if needed to improve testing.
-
If anyone is still following this thread I have just managed to get my FWG working in router mode connected to Sky FTTC (They call it Superfast) in the UK. I have been using a Draytek Vigor 166, although I imagine it would also work with one of the White Openreach modems. I do have 2 here so will probably try those as some point.
I had always been running the Beta but, it's the Alpha you need. I had to upgrade my Box to 1.9742 and the app on my phone to 1.51. Thanks to FW Support for sorting this out.
Doing this gives access to DHCP option 61 (Client Identifier). 1.50 gives access to option 60 (Vendor Class Identifier) but it's 61 that you must have. Sky now disregard the specific authentication which means you can use abcdefgh@skydsl|1234567890abcdef but, you have to use that ascii string expressed in hex. I saw this when I used to have a Cisco VDSL router. So you just have to convert it or copy and paste it from here...
616263646566676840736B7964736C7C31323334353637383930616263646566
Happy to supply more details if needed. I would be happier if this functionality made it into the Beta/Production ASAP please.
Please sign in to leave a comment.
Comments
8 comments