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

Feedback on 33RC1

Discussion in 'Tarifa Firmware' started by Outer Marker, Aug 8, 2008.

  1. Outer Marker

    Outer Marker Guest

    Just wanted to say thank you very much for Tarifa 33RC1. NAT-PMP is working beautifully with all applications that support it. I have been able to use telnet to adjust the rule cleaning parameter therhold to 10 instead of the default 20.

    The only persistant issue is that of losing DHCP to the ISP every 3 days. I cannot use the DHCP Renew button in the router web interface as that fails to re-establish an IP address from the ISP. My only options are to reboot the router, or make a change in the setup screen. Usually I change the MTU value, or sometimes I just change the name of the Router and hit save settings. Then things start working again. Very bizzare!
     
  2. jchuit

    jchuit Network Guru Member

    The Release and Renew button only releases the client ip and Renews the ip, if you change a setting then udhcpc is stopped and restarted.

    The program udhcpc is doing all the client ip processing, the syslog isn't giving a lot of info. The udhcpd server does give a lot more, I changed udhcpc a bit to give the same syslog messages as udhcpd does.

    You can download this RC2 vesion here: ftp://krumdeel.dyndns.org/Public/wrt54gl/Tarifa033RC2/

    Did your WAN ip change after restarting? see: http://192.168.1.1/Status_Router.asp
    Or did it stay the same?

    The syslog (after enabling and NOT setting an ip number in the syslog field) can be found in /tmp/var/log.

    To view: cat /tmp/var/log/messages
     
  3. Outer Marker

    Outer Marker Guest

    Thanks for your help. The WAN IP remained the same after the restart, it did not change.

    I will install and try out your RC2 firmware this evening. Please give me a few days to run the log and see if we can capture one of these "events"

    -- Outer Marker.
     
  4. jchuit

    jchuit Network Guru Member

    udhcpc: setting an ip address for the WAN port.

    Some more info:

    Most users have a adsl or cable connection and get their WAN ip-address assigned by DHCP.
    The Router (udhcpc client) receives this ip-address from your Internet Provider and uses this to give an ip-address to the WAN port of your WRT54GL.

    The ip-address is leased for a period of time, after this period the ip-address isn't valid anymore and reset, the lease time is set by your Provider and will expire after a few days.

    At 50% of the lease time, udhcpc will try to renew the ip address, normally this will succeed, if this doesn't, udhcpc will keep retrying until expiring.
    After expiring the program will re-init again. (INIT_SELECTING)

    After INIT_SELECTING the program starts the discover process. An option called requested ip can be used here to ask an specific ip from your provider.

    This requested ip-address option isn't set at INIT_SELECTING, but it is used in the discover process. I think this value should be set to 0.
     
  5. Outer Marker

    Outer Marker Guest

    So far, so good. I have been up for 4 days, 20 hours with no problems. I have syslogd active, hoping I would catch an event that would tell us what is happening with the disconnects. My next test will be to turn syslogd off and see if it disconnects after 3 days again!

    I was wondering though... how do I clear syslogd? Is it automatically cleared when I disable it, or is it only deleted when I clear nvram? I'd rather not have to re-configure router after clearing nvram just to clear the log.
     
  6. jchuit

    jchuit Network Guru Member

    Tarifa b033

    Good to hear the problem didn't show up.

    The LOG file will clear after restarting and is stored in RAM memory, the /tmp/..... directory is a RAMdisc. After restarting the RAMdisc is empty again.
    Or just type: rm /tmp/var/log/mes*.*

    Meanwhile I tested udhcpc on three different routers, this to see if could find any problem.

    Configured a range of 5 ip's in my dhcp server to serve 3 ISP addresses.
    I tested lease times between 600 seconds and infinity.

    The routers all worked fine, except one time a packet 'discover' was send to the dhcp server, the dhcp server stopped responding for this specific router. The others just worked fine!

    11:20:40 (none) daemon.info udhcpc[149]: state is INIT_SELECTING
    11:20:40 (none) daemon.info udhcpc[149]: Sending discover... (40840)
    11:20:40 (none) daemon.info udhcpc[149]: Waiting on select...

    As you can see the WRT54GL router didn't just send one packed, but 40840, this without any answer. A day later I came to the idea to swap the ISP dhcp server for an WRT54G, and the router continued working again:

    11:20:41 (none) daemon.info udhcpc[149]: state is INIT_SELECTING
    11:20:41 (none) daemon.info udhcpc[149]: state is REQUESTING
    11:20:41 (none) daemon.info udhcpc[149]: Sending select for 192.168.1.101...
    11:20:41 (none) daemon.info udhcpc[149]: Waiting on select...
    11:20:41 (none) daemon.info udhcpc[149]: state is REQUESTING
    11:20:41 (none) daemon.info udhcpc[149]: state is RENEWING
    11:20:41 (none) daemon.info udhcpc[149]: state is REBINDING
    11:20:41 (none) daemon.info udhcpc[149]: Lease of 192.168.1.101 obtained, lease time 120

    Connected the ISP back again, but no luck, the dhcp server had first to be restarted.

    This problem is pointing to INIT_SELECTING and here I found the 'requested ip' isn't set, in fact it can have any value for the first run of dhcpc 0.98, since this value isn't given as a program startup option.
    In the current udhcpc from busybox this value is preset at 0, as it should.

    I will change this in the upcoming Tarifa 033.
     
  7. Outer Marker

    Outer Marker Guest

    Thank you so much for your research and explanations. Tarifa is sensational!
     
  8. Outer Marker

    Outer Marker Guest

    RC4 resuslts

    Per my PM, here is my syslogd. It is attached.
     

    Attached Files:

    • Log.zip
      File size:
      57 KB
      Views:
      35
  9. jchuit

    jchuit Network Guru Member

    Tarifa033RC1

    Thanks for your input, the Tarifa 033RC1 will be the last firmware in this release.

    Next firmware 034 will be based on 4.30.12 source and not the 4.71.1 source.

    This change will ensure support for all future WRT54GL models.
    In the 4.30.12 source there are a lot of problems solved by linksys, there is even a partial support for static ip's.

    Some problems solved in the Tarifa firmware are now solved in the Linksys original firmware, this makes implementing the Tarifa source a little bit difficult.

    Greetings,
    jchuit
     
  10. Outer Marker

    Outer Marker Guest

    Will this still support my WRT54G v2.0 router? I don't have the GL
     
  11. jchuit

    jchuit Network Guru Member

    It will support all WRT54G from v1.0 to v4, wrt54gs from 1.0 to v4 and the WRT54GL v1.x.
     
  12. Outer Marker

    Outer Marker Guest

    I will await Tarifa 034 for the new source code changes. Thank you for your development. In the meantime, since everything else work perfectly, could you tell me what script I can paste in the startup box to make my router reboot every day at 0800 hrs? I think that way I can at least workaround this DHCP crash until Traifa 034 comes out.

    -- Outer Marker
     
  13. jchuit

    jchuit Network Guru Member

    script

    I copied this out of the manual

    nvram set rc_startup='#!/bin/sh
    /bin/sleep 86400
    /sbin/reboot
    '

    Or copy and paste this in your rc_startup:

    #!/bin/sh
    /bin/sleep 86400
    /sbin/reboot

    And a script to restart dhcpc program and .rc_startup script:

    #!/bin/sh
    /bin/sleep 86400
    /usr/sbin/udhcpc_kill.sh
    /bin/sleep 10
    /usr/sbin/udhcpd /tmp/udhcpd.conf
    /tmp/.rc_startup.sh

    As of Tarifa 034 the name .rc_startup.sh will change to rc_startup.sh

    Greetings,
    jchuit
     

Share This Page