Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


Aaron2222

220 posts

Master Geek
+1 received by user: 111


#245427 3-Feb-2019 12:35
Send private message

I'm having issues with a new Synology RT2600ac on Spark (fibre connection). When the router is turned on (it gets turned off overnight, nothing I can do about that), it fails to establish a PPPoE connection. It won't try again unless the connect button in the Web UI is pressed or the WAN cable unplugged and plugged back in again, in which case the connection establishes. Any ideas on what's causing it or how to get the router to retry the connection again after it fails the first time? Router is on the latest firmware. 


Create new topic

This is a filtered page: currently showing replies marked as answers. Click here to see full discussion.

Aaron2222

220 posts

Master Geek
+1 received by user: 111


  #2172924 4-Feb-2019 18:01
Send private message

Turns out Synology recently released an update (1.2.1) that isn't available through the router interface yet but is available from their site that among other things:

 

 

Fixed an issue where PPPoE might not be able to re-establish the connection once it has disconnected.

 

 

Now it fails on the first PPPoE connection attempt (like before), but now retries and succeeds on the third or fourth attempt (so after about 4 minutes 30 seconds from the router being turned on at the wall). So not sure if it's the router or something at Spark's end. So it works now, but the added delay is annoying some (for a comparison I tried our old router, an old Netgear, which boots in 1 minute 30 seconds and gets a PPPoE connection immediately).

 

freitasm:

 

Ok, I have a RT2600ac but on a 2degrees connection so won't have any other suggestion...

 

 

What happens when you reboot your router? Mine takes about 2 minutes to boot, then tries its first PPPoE connection attempt (I can tell by the ONT lights). A second one comes a bit later and a third around the 4:30 mark, which succeeds (this is on 1.2.1). If it's a router bug, it may exhibit itself on yours as well, unless it's something specific with my config (but I haven't changed much) or its something ISP specific triggering it (I presume you don't reboot your router all that often, so probably wouldn't have noticed the issue if it exists?). 


Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.