Shibby - Random Reboots with 099

Anybody else experiencing this?

Not since I first flashed the firmware. I'm at 23 hours uptime. I'm running the VPN build on my E3000. Not running anything special, just one virtual wireless network setup.

2 days, 1 hour uptime. The last time I rebooted the router was when I flashed 099. No random reboots. Running RT-N AIO 64K build.

Hmmm, okay. Thanks.

GhaladReam, do you use Access Restrictions?

No Access Restrictions, and I don't use dnscrypt-proxy, but I do use 2 DDNS services, dyndns and opendns. No issues so far.

The last entry in its log (SD card) before reboots is an activation of Access Restrictions rule, so I think that's causing reboots.

Uptime
3 days, 08:15:07

Running fine here for 1 day, 09:03:36 since flash. Didn't even need to power down Nice build Shibby. Thanks

Ok, thanks.

I was running 99 on an e4200 (CTF enabled) and I lost internet connection in less than 1 day and couldn't access the router GUI. Had to power down and power up. Reflashed toastman's 497.1 and all is well.

Uptime now 5 days, 1 hour. No issues.

With CTF enabled?

No.

Version 100 also reboots randomly.

no way.
Uptime
1 day, 02:14:15

did you make nvram clean? Did you try install OFW and check? Maybe you have a hardware problem.

It was fine with 097, though.

I'm trying it (100) out with Access Restrictions turned off. I'll clear nvram next.

Thanks.

Do you have any firewall scripts running ? If then try to remove all of them and reboot and se if that solves your problem.

I've one iptable statement in there. Will try.

Thanks.

OT question for shibby, When I set nvram clkfreq to 532,266,133 commit and reboot, it still shows the CPU freq as 480 Mhz in the GUI, specifically Status: Overview. Why isn't there a GUI option to set clkfreq like other firmwares such as Toastman's?

Update: I fixed the 480 Mhz bug. I set the clkfreq to 533 instead of 532 and that caused the GUI to report the CPU clock as 480 Mhz. It now displays 532 Mhz in the GUI.

This. If after NVRAM wipe and/or OFW does the same thing, then you most certainly have a hardware problem. Otherwise, there is something in your configuration that's not working properly...

Looks like I'm not the only one... http://www.linksysinfo.org/index.php?posts/187193/

Hi, I am the other person with random reboots and it seems that both of us are running a firewall script. Here is my script keep in mind all of this worked fine on 87 for months without reboot (also it works fine for awhile before the reboot, sometimes a few minutes sometimes a few hours) Maybe you can spot something that you think would force the router to reboot.

echo 1 > /proc/sys/net/ipv6/conf/all/forwarding
echo 0 > /proc/sys/net/ipv6/conf/all/disable_ipv6
echo 0 > /proc/sys/net/ipv6/conf/default/disable_ipv6
echo 1 > /proc/sys/net/ipv6/conf/default/forwarding
modprobe sit
insmod nf_conntrack_ipv6
sleep 5
HOST6RD=$(nslookup 6rd.charter.com |grep "Address"|awk '{ print $3 }'|grep -v 127.0.0.1 -m1)
WANIP=$(ip -4 addr show dev vlan2 | grep 'inet ' | awk '{print $2}' | cut -d/ -f1)
if [ -n "$WANIP" ]
then
V6PREFIX=$(printf ' 2602:100:%02x%02x:%02x%02x' $(echo $WANIP | tr . ' '))
ip tunnel add tun6rd mode sit ttl 255 remote any local $WANIP
ip link set tun6rd mtu 1280
ip link set tun6rd up
echo 0 > /proc/sys/net/ipv6/conf/tun6rd/disable_ipv6
echo 1 > /proc/sys/net/ipv6/conf/tun6rd/forwarding
ip addr add $V6PREFIX:0::1/32 dev tun6rd
ip addr add $V6PREFIX:1::1/64 dev br0
ip -6 route add 2000::/3 via ::$HOST6RD dev tun6rd
fi
echo "interface br0 { \
MinRtrAdvInterval 3; MaxRtrAdvInterval 10; AdvLinkMTU 1280; AdvSendAdvert on; \
prefix $V6PREFIX::/64 { AdvOnLink on; AdvAutonomous on; AdvValidLifetime 86400; \
AdvPreferredLifetime 86400; }; \
RDNSS 2607:f428:1::5353:1 2607:f428:2::5353:1 { }; };" \
> /tmp/home/root/radvd.conf
radvd -C /tmp/home/root/radvd.conf start
ip6tables -F
ip6tables -P INPUT DROP
ip6tables -P FORWARD DROP
ip6tables -P OUTPUT DROP
ip6tables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
ip6tables -A INPUT -p ipv6-icmp -j ACCEPT
ip6tables -I FORWARD -p ipv6-icmp -j ACCEPT
ip6tables -A FORWARD -i br0 -j ACCEPT
ip6tables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
ip6tables -I OUTPUT -p ipv6-icmp -j ACCEPT
ip6tables -A OUTPUT -j ACCEPT
ip6tables -A OUTPUT -o lo -j ACCEPT

(Cyberian75 sorry to hijack thread but this seems a good place for it)

I only have...

Sorry, I'm not good with Linux. I'd suggest you to follow experts' advices above.

I think there's a memory leak somewhere. Once I start downloading torrents, memory keeps falling which eventually leads to reboots. This -- at least random reboots -- didn't happen in 097, and it was worse in 099.

it happened to my e4200 rather frequently when I turned on the bandwidth limiter...had to turn it off...both Shibby and Toastman builds have the same problem

I'm not using that. It happens once I start µTorrent, not downloading anything.

Free memory plummets when I watch YouTube videos, eventually causing reboots. I think I'll downgrade to 097.

FYI, it's not happening in 097 with the same exact settings.