Gargoyle Forum

Thanks again for your help...
I have updated the thread at OpenWRT https://dev.openwrt.org/ticket/18680 and added a link back to this one.
Is there anything else I could/should do to attract some attention there? I don't know anything about how that forum works.

Thanks.

Wish I had better news... I replaced the etc/config/network file with the updated code and rebooted... nothing blew up but the behavior did not change from before. For good measure I power cycled everything (modem+router), it came up fine. I rebooted the router and confirmed power cycling the modem ...

As requested... and thanks for your interest and help. config interface 'loopback' option ifname 'lo' option proto 'static' option ipaddr '127.0.0.1' option netmask '255.0.0.0' config globals 'globals' option ula_prefix 'fd3b:39c0:7a1b::/48' config interface 'lan' option ifname 'eth1' option force_l...

The crossover cable didn't fix it either...

It was useable, but didn't change the behavior on reset of router.

Any other thoughts?

Thanks.

As expected I suppose, the move to 1.9 didn't address the issue.

Just for laughs, I'll make a crossover cable and try it out a bit later.

If Chaos40 is running 1.9.0, maybe the supposed 'fix' from OpenWRT site isn't...

Guess I'll upgrade anyway.

OK.

I will upgrade- likely on the weekend as there is a fair amount of manual provisioning I need to do assuming you shouldn't attempt to 'preserve settings'.

Will report back on whether this update resolves the issue.

Thanks.

Hmmmmm... Maybe I jumped to conclusions- the line I added to the root crontab didn't seem to work after I verified the wget did work from a command line; then I saw a note somewhere on OpenWRT that said cron wasn't enabled by default. The specific command I used was '/etc/init.d/cron start' If you'r...

...onto the next problem...

Realized eventually Cron isn't enabled by default on OpenWRT.

When I issue the start commend I get an error message saying 'uninteger - 9 = true'. Any idea why that should happen?

THanks.

I did a little more scouting around the OpenWRT site and found the place to report bugs... While there, I found this: https://dev.openwrt.org/ticket/18680 Seems like the same issue we are having... I rebooted the router and while it was in the 'bad' state I unplugged/replugged the WAN cable- it did ...