Posted: Tue Jan 26, 2010 20:29 Post subject: WRT54G v 1.1 - WAN issues on startup only
I have this WRT54G v1.1, flashed to
DD-WRT v24-sp2 (07/22/09) std
(SVN revision 12548M VINT Eko)
.
Everything works as expected, except for the startup WAN problem.
The problem is as follows:
When the router is being rebooted (hard reboot through powercycle, or soft reboot through telnet or web interface, no matter), it does not respond if it connected to anything at all with its WAN port. Too boot it, I must unplug the wire from WAN, let it boot, and plug it back in. It's a minor inconvinience, but i would really like to resolve it!
dmesg:
Code:
CPU revision is: 00024000
Enabling BCM4710A0 cache workarounds.
Linux version 2.4.35 (eko@dd-wrt) (gcc version 3.4.4 (OpenWrt-2.0)) #3320 Wed Ju
l 22 11:23:50 CEST 2009
Determined physical RAM map:
memory: 01000000 @ 00000000 (usable)
On node 0 totalpages: 4096
zone(0): 4096 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/mtdblock2 rootfstype=squashfs,jffs2 noinitrd cons
ole=ttyS0,115200
CPU: BCM4710 rev 0 at 125 MHz
Using 62.400 MHz high precision timer.
!unable to setup serial console!
Calibrating delay loop... 82.94 BogoMIPS
Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)
Inode cache hash table entries: 1024 (order: 1, 8192 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
Checking for 'wait' instruction... unavailable.
POSIX conformance testing by UNIFIX
PCI: Initializing host
PCI: Fixing up bus 0
PCI: Fixing up bridge
PCI: Setting latency timer of device 01:00.0 to 64
PCI: Fixing up bus 1
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI en
abled
Software Watchdog Timer: 0.05, timer margin: 60 sec
PCI: Setting latency timer of device 00:02.0 to 64
PCI: Setting latency timer of device 00:08.0 to 64
Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky
cfi_cmdset_0001: Erase suspend on write enabled
0: offset=0x0,size=0x2000,blocks=8
1: offset=0x10000,size=0x10000,blocks=63
Using word write method
Flash device: 0x400000 at 0x1fc00000
bootloader size: 262144
Physically mapped flash: Filesystem type: squashfs, size=0x2e4f95
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x003f0000 : "linux"
0x000d8000-0x003c0000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-o
nly
0x003f0000-0x00400000 : "nvram"
0x003c0000-0x003f0000 : "ddwrt"
Initializing Cryptographic API
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 1024 bind 2048)
ip_conntrack version 2.1 (512 buckets, 4096 max) - 336 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
ipt_random match loaded
netfilter PSD loaded - (c) astaro AG
ipt_osf: Startng OS fingerprint matching module.
ipt_IPV4OPTSSTRIP loaded
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (squashfs filesystem) readonly.
Mounted devfs on /dev
Warning: unable to open an initial console.
diag boardtype: 0000041a
PCI: Setting latency timer of device 01:08.0 to 64
PCI: Enabling device 01:08.0 (0004 -> 0006)
eth2: Broadcom BCM4320 802.11 Wireless Controller 4.80.56.0
vlan0: add 01:00:5e:00:00:01 mcast address to master interface
vlan0: del 01:00:5e:00:00:01 mcast address from vlan interface
vlan0: del 01:00:5e:00:00:01 mcast address from master interface
vlan0: add 01:00:5e:00:00:01 mcast address to master interface
vlan0: dev_set_promiscuity(master, 1)
device eth0 entered promiscuous mode
device vlan0 entered promiscuous mode
device eth2 entered promiscuous mode
device vlan1 entered promiscuous mode
vlan1: Setting MAC address to 00 0c 41 a2 3f 40.
vlan1: dev_set_promiscuity(master, 1)
vlan1: dev_set_allmulti(master, 1)
vlan1: dev_set_promiscuity(master, -1)
device vlan1 left promiscuous mode
vlan1: dev_set_allmulti(master, -1)
vlan1: add 01:00:5e:00:00:01 mcast address to master interface
etherip: Ethernet over IPv4 tunneling driver
vlan1: add 01:00:5e:7f:ff:fa mcast address to master interface
vlan1: del 01:00:5e:7f:ff:fa mcast address from master interface
vlan1: add 01:00:5e:7f:ff:fa mcast address to master interface
vlan1: dev_set_allmulti(master, 1)
vlan1: add 01:00:5e:40:98:8f mcast address to master interface
ignore hotplug for prism0 interface
alloc_skb called nonatomically from interrupt 800ea920
ignore hotplug for prism0 interface
alloc_skb called nonatomically from interrupt 800ea920
ipt_tcpmss_target: bad length (232 bytes)
Yes, I did uncheck it! I will try this as soon as I get home, I can't risk rebooting the router remotely. Thanks! I will definitely report back with results.
Interesting, I had a very similar thing happening with my WRT54g v1.1 running v24-13064_VINT_std. It works fine as long as nothing is connected to the WAN port at boot time, but is inaccessible otherwise. Since the same release worked fine with my WRT54gs v1.0 I figured that the 6 year old hardware was just getting flaky on me.
I'm using it as a WAP right now, so I'll have to try to find some time to swap it out and see what happens when I reconfigure it as a router and disable "Filter Multicast".
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Tue Feb 09, 2010 19:04 Post subject:
dusty_wrt54g wrote:
Interesting, I had a very similar thing happening with my WRT54g v1.1 running v24-13064_VINT_std. It works fine as long as nothing is connected to the WAN port at boot time, but is inaccessible otherwise. Since the same release worked fine with my WRT54gs v1.0 I figured that the 6 year old hardware was just getting flaky on me.
I'm using it as a WAP right now, so I'll have to try to find some time to swap it out and see what happens when I reconfigure it as a router and disable "Filter Multicast".
Just to be clear here...you want the "Filter Multicast" checked on the Security>>Firewall tab.
It IS by default after a hard reset.
redhawk _________________ The only stupid question....is the unasked one.
I tried checking "filter multicast".
Didn't do anything at all.
The router did not boot with WAN plugged in. Take WAN out, reboot - the router is back up.
Unfortunately, this is the best router I have - my 'production' router. If i keep messing with it reinstalling firmware, etc. - is there a way to save all the settings that I set up (WDS, couple of MAC filters, forwarded ports, the like); possibly, a script?
Here is the dmesg with "filter multicast" enabled (and WAN plugged after the router is booted up):
Code:
root@keep-out:~# dmesg
CPU revision is: 00024000
Enabling BCM4710A0 cache workarounds.
Linux version 2.4.35 (eko@dd-wrt) (gcc version 3.4.4 (OpenWrt-2.0)) #3320 Wed Ju
l 22 11:23:50 CEST 2009
Determined physical RAM map:
memory: 01000000 @ 00000000 (usable)
On node 0 totalpages: 4096
zone(0): 4096 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/mtdblock2 rootfstype=squashfs,jffs2 noinitrd cons
ole=ttyS0,115200
CPU: BCM4710 rev 0 at 125 MHz
Using 62.400 MHz high precision timer.
!unable to setup serial console!
Calibrating delay loop... 82.94 BogoMIPS
Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)
Inode cache hash table entries: 1024 (order: 1, 8192 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
Checking for 'wait' instruction... unavailable.
POSIX conformance testing by UNIFIX
PCI: Initializing host
PCI: Fixing up bus 0
PCI: Fixing up bridge
PCI: Setting latency timer of device 01:00.0 to 64
PCI: Fixing up bus 1
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI en
abled
Software Watchdog Timer: 0.05, timer margin: 60 sec
PCI: Setting latency timer of device 00:02.0 to 64
PCI: Setting latency timer of device 00:08.0 to 64
Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky
cfi_cmdset_0001: Erase suspend on write enabled
0: offset=0x0,size=0x2000,blocks=8
1: offset=0x10000,size=0x10000,blocks=63
Using word write method
Flash device: 0x400000 at 0x1fc00000
bootloader size: 262144
Physically mapped flash: Filesystem type: squashfs, size=0x2e4f95
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x003f0000 : "linux"
0x000d8000-0x003c0000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-o
nly
0x003f0000-0x00400000 : "nvram"
0x003c0000-0x003f0000 : "ddwrt"
Initializing Cryptographic API
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 1024 bind 2048)
ip_conntrack version 2.1 (512 buckets, 4096 max) - 336 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
ipt_random match loaded
netfilter PSD loaded - (c) astaro AG
ipt_osf: Startng OS fingerprint matching module.
ipt_IPV4OPTSSTRIP loaded
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (squashfs filesystem) readonly.
Mounted devfs on /dev
Warning: unable to open an initial console.
diag boardtype: 0000041a
PCI: Setting latency timer of device 01:08.0 to 64
PCI: Enabling device 01:08.0 (0004 -> 0006)
eth2: Broadcom BCM4320 802.11 Wireless Controller 4.80.56.0
vlan0: add 01:00:5e:00:00:01 mcast address to master interface
vlan0: del 01:00:5e:00:00:01 mcast address from vlan interface
vlan0: del 01:00:5e:00:00:01 mcast address from master interface
vlan0: add 01:00:5e:00:00:01 mcast address to master interface
vlan0: dev_set_promiscuity(master, 1)
device eth0 entered promiscuous mode
device vlan0 entered promiscuous mode
device eth2 entered promiscuous mode
device wds0.1 entered promiscuous mode
device vlan1 entered promiscuous mode
vlan1: Setting MAC address to 00 0c 41 a2 3f 40.
vlan1: dev_set_promiscuity(master, 1)
vlan1: dev_set_allmulti(master, 1)
vlan1: dev_set_promiscuity(master, -1)
device vlan1 left promiscuous mode
vlan1: dev_set_allmulti(master, -1)
vlan1: add 01:00:5e:00:00:01 mcast address to master interface
etherip: Ethernet over IPv4 tunneling driver
vlan1: add 01:00:5e:7f:ff:fa mcast address to master interface
vlan1: del 01:00:5e:7f:ff:fa mcast address from master interface
vlan1: add 01:00:5e:7f:ff:fa mcast address to master interface
Last edited by catzilla on Wed Feb 10, 2010 0:34; edited 1 time in total
Just for the heck of it, I flashed VINT_13491_mini like redhawk0 (hard reset before & after) and my dmesg output was a little different (looks due to my changing WAN MAC address for Comcast):
I still have everything lock up when it boots with my cable modem attached to the WAN port and it becomes accessible once I remove the cable. It worked fine using another router as a DHCP server through. I tried a few different cables and rebooted my cable modem and it still froze up my WRT54G 1.1 where my WRT54GS 1.0 running the same firmware worked fine.
Just for grins, I put Sveasoft Alchemy on there and the same thing happened. I think this is just bad hardware. I haven't used the WAN port in such a long time that it could have been that way for a couple of years for all I know.
It's nice pushing it all on hardware. However, the router worked fine with stock firmware. How would you explain this? Of course, I'll live with it until I am able to afford (I am a poor college student) a WRT54G-TM, but this issue just bugs me.
It's nice pushing it all on hardware. However, the router worked fine with stock firmware. How would you explain this? Of course, I'll live with it until I am able to afford (I am a poor college student) a WRT54G-TM, but this issue just bugs me.
I haven't tried the stock firmware on mine, so I suppose that's another option. If you revert back with yours does your WAN port work properly again? If so, I might just give that a shot.
I'd really like this to work since I'd like to put it into place at my parents house, but I've had the thing for almost 6 years now and a hardware issue doesn't seem out of the question.
To be truthful, I did not push factory FW on the router since I put dd-wrt on it.
I suppose dd-wrt might have broken something in it hardware-wise - why not?
I cannot try, unfortunately, because, as I said, it's my 'production' router. Until I get another one, I cannot experiment with this one.
To be truthful, I did not push factory FW on the router since I put dd-wrt on it.
I suppose dd-wrt might have broken something in it hardware-wise - why not?
I cannot try, unfortunately, because, as I said, it's my 'production' router. Until I get another one, I cannot experiment with this one.
I tried the stock Linksys firmware version 4.21.1 linked to in the wiki and it does work properly. I can reboot with the WAN cable plugged in with no problem as expected. Maybe this isn't a hardware problem after all!!!
I then flashed back to dd-wrt.v24_mini_generic.bin and my router would hang when booted with the WAN connection plugged in to my Comcast cable modem.
I unplugged the WAN cable, enabled syslogd, and rebooted again with the WAN cable plugged back in. After it was hung, I unplugged the WAN cable and grabbed the following /var/log/messages file:
Code:
Jan 1 00:00:05 DD-WRT syslog.info syslogd started: BusyBox v1.13.4
Jan 1 00:00:05 DD-WRT user.notice kernel: klogd started: BusyBox v1.13.4 (2009-10-10 01:26:36 CEST)
Jan 1 00:00:05 DD-WRT user.emerg kernel: CPU ProcId is: 0x00024000, options: 0x0000004d
Jan 1 00:00:05 DD-WRT user.emerg kernel: Enabling BCM4710A0 cache workarounds.
Jan 1 00:00:05 DD-WRT user.emerg kernel: Linux version 2.4.37 (root@dd-wrt) (gcc version 3.4.6 (OpenWrt-2.0)) #7581 Sat Oct 10 01:29:13 CEST 2009
Jan 1 00:00:05 DD-WRT user.emerg kernel: Determined physical RAM map:
Jan 1 00:00:05 DD-WRT user.emerg kernel: memory: 01000000 @ 00000000 (usable)
Jan 1 00:00:05 DD-WRT user.emerg kernel: On node 0 totalpages: 4096
Jan 1 00:00:05 DD-WRT user.emerg kernel: zone(0): 4096 pages.
Jan 1 00:00:05 DD-WRT user.emerg kernel: zone(1): 0 pages.
Jan 1 00:00:05 DD-WRT user.emerg kernel: zone(2): 0 pages.
Jan 1 00:00:05 DD-WRT user.emerg kernel: Kernel command line: root=/dev/mtdblock2 rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200
Jan 1 00:00:05 DD-WRT user.emerg kernel: CPU: BCM4710 rev 0 at 125 MHz
Jan 1 00:00:05 DD-WRT user.emerg kernel: Using 62.400 MHz high precision timer.
Jan 1 00:00:05 DD-WRT user.emerg kernel: !unable to setup serial console!
Jan 1 00:00:05 DD-WRT user.emerg kernel: Calibrating delay loop... 82.94 BogoMIPS
Jan 1 00:00:05 DD-WRT user.info kernel: Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)
Jan 1 00:00:05 DD-WRT user.info kernel: Inode cache hash table entries: 1024 (order: 1, 8192 bytes)
Jan 1 00:00:05 DD-WRT user.info kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Jan 1 00:00:05 DD-WRT user.info syslog: klogd : klog daemon successfully started
Jan 1 00:00:05 DD-WRT user.info kernel: Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 00:00:05 DD-WRT user.emerg kernel: Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
Jan 1 00:00:05 DD-WRT user.emerg kernel: Checking for 'wait' instruction... unavailable.
Jan 1 00:00:05 DD-WRT user.emerg kernel: POSIX conformance testing by UNIFIX
Jan 1 00:00:05 DD-WRT user.emerg kernel: PCI: Initializing host
Jan 1 00:00:05 DD-WRT user.emerg kernel: PCI: Fixing up bus 0
Jan 1 00:00:05 DD-WRT user.emerg kernel: PCI: Fixing up bridge
Jan 1 00:00:05 DD-WRT user.debug kernel: PCI: Setting latency timer of device 01:00.0 to 64
Jan 1 00:00:05 DD-WRT user.emerg kernel: PCI: Fixing up bus 1
Jan 1 00:00:05 DD-WRT user.emerg kernel: Initializing RT netlink socket
Jan 1 00:00:05 DD-WRT user.emerg kernel: Starting kswapd
Jan 1 00:00:05 DD-WRT user.info kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
Jan 1 00:00:05 DD-WRT user.info kernel: devfs: boot_options: 0x1
Jan 1 00:00:05 DD-WRT user.info kernel: squashfs: version 3.0 (2006/03/15) Phillip Lougher
Jan 1 00:00:05 DD-WRT user.emerg kernel: pty: 256 Unix98 ptys configured
Jan 1 00:00:05 DD-WRT user.info kernel: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
Jan 1 00:00:05 DD-WRT user.debug kernel: PCI: Setting latency timer of device 00:02.0 to 64
Jan 1 00:00:05 DD-WRT user.debug kernel: PCI: Setting latency timer of device 00:08.0 to 64
Jan 1 00:00:05 DD-WRT user.debug kernel: PCI: Setting latency timer of device 01:08.0 to 64
Jan 1 00:00:05 DD-WRT user.emerg kernel: PCI: Enabling device 01:08.0 (0004 -> 0006)
Jan 1 00:00:05 DD-WRT user.info kernel: PPPoL2TP kernel driver, V0.13
Jan 1 00:00:05 DD-WRT user.info kernel: Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky
Jan 1 00:00:05 DD-WRT user.notice kernel: Amd/Fujitsu Extended Query Table v1.1 at 0x0040
Jan 1 00:00:05 DD-WRT user.warn kernel: Physically mapped flash: Swapping erase regions for broken CFI table.
Jan 1 00:00:05 DD-WRT user.notice kernel: number of CFI chips: 1
Jan 1 00:00:05 DD-WRT user.notice kernel: cfi_cmdset_0002: Disabling fast programming due to code brokenness.
Jan 1 00:00:05 DD-WRT user.emerg kernel: Flash device: 0x400000 at 0x1fc00000
Jan 1 00:00:05 DD-WRT user.emerg kernel: bootloader size: 262144
Jan 1 00:00:05 DD-WRT user.emerg kernel: Physically mapped flash: Filesystem type: squashfs, size=0x20cd23
Jan 1 00:00:05 DD-WRT user.emerg kernel: partition size = 2208768
Jan 1 00:00:05 DD-WRT user.notice kernel: Creating 5 MTD partitions on "Physically mapped flash":
Jan 1 00:00:05 DD-WRT user.notice kernel: 0x00000000-0x00040000 : "cfe"
Jan 1 00:00:05 DD-WRT user.notice kernel: 0x00040000-0x003f0000 : "linux"
Jan 1 00:00:05 DD-WRT user.notice kernel: 0x00124c00-0x00340000 : "rootfs"
Jan 1 00:00:05 DD-WRT user.emerg kernel: mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
Jan 1 00:00:05 DD-WRT user.notice kernel: 0x003f0000-0x00400000 : "nvram"
Jan 1 00:00:05 DD-WRT user.notice kernel: 0x00340000-0x003f0000 : "ddwrt"
Jan 1 00:00:06 DD-WRT user.err kernel: sflash not supported on this router
Jan 1 00:00:06 DD-WRT user.info kernel: Initializing Cryptographic API
Jan 1 00:00:06 DD-WRT user.info kernel: IP Protocols: ICMP, UDP, TCP, IGMP
Jan 1 00:00:06 DD-WRT user.info kernel: IP: routing cache hash table of 512 buckets, 4Kbytes
Jan 1 00:00:06 DD-WRT user.info kernel: TCP: Hash tables configured (established 1024 bind 2048)
Jan 1 00:00:06 DD-WRT user.emerg kernel: ip_conntrack version 2.1 (512 buckets, 4096 max) - 336 bytes per conntrack
Jan 1 00:00:06 DD-WRT user.emerg kernel: ip_tables: (C) 2000-2002 Netfilter core team
Jan 1 00:00:06 DD-WRT user.emerg kernel: ipt_random match loaded
Jan 1 00:00:06 DD-WRT user.emerg kernel: netfilter PSD loaded - (c) astaro AG
Jan 1 00:00:06 DD-WRT user.info kernel: ipt_osf: Startng OS fingerprint matching module.
Jan 1 00:00:06 DD-WRT user.emerg kernel: ipt_IPV4OPTSSTRIP loaded
Jan 1 00:00:06 DD-WRT user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Jan 1 00:00:06 DD-WRT user.info kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
Jan 1 00:00:06 DD-WRT user.info kernel: All bugs added by David S. Miller <davem@redhat.com>
Jan 1 00:00:06 DD-WRT user.emerg kernel: VFS: Mounted root (squashfs filesystem) readonly.
Jan 1 00:00:06 DD-WRT user.info kernel: Mounted devfs on /dev
Jan 1 00:00:06 DD-WRT user.emerg kernel: Warning: unable to open an initial console.
Jan 1 00:00:06 DD-WRT user.info kernel: diag boardtype: 0000041a
Jan 1 00:00:06 DD-WRT user.debug kernel: vlan0: add 01:00:5e:00:00:01 mcast address to master interface
Jan 1 00:00:06 DD-WRT user.debug kernel: vlan0: del 01:00:5e:00:00:01 mcast address from vlan interface
Jan 1 00:00:06 DD-WRT user.debug kernel: vlan0: del 01:00:5e:00:00:01 mcast address from master interface
Jan 1 00:00:06 DD-WRT user.debug kernel: vlan0: add 01:00:5e:00:00:01 mcast address to master interface
Jan 1 00:00:06 DD-WRT user.debug kernel: vlan0: del 01:00:5e:00:00:01 mcast address from vlan interface
Jan 1 00:00:06 DD-WRT user.debug kernel: vlan0: del 01:00:5e:00:00:01 mcast address from master interface
Jan 1 00:00:06 DD-WRT user.debug kernel: vlan0: add 01:00:5e:00:00:01 mcast address to master interface
Jan 1 00:00:06 DD-WRT user.info kernel: vlan0: dev_set_promiscuity(master, 1)
Jan 1 00:00:06 DD-WRT user.info kernel: device eth0 entered promiscuous mode
Jan 1 00:00:06 DD-WRT user.info syslog: wland : WLAN daemon successfully started
Jan 1 00:00:06 DD-WRT user.info kernel: device vlan0 entered promiscuous mode
Jan 1 00:00:06 DD-WRT user.info kernel: device eth2 entered promiscuous mode
Jan 1 00:00:08 DD-WRT user.info kernel: device vlan1 entered promiscuous mode
Jan 1 00:00:08 DD-WRT user.info syslog: dnsmasq : dnsmasq daemon successfully started
Jan 1 00:00:08 DD-WRT user.emerg kernel: vlan1: Setting MAC address to 00 b0 d0 3e 52 1f.
Jan 1 00:00:08 DD-WRT user.info kernel: vlan1: dev_set_promiscuity(master, 1)
Jan 1 00:00:08 DD-WRT user.info kernel: vlan1: dev_set_allmulti(master, 1)
Jan 1 00:00:08 DD-WRT user.info kernel: vlan1: dev_set_promiscuity(master, -1)
Jan 1 00:00:08 DD-WRT user.info kernel: device vlan1 left promiscuous mode
Jan 1 00:00:08 DD-WRT user.info kernel: vlan1: dev_set_allmulti(master, -1)
Jan 1 00:00:08 DD-WRT user.info syslog: cron : cron daemon successfully started
Jan 1 00:00:09 DD-WRT cron.info cron[181]: (CRON) STARTUP (fork ok)
Jan 1 00:00:09 DD-WRT cron.info cron[181]: (crontabs) ORPHAN (no passwd entry)
Jan 1 00:00:09 DD-WRT user.info syslog: ttraff : traffic counter daemon successfully started
Jan 1 00:00:11 DD-WRT user.debug kernel: vlan1: add 01:00:5e:00:00:01 mcast address to master interface
Jan 1 00:00:11 DD-WRT user.info syslog: dropbear : ssh daemon successfully started
Jan 1 00:00:11 DD-WRT authpriv.info dropbear[216]: Running in background
Jan 1 00:00:11 DD-WRT user.info syslog: klogd : klog daemon successfully stopped
Jan 1 00:00:11 DD-WRT user.info syslog: syslogd : syslog daemon successfully stopped
Jan 1 00:00:13 DD-WRT syslog.info syslogd started: BusyBox v1.13.4
Jan 1 00:00:13 DD-WRT user.notice kernel: klogd started: BusyBox v1.13.4 (2009-10-10 01:26:36 CEST)
Jan 1 00:00:14 DD-WRT user.info kernel: etherip: Ethernet over IPv4 tunneling driver
Jan 1 00:00:15 DD-WRT user.info syslog: vpn modules : vpn modules successfully unloaded
Jan 1 00:00:15 DD-WRT user.info syslog: vpn modules : ip_conntrack_proto_gre successfully loaded
Jan 1 00:00:16 DD-WRT user.info syslog: vpn modules : ip_nat_proto_gre successfully loaded
Jan 1 00:00:16 DD-WRT user.emerg kernel: ip_conntrack_pptp version 1.9 loaded
Jan 1 00:00:16 DD-WRT user.info syslog: vpn modules : ip_conntrack_pptp successfully loaded
Jan 1 00:00:16 DD-WRT user.emerg kernel: ip_nat_pptp version 1.5 loaded
Jan 1 00:00:16 DD-WRT user.info syslog: vpn modules : ip_nat_pptp successfully loaded
Then I plugged the WAN cable back in and rebooted, resulting in these additional entries to /var/log/messages:
Code:
115a116,161
> Jan 1 00:01:03 DD-WRT authpriv.info dropbear[414]: exit after auth (root): Exited normally
> Jan 1 00:02:00 DD-WRT user.info syslog: process_monitor successfully started
> Jan 1 00:02:01 DD-WRT daemon.err process_monitor[470]: Last update failed, we need to re-update after 30 seconds
> Jan 1 00:02:01 DD-WRT daemon.debug process_monitor[470]: We need to re-update after 3600 seconds
> Jan 1 00:02:27 DD-WRT user.emerg kernel: ip_nat_pptp version 1.5 unloaded
> Jan 1 00:02:27 DD-WRT user.emerg kernel: ip_conntrack_pptp version 1.9 unloaded
> Jan 1 00:02:27 DD-WRT user.info syslog: vpn modules : vpn modules successfully unloaded
> Jan 1 00:02:27 DD-WRT user.info syslog: vpn modules : ip_conntrack_proto_gre successfully loaded
> Jan 1 00:02:27 DD-WRT user.info syslog: vpn modules : ip_nat_proto_gre successfully loaded
> Jan 1 00:02:27 DD-WRT user.emerg kernel: ip_conntrack_pptp version 1.9 loaded
> Jan 1 00:02:27 DD-WRT user.info syslog: vpn modules : ip_conntrack_pptp successfully loaded
> Jan 1 00:02:27 DD-WRT user.emerg kernel: ip_nat_pptp version 1.5 loaded
> Jan 1 00:02:27 DD-WRT user.info syslog: vpn modules : ip_nat_pptp successfully loaded
> Jan 1 00:02:27 DD-WRT user.info syslog: process_monitor successfully stopped
> Jan 1 00:02:28 DD-WRT user.info syslog: process_monitor successfully started
> Feb 10 09:30:08 DD-WRT user.info syslog: cron : cron daemon successfully stopped
> Feb 10 09:30:09 DD-WRT daemon.debug process_monitor[560]: Restarting cron
> Feb 10 09:30:09 DD-WRT daemon.debug process_monitor[560]: We need to re-update after 3600 seconds
> Feb 10 09:30:09 DD-WRT cron.info cron[603]: (CRON) STARTUP (fork ok)
> Feb 10 09:30:09 DD-WRT user.info syslog: cron : cron daemon successfully started
> Feb 10 09:30:09 DD-WRT cron.info cron[603]: (crontabs) ORPHAN (no passwd entry)
> Feb 10 09:30:15 DD-WRT user.emerg kernel: ip_nat_pptp version 1.5 unloaded
> Feb 10 09:30:15 DD-WRT user.emerg kernel: ip_conntrack_pptp version 1.9 unloaded
> Feb 10 09:30:15 DD-WRT user.info syslog: vpn modules : vpn modules successfully unloaded
> Feb 10 09:30:15 DD-WRT user.info syslog: vpn modules : ip_conntrack_proto_gre successfully loaded
> Feb 10 09:30:16 DD-WRT user.info syslog: vpn modules : ip_nat_proto_gre successfully loaded
> Feb 10 09:30:16 DD-WRT user.emerg kernel: ip_conntrack_pptp version 1.9 loaded
> Feb 10 09:30:16 DD-WRT user.info syslog: vpn modules : ip_conntrack_pptp successfully loaded
> Feb 10 09:30:16 DD-WRT user.emerg kernel: ip_nat_pptp version 1.5 loaded
> Feb 10 09:30:16 DD-WRT user.info syslog: vpn modules : ip_nat_pptp successfully loaded
> Feb 10 09:30:17 DD-WRT user.info syslog: wland : WLAN daemon successfully stopped
> Feb 10 09:30:18 DD-WRT user.debug syslog: ttraff: data collection started
> Feb 10 09:30:20 DD-WRT user.emerg kernel: ip_nat_pptp version 1.5 unloaded
> Feb 10 09:30:20 DD-WRT user.emerg kernel: ip_conntrack_pptp version 1.9 unloaded
> Feb 10 09:30:20 DD-WRT user.info syslog: vpn modules : vpn modules successfully unloaded
> Feb 10 09:30:20 DD-WRT user.info syslog: vpn modules : ip_conntrack_proto_gre successfully loaded
> Feb 10 09:30:20 DD-WRT user.info syslog: vpn modules : ip_nat_proto_gre successfully loaded
> Feb 10 09:30:20 DD-WRT user.emerg kernel: ip_conntrack_pptp version 1.9 loaded
> Feb 10 09:30:20 DD-WRT user.info syslog: vpn modules : ip_conntrack_pptp successfully loaded
> Feb 10 09:30:20 DD-WRT user.emerg kernel: ip_nat_pptp version 1.5 loaded
> Feb 10 09:30:20 DD-WRT user.info syslog: vpn modules : ip_nat_pptp successfully loaded
> Feb 10 09:30:22 DD-WRT user.info syslog: wland : WLAN daemon successfully started
> Feb 10 09:30:22 DD-WRT user.info syslog: WAN is up. IP: X.X.X.X
I've pulled my WRT54G v1.1 out of my environment and am willing to test whatever anyone more knowledgeable about issues like this can suggest. This hangs only with my Comcast cable modem, which uses a DHCP connection and requires a cloned MAC address and works fine when I use another router as a DHCP server or when I plug cable modem into the WAN port after the WRT54G has already booted. I've tried using multiple cables (which work fine with my WRT54GS running the same DD-WRT firmware) and rebooting my cable modem with no success.
My WRT45G still has dd-wrt.v24_mini_generic.bin on it, but I have also seen this issue with dd-wrt.v24-13064_VINT_std.bin, dd-wrt.v24-13064_VINT_openvpn.bin, dd-wrt.v24-13491_VINT_mini.bin, and Sveasoft Alchemy 1.0. I'm hoping to use this at my parents house this weekend, so I will most likely flash it back to Linksys stock firmware later this week since I know that works.
