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

Tomato 1.24 ND release not working? Post up!

Discussion in 'Tomato Firmware' started by FattysGoneWild, May 24, 2009.

  1. FattysGoneWild

    FattysGoneWild LI Guru Member

    I see other people are running into the same thing as me. The router and modem not linking up together after flashing the firmware. I thought by making this thread. It might help find the problem since we all have so many setups. The non ND version of 1.24 is working fine for me. I see other people reporting the same thing.

    Hardware:

    Linksys CM100 cable modem
    Linksys WRT54GL v1.1

    Flashing:

    1. Reset back to defaults.
    2. Cleared NVRAM
    3. Flashed
    4. Cleared NVRAM
    5. Configured

    I was running Victek's ND 1.23 release before upgrading to 1.24 ND. Which worked fine. Flashed back to his after finding 1.24 ND not working. Worked fine once again. Wanted to test non ND 1.24 version and flashed with that. Since others said it worked fine for them but not the ND version.

    *****EDIT******

    I should have added this earlier when I first posted. Can you also please post if the 1.24 ND version is working fine for you. With make and model of modem/router.
     
  2. neoufo51

    neoufo51 Network Guru Member

    I can confirm everything you say. D-Link cable modem here so it's not just your modem.
     
  3. nvtweak

    nvtweak LI Guru Member

    have any logs?
     
  4. FattysGoneWild

    FattysGoneWild LI Guru Member

    This is what I found in the log after flashing to the ND version. I only edited out my mac address and pc name.

    Dec 31 16:00:06 unknown user.warn kernel: tomato_ct.c [May 22 2009 20:34:55]
    Dec 31 16:00:06 unknown user.info kernel: vlan0: dev_set_promiscuity(master, 1)
    Dec 31 16:00:06 unknown user.info kernel: device eth0 entered promiscuous mode
    Dec 31 16:00:06 unknown user.info kernel: device vlan0 entered promiscuous mode
    Dec 31 16:00:06 unknown user.info kernel: device eth1 entered promiscuous mode
    Dec 31 16:00:06 unknown user.info kernel: br0: port 2(eth1) entering learning state
    Dec 31 16:00:06 unknown user.info kernel: br0: port 1(vlan0) entering learning state
    Dec 31 16:00:06 unknown user.warn kernel: vlan1: Setting MAC address to
    Dec 31 16:00:06 unknown user.info kernel: br0: port 2(eth1) entering forwarding state
    Dec 31 16:00:06 unknown user.info kernel: br0: topology change detected, propagating
    Dec 31 16:00:06 unknown user.info kernel: br0: port 1(vlan0) entering forwarding state
    Dec 31 16:00:06 unknown user.info kernel: br0: topology change detected, propagating
    Dec 31 16:00:06 unknown user.info kernel: vlan1: add 01:00:5e:00:00:01 mcast address to master interface
    Dec 31 16:00:07 unknown daemon.info dnsmasq[82]: started, version 2.47 cachesize 150
    Dec 31 16:00:07 unknown daemon.info dnsmasq[82]: compile time options: no-IPv6 GNU-getopt no-RTC no-DBus no-I18N no-TFTP
    Dec 31 16:00:07 unknown daemon.info dnsmasq[82]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d
    Dec 31 16:00:08 unknown daemon.warn dnsmasq[82]: failed to access /etc/resolv.dnsmasq: No such file or directory
    Dec 31 16:00:08 unknown daemon.info dnsmasq[82]: read /etc/hosts - 0 addresses
    Dec 31 16:00:08 unknown daemon.info dnsmasq[82]: read /etc/hosts.dnsmasq - 3 addresses
    Dec 31 16:00:08 unknown cron.err crond[86]: crond (busybox 1.14.0) started, log level 9
    Dec 31 16:00:08 unknown user.info init[1]: Tomato 1.24.1715
    Dec 31 16:00:08 unknown user.info init[1]: Linksys WRT54G/GS/GL
    Dec 31 16:00:08 unknown daemon.notice miniupnpd[91]: HTTP listening on port 5000
    Dec 31 16:00:11 unknown daemon.info dnsmasq[82]: DHCPREQUEST(br0) 192.168.1.100
    Dec 31 16:00:11 unknown daemon.info dnsmasq[82]: DHCPACK(br0) 192.168.1.100

    I also dl the system log if you need that as well.
     
  5. nvtweak

    nvtweak LI Guru Member

    Try enabling more options in logging section, at least select "DHCP Client". Save, reboot all of your equipment, then repost the new log file.
     
  6. FattysGoneWild

    FattysGoneWild LI Guru Member

    Here is the system log from the ND version. I done the same with this log editing out pc name and mac address. I think I am to late with what you want me to do since the ND version would not work for me. I am on the standard version now. :(

    Dec 31 16:00:05 unknown syslog.info syslogd started: BusyBox v1.14.0
    Dec 31 16:00:06 unknown user.notice kernel: klogd started: BusyBox v1.14.0 (2009-05-22 20:30:36 PDT)
    Dec 31 16:00:06 unknown user.warn kernel: CPU revision is: 00029008
    Dec 31 16:00:06 unknown user.warn kernel: Primary instruction cache 16kb, linesize 16 bytes (2 ways)
    Dec 31 16:00:06 unknown user.warn kernel: Primary data cache 8kb, linesize 16 bytes (2 ways)
    Dec 31 16:00:06 unknown user.warn kernel: Linux version 2.4.20 (root@tobu) (gcc version 3.2.3 with Broadcom modifications) #1 Fri May 22 20:33:07 PDT 2009
    Dec 31 16:00:06 unknown user.warn kernel: Setting the PFC to its default value
    Dec 31 16:00:06 unknown user.warn kernel: Determined physical RAM map:
    Dec 31 16:00:06 unknown user.warn kernel: memory: 01000000 @ 00000000 (usable)
    Dec 31 16:00:06 unknown user.warn kernel: On node 0 totalpages: 4096
    Dec 31 16:00:06 unknown user.warn kernel: zone(0): 4096 pages.
    Dec 31 16:00:06 unknown user.warn kernel: zone(1): 0 pages.
    Dec 31 16:00:06 unknown user.warn kernel: zone(2): 0 pages.
    Dec 31 16:00:06 unknown user.warn kernel: Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
    Dec 31 16:00:06 unknown user.warn kernel: CPU: BCM5352 rev 0 at 200 MHz
    Dec 31 16:00:06 unknown user.warn kernel: Calibrating delay loop... 199.47 BogoMIPS
    Dec 31 16:00:06 unknown user.info kernel: Memory: 14428k/16384k available (1371k kernel code, 1956k reserved, 108k data, 64k init, 0k highmem)
    Dec 31 16:00:06 unknown user.info kernel: Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)
    Dec 31 16:00:06 unknown user.info kernel: Inode cache hash table entries: 1024 (order: 1, 8192 bytes)
    Dec 31 16:00:06 unknown user.warn kernel: Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
    Dec 31 16:00:06 unknown user.warn kernel: Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
    Dec 31 16:00:06 unknown user.warn kernel: Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
    Dec 31 16:00:06 unknown user.warn kernel: Checking for 'wait' instruction... unavailable.
    Dec 31 16:00:06 unknown user.warn kernel: POSIX conformance testing by UNIFIX
    Dec 31 16:00:06 unknown user.warn kernel: PCI: no core
    Dec 31 16:00:06 unknown user.warn kernel: PCI: Fixing up bus 0
    Dec 31 16:00:06 unknown user.info kernel: Linux NET4.0 for Linux 2.4
    Dec 31 16:00:06 unknown user.info kernel: Based upon Swansea University Computer Society NET3.039
    Dec 31 16:00:06 unknown user.warn kernel: Initializing RT netlink socket
    Dec 31 16:00:06 unknown user.warn kernel: Starting kswapd
    Dec 31 16:00:06 unknown user.info kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
    Dec 31 16:00:06 unknown user.info kernel: devfs: boot_options: 0x1
    Dec 31 16:00:06 unknown user.info kernel: squashfs: version 3.0 (2006/03/15) Phillip Lougher
    Dec 31 16:00:06 unknown user.warn kernel: pty: 256 Unix98 ptys configured
    Dec 31 16:00:06 unknown user.info kernel: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
    Dec 31 16:00:06 unknown user.info kernel: ttyS00 at 0xb8000300 (irq = 3) is a 16550A
    Dec 31 16:00:06 unknown user.info kernel: ttyS01 at 0xb8000400 (irq = 0) is a 16550A
    Dec 31 16:00:06 unknown user.warn kernel: HDLC line discipline: version $Revision: 1.1.1.4 $, maxframe=4096
    Dec 31 16:00:06 unknown user.info kernel: N_HDLC line discipline registered.
    Dec 31 16:00:06 unknown user.info kernel: PPP generic driver version 2.4.2
    Dec 31 16:00:06 unknown user.debug kernel: Physically mapped flash: Found an alias at 0x400000 for the chip at 0x0
    Dec 31 16:00:06 unknown user.debug kernel: Physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
    Dec 31 16:00:06 unknown user.debug kernel: Physically mapped flash: Found an alias at 0xc00000 for the chip at 0x0
    Dec 31 16:00:06 unknown user.debug kernel: Physically mapped flash: Found an alias at 0x1000000 for the chip at 0x0
    Dec 31 16:00:06 unknown user.debug kernel: Physically mapped flash: Found an alias at 0x1400000 for the chip at 0x0
    Dec 31 16:00:06 unknown user.debug kernel: Physically mapped flash: Found an alias at 0x1800000 for the chip at 0x0
    Dec 31 16:00:06 unknown user.debug kernel: Physically mapped flash: Found an alias at 0x1c00000 for the chip at 0x0
    Dec 31 16:00:06 unknown user.notice kernel: Amd/Fujitsu Extended Query Table v1.1 at 0x0040
    Dec 31 16:00:06 unknown user.notice kernel: number of CFI chips: 1
    Dec 31 16:00:06 unknown user.notice kernel: Flash device: 0x400000 at 0x1c000000
    Dec 31 16:00:06 unknown user.notice kernel: Creating 5 MTD partitions on "Physically mapped flash":
    Dec 31 16:00:06 unknown user.notice kernel: 0x00000000-0x00040000 : "pmon"
    Dec 31 16:00:06 unknown user.notice kernel: 0x00040000-0x003f0000 : "linux"
    Dec 31 16:00:06 unknown user.notice kernel: 0x000e710c-0x00310000 : "rootfs"
    Dec 31 16:00:06 unknown user.notice kernel: 0x00310000-0x003f0000 : "jffs2"
    Dec 31 16:00:06 unknown user.notice kernel: 0x003f0000-0x00400000 : "nvram"
    Dec 31 16:00:06 unknown user.err kernel: sflash: found no supported devices
    Dec 31 16:00:06 unknown user.info kernel: NET4: Linux TCP/IP 1.0 for NET4.0
    Dec 31 16:00:06 unknown user.info kernel: IP Protocols: ICMP, UDP, TCP, IGMP
    Dec 31 16:00:06 unknown user.info kernel: IP: routing cache hash table of 512 buckets, 4Kbytes
    Dec 31 16:00:06 unknown user.info kernel: TCP: Hash tables configured (established 1024 bind 2048)
    Dec 31 16:00:06 unknown user.info kernel: Linux IP multicast router 0.06 plus PIM-SM
    Dec 31 16:00:06 unknown user.warn kernel: ip_conntrack version 2.1 (8092 buckets, 4096 max) - 368 bytes per conntrack
    Dec 31 16:00:06 unknown user.warn kernel: ip_tables: (C) 2000-2002 Netfilter core team
    Dec 31 16:00:06 unknown user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
    Dec 31 16:00:06 unknown user.info kernel: NET4: Ethernet Bridge 008 for NET4.0
    Dec 31 16:00:06 unknown user.alert kernel: 802.1Q VLAN Support v1.7 Ben Greear <greearb@candelatech.com>
    Dec 31 16:00:06 unknown user.alert kernel: All bugs added by David S. Miller <davem@redhat.com>
    Dec 31 16:00:06 unknown user.warn kernel: VFS: Mounted root (squashfs filesystem) readonly.
    Dec 31 16:00:06 unknown user.info kernel: Mounted devfs on /dev
    Dec 31 16:00:06 unknown user.info kernel: Freeing unused kernel memory: 64k freed
    Dec 31 16:00:06 unknown user.warn kernel: Algorithmics/MIPS FPU Emulator v1.5
    Dec 31 16:00:06 unknown user.warn kernel: ip_conntrack_pptp version 1.9 loaded
    Dec 31 16:00:06 unknown user.warn kernel: ip_nat_pptp version 1.5 loaded
    Dec 31 16:00:06 unknown user.warn kernel: ip_conntrack_rtsp v0.01 loading
    Dec 31 16:00:06 unknown user.warn kernel: ip_nat_rtsp v0.01 loading
    Dec 31 16:00:06 unknown user.warn kernel: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 4.130.25.0
    Dec 31 16:00:06 unknown user.warn kernel: eth1: Broadcom BCM4320 802.11 Wireless Controller 4.130.19.0
    Dec 31 16:00:06 unknown user.warn kernel: tomato_ct.c [May 22 2009 20:34:55]
    Dec 31 16:00:06 unknown user.info kernel: vlan0: dev_set_promiscuity(master, 1)
    Dec 31 16:00:06 unknown user.info kernel: device eth0 entered promiscuous mode
    Dec 31 16:00:06 unknown user.info kernel: device vlan0 entered promiscuous mode
    Dec 31 16:00:06 unknown user.info kernel: device eth1 entered promiscuous mode
    Dec 31 16:00:06 unknown user.info kernel: br0: port 2(eth1) entering learning state
    Dec 31 16:00:06 unknown user.info kernel: br0: port 1(vlan0) entering learning state
    Dec 31 16:00:06 unknown user.warn kernel: vlan1: Setting MAC address to
    Dec 31 16:00:06 unknown user.info kernel: br0: port 2(eth1) entering forwarding state
    Dec 31 16:00:06 unknown user.info kernel: br0: topology change detected, propagating
    Dec 31 16:00:06 unknown user.info kernel: br0: port 1(vlan0) entering forwarding state
    Dec 31 16:00:06 unknown user.info kernel: br0: topology change detected, propagating
    Dec 31 16:00:06 unknown user.info kernel: vlan1: add 01:00:5e:00:00:01 mcast address to master interface
    Dec 31 16:00:07 unknown daemon.info dnsmasq[82]: started, version 2.47 cachesize 150
    Dec 31 16:00:07 unknown daemon.info dnsmasq[82]: compile time options: no-IPv6 GNU-getopt no-RTC no-DBus no-I18N no-TFTP
    Dec 31 16:00:07 unknown daemon.info dnsmasq[82]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d
    Dec 31 16:00:08 unknown daemon.warn dnsmasq[82]: failed to access /etc/resolv.dnsmasq: No such file or directory
    Dec 31 16:00:08 unknown daemon.info dnsmasq[82]: read /etc/hosts - 0 addresses
    Dec 31 16:00:08 unknown daemon.info dnsmasq[82]: read /etc/hosts.dnsmasq - 3 addresses
    Dec 31 16:00:08 unknown cron.err crond[86]: crond (busybox 1.14.0) started, log level 9
    Dec 31 16:00:08 unknown user.info init[1]: Tomato 1.24.1715
    Dec 31 16:00:08 unknown user.info init[1]: Linksys WRT54G/GS/GL
    Dec 31 16:00:08 unknown daemon.notice miniupnpd[91]: HTTP listening on port 5000
    Dec 31 16:00:11 unknown daemon.info dnsmasq[82]: DHCPREQUEST(br0) 192.168.1.100
    Dec 31 16:00:11 unknown daemon.info dnsmasq[82]: DHCPACK(br0) 192.168.1.100

     
  7. nvtweak

    nvtweak LI Guru Member

    It looks like the same log as before, only this time you show more stuff from the kernel.

    I think the problem might be related to DHCP Client, but it doesn't look like you have enabled logging for it. It's disabled by default.
     
  8. FattysGoneWild

    FattysGoneWild LI Guru Member

    You are probably right and it makes sense. Damn it I wish I had enabled that. It would probably show the problem right away since DHCP was not working. I would go back and do it but it is a lot of work. Maybe if some one else sees this thread. They will post up what you need.
     
  9. nvtweak

    nvtweak LI Guru Member

    It could also be the case that the logs will show nothing wrong at all. It has happened to me before.
     
  10. rkloost

    rkloost Addicted to LI Member

    Afaik ND is not for WRT54GL v1.1

    Not mentioned in the readme too.
     
  11. Toastman

    Toastman Super Moderator Staff Member Member

    This post to correct the various comments here - the 54GL always has - and still should be able to use the ND version. [Why should it be used if possible to do so ? To avoid the old problem of the router rebooting when Intel wireless adapters such as the 2200B/G associate.]

    Why these particular problems - time will tell but best wait for Jon's correction later today.
     
  12. FattysGoneWild

    FattysGoneWild LI Guru Member

    The people that have a Linksys WRT54GL v1.1 Are the majority of you having no issue running Tomato 1.25 ND release version?
     
  13. rhester72

    rhester72 Network Guru Member

    I have had no issues with ND on the GL (1.1) since 1.18 or so.

    Rodney
     
  14. LanceMoreland

    LanceMoreland Network Guru Member

    No problems with either release on two WRT54G routers.

    Fattysgonewild,

    Did you check to see if for some reason on the new releases if your option to change the WAN port to a LAN port is checked? That would prevent the router from communicating properly with the modem.
     
  15. FattysGoneWild

    FattysGoneWild LI Guru Member

    I made sure to check that when it was installed. It was set to DHCP. Maybe I should leave my WAN port speed set to auto instead of 100Mb Full? I am at a loss why this ND version does not work for me yet Victek's 1.23 mod ND release works fine for me.

     
  16. FattysGoneWild

    FattysGoneWild LI Guru Member

    That was the problem. Set WAN port speed to auto and it linked up right away. I also seen a major wireless improvement. I am a happy camper now.
     
  17. FattysGoneWild

    FattysGoneWild LI Guru Member

    I was just curious. Any one know why this issue might have happened?
     

Share This Page