DrayTek UK Users' Community Forum

Help, Advice and Solutions from DrayTek Users

vigor 130 + latest firmware = no Sky fibre

  • mbames
  • Topic Author
  • User
  • User
More
30 Jan 2017 09:03 #7 by mbames
Replied by mbames on topic Re: vigor 130 + latest firmware = no Sky fibre
As I found, the .all doesn't seem ti necessarily keep every you need.

Pop on the .rst and then reconfigure the 130. At one point I saw the default gateway in my 2925 was showing as the 130, rather than that of my ISP, so I knew something wasn't right - which was what sent me down the full reconfig path. Even though it is said the 130 will work out out of the box, that certainly hasn't been my experience for Sky.

I do notice my (reported) sync speeds (in the 2925) have dropped very slightly, but not enough for me to be worried - least not yet! I have have stopped having to use my backups vodafone 3g sim, so I'm happy :-)

Please Log in or Create an account to join the conversation.

More
31 Jan 2017 20:49 #8 by drewy
Replied by drewy on topic Re: vigor 130 + latest firmware = no Sky fibre
Exactly the same problem here. Flashed the new firmware. Can no longer connect (Zen). Tried reloading previously backed up config, no joy. Messed around with the settings for an hour, no luck.
Managed to re-flash the old firmware.

Very non-plussed.

Pi$$ poor service.

Please Log in or Create an account to join the conversation.

  • andyfox
  • User
  • User
More
31 Jan 2017 21:32 #9 by andyfox
Replied by andyfox on topic Re: vigor 130 + latest firmware = no Sky fibre
Same problem here when using pfSense 2.3.2-RELEASE-p1. Works fine with 3.7.4 firmware on the 130. Upgrading to 3.8.0 simply results in the following messages in the pfSense log, and no connection.
Tried resetting the 130, and reconfiguring and it still fails to work. Reverting back to 3.7.4 fixes the problem.

Jan 31 15:48:02 ppp [wan_link0] LCP: no reply to 2 echo request(s)
Jan 31 15:48:23 ppp [wan_link0] PPPoE: connection closed
Jan 31 15:48:23 ppp [wan_link0] Link: DOWN event
Jan 31 15:48:23 ppp [wan_link0] LCP: Down event
Jan 31 15:48:23 ppp [wan_link0] LCP: state change Opened --> Starting
Jan 31 15:48:23 ppp [wan_link0] Link: Leave bundle "wan"
Jan 31 15:48:23 ppp [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Jan 31 15:48:23 ppp [wan] IPCP: Close event
Jan 31 15:48:23 ppp [wan] IPCP: state change Opened --> Closing
Jan 31 15:48:23 ppp [wan] IPCP: SendTerminateReq #4
Jan 31 15:48:23 ppp [wan] IPCP: LayerDown
Jan 31 15:48:23 check_reload_status Rewriting resolv.conf
Jan 31 15:48:23 ppp [wan] IFACE: Down event
Jan 31 15:48:23 ppp [wan] IFACE: Rename interface pppoe0 to pppoe0
Jan 31 15:48:23 ppp [wan] IPV6CP: Close event
Jan 31 15:48:23 ppp [wan] IPV6CP: state change Stopped --> Closed
Jan 31 15:48:23 ppp [wan] IPCP: Down event
Jan 31 15:48:23 ppp [wan] IPCP: LayerFinish
Jan 31 15:48:23 ppp [wan] Bundle: No NCPs left. Closing links...
Jan 31 15:48:23 ppp [wan] IPCP: state change Closing --> Initial
Jan 31 15:48:23 ppp [wan] IPV6CP: Down event
Jan 31 15:48:23 ppp [wan] IPV6CP: state change Closed --> Initial
Jan 31 15:48:23 ppp [wan_link0] LCP: LayerDown
Jan 31 15:48:23 ppp [wan_link0] Link: reconnection attempt 1 in 3 seconds
Jan 31 15:48:26 ppp [wan_link0] Link: reconnection attempt 1
Jan 31 15:48:26 ppp [wan_link0] PPPoE: Connecting to ''
Jan 31 15:48:35 ppp [wan_link0] PPPoE connection timeout after 9 seconds
Jan 31 15:48:35 ppp [wan_link0] Link: DOWN event
Jan 31 15:48:35 ppp [wan_link0] LCP: Down event
Jan 31 15:48:35 ppp [wan_link0] Link: reconnection attempt 2 in 2 seconds
Jan 31 15:48:37 ppp [wan_link0] Link: reconnection attempt 2
Jan 31 15:48:37 ppp [wan_link0] PPPoE: Connecting to ''
Jan 31 15:48:46 ppp [wan_link0] PPPoE connection timeout after 9 seconds
Jan 31 15:48:46 ppp [wan_link0] Link: DOWN event
Jan 31 15:48:46 ppp [wan_link0] LCP: Down event
Jan 31 15:48:46 ppp [wan_link0] Link: reconnection attempt 3 in 2 seconds

I'm using PlusNet FttC.
Would appreciate some comments from DrayTek on this one, as I'm clearly not alone.

Please Log in or Create an account to join the conversation.

More
01 Feb 2017 21:57 #10 by loopyjuice
Replied by loopyjuice on topic Re: vigor 130 + latest firmware = no Sky fibre

andyfox wrote: Same problem here when using pfSense 2.3.2-RELEASE-p1. Works fine with 3.7.4 firmware on the 130. Upgrading to 3.8.0 simply results in the following messages in the pfSense log, and no connection.
Tried resetting the 130, and reconfiguring and it still fails to work. Reverting back to 3.7.4 fixes the problem.

Jan 31 15:48:02 ppp [wan_link0] LCP: no reply to 2 echo request(s)
Jan 31 15:48:23 ppp [wan_link0] PPPoE: connection closed
Jan 31 15:48:23 ppp [wan_link0] Link: DOWN event
Jan 31 15:48:23 ppp [wan_link0] LCP: Down event
Jan 31 15:48:23 ppp [wan_link0] LCP: state change Opened --> Starting
Jan 31 15:48:23 ppp [wan_link0] Link: Leave bundle "wan"
Jan 31 15:48:23 ppp [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Jan 31 15:48:23 ppp [wan] IPCP: Close event
Jan 31 15:48:23 ppp [wan] IPCP: state change Opened --> Closing
Jan 31 15:48:23 ppp [wan] IPCP: SendTerminateReq #4
Jan 31 15:48:23 ppp [wan] IPCP: LayerDown
Jan 31 15:48:23 check_reload_status Rewriting resolv.conf
Jan 31 15:48:23 ppp [wan] IFACE: Down event
Jan 31 15:48:23 ppp [wan] IFACE: Rename interface pppoe0 to pppoe0
Jan 31 15:48:23 ppp [wan] IPV6CP: Close event
Jan 31 15:48:23 ppp [wan] IPV6CP: state change Stopped --> Closed
Jan 31 15:48:23 ppp [wan] IPCP: Down event
Jan 31 15:48:23 ppp [wan] IPCP: LayerFinish
Jan 31 15:48:23 ppp [wan] Bundle: No NCPs left. Closing links...
Jan 31 15:48:23 ppp [wan] IPCP: state change Closing --> Initial
Jan 31 15:48:23 ppp [wan] IPV6CP: Down event
Jan 31 15:48:23 ppp [wan] IPV6CP: state change Closed --> Initial
Jan 31 15:48:23 ppp [wan_link0] LCP: LayerDown
Jan 31 15:48:23 ppp [wan_link0] Link: reconnection attempt 1 in 3 seconds
Jan 31 15:48:26 ppp [wan_link0] Link: reconnection attempt 1
Jan 31 15:48:26 ppp [wan_link0] PPPoE: Connecting to ''
Jan 31 15:48:35 ppp [wan_link0] PPPoE connection timeout after 9 seconds
Jan 31 15:48:35 ppp [wan_link0] Link: DOWN event
Jan 31 15:48:35 ppp [wan_link0] LCP: Down event
Jan 31 15:48:35 ppp [wan_link0] Link: reconnection attempt 2 in 2 seconds
Jan 31 15:48:37 ppp [wan_link0] Link: reconnection attempt 2
Jan 31 15:48:37 ppp [wan_link0] PPPoE: Connecting to ''
Jan 31 15:48:46 ppp [wan_link0] PPPoE connection timeout after 9 seconds
Jan 31 15:48:46 ppp [wan_link0] Link: DOWN event
Jan 31 15:48:46 ppp [wan_link0] LCP: Down event
Jan 31 15:48:46 ppp [wan_link0] Link: reconnection attempt 3 in 2 seconds

I'm using PlusNet FttC.
Would appreciate some comments from DrayTek on this one, as I'm clearly not alone.




Exactly the same scenario here with BT Infinity 2, spent the best part of a day trying to figure out what is wrong and then went back to Sophos which still has the issue due to this firmware being the cause!

Please Log in or Create an account to join the conversation.

  • andyfox
  • User
  • User
More
02 Feb 2017 11:31 #11 by andyfox
Replied by andyfox on topic Re: vigor 130 + latest firmware = no Sky fibre
I raised a support ticket with DrayTek for this issue, and they assure me that there are no known issues with the firmware.
I tried the upgrade again, using the .rst file, but this time I followed the update with a power cycle of the modem.
I simply left the modem configuration alone, following the reset. I did change the admin password, which had been restored to default.
That appears to have fixed it for me. I am now able to connect again using pfSense with no problems.

Please Log in or Create an account to join the conversation.

More
02 Feb 2017 14:54 #12 by jaybea
Replied by jaybea on topic Re: vigor 130 + latest firmware = no Sky fibre

andyfox wrote: I tried the upgrade again, using the .rst file, but this time I followed the update with a power cycle of the modem.
I simply left the modem configuration alone, following the reset.



Thanks! I tried that too, and the power cycle appears to do the trick, although I will have to monitor it for a while to see how it performs.

There is, however, something wrong with the firmware upgrade process if it requires a factory reset and a power cycle to work. I tried a power cycle after applying the .all file, but that did not work.

Please Log in or Create an account to join the conversation.