7402nx driving me nuts

ok after giving up on the 7402nx to hold a decent sync speed on my long line, i decided to use a spare dg834gt i had, and voila, after some snr tweaking i can now hold a 2272 sync all day and night with a 2mbps profile , the 7402nx could only manage maybe 1784 ish with a 1250mbps profile :| .

anyway i have now decided to try and link the dg834gt to the 7402nx, and here in lies the problem, Ewan doesnt work in the s6 firmware im running.

i first tried using the dg834gt as a dumb modem, but here in the UK most isp's use pppoa not pppoe, so Billion need to add this to the Ewan config.

ok i thought ill turn off nat on the dg834gt and use it that way, no. first problem i have a dynamic external ip, which i resolve using dyndns.

ok i thought ill leave nat on and use a fixed ip setup. so i configured the 7402nx to Ewan and fixed ip, put in the details, and [censored], the 7402nx wont save the private range ip it just keeps 0'ing.

is there any way to get the 7402nx to do the routing while having the dg834gt do the modem bit? could Billion add pppoa to the Ewan config?

yep I want to do the same thing see here.

http://forums.thinkbroadband.com/ukonline/t/3813414-...

Does your 7402nx ever reboot itself?

it looks like it may be possible to get the ewan working by putting the original router in either bridge mode or dmz mode and then using the static ip option. The other router wouldnt then be completely dumb but at least it still allows you to use the nx to route your lan traffic.

I managed to get billion to send me a uk version of the s6.b1 firmware but there is no pppoa ewan option on it and I have no idea why they dont put these firmwares on the website.

it seems the dg834gt can do a half bridge mode, but im not sure how to get it working with the new firmware.

Have a google for modem mode.

Post deleted by cypher007

there seems to be quite a few unofficial versions of S6. Billion have sent me a couple and the latest one I've tried introduced EWAN. I'm running 5.53.s6.rc11.ds5.64 on my 7402NX (not in EWAN mode as I'm ADSL), but I thought that I'd mention this in case it helps as it may be worth contacting Billion for this unofficially released revision. I might have a copy on email if that helps.

hmm how long have you had it? I am inclined to believe that is older than s6.b1 based on on how billion do their versioning in the past however I would not mind a copy of that firmware so am going to send you a PM with my email addy to forward on to thanks, I will send s6.b1 the other way no problem. s6.b1 is newer than the final s6. On the australian site its not classed as beta either. I dont know if its considered beta in the uk, I was not told its beta firmware by uk tech support.

also the .64 at the end might be reffering to newer adsl code which widens my eyes even more, I would be very grateful if you could goto the adsl status page in the gui and check this line.

DSP Firmware Version

please tell me what value it has (adsl firmware version), mine is E.25.41.55 A and I am curious if yours will be E.25.41.64 A

Edited by Chrysalis (Sat 20-Mar-10 22:51:09)

Hi

My ADSL Code is indeed E.25.41.64 A. Billion support sent me this code at the beginning of March '10. I'm presuming that the version I'm running introduced the int_2.5 (9b coding gain) as this has also helped me get my speed back up, but I'm sure it only ever went up to 7. I hope it's still there in S6.b1.

I'll check my PM in a mo.

Cheers
Pete

I'm about 1km from the exchange as the crow flies.

DSP Firmware Version E.25.41.64 A
Connected true
Operational Mode G.Dmt
Annex Type AnnexA
Upstream 448000
Downstream 6560000
Elapsed Time 0 day 7 hr 56 min 27 sec
SNR Margin(Upstream) 27 dB
SNR Margin(Downstream) 16.5 dB
Line Attenuation(Upstream) 31.5 dB
Line Attenuation(Downstream) 34.5 dB
CRC Errors(Upstream) 31
CRC Errors(Downstream) 0
Latency(Upstream) Interleave
Latency(Downstream) Interleave

in telnet this command can increase your sync speed by setting your downstream margin lower, obviously there is a risk to stability with a lower margin, also I dont know yet how to make it go back to using the isp value, so to do that I assume could just set it manually again to whatever your margin is which I think looks like 15db now.

so you can telnet in 192.168.1.254 port 23.

port a1 set ActivateLine abort
port a1 set AnnexAForceSNRMarginDn 70
port a1 set ActivateLine start

that would set the snr margin to 7db, so 80 is 8db and so on. 150 would be back to 15db.

I got the info and the firmware many thanks for that, it is indeed older firmware but one that comes with a newer dsl code. Also grabbed a load of newer uk firmware for my other billion routers from the 2nd link you gave me.

The .55 firmware does also have the int coding gain settings as well. The problem I am looking to resolve is that SRA (seamless rate adaptation) seems to effectively crash on the version I am using.

Edited by Chrysalis (Sun 21-Mar-10 16:43:33)

I have used the commands below, but the router is pretty adamant that it's going to use 15db, despite the commands being accepted and the line re-synch'd.

Could this be because I'm so close to the exchange that a higher SNR down is usual?

In reply to a post by DSLPete:

Could this be because I'm so close to the exchange that a higher SNR down is usual?

34.5db is not a short line. My 24.5db line is reported to be 1700m, and that must be wrong; given my flat is behind some 1920's houses, and the exchange is at the end of the road of 1920s build - the BT cables must run down that road, then into mine, which is a 1km distance.

does the sync speed stay exactly the same? could be your sync speed is capped.

or it also could be the setting doesnt work with your provider, or even it doesnt work on g.dmt. (I use it on adsl2)

here is my line using the 70 setting.

Parameters
DSP Firmware Version E.25.41.55 A
Connected true
Operational Mode G.Dmt.Bis
Annex Type AnnexA
Upstream 1024000
Downstream 5456620
Elapsed Time 1 day 0 hr 20 min 3 sec
SNR Margin(Upstream) 7.0 dB
SNR Margin(Downstream) 7.25 dB
Line Attenuation(Upstream) 28.0 dB
Line Attenuation(Downstream) 53.5 dB
CRC Errors(Upstream) 0
CRC Errors(Downstream) 0
Latency(Upstream) Fast
Latency(Downstream) Fast

the command I used was slightly different because of the modulation.

port a1 set BisAForceSNRMarginDn 70

There is AnnexA which I assume is for adsl1
BisA adsl2 adsl2+
BisM adsl2 adsl2+ using annexM

Edited by Chrysalis (Sun 21-Mar-10 22:37:55)

here I am going to reveal some testing I did on the router with the bitloading

bear in mind this is a lot of numbers.

so the way this is layed out is the number on the left is the bin # of the first value, then the 2nd value is one bin higher and so on, so if it says bin32 then the first value is for bin32 and then the next bin 33 and so on. 15 is the highest possible bitloading per bin. The numbers drop off as the bin's go higher as that is on the weaker part of the line, but also notice the first few bin's are not maximum due to crosstalk with the upstream. These will show the affect that reducing the upstream power has on these bin's.

so this below is auto coding gain (conservative) with default full upstream power on my line. I cannot remember if the noise margin was 6db or 7db on these tests.

Bin 32 = 5 6 6 6 7 7 8 8 8 9 9 10 10 11 9 11
Bin 48 = 11 11 11 12 12 12 12 12 2 12 12 12 12 11 11 11
Bin 64 = 12 11 11 11 11 11 11 11 12 12 11 12 11 12 12 12
Bin 80 = 12 12 12 11 11 11 11 11 11 11 11 11 11 11 11 11
Bin 96 = 11 11 10 11 11 11 11 10 10 10 10 10 10 10 10 10
Bin 112 = 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
Bin 128 = 10 10 10 10 10 10 10 10 10 9 9 9 9 9 9 9
Bin 144 = 9 9 8 8 9 8 8 8 7 7 7 7 6 5 5 3
Bin 160 = 1 0 2 4 5 5 6 6 6 7 7 6 7 7 7 7
Bin 176 = 7 7 6 6 6 7 6 6 6 6 5 5 5 5 4 3
Bin 192 = 1 0 0 0 0 2 2 2 2 2 2 2 0 0 2 2
Bin 208 = 2 2 0 0 2 3 3 3 5 4 4 0 3 3 4 4
Bin 224 = 3 3 2 3 3 3 0 1 0 2 2 2 2 3 2 2
Bin 240 = 0 2 1 0 0 0 0 0 0 0 0 0 0 0 0 0

now this one is the same with auto coding gain but with the upstream power reduced by 3db, so using the tx_attenuation bis3_0db setting. See the improvement on the 1st line, its an important improvement since those tones wont drop at night they stay at full strength on the strong part of line.

Bin 32 = 8 8 9 9 10 10 11 11 11 12 12 12 12 12 9 12
Bin 48 = 12 2 12 12 12 12 12 12 12 12 12 12 12 12 11 12
Bin 64 = 12 12 11 11 11 11 11 11 11 11 11 12 11 12 12 12
Bin 80 = 12 12 12 11 11 11 11 11 11 11 11 11 11 10 11 11
Bin 96 = 11 11 10 11 11 11 11 11 10 10 10 10 10 10 10 10
Bin 112 = 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
Bin 128 = 10 10 10 10 10 10 10 9 10 9 9 9 9 9 9 9
Bin 144 = 9 9 8 9 8 8 8 8 7 7 7 6 6 5 4 3
Bin 160 = 1 0 2 4 5 5 6 7 7 7 7 7 7 7 7 7
Bin 176 = 7 7 6 6 6 7 7 6 5 6 5 5 6 5 4 4
Bin 192 = 2 0 0 0 1 3 3 3 3 3 2 2 1 0 2 2
Bin 208 = 2 3 0 0 1 3 3 3 4 3 4 0 3 3 4 2
Bin 224 = 3 2 3 3 3 3 1 1 0 2 2 2 2 3 2 2
Bin 240 = 2 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0

increment +1.0 coding gain reduced upstream power by 3db

Bin 32 = 8 9 9 9 10 10 11 11 12 12 12 12 12 12 9 12
Bin 48 = 12 12 2 12 12 12 12 12 12 12 12 12 12 12 12 12
Bin 64 = 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12
Bin 80 = 12 12 12 12 12 12 12 12 11 11 11 11 11 11 11 11
Bin 96 = 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
Bin 112 = 11 11 10 10 10 10 10 10 10 10 10 11 10 10 10 10
Bin 128 = 10 10 10 10 10 10 10 10 10 10 10 10 9 9 9 9
Bin 144 = 9 9 8 9 9 9 8 8 8 7 7 7 6 5 5 3
Bin 160 = 0 0 3 4 5 6 6 7 7 7 8 7 8 7 8 8
Bin 176 = 7 7 7 7 7 7 7 7 5 7 6 5 6 6 5 4
Bin 192 = 3 0 0 0 2 3 3 3 3 3 3 2 0 0 3 3
Bin 208 = 4 4 3 0 4 5 4 4 5 4 4 0 4 4 4 3
Bin 224 = 3 3 4 4 3 3 1 1 0 2 1 2 2 3 2 3
Bin 240 = 0 2 1 0 0 0 0 0 0 0 0 0 0 0 0 0

as above but after gone dark and lost 1000kbit speed

Bin 32 = 8 9 9 10 10 10 11 11 12 12 12 12 12 12 9 12
Bin 48 = 12 12 13 12 12 12 12 2 12 12 12 12 12 12 12 12
Bin 64 = 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12
Bin 80 = 12 12 12 11 12 12 12 12 12 12 11 11 11 11 11 11
Bin 96 = 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
Bin 112 = 11 10 10 10 10 10 10 10 10 10 10 10 10 10 10 9
Bin 128 = 10 10 10 10 10 10 10 10 10 10 9 9 7 9 8 9
Bin 144 = 6 9 8 8 7 8 8 8 7 7 6 6 6 5 4 2
Bin 160 = 0 0 0 3 4 0 5 6 6 5 7 0 6 5 5 0
Bin 176 = 4 4 2 0 0 2 4 0 0 0 0 4 0 4 0 0

Seems I didnt record the tests that got tones loaded to 15, but I think I had to reduce the noise margin to get tones to 15 bits.

here is the SRA problem I refer to, I plan to flash the firmware after it next happens. I marked with a black diamond shape the time on the graph where SRA stops working. You see it works again after I restart the sync.

noise margin
sync speed

Edited by Chrysalis (Mon 22-Mar-10 00:11:20)

ok just synced up on this firmware. I dont see any obvious changes to the dsl stuff, so I am hoping it has stability fixes.

DSP Firmware Version E.25.41.64 A
Connected true
Operational Mode G.Dmt.Bis
Annex Type AnnexA
Upstream 1024000
Downstream 6472489
Elapsed Time 0 day 0 hr 0 min 38 sec
SNR Margin(Upstream) 7.5 dB
SNR Margin(Downstream) 7.05 dB
Line Attenuation(Upstream) 28.0 dB
Line Attenuation(Downstream) 51.5 dB
CRC Errors(Upstream) 0
CRC Errors(Downstream) 0
Latency(Upstream) Fast
Latency(Downstream) Fast

Edited by Chrysalis (Mon 22-Mar-10 17:31:11)

ok so far no actual SRA freeze up, but the router resynced earlier today. That itself is unusual and bad since with SRA I dont expect my sync to drop at all.

looking at the tbb quality graph I see a 'lot' more red than usual which either means today my line has been very noisy (this red even occured after the resync which was also at higher speed) or that the new firmware is not handling noise as well.

Compared to the .55 version I am running at the same dsl settings which are inc1_0 coding gain (higher than default but not very agressive) and snrm of 7db (more conservative than the 6db isp setting). As well as -3db of upstream power and disabled upstream SRA.

so there was a dip in sync speed at 8am, probably noise burst, then no more dips until the router lost sync, however even tho the snrm was always around 7db there was errors occuring due to background noise on my line, then when the speed jumps up at just after 1pm is the router resyncing, after that various dips show because of more noise bursts. Then a gap in the graph where I dropped the sync to change a setting.

Speed graph
SNRM graph

Edited by Chrysalis (Tue 23-Mar-10 18:00:33)

I have moth balled my 7402GXL for now and are following your threads and hope you work out theses new chipset 7402 .
Even thou i got a spare 7402r2 and 7402VGP i would like to use the new feature set you have discovered on the new 7402

well after changing coding gain to 6 things seem quite a bit better with the same sort of synch speed as 1_0.

billion also replied to me today with a url to my requested b1.64 firmware, so I think things are looking up on this router now, I wont flash tho until my next problem occurs.

If anyone wants the url msg me.

todays graphs.

Speed
Noise Margin

Edited by Chrysalis (Thu 25-Mar-10 19:42:29)

I been using the s6.b1.64 firmware now, works fine just as good as the older .64 firmware.

Also I now configure my line differently and the result pleasantly surprised me.

1 - I reduced coding gain to auto.
2 - I decreased target noise margin to 4db.
3 - I increased rein checking to the max 120pps.

Result is a sync that hovers between about 6-6.15mbit second and crc errors are suprisingly much improved.

The bit loading on this setup is that the higher(weaker) tones are used much less (meaning less night time speed loss) and the stronger tones have higher bitloading around the 13/14 mark instead of 11/12. Coding gain appears to get its extra speed by loading up bits on the weaker tones.

On my older setting sync would start initially at around 6.5-6.7mbit (higher if coding gain 7) but at the first night this would drop to well below 6mbit and then only recover to maybe just over 6mbit. So daytime speeds were perhaps a little less but night time speeds were more less. Since there is now less variance SRA has less work to do.

I have also discovered what one of the unknown settings does, and the setting allows you to disable adsl2/+ low power modes, it is also linked to SRA functions, ie. SRA supposedbly works better without the low power modes. I havent touched this setting tho as I am all for reducing crosstalk which is what the low power modes do. In these graphs, the first gap is me changing the settings, flashing firmware etc. There is a 2nd small gap and that was not a sync problem, the graphing server had a connectivity issue to the uk for a short period.

Speed - auto coding gain, reduced upstream power, 4db margin
Noise Margin - auto coding gain, reduced upstream power, 4db margin

DSP Firmware Version E.25.41.64 A
Connected true
Operational Mode G.Dmt.Bis
Annex Type AnnexA
Upstream 1024000
Downstream 6032048
Elapsed Time 0 day 20 hr 50 min 54 sec
SNR Margin(Upstream) 7.5 dB
SNR Margin(Downstream) 4.45 dB
Line Attenuation(Upstream) 28.0 dB
Line Attenuation(Downstream) 50.5 dB
CRC Errors(Upstream) 0
CRC Errors(Downstream) 0
Latency(Upstream) Fast
Latency(Downstream) Fast

Edited by Chrysalis (Sun 28-Mar-10 02:51:05)

ok long overdue update.

Was a bit of a false dawn my positive news on the new firmware.

Is a shame I am the only user testing this who has SRA as ideally we need more feedback.

But on the newer adsl firmware I still had the following problems.

1 - if Retrain allowed (default is allowed on 'overallonly' which I think means if noise margin is too far out from target) then the sync drops too often but otherwise stable no freeze ups.
2 - if Retrain not allowed so to stop the sync drops, then the router semi freezes, the sync speed goes right down to a very low level, the sync stays up, SRA stops working but the snr margin stats still update. I initially thought this was better but the older firmware behaviour is better as the sync stays in a much more useable state.
3 - It seems the freeze bug is still there but reversed, on the new adsl firmware if SRA is disabled then the stats freeze up, whilst on the old firmware the stats freeze up when SRA is enabled, strange.
4 - To make sure these issues werent caused by the router working too hard dealing with noise I even tested on a 20db noise margin but the router still behaves the same.

The NX defenitly deals with noise better in terms of bitswapping (reduced crc errors) and has a nice gui, decent wireless, but still too problematic for me. I am in two minds whether this is a chipset problem or a software problem. A comparison router with a almost the same chipset is the netgear 384v5 and that does also lose sync with SRA on but it doesnt have any of the other problems. On the netgear no tuning can be done tho so I would say with the NX on default settings and on the new adsl firmware its behaviour is very similiar to the netgear.

When compared to the older Billion 7402 router's the old router's on original firmware are rock solid on holding onto sync with SRA, they are almost bulletproof, however on my 7402VGP when I flash to the latest firmware issues start occuring with crc errors (but not holding onto sync).

For the OP's issues I did try again to get the ewan to work but got nowhere, its got next to no documention so isnt easy to do. I tried a few things, but I expect what the OP was trying to do is get the router connected to the dsl line in a full dumb modem bridge mode, so doesnt ppp auth only does the sync, and get the NX to do the ppp auth and route the traffic. I agree with the op that it seems it will need pppoa capability on the ewan which seems missing. The other ewan modes look far more complicated and at the very least will require some special router configuration so is more work using undocumented features. I tried and failed.

Edited by Chrysalis (Wed 07-Apr-10 14:16:23)

ok I have got this info now.

SRA 'is' fixed when you dont use the force snr margin option, ie. just leave it at default and use the isp configured default.

so .64 should be ok on SRA now but if you use the snr margin overide it breaks things, I did a lot of reading on how SRA works and my feelings are that when you set the snr margin overide and enable SRA it sets the min and max threshold margin too close to the target margin which causes it to resync. I dont know if using the target snr margin also has an affect when SRA is disabled, I cant really test that as my line is set to 4db and using that without SRA would be bad

Hi,

I am just about to buy a Billion 7402nx. I use O2 LLU broadband (formerly BEunlimited).

I have heard there are issues with this router with O2.

Should I proceed with the purchase or look for another router? The key things I am after are Gigabit LAN and Wireless N

Any help appreciated.

Jago

Hard to say how good it would be with O2 but I suggest you look for a broadcom based router instead. This one is connexant based.

In terms of the wireless N performance and gigabit lan those 2 features work fine.

uk 6.02b firmware released. Fixes the upload burst speed problem I reported and some extra adsl options in the gui, also extra firewall stuff.

It is using the .55 dsp firmware tho.

Ok, thanks, i'll check it out.

I've had to use a drink 2402 router as my recent upgrade to 21cn resulted in my 7mb sync dropping to 1.5mb. Have had the dan ding reset and the drink is now up to 14mb with a new bras profile of 10mb.

If I put the billion on, the attenuation is 38db. The drink drops it to 33db. Both have an snr that fluctuate between 4-6db. Both have multiple line drops and resynch.

Coukd this be sra at play?

I want to get the billion back up and running but I'm nervous it'll screw my connection again.

For adsl2+, what are the optimum wan dsl configs in terms of signalling and modulation?

Cheers
Pete

Hi,

@Crysallis: Can you send me the link back - I can no longer find the firmware URL? Thanks

You may also be able to help me:

I have recently had my ADSL 'upgraded' to 2+, but have had horrendous issues with my profile being capped down at 0.5mb whereas before it was 7.5mb.

Anyway, I tried all the usual: straight into the test socket, new filters and a new router. Changing from the Billion 7402NX to a borrowed Dlink 2640R, resulted in a lot more stability on the line but also higher sync speeds.

I've left the Dlink connected for a couple of weeks to get some stability and it's fairly steadily synching at 13.5-14.5mb, but is dropping the line about 5-7 times a day. The attenuation was around 33db.

I have reconnected the Billion as this was always a better router for handling noise etc. The attenuation has gone up to 38.5db and so my line speed is now less than the DLink.

I really want my nice Billion GUI router back in my setup, but it's driving me crazy.

It now is showing that the line is synched all OK with IP and DNS all issued OK, but the internet just isn't working. Zen say that its not passing the radius servers, but it must be to get the IP details. If I reboot it - it's OK for a short while.

I've noticed that it takes up to 90 seconds for the line to synch with the billion, whereas the Dlink was a matter of a few seconds. I've checked with Billion, who have remoted onto the router and they confirm that the settings are correct for ADSL2+, but it feels like there's a modulation / encapsulation error. Here are my current settings:

ADSL Port
PPOA, VCi/VPi 0, 38,
ATM: UBR
Auth: CHAP
MTU: 1456
RIP2 Multicast enabled
TCP MSS enabled
Obtain DNS Automatically


DSLMode:
ADSL2+, automatic fallback
G.DmtBISPlusAuto
Profile type: Main
Activate Line: True
Coding Gain: Auto
TX Attenuation: 0

No errors in the event or error logs. No upstream or downstream CRC errors reported.

What the hell can I try in order to get my Billion to be a bit more stable on the line? I'm starting to think that there may be a line / equipment fault as the Dlink is also unstable, but less so that the Billion.

its in your inbox

it may be tho that the dlink is simply better for your line on adsl2+. The connexant dsl chipset generally is not highly rated, especially the one in the 7402NX. I have not seen a good review for this router on a non easynet line.

What we need is your new stats, like the ones you posted before, and also when you say it takes a long time to connect watch the lights on the front and tell me if its either the adsl light flashing or waiting for the ppp/isp light to come on, the former is a slow sync and the latter is a slow isp auth.

Thanks.

Zen want to send BT as the dlink is still intermittent (7 drops a day). Before I agree, I want to try a new router.

What's a good non connexant chipsets router, preferably with gigabit Ethernet?

Cheers,
pete

I have been using a Billion 7800N for a few months now and it has been rock solid with its Broadcom chipset on Be network. Pretty happy with the gigabit LAN and wireless N also.

funny enough I have this working but in a very strange way.

I moved to tiscali LLU via xilo and the 7402nx is proving to not be very good on that service (even tho still globespan), so am using my speedtouch 585 for the modem again. I wanted to keep wireless n and my gigabit lan so did more work on this.

When I chose ewan fixed ip, I lost access to the billion router and had to reboot to regain access, could still ping other lan devices. No internet.
When I chose ewan automatically assign ip, I could access everything but no internet.
The other 2 options would require me to bridge the speedtouch which I have not done yet.

However I discovered something new. If I activate ewan mode with auto assign ip and then switch back to adsl mode. It sort of half works, it obviously sets up a new routing path as I now see this on outgoing traceroutes (previously if I set speedtouch as router 192.168.1.254 didnt work ass gateway and was invisible). speedtouch is 192.168.1.252.

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.router [192.168.1.254]
2 73 ms 99 ms 99 ms home.gateway3 [192.168.1.252]
3 21 ms 22 ms 21 ms lns2.uan.thn.uk.murphx.net [89.145.254.70]
4 21 ms 21 ms 21 ms uan-er1.uan.thn.uk.murphx.net [89.145.254.65]

I am going to experiment more when I full bridge the speedtouch, found some guides from BE users as they have the 585v7.

In this setup its the speedtouch that still handles the port forwarding.

In reply to a post by DSLPete:

Hi

My ADSL Code is indeed E.25.41.64 A. Billion support sent me this code at the beginning of March '10. I'm presuming that the version I'm running introduced the int_2.5 (9b coding gain) as this has also helped me get my speed back up, but I'm sure it only ever went up to 7. I hope it's still there in S6.b1.

I'll check my PM in a mo.

Cheers
Pete

the link we used to get the new firmwares has been taken down by billion now, many beta and release but unpublished firmwares were on that site.