Vodafone Credentials for PPPoE

[JoeD210]

Hi All. I'm attempting to get my credentials from Vodafone so i can re-set up my own router and modem.  The existing dsl**********@broadband.vodafone.co.uk no longer works for some reason? I have tried the online chat but 15 minutes between every question is unacceptable (sorry to sound grumpy). I'm hoping a moderator linked with Vodafone could help?

Regards

Joe

[WelshPaul]

What do you mean when you say "existing dsl**********@broadband.vodafone.co.uk no longer works"?

Had you requested your PPPoE credentials previously and if so, had you used them with a third party device already? I'm trying to understand why would they stop working. Have you changed broadband teirs or moved from FTTC to FFTP?

[JoeD210]

Thanks for the response. I'm still on the existing tier. I requested my credentials from Vodafone a number of years ago and set up using third party equipment. I'm using a Draytek Vigor 130 modem and a Asus Rt-Ac68u router. It worked fine until last Saturday. I did do a firmware update on the router. When I try to connect it tells me that my password is incorrect. I'm at a loss. Have factory reset both, copy and pasted my credentials into the router and set it to bridge mode. Wasn't sure if Vodafone had changed my credentials, which i wanted them to confirm, but could'nt get through to support or if i've made an error somewhere in my configuration.

I

[CrimsonLiar]

Okay, so a couple of things - what you are describing happened to me just after christmas.

Unplug the Vigor 130 modem from the wall and change it's connection from MPoA to PPPoE/PPPoA, set the modem DNS servers to 90.255.255.90 and 90.255.255.255, and if you've changed it in the console set "vdsl snr 0", when all set turn the power off.  Keep the modem unplugged for about it about 30 minutes from your last conversation with VF.  Then turn it back on and try again.

Have fun, the tech person I spoke with took almost 45 minutes to persuade that it was a connection/authentication issue and nothing whatsoever to do with the WiFi!

MPoA has never been officially supported on the OpenReach network.  Sometime a few months back it would appear that VF changed a few things around that meant our Internet Gateway IP was no longer the same as our Internet (WAN port) IP, and that when using MPoA while you received an Internet IP, the lease is never issued/refreshed.  So far so good, but after a couple of months of this it seems to register as a dormant connection eventually leading to the account being marked as dormant and the ability for the modem/router to log in disappearing.

[JoeD210]

I will give that a go tomorrow. Can't access the router Ui now for some reason? Been at it all day. I think i need a drink now! I don't remember it being this difficult when i originally set it up. Will get back to you and let you know the results. This  Thanks for your help.

[JoeD210]

Hi Crimson Liar.

Sorry about the late reply. I gave your suggestion a go. Tried for a couple of days, but unfortunately got no joy. Its been so long since i set this up that i've forgotten the settings. I know i'm doing something wrong somewhere, but i just can't remember what. I originally used this method with the modem https://www.youtube.com/watch?v=DFFr3b1Psoo. Then added the Vodafone credentials to the RT-Ac68u. Worked no problems. Maybe i have 'bricked' the router during the last firmware update.

Its not having it now though. If anybody has a similar setup then i'd appreciate some advice on the configuration for both modem and router. 

Regards

Joe.

[CrimsonLiar]

Okay, so....  If that video corresponds to the menus on your Vigor 130, it's not a UK spec version!

Here are the basics that you should have:

The OpenReach network has never officially supported MPoA mode, so using PPPoE/PPPoA mode is advised, even if MPoA has previously worked.  PPPoE/PPPoA mode still presents the modem transparently (it won't show up in your traceroutes), it's just a tiny bit less efficient than MPoA.

Provided you have the correct username/password, the above is all you need to do 

*Note for the mods, all personal info in the images has been either blurred or edited to make it safe

[JoeD210]

Hi Crimson. Tried what you advised. Still cannot get connected. Can't now enter the Vigor130 ui or the router ui. Tried everything i can think of.  Think it's possibly kaput. The vigor Act, Lan and Dsl lights are flashing quickly. Tried accessing from 192.168.1.1 and 192.168.2.1 with no joy for either.  Thanks for your time in answering though. Much appreciated. Looks like i'm stuck with the Vodafone router for now.

Regards

Joe

[CrimsonLiar]

When some errors are made in the Vigor 130 configs the only way you'll get access to its menus is a hard reset - which should also leave it correctly set up such that no config modifications are needed anyhow.  In that state the only way you'd be able to access the WEBUI of the Vigor 130 is to create a working PPPoE connection to the internet (the secondary channel wont work till the primary is running), to to connect directly from a computer to the Vigor with no router in between - your computer should be set to receive it's IP from the Vigor's DHCP, and examining the settings assigned you should then be able to get into menus if needed.

*I play around with various bit of kit so while I think the Vigor 130 WEBUI should be at 192.168.2.1, it could be 5.1 or 10.1

**I really doubt the Vigor is broken, inaccessible without that hard rest, but not broken!

***If you cant get into the router WEBUI then try using the address HTTP://router.asus.com (no internet required), again if it doesn't work a hard reset is not going to lose you anything!

[JoeD210]

Hi again Crimson.

I've managed to sort the modem out using the TPTP utility. Everything is showing as connected.  When entering the router UI I get a message of Invalid PPPoE account or password, please modify it. I'm definitely inputting the correct details. Its an authentication problem. I asked for myPPPoE details which Vodafone provided, but it still won't autenticate. I've tried to manually assign the DNS as you suggested and turned everything off for a few hours. No luck unfortunately. Any other suggestions?