1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

WAG354G and DNS failures on client

Discussion in 'Other Linksys Equipment' started by icest0rm, Dec 28, 2005.

  1. icest0rm

    icest0rm Network Guru Member

    I had set on each of my client connected wireless or wired to the WAG354G, the router IP itself as DNS for resolving hostnames...while this worked for some time, after a bit it stopped working and I had to put on clients my IPS dns to solve correctly hostnames...did I missed out something?
     
  2. booly

    booly Network Guru Member

    Are you using the DHCP ?
     
  3. icest0rm

    icest0rm Network Guru Member

    no, static IPs
     
  4. arubinst

    arubinst Network Guru Member

    I have the same problem

    Abraham
     
  5. booly

    booly Network Guru Member

    It's no a router issue
    I've you setup secondary dns on your pc
     
  6. icest0rm

    icest0rm Network Guru Member

    no, but this setup always worked with my old router
     
  7. BlackAle

    BlackAle Guest

    It IS a router issue, rebooting the router cures the problem and if you bypass using the router for DNS then there is no problem.
     
  8. rrouter

    rrouter Network Guru Member

    I've got exactly the same problem

    I've got that problem too. It works fine for a day or two, then I have to reboot the router to get the DNS resolution working again. I worked around it on one PC by entering the ISP's DNS server addresses, bypassing the router's DNS proxy. However, for whatever reason, that work-around doesn't solve the problem from my laptop.

    I mailed the following to Linksys support:

    I have recently bought a WAG354G and am having problems with the DNS proxy.
    I configure my PCs with the router's IP address as the DNS address. This works fine for a day or two, but then it inexplicably stops resolving names. A power cycle is required to clear the problem, which I'm not satisfied with.

    Is this a known bug? When will fixed firmware be released. I'm currently using 1.01.05, Oct 20 2005


    They responded as follows:

    Thank you for contacting Linksys Customer Support.

    This is the first time we have heard of this concern. Although using the router's address as the DNS address on the computers will work it would be an additional load on the router because it will be the one who needs to resolve the DNS address. It would be better if you use the DNS address coming from your Internet Service Provider (ISP). This addtional load could be the reason why the router stops functioning after a few days.

    Since you are already using the latest firmware, you can try reflashing the same firmware on the router and then do a hard reset on it. You need to reconfigure the device for internet access after the reset.

    1] Press and hold the reset button for 10 seconds.
    2] Let go of the reset button and then unplug the power form the router.
    3] Wait 5 seconds and then plug back the power.

    We do not have any information as to when the next firmware will be released for this router.


    Not very useful...

    I don't buy the 'additional load' excuse. I can't believe I'm the first person to have reported this to Linksys either. If I can persuade my laptop to work with the ISP's DNS addresses, I'll probably put up with the problem. If not, I'll be returning the router and will probably get a Netgear instead.
     
  9. icest0rm

    icest0rm Network Guru Member

    i've already reported that to them too and they said i was the first reporting this issue... :drinking:
     
  10. rrouter

    rrouter Network Guru Member

    Giving Linksys the benefit of the doubt, perhaps they've failed to associate the cases as being the same problem.

    icest0rm - would you mind giving my the support case number they issued you? I'll reply to them telling them it's the same problem. I want them to acknowledge that it's a bug and assign some sort of bug number. I'll then regularly chase a firmware fix.

    arubinst - did you raise the problem with Linksys Customer Support?

    I've found another mention of this problem within the customer reviews on http://www.ebuyer.co.uk. It's the one-star review by Richard Fry.

    I'm kicking myself for buying another Linksys product. I briefly owned the WET54GS5 5-port switch & wireless bridge, until I found that a bug in the WPA-PSK implementation made that mode of security unusable. Customer Services were useless, so I returned it.
     
  11. icest0rm

    icest0rm Network Guru Member

    this is the case number: [Incident: 060103-025413]

    and that is what I reported:

    1) (I've talked about it with Ferdinand, Tech ID 18955): when I setup
    timezone GMT+1 (I live in Italy) router set the time 1 hour in advance
    respect to my real time.

    2) when setting static IPs on my clients connected to the router (1 win
    XP and 1 Linux client) and setting router IP as DNS on both, after some
    time of working correctly they can no more resolve hostnames (this
    doesn't happen simutaneusly on both, one can work and the other not)
    only solution is to restart the router itself.

    I hope that these problems can be fixed on next fw release.

    Would it be possible to have some more detailed statistic on DSL
    connection as CRC errors etc? and on Diagnostic page the possibility to
    ping also an hostname and not only an IP (maybe with a tool to resolve
    hostnames to check that router is still resolving ok).

    Another question, when I try to ping some IPs from within Diagnostic
    page of the router I get an RTT of 30ms for example, the same IP pinged
    on a PC connected by LAN to the router has a response of 54ms...how can
    it be this difference? router pinged from the PC answers at about 0.9/1ms...

    they just changed the status of my case to SOLVED because I didn't answer to their latest reply (getting info about modem purchase etc maybe proposing a replacement...because I told them I was using latest fw and hard reset did not solve the probl)
     
  12. Tjiwa

    Tjiwa Guest

    Yep I got the same problem, the weird thing is, that the wireless connection hasn't got this problem. my laptop keeps working when my Wired pc stops resolving DNS's.

    This is my 3rd Linksys Router though the RMA. I bought a WAG54G v1, and trade it for an WAG54G V2 and last week I got an WAG354G for it...

    Still problems.... :cry:
     
  13. spawnofsonic

    spawnofsonic Guest

    same issue here sadly,

    wireless using dhcp works fine, wired using static messes up, since changing the wired to use isp's dns seems fine. Shame its a bug :(
     
  14. Steed

    Steed Guest

    Me too

    Hi,

    I have exactly the same issue on the WAG354G.

    Hope it is fixed soon!
     
  15. icest0rm

    icest0rm Network Guru Member

    I suggest you all to send questions about this issue to Linksys support, so they will have to reflect and fix it and not to answer that they never had complaints about it :thumbdown:
     
  16. petdoctors

    petdoctors Network Guru Member

    Me too

    Just in case you need more 'evidence' - I too find that DNS proxying stops after a while and I have to reset the router.

    Needs sorting Linksys - y'hear us!?

    Also I have a problem with port 23 (telnet) (not) forwarding but I'll checkout other threads and leave a new one if necessary.
     
  17. icest0rm

    icest0rm Network Guru Member

    Re: Me too

    please drop a mail to support@linksys.com!

    this is working ok here.
     
  18. petdoctors

    petdoctors Network Guru Member

  19. petdoctors

    petdoctors Network Guru Member

    Got a reply from Linksys

    I got a reply from Linksys about the DNS proxy issue. The reply was a 'cut and paste' job from a standard list of things to try - all the way from a power cycle, through a re-setup to a reflash! :thumbdown: :cry:

    I have told them to actually READ my email and COMPOSE a response that bears some resemblance to the points I raised. I wonder what will turn up now!
     
  20. phyber

    phyber Network Guru Member

    Hi there,
    well i dont knowif it solves your problems, but theres a new BETA FW out atleast in germany wich supports ADSL2+.
    Maybe they also changed some other things...
    You can get it from:here
    Username: linksys
    PW: beta7

    then selecting the wag354g folder and then look out for the FW from the 13.02.2006 in the DE folder.
    I know the whole GUI is then written in german but maybe someone can test out if it fixes your problems.

    cya Tobi

    PS: It still says FW 1.01.5 after flashing but it has changed.
     
  21. icest0rm

    icest0rm Network Guru Member

    unfortunately Annex B fw won't work for EU-versions so only DE users will be able to try this update....let's hope it fixes all these issues and that it will be released soon also for EU version...

    just for curiosity...how did u get into that?
     
  22. AdamHussain

    AdamHussain Network Guru Member

    O/T WAG345G-UK or NetGear DG834?

    Sorry to get off topic.

    I was all set to buy a 345, but this thread has me stalling. I’m new to ADSL, so I don’t really know the significance of these DNS failures.

    I’ve a small business, so reliability and stability are important. Just signed with ISP Zen (UK), who appear to support various hardware, including NetGear, but not Linksys, if that makes any odds. Should I go for a 345 or DG834, or maybe a WRT54G/GS(v4)GL / ADSL2MUE combo?
     
  23. icest0rm

    icest0rm Network Guru Member

    this is not a big issue, just a minor bug.

    if u put your ISP DNS in network settings you won't get any problem at all
     
  24. AdamHussain

    AdamHussain Network Guru Member

    Thanks for the heads up, icest0rm. All I needed to know :thumb:
     
  25. OohAhh

    OohAhh Network Guru Member

    Well I get this too. The problem seems to be that dnsmasq, which forwards DNS requests to the ISP's servers, dies. You can see this via the SNMP daemon. When it works you get something like this...

    $ snmpwalk -Os -c public -v 2c brick .1.3.6.1.2.1.25.4.2.1.2
    hrSWRunName.1 = STRING: "init"
    hrSWRunName.2 = STRING: "keventd"
    hrSWRunName.3 = STRING: "ksoftirqd_CPU0"
    hrSWRunName.4 = STRING: "kswapd"
    hrSWRunName.5 = STRING: "bdflush"
    hrSWRunName.6 = STRING: "kupdated"
    hrSWRunName.7 = STRING: "mtdblockd"
    hrSWRunName.8 = STRING: "mail"
    hrSWRunName.12 = STRING: "resetbutton"
    hrSWRunName.22 = STRING: "antsel"
    hrSWRunName.24 = STRING: "cron"
    hrSWRunName.27 = STRING: "tftpd"
    hrSWRunName.30 = STRING: "httpd"
    hrSWRunName.40 = STRING: "snmpd"
    hrSWRunName.45 = STRING: "syslogd"
    hrSWRunName.46 = STRING: "klogd"
    hrSWRunName.47 = STRING: "upnpd-igd"
    hrSWRunName.56 = STRING: "checkadsl"
    hrSWRunName.57 = STRING: "pppd"
    hrSWRunName.58 = STRING: "redial"
    hrSWRunName.60 = STRING: "wanledctrl"
    hrSWRunName.81 = STRING: "dnsmasq"
    hrSWRunName.82 = STRING: "IGMPProxy"

    It seems to have had to reauth in between, as the new pppd PID shows, but this is it when it has failed. Notice dnsmasq is no longer listed.

    $ snmpwalk -Os -c public -v 2c brick .1.3.6.1.2.1.25.4.2.1.2
    hrSWRunName.1 = STRING: "init"
    hrSWRunName.2 = STRING: "keventd"
    hrSWRunName.3 = STRING: "ksoftirqd_CPU0"
    hrSWRunName.4 = STRING: "kswapd"
    hrSWRunName.5 = STRING: "bdflush"
    hrSWRunName.6 = STRING: "kupdated"
    hrSWRunName.7 = STRING: "mtdblockd"
    hrSWRunName.8 = STRING: "mail"
    hrSWRunName.12 = STRING: "resetbutton"
    hrSWRunName.22 = STRING: "antsel"
    hrSWRunName.24 = STRING: "cron"
    hrSWRunName.27 = STRING: "tftpd"
    hrSWRunName.30 = STRING: "httpd"
    hrSWRunName.40 = STRING: "snmpd"
    hrSWRunName.45 = STRING: "syslogd"
    hrSWRunName.46 = STRING: "klogd"
    hrSWRunName.47 = STRING: "upnpd-igd"
    hrSWRunName.56 = STRING: "checkadsl"
    hrSWRunName.58 = STRING: "redial"
    hrSWRunName.60 = STRING: "wanledctrl"
    hrSWRunName.241 = STRING: "pppd"
    hrSWRunName.280 = STRING: "IGMPProxy"
     
  26. icest0rm

    icest0rm Network Guru Member

    forward your discovery to linksys support pls
     
  27. KoP

    KoP Network Guru Member

    Yep..well done @OohAhh, maybe you could teach linksys :grin:
     
  28. OohAhh

    OohAhh Network Guru Member

    Done it just now. Now to see how they react.

    You might find this Gentoo dnsmasq security advisory interesting too. Seems it may be possible to poison the DNS or crash it. The version of dnsmasq in WAG354G firmware is 1.10 and the code in the GPL source dates from about a month or so before the advisory so it may be vulnerable.
     
  29. OohAhh

    OohAhh Network Guru Member

    You never know! :D
     

Share This Page