PDA

View Full Version : Having the routing problem? Download fixed firmware here


James
31/07/2009, 22:06
If anyone is having the issue whereby their Netgear/D-Link router is randomly losing routing even though all lights are on and the status page says Connected, you can try upgrading the firmware on your router to the appropriate one below.

These firmwares are modified versions of the official GPL release from Netgear/D-Link (they are not the dgteam or other third-party build). For peace of mind, the only thing I have changed before building these firmwares is 4 new lines in the router startup script:

# temp fix for ADSL24 LLU service 31/07/2009
echo 0 > /proc/sys/net/ipv4/neigh/default/ucast_solicit
echo 0 > /proc/sys/net/ipv4/neigh/all/ucast_solicit
echo 0 > /proc/sys/net/ipv4/neigh/nas0/ucast_solicit

Download below:

Wired versions:
DG834 v1/2 - http://adsl24.co.uk/files/llu/DG834v1v2_3.01.38_adsl24_llu.img
DG834 v3 - http://adsl24.co.uk/files/llu/DG834v3_4.01.40_adsl24_llu.img
DG834 v4 - http://adsl24.co.uk/files/llu/DG834v4_5.01.14_adsl24_llu.img

Wireless versions:
DG834G v1 - http://adsl24.co.uk/files/llu/DG834Gv1_3.01.32_adsl24_llu.img
DG834G v2 - http://adsl24.co.uk/files/llu/DG834Gv2_3.01.38_adsl24_llu.img
DG834G v3 - http://adsl24.co.uk/files/llu/DG834Gv3_4.01.40_adsl24_llu.img
DG834G v4 - http://adsl24.co.uk/files/llu/DG834Gv4_5.01.14_adsl24_llu.img

DG834GT - http://adsl24.co.uk/files/llu/DG834GT_1.02.19_adsl24_llu.img
DG834PN - http://adsl24.co.uk/files/llu/DG834PN_1.03.39_adsl24_llu.img
DG834N - http://adsl24.co.uk/files/llu/DG834N_1.02.15_adsl24_llu.img
DGN2000 - http://adsl24.co.uk/files/llu/DGN2000_1.1.8.0_adsl24_llu.img (updated 23 Sep 2009)

DSL-2640B - http://adsl24.co.uk/files/llu/DSL-2640B_3.07_adsl24_llu.bin
DSL-2740B - http://adsl24.co.uk/files/llu/DSL-2640B_2.87_adsl24_llu.bin

Remember the problem is still being looked in to by the network engineers but we thought it's best to see if we can at least try to release a temporary fix for you guys until it's sorted.

If you have any issues with any of these firmwares please let me know.

tonys
03/08/2009, 10:03
Anyone tried James' fix yet? Would be useful to post back here the router you're using and confirm successful in your own case - or any issues encountered.

James, don't want to seem ungrateful :) but as some of us with GT's have reverted to firmware 1.02.16, is there any chance you could prepare an image file for that version?

James
03/08/2009, 14:06
If Netgear still allow me to download that source version I should be able to compile it for you :)

James
03/08/2009, 19:35
DG834GT v1.02.16 firmware fix - http://adsl24.co.uk/files/llu/DG834GT_1.02.16_adsl24_llu.img

tonys
03/08/2009, 19:46
Thanks James, will try it tomorrow and let you know how I get on.

tonys
03/08/2009, 23:06
Thanks James, will try it tomorrow and let you know how I get on.

22:30 03/08/09
v1.02.16 adsl4 firmware now installed on my DG834GT and sync'd up. Had to reset router to factory defaults and start from scratch, as when I flashed over the top of my existing settings I kept getting error message whilst trying to access the wireless settings page. Might have had something to do with running DGTeam firmware beforehand. Didn't make a note of the error message but it was something like unable to load <filename.htm>

Will keep you posted on progress, both cabled and wireless. :)

fjs
05/08/2009, 18:18
echo 0 > /proc/sys/net/ipv4/neigh/default/ucast_solicit
echo 0 > /proc/sys/net/ipv4/neigh/all/ucast_solicit
echo 0 > /proc/sys/net/ipv4/neigh/nas0/ucast_solicit



Why did you choose these 3 lines of code?
Was it a catch-all approach?

The problem I have is that they work.

On the router I am using (vlan1 substitutes for nas0), the three lines manipulating the unicast response work, but the first line, affecting the WAN interface alone, does not.

James
05/08/2009, 20:35
Yep, it was to be safe, as just changing echo 0 > /proc/sys/net/ipv4/neigh/nas0/ucast_solicit did not work.

I think it copies the setting from echo 0 > /proc/sys/net/ipv4/neigh/default/ucast_solicit

mark7927
05/08/2009, 22:30
hmm downloaded the http://adsl24.co.uk/files/llu/DG834GT_1.02.19_adsl24_llu.img tryed to open with winzip its saying (internal error processing iso image) any ideas am i doing something wrong?

Oliver341
05/08/2009, 22:33
hmm downloaded the http://adsl24.co.uk/files/llu/DG834GT_1.02.19_adsl24_llu.img tryed to open with winzip its saying (internal error processing iso image) any ideas am i doing something wrong?
You aren't supposed to load it into Winzip, you're supposed to load it into your router via the router's web interface upgrade page.

mark7927
05/08/2009, 22:40
ok thanks iv loaded up the software on my router ill give it a few weeks and let you know how it goes thank you.

fjs
05/08/2009, 22:41
Yep, it was to be safe, as just changing echo 0 > /proc/sys/net/ipv4/neigh/nas0/ucast_solicit did not work.

I think it copies the setting from echo 0 > /proc/sys/net/ipv4/neigh/default/ucast_solicit

Did the 'nas0' line alone not work for you on a DG834GT?
I am interested if it did not.

I do not think the 'all' line is doing anything, but its presence has no ill effects.
I am testing without it, just out of interest.

mark7927
06/08/2009, 21:13
ok just a wee update for u i tryed the router fix and im not having much joy it's still cutting out and re-connecting Im not computer minded so i dont have an explanation but thanks for your effort.

grunson
12/08/2009, 00:40
Did the 'nas0' line alone not work for you on a DG834GT?
I am interested if it did not.

I do not think the 'all' line is doing anything, but its presence has no ill effects.
I am testing without it, just out of interest.

A belated response to this, as I've not been monitoring the threads so closely since I've ceased to experience any problems for whatever reason.

As I believe I mentioned on another forum, though it may have got lost in the excited traffic at the time, the 'nas0' line isn't going to work in /usr/etc/rcS on the Netgear when using dynamic IP because the interface doesn't exist until the DHCP client does its work. In 1.02.19 the interface gets configured by the /usr/etc/udhcpc.fix.script (it may be different on other releases) and so that is probably the ideal place to set ucast_solicit to 0 if one wants to be strictly 'correct'.

G.

fjs
12/08/2009, 20:39
Thank you. Your point about the DHCP Client having to be up first answers the question nicely.

tonys
14/08/2009, 16:26
Since very few have posted on this thread I don't know if no-one else has tried James' amended firmware, or if the problem has just gone away for adsl24 customers who originally experienced loss of routing. It would be nice to get some other reports!

FWIW my Netgear 834GT has been up, with constant sync rate, for 257 hours, with no loss of routing (at least none that I've observed). I have James firmware 1.02.16 plus Oliver's firewall rule implemented.

What I have noticed is that after a run of regular expected 6 hourly lease renewals (dynamic IP) there is an odd run of one or two renewals at 8 or 9 hour intervals. The run of 6's has decreased from an initial nine to a most recent two before the extended renewal time, so I shall be interested to see what happens in the next 24/48 hours.

fjs
14/08/2009, 17:35
The loss of routing problem has not gone away.

I have not adopted the James approach., and suffered an episode from 0630 today, discovered at 1100, which might have been a loss of routing, despite having modified rc_startup (In my case).

I have changed the device mode of the DG834GT to modem, and added a router to the circuit after this. My assumption was that the commands should be applied to the device doing the routing, not the transceiver.

This may not be the case.

Also, I have determined that the log message received is

udhcpc[291]: Lease of 94.192.xxx.xxx obtained, lease time 43200

at lease renewal.

tonys
14/08/2009, 18:52
Is there any reason why you haven't tried James' firmware to the Netgear and used this as the one device? It does seem to provide a viable solution.

fjs
14/08/2009, 22:24
When your start looking at other firmware, the DG834GT has limited functionality.

I do not think this episode will be the last. Having a separate router, using DD-WRT or a variant of Tomato, allows rapid addition of rules without recompilation, ready for the next time.

The next issue is ipv6, which the OS I use supports.
This should make life easier.
I would like configurable router firmware which supports this.
I doubt this will come to the DG834GT, unfortunately.

Pre-ADSL2+ I had a router I could leave alone for 9 months or a year.
Now it needs care and feeding. I am incorporating flexibility to deal with a labile situation.

(Please note the above is a geek answer.)

fjs
16/08/2009, 02:11
After 2 episodes in 2 days, I am forced to apply the command to the modem, to modify ucast_solicit on nas0 on a DG834GT.

It has its own ARP Cache, even when operating as a 'modem'.

jammy
19/08/2009, 14:39
n/m seems i had a different problem entirely out of my hands *sigh*

Noto
20/08/2009, 10:40
Hi James & all,

what is the routing problem?!? is it the same as the netgear problem w/ dynamic ip in the sticky?

or totally separate lol

James
20/08/2009, 17:59
In reality it's separate but only affects certain lines/exchange as we have hundreds using a Netgear and only a handful having the routing issue

jammy
21/08/2009, 01:52
i found the ADSL24 version of the DGN2000 firmware didn't work at all, almost like a corrupted firmware? it restarted in a 'basic mode' and prompted me to upload a new firmware image. I downloaded from three different ISP's and different browsers. Same result.

cookster
24/08/2009, 09:43
OK Guys....Ive got the Netgear DG834 V4 and I obviously have this routing outage issue. I have now flashed my firmware with both the ADSL24 tweaked version and the Netgear DG834Gv4_V5.01.14 version both to no avail. I ahve already called yourselves and ahve had the speed of my line reduced and the stability increased but this made no difference.
I have also this morning had a BT engineer out to check my line and he can find no fault. Whilst the BT engineer was here we also used the test port on the master socket and still had the issue.
What else am i supposed to do here?

James
24/08/2009, 19:38
I think your problem is actually related to your line dropping out, which is not the same problem as this thread is related to. Looking at your line it's re-syncing to the exchange, so this indicates noise on the line. I know your ticket was replied to/you were called today so we'll see how that goes.

cookster
25/08/2009, 11:20
Thanks for the reply James......Im really hoping you can get this sorted ASAP as it is really affecting my work.
I have performed the BT quiet Line test on both the master socket and socket I want to use and there is no noise interference that I can hear from either. BT also say the line is fine, so basically im waiting on you guys to sort out where the issue lies and rectify.

Thanks
cookster

James
26/08/2009, 21:21
According to BT (we've ran serveral tests) they can't see any obvious issues. The next step is to have the router plugged direct in the BT test socket (behind the master faceplate, not in the front of the master) for a good 24-48hrs as we can they see your connection speed differences. If the problem still persists in the test socket after 24hrs then the fault can only be the router, filter, or the external line/exchange equipment and we can get it logged appropriately.

cookster
28/08/2009, 12:52
Ok have configured the modem yesterday morning to use the static IP details that you gave me and checked last night and im getting a constant connection now with no outage. Happy days.
Not sure whether there has been any other work done in the background with yourselves/BT to remedy the issue, but as of last night it was working fine.

Thanks again.

KdMg
02/09/2009, 17:01
Hiya..

Any chance for an updated link for the
DSL-2740B - http://adsl24.co.uk/files/llu/DSL-2640B_2.87_adsl24_llu.bin

DooGie
02/09/2009, 21:28
I was having the same loss of routing problem until I applied the static IP settings.

WAN uptime now at 429 hours so fingers crossed it's worked. However I'm thinking that BE could have changed something over the past couple of weeks.

cookster
05/09/2009, 11:24
I was having the same loss of routing problem until I applied the static IP settings.

WAN uptime now at 429 hours so fingers crossed it's worked. However I'm thinking that BE could have changed something over the past couple of weeks.

I was the same....i had the continual routing issue until I was given a static IP and have been up for 2 weeks now with no outage at all.

I was unsure also whether ADSL24 or BT had done any work in the background or whether it was simply the static IP that sorted.
No one ever confirmed. James?

I hope I get to keep the static IP anyway :)

Cheers
Cookster

Noto
05/09/2009, 14:00
can i ask "losing routing" is this when your browsing and get blank pages and have to hit F5 a few times for it to load...

James
05/09/2009, 21:15
No, that's not the same thing.

Noto
14/09/2009, 16:00
Hi James,

I have tried the modified firmware for DG834Gv4. But unfortunately as before the latest firmware for the v4 has a known problem which i have asked about on these forums. All valve based games like CS, CS:S, TF2 HLDM, and even HoN dont work. Also wont let any mobile devices connect to my router.

So i have had to downgrade back to 5.01.09. Any chance you can add the 4 lines of code into 5.01.09?!?

I have linked the file below:
http://kb.netgear.com/app/answers/detail/a_id/271


Many thanks

Noto

Oliver341
14/09/2009, 20:41
I have tried the modified firmware for DG834Gv4. But unfortunately as before the latest firmware for the v4 has a known problem which i have asked about on these forums. All valve based games like CS, CS:S, TF2 HLDM, and even HoN dont work. Also wont let any mobile devices connect to my router.
Try ticking "Disable Port Scan and DOS Protection" in WAN Setup.

Noto
16/09/2009, 11:04
Try ticking "Disable Port Scan and DOS Protection" in WAN Setup.

wont that put me at risk? because if you see http://adsl24.co.uk/forum/showthread.php?t=7813

I am being port scanned a fair amount

Oliver341
19/09/2009, 19:04
wont that put me at risk?
No. The feature is practically no use in terms of security and sometimes causes problems. If you ever contact Netgear about this issue, they will most likely advise disabling it as a test.

Noto
21/09/2009, 16:09
hi there, this has worked and allowed me to use the latest firmware as a temp fix, I dont quite like the idea of being open to port scans... from the days of ICQ bombing... but it will do for now i guess.

Thanks oliver!

James
23/09/2009, 10:10
New DGN2000 version - http://adsl24.co.uk/files/llu/DGN2000_1.1.8.0_adsl24_llu.img

ChrisRobertson
24/09/2009, 19:38
Hello James
I was on the forum a few weeks ago complaining of this same issue - router says connected - Iron gets no Data. I am using a workaround - have put a time clock on the router that switches off then on around midnight - this seems to keep the connection working more or less but still have to do a software reboot of the router occasionally. Member KdMg pointed out that the link to the DSL-2740B firmware flash is a 404. I haven't done the flash (and I'm not holding my breath) but if you could fix the link I would try it.
Chris R

KdMg
02/10/2009, 17:18
Any chance of a reply to this post...

http://adsl24.co.uk/forum/showpost.php?p=96897&postcount=30

Much appreciated if you may

James
02/10/2009, 23:06
Apologies for the missing linke(s)

The problem I have at present is that the certain Linksys and D-Link firmwares ware not compiling correctly (for some reason) and I've been trying to get these sorted for weeks with no joy yet.

For anyone still waiting for these files, I would advise you to manually apply the fix to your router by logging in to telnet via the command prompt and typing in the below 3 lines, one by one:

echo 0 > /proc/sys/net/ipv4/neigh/default/ucast_solicit

echo 0 > /proc/sys/net/ipv4/neigh/all/ucast_solicit

echo 0 > /proc/sys/net/ipv4/neigh/nas0/ucast_solicit

This is what the firmware has built in. Note you need to apply the telnet commands above if you reboot the router as it won't save them (which the firmware does).

Oliver341
02/10/2009, 23:24
James, any news on whether BE will ever fix this issue in their network? It's been going on for about 5 months now.

James
02/10/2009, 23:30
I wish I could give you an answer. I've blubbed on about it so much I think every member of staff there now knows about it but I think they are not too interested due to the fact the use Thomson routers which don't have the issue. That doesn't help any ISP like ourselves trying to promote their service and improve our customer base, so they have been informed that it *does* need to be fixed one way or the other as it certainly can affect our business.

DooGie
02/10/2009, 23:39
I thought I'd got rid of the problem when I had no loss of routing for over a month.
However over the past couple of weeks it seems to be rearing its ugly head again for me.

Oliver341
02/10/2009, 23:39
I can definitely understand your frustrations. If O2/BE want to expand their wholesale/reselling operations, they would do well to listen to their customers (e.g. you) a bit more. Like you say, the stock answer of "use the supplied router" which O2/BE customers get given just doesn't work for you.

tonys
03/10/2009, 12:48
From the recent lack of comments on this and TBB forum, it would appear that those of us who were most vocal about the issue have now implemented the 'temporary' fix either directly or via James' amended firmware and are quietly getting on with our lives. Others are either using Be/O2 or other Thomson routers, not having the problem, not realising they have the problem, or just putting up with it as they know no better.

Unfortunately, whichever way you look at it, James (and other resellers if there are any) will have to cope with the aftermath unless and until Be/O2 accept they they have to do something. Not the best customer service from a major broadband supplier :rolleyes:

Oliver341
03/10/2009, 16:40
The only light at the end of the tunnel is that the DHCP WAN IP lease renewal bug was eventually fixed, albeit 7 months after I first reported it.