Might be a bit of a naff question, but curious.
Might be a bit of a naff question, but curious.
Before I finally got myself my new Netgear, the Sagem was up for around 300 hours. There was a national drop in the BB which caused mine to reset a few weeks ago.
I'll continue to watch the Sagem 2304n threads though. Hopefully many of the issues will now fall in line with the other Sky routers.
Well, looking through my screen-captures. my best over the 27 days since moving from O2 to Sky is 60 hours
I know it's early days for me but .........:eek:
As has been pointed out to me, O2 use lower target noise margins - but dropouts were pretty few and far between. With Sky - and the more conservative margins - dropouts must be more than I ever had in 3 years with O2. My Sky connection seems pretty random.
Sometimes I need to re-boot to either 'wake' the WAN up when router initialises but minus WAN. Or, (like this morning), I was at 4meg/400k - re-booted and back up to just under 17meg/1.1meg.
Just to recap:
Nothing has changed my end in terms of wiring. Actually, I'm even straight into the test socket (master is the only BT point in the house) for the last week or two.
Binned the Sky (LEA) filters as suspect but even having used other filters, my impression is that either there may be an ISAM problem or the router is a bit of a nut-job. I reckon it's the latter :eek:
In either case, if you are moving from O2 LLU equipment to Sky LLU equipment, then you will now be using different wiring in the exchange and a socket on a different set of equipment as well.
Is that with the 2304n, your Profile lists the 2504?
Interesting you don't use wireless, I think that adds to the stability as the wireless creates more heat, therefore more strain on the router.
I have regular powercuts so could never build up a long uptime.
I use the Sagem router as the Modem, wireless is handled by a Netgear N+ router. Ignore my post. Think I've posted in the wrong place with some unrelated uptime of 5 months. Sorry.
Thanks for your time. I will later come back to the points you have made but I am trying to gather all my notes and enter all my saved stats into a s/sheet to try and reveal any possible patterns. Maintaining a detailed log is looking like an essential thing :)
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.
Unrelated to this, but I guess I can ignore Sky Portal info as bogus when it reports that my line tesding finished on 24/06/11 and speed set to 4096/512k? Not really important, as I am not set at that - but I am really struggling to find some sort of consistency since moving to this setup with SKY. Do not relish the prospect of another call to Sky, again, because of the inconsistent information which I have had so far :( Guess if I do contact them it might be better via email rather than phone?
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.
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 :o
Anyway, does anyone have any ideas?
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.
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.
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. ;)
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?" :eek:
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.
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.
Could you post the firmware version that you now have on the router please?
It's 18.104.22.168a4N, which is the same as was shipped with the router.
But the config file shows different versions (of firmware?), or am I misinterpreting things?
While on MER:
http://fast2304.skyfirmware.com 3 1 3 1 3 1308605998
http://fast2304.skyfirmware.com 3 1 3 1 3 1310068157
The differences to the end of my config file:
DSL TRUE 1 0 Complete 3000 TRUE EoA PVC: 0/40 VCMUX TRUE atm0 TRUE IP_Routed ipoe_0_0_40 TRUE TRUE atm0 0 0 atm0 atm0
DSL TRUE 0 1 TRUE PPPoA PVC: 0/38 VCMUX TRUE atm0 TRUE IP_Routed pppoa_0_0_38 TRUE TRUE sky c2t5AA== pppoa0 22.214.171.124,126.96.36.199 0 TRUE 1500 FALSE 0 pppoa0 pppoa0
Ok, you have the latest firmware version and don't have an even newer one.
Someone else may be able to help with the other information though.
With regards to the difference between MER & PPPoA connection settings, we are aware that there is a difference though.
Anyway, basically 70 hrs WAN now after the switch from MER to PPP0A (is this just a coincidence?), my best since going live on the 7th of last month.
To wrap this one up, I am pretty much convinced that apart from my router initially going live at a sync down of 621k, that the culprit for the instability has been the wireless implementation within this router.
Maybe the hardware is a bit suspect - maybe certain firmware exacerbates the problem, I don't know. Anyway, if I disable wireless it seems to be quite happy.