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

Tomato » WRT54GL weird dhcp issue

Discussion in 'Tomato Firmware' started by loginatnine, Apr 2, 2009.

  1. loginatnine

    loginatnine Addicted to LI Member

    Hey
    I have a WRT54GL with tomato firmware with mlppp (latest version). Recently, my girlfriend hasn't been able to connect to the wireless network. The dhcp range is 192.168.1.100 to 192.168.1.120 and her computer is always assigned the IP 192.168.1.4. She can access the tomato config page but she cannot access the internet. All the other computer on the network connect fine via DHCP or static dhcp(the address are out of the dhcp range). Here is the ipconfig result (in french sorry):

    Adresse physique . . . . . . . . . . . : 00-1F-3B-CA-47-89
    DHCP activé. . . . . . . . . . . . . . : Oui
    Configuration automatique activée. . . : Oui
    Adresse IPv6 de liaison locale. . : fe80::dc1e:590a:dac8:42ab%12(préféré)
    Adresse IPv4. . . . . . . . . . . : 192.168.1.4(préféré)
    Masque de sous-réseau. . . . . . . . . : 255.255.255.0
    Bail obtenu. . . . . . . . . . . . . . : 1 avril 2009 22:00:46
    Bail expirant. . . . . . . . . . . . . : 11 avril 2009 22:00:47
    Passerelle par défaut. . . . . . . . . : 192.168.1.254
    Serveur DHCP . . . . . . . . . . . . . : 192.168.1.254
    Serveurs DNS. . . . . . . . . . . . . : 192.168.1.1
    NetBIOS sur Tcpip. . . . . . . . . . . : Activé

    Here's what I get from the log :
    Dec 31 19:00:07 unknown daemon.info dnsmasq[103]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Dec 31 19:00:07 unknown daemon.info dnsmasq[103]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXXX
    Dec 31 19:00:10 unknown daemon.info dnsmasq[103]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Dec 31 19:00:10 unknown daemon.info dnsmasq[103]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXXX

    I've tried :
    -rebooting several times
    -giving her a static dhcp lease (it still give her 192.168.1.4)
    -disabling ipv6
    She is using windows vista home premium.

    I'm lost, thanks for your help!
     
  2. astehn

    astehn LI Guru Member

    Sorry if this is too obvious a reply, but it sounds like your girlfriends problem is unrelated to Tomato. It sounds like it's the settings for her wireless card (perhaps it is manually set up to use the wrong address of 192.168.1.4 ?)

    Have you confirmed that her wireless card is properly set up to automatically use DHCP to get an address? If you have, and it still doesn't work, what happens if you manually configure her wireless card to use an address within the proper range, say, 192.168.1.105 ?

    Like I said, these may be stupid questions, but I got the feeling you were looking at the problem as though it stems from Tomato, when it seems more like it's your girlfriend's wireless configuration. At the very least, you should be able to manually configure her wireless card to use an IP address w/in Tomato's DHCP range.

    Another thing that seems goofy is that I would think "Passerelle par défaut" and "Serveur DHCP" should be that IP of your Tomato router, which I assume is 192.168.1.1 This also suggests to me that the problem lies in the configuration of the wireless card.
     
  3. loginatnine

    loginatnine Addicted to LI Member

    That's what I thought also but she can connect fine in many other wifi hotspot throughout the city so I assumed it was ok...I'll check it out when she gets back today.

    I'm also monitoring the log and there is some strange stuff going on, lots of DHCP requests :

    Apr 2 04:22:09 unknown daemon.info dnsmasq[111]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXX
    Apr 2 04:23:38 unknown daemon.info dnsmasq[111]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Apr 2 04:23:38 unknown daemon.info dnsmasq[111]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXX
    Apr 2 04:25:07 unknown daemon.info dnsmasq[111]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Apr 2 04:25:07 unknown daemon.info dnsmasq[111]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXX
    Apr 2 04:25:10 unknown daemon.info dnsmasq[111]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Apr 2 04:25:10 unknown daemon.info dnsmasq[111]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXX
    Apr 2 04:26:28 unknown daemon.info dnsmasq[111]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Apr 2 04:26:28 unknown daemon.info dnsmasq[111]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXX
    Apr 2 04:27:56 unknown daemon.info dnsmasq[111]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Apr 2 04:27:56 unknown daemon.info dnsmasq[111]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXX
    Apr 2 04:29:04 unknown daemon.info dnsmasq[111]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Apr 2 04:29:04 unknown daemon.info dnsmasq[111]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXX
    Apr 2 04:30:14 unknown daemon.info dnsmasq[111]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Apr 2 04:30:14 unknown daemon.info dnsmasq[111]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXX
    Apr 2 04:31:43 unknown daemon.info dnsmasq[111]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Apr 2 04:31:43 unknown daemon.info dnsmasq[111]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXX
    Apr 2 04:31:46 unknown daemon.info dnsmasq[111]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Apr 2 04:31:46 unknown daemon.info dnsmasq[111]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXX
    Apr 2 04:33:32 unknown daemon.info dnsmasq[111]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Apr 2 04:33:32 unknown daemon.info dnsmasq[111]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXX
    Apr 2 04:35:00 unknown daemon.info dnsmasq[111]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Apr 2 04:35:00 unknown daemon.info dnsmasq[111]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXX
    Apr 2 04:36:29 unknown daemon.info dnsmasq[111]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Apr 2 04:36:29 unknown daemon.info dnsmasq[111]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXX
    Apr 2 04:38:29 unknown daemon.info dnsmasq[111]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Apr 2 04:38:29 unknown daemon.info dnsmasq[111]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXX

    and a new command that I didn't see anywhere : DHCPOFFER:

    Apr 2 08:07:42 unknown daemon.info dnsmasq[111]: DHCPREQUEST(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Apr 2 08:07:42 unknown daemon.info dnsmasq[111]: DHCPNAK(br0) 192.168.1.4 00:1f:3b:ca:47:89 address not available
    Apr 2 08:07:43 unknown daemon.info dnsmasq[111]: DHCPDISCOVER(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Apr 2 08:07:43 unknown daemon.info dnsmasq[111]: DHCPOFFER(br0) 192.168.1.160 00:1f:3b:ca:47:89
    Apr 2 08:07:52 unknown daemon.info dnsmasq[111]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89
    Apr 2 08:07:52 unknown daemon.info dnsmasq[111]: DHCPACK(br0) 192.168.1.4 00:1f:3b:ca:47:89 PC-de-XXXX
    Apr 2 08:07:55 unknown daemon.info dnsmasq[111]: DHCPINFORM(br0) 192.168.1.4 00:1f:3b:ca:47:89

    thanks for your help!
     
  4. Toastman

    Toastman Super Moderator Staff Member Member

    I think maybe you have an Intel Wireless card., perhaps a HP/Compaq laptop. It may be your tomato version does not have the newer drivers. Look at this thread: http://www.linksysinfo.org/forums/sh...ad.php?t=60509

    Looking at the last bit - that made a bit more sense. Your laptop was asking for 192.168.1.4 but was told that it was in unavailable (probably marked as in use). At least here we had a NACK. Then it was OFFERed .160...
     
  5. loginatnine

    loginatnine Addicted to LI Member

    Yes I believe she has a intel 3945abg card, it's a dell laptop. I'll try this as well thank you very much :biggrin:
     
  6. Toastman

    Toastman Super Moderator Staff Member Member

    Try Victek's latest version, wireless driver 4.158.4.0 - if that works, check with the author of MLPP, if you need to use it. http://cdn.adslzone.net/pub/repos/victek/Tomato/Tomato_RAF_1.23.8515.4-ND.7z

    That "might" clear up some problems, if not look again. For some reason that laptop has the default gateway set to 192.168.1.254, it should have been assigned the same IP as DNS which is 192,168.1.1. Something is screwed up. In my experience, the two causes of problems like this are caused by a) Intel wireless cards and b) Windows Vista.
     
  7. loginatnine

    loginatnine Addicted to LI Member

    Does running the three commands you pointed out should solve the problem or this version does more than that? I'm diagnosing this problem from 250km away (my gf doesn't live in the same town as me) so updating the firmware would remove the remote login option that I use to test stuff on the router...
     
  8. Toastman

    Toastman Super Moderator Staff Member Member

    OK, firstly, does she definitely have one of the ND drivers? Info in "ABOUT" should say. If so then those commands will do the trick. Remote login is also available on all tomato versions via HTTP or SSH, but maybe you have something else in mind... ? I am not familiar with MLPPP.

    good luck...
     
  9. loginatnine

    loginatnine Addicted to LI Member

    That's what it says in the about page :
    Tomato Firmware v1.19.0107
    Copyright (C) 2006-2008 Jonathan Zarate
    http://www.polarcloud.com/tomato/

    Built on Thu, 17 Jul 2008 01:21:00 -0400

    I was just trying to say that I can't upgrade the firmware from here since I can't be physically connected to the router....
     
  10. fyellin

    fyellin LI Guru Member

    I wanted to point out that the DHCP with the NAK's and the OFFER is what I was expecting to see all along. It's the correct behavior.

    The conversation is something like:
    I'd like to renew my lease on this DHCP address
    NAK (negative acknowledgement), I can't do that
    DISCOVER: Someone give me a DHCP address then
    OFFER: Here's one, what to you think
    REQUEST: Sure, may I please have that address
    ACK: Acknowledged.​
     
  11. loginatnine

    loginatnine Addicted to LI Member

    Very informative thanks
    However, what is DHCPINFORM ? Also, this line is weird :
    Apr 2 08:07:43 unknown daemon.info dnsmasq[111]: DHCPOFFER(br0) 192.168.1.160 00:1f:3b:ca:47:89
    because it's outside the DHCP range I've setted (192.168.1.100-192.168.1.120)
     
  12. Toastman

    Toastman Super Moderator Staff Member Member

    The most recent DHCPv4 Standard [RFC2131] added a new DHCPv4 message:
    DHCPINFORM. The intent of the DHCPINFORM message was for clients
    that used manually entered fixed IPv4 addresses to still be able to
    get some configuration state dynamically. Since that time, however,
    we have seen this message used by normal DHCPv4 dynamically addressed
    clients; clients that have previously succeeded in receiving
    configuration through DHCPDISCOVER, DHCPOFFER, DHCPREQUEST, and
    finally DHCPACK messages.

    These clients are attempting DHCPINFORM messages in order to obtain
    additional configuration state that was not present in their lease
    binding. The discovery is that DHCPINFORM can be used to reach extra
    DHCP servers, other than the one that gave an address, which may have
    more configuration options available but aren't in a position to give
    addresses. This extra configuration state is often required by
    applications that were not running at system startup, when the DHCP
    client was initialized.

    If a client has obtained a network address through some other means
    (e.g., manual configuration), it may use a DHCPINFORM request message
    to obtain other local configuration parameters. Servers receiving a
    DHCPINFORM message construct a DHCPACK message with any local
    configuration parameters appropriate for the client without:
    allocating a new address, checking for an existing binding, filling
    in 'yiaddr' or including lease time parameters. The servers SHOULD
    unicast the DHCPACK reply to the address given in the 'ciaddr' field
    of the DHCPINFORM message.

    http://tools.ietf.org/html/draft-ietf-dhc-dhcpinform-clarify-00

    I saw a reference (somewhere) that said Tomato sends a DHCP INFORM to"discover rogue servers"... ???
     
  13. loginatnine

    loginatnine Addicted to LI Member

    So that tells me that it's either a "hidden" dhcp server or

    that it's configured to use a static ip address, did I miss anything?
     
  14. Toastman

    Toastman Super Moderator Staff Member Member

    Well, the RFC's seem to waffle on and on, but seems that is about the gist of it. However, I have seen Intel cards take part in exchanges like this before ending up in a "associated" state but with no internet access. That's why I thought it might be helpful.

    It is also very common for a machine that has a static IP address issued by DHCP to appear after being switched off for a while, only to be told that " the ip address cannot be issued because it is already allocated to 00.11.22.33.44.55 - but in fact that is the correct MAC address of the machine it is denying it to.... and sometimes this dialogue continues for hours.

    Thinking about it, if one were entering an IP address manually in windows, a typo like entering .254 for gateway might be an easy thing to do... has she checked?
     
  15. loginatnine

    loginatnine Addicted to LI Member

    I will definitely check those settings tonight when she comes back. I'll keep you guys updated about it. Thanks one more time for your help!
     
  16. Toastman

    Toastman Super Moderator Staff Member Member

    How about:

    I'd like to renew my lease on this DHCP address
    NAK (negative acknowledgement), I can't do that, some b*****d already took it
    DISCOVER: Someone give me a DHCP address then
    OFFER: Here's one, what do you think?
    SOUNDITOUT: Is it free?
    OFFER: Yes
    REQUEST: OK, can I have 10 please?
    ACK: Acknowledged.
     
  17. loginatnine

    loginatnine Addicted to LI Member

    Hahaha why don't computers act like that that'd be cool :D
     
  18. loginatnine

    loginatnine Addicted to LI Member

    Reporting back, the wireless card is configured to use DHCP so it's not a static IP problem. BUT, I'm not sure why (maybe Toastman's command), it worked now! The laptop got assigned the IP via static DHCP like it was supposed to be....
    THANKS TOASTMAN you rock, i've bookmarked your thread and will use it if the problems comes again....
    Thanks to all of you for your help!
     
  19. Toastman

    Toastman Super Moderator Staff Member Member

    Can you confirm that the command to set wireless regulatory domain to off is what worked?

    Good news..
     
  20. loginatnine

    loginatnine Addicted to LI Member

    Sry toastman, forgot to check back the thread ;)

    well I can't confirm anything at 100% but, I ran those commands during the day and when she got back, her laptop got assigned the correct IP via static dhcp. I haven't done anything else on the router nor her computer so I guess it's the thread you pointed out who did the trick...
    Take it for what it's worth, but one thing for sure, you rock and thanks a billion times for your help it is very appreciated!
     
  21. Toastman

    Toastman Super Moderator Staff Member Member

    Thanks for confirming! That may help others with similar problems. These days, almost all my problems in residential buildings here seem to be with Intel cards!
     

Share This Page