2304n: longest WAN uptime record?

[Giskard]

The WGR614v9 is not an ADSL router so you will not be able to connect it direct to the Internet. You can connect it to your Sky router, but as it is only wireless G the performance may be no better than your Sky router.

Thanks. It's cable then. Did wonder.

Edit:
Allow me to correct myself: I was wrong to say cable as it's simply a router, rather than a modem/router.

[Giskard]

For now though, an ideas on my latest development?:
Link dropping every couple of minutes (over a 40 min span) before I went to bed last night. Checked this morning and WAN back up somewhere around two in the morning and lower speed/higher margin and............PPPoA!

Why PPPoA when I have been on MER since going live just about a month ago?
Would prefer PPPoA (alternative router option), but don't understand the switch.

Erm, sorry about this but re-reading my above comments, I see that I did not explain things very well (one of my faults, I'm afraid).

Would prefer to be on PPPoA (which allows for the use of an alternative router option), but don't understand the reason why I have been switched from one encapsulation method (MER) to another (PPPoA)

Again, I'm sorry for my awkwardness in communication - it's pretty cringeworthy

Anyway, does anyone have any ideas?


Thanks.

[Scubbie]

It seems that both PPPoA & MER are available on some lines with Sky at present.

In the past I have noticed that the Sagem 2304n initially connects using PPPoA, then attempts to connect using MER.

It may well be that something has occurred to prevent the router from connecting using MER.

At this stage I wouldn't see this as a serious problem. However, it a power fault has caused a component to fail, then the rest of the router could fail in due course.

[Giskard]

It seems that both PPPoA & MER are available on some lines with Sky at present.

In the past I have noticed that the Sagem 2304n initially connects using PPPoA, then attempts to connect using MER.

Yes, mine (prior to this event) would initialise as PPPoA/MER, then to MER proper once established.

It may well be that something has occurred to prevent the router from connecting using MER.

Ooerrr

At this stage I wouldn't see this as a serious problem. However, it a power fault has caused a component to fail, then the rest of the router could fail in due course.

So, you reckon it's more likely to be the router rather than an issue at the exchange, or systems/someone having to override MER in this case, for some reason?

If this could be an indication of router though, should I not think about having a word with Sky?

Have to say that since the switch to PPPoA, things seem pretty stable.


Thanks for your continued help.

[Scubbie]

Have to say that since the switch to PPPoA, things seem pretty stable.

This being the case, could I recommend that you keep an eye on things.

Since you are connected and things seem to be more stable, why try to 'fix it'?

[Giskard]

This being the case, could I recommend that you keep an eye on things.

Will update here accordingly.

Since you are connected and things seem to be more stable, why try to 'fix it'?

Yes, I would much prefer it to stay as PPPoA - just curious as to what was behind the change. I really don't want to talk to Sky unless I am forced to.

When the link came back as PPPoA I had lost over 3meg sync down to 13640, with an associated rise in margin up to 12.4db from around 7db.

I am coming up to 31.5hrs WAN. Even though my sync is lower, I'm going to wait to see if I can get past my best uptime of 66 hrs with the current configuration. Maybe it's clutching at straws but perhaps the switch to PPPoA might introduce a re-training period (?) whereby the sync could potentialy rise from this rate. Wishful thinking, but it would save me from the challenges of trying to make contact with a member of the Sky inner sanctum.

Oh, btw, 'Those who must not be approached' would probably be easier to track down if they were actually within some Himalayan mountainside. Though I have heard accounts of a few Ascended Masters that choose to dwell among us.

[Giskard]

Well, nearly 63hrs WAN uptime under PPPoA and apart from the drop in sync, the connection has been solid, with negligible margin fluctuation.

So, was wondering two things:

1. Could the MER implementation be a bit flaky?

2. Regarding the drop in sync, could a re-boot be worth a shot to see if the re-negotiation would result in a sync back up to around where it was before it changed over to PPPoA? Thought this could be worth a try before resorting to contacting Sky.

Bit hesitant to re-boot in case it reverts to MER. More hesitant to speak to Sky because of the 1st-line support 'Zen' riddles like "Why do you want the extra speed?"

[Scubbie]

I have an MER connection where I live, when I have the Sagem 2304n connected. My stats below were taken with this setup. It was connected and stayed up for 500+ hours.

I currently have a Netgear DGND3700 connected using PPPoA. It's providing me with identical connection speeds.

Whilst the up time on the Netgear isn't as high, this is purely because I've been playing with it. Changing the WiFi details causes the router to reboot. I've also got a large capacity external drive that is also causing it to reset.

Otherwise the router has been connected and on-line for the whole of this month without any issues.

[Giskard]

Thanks for the reply Scubbie.

Looking at my router config file, apart from now showing PPPoA it shows a different fast2304.skyfirmware.com version than when on MER.

[Scubbie]

Could you post the firmware version that you now have on the router please?