Hi there, I use a TP-Link TL-WR1043ND with backfire. I tried to use a 4GB USB stick to create a persistent /var partition. This is needed for a few services that I want to run. After a bit of futzing around, I found this post[1] which enables OpenWRT to run at least, after retargeting the /tmp symlink to point to the mounted USB disk.
However, when using this, although the router comes up and I can connect to the wifi successfully, it does not perform any routing as such. I viewed iptables rules with 'iptables -L' and there were no rules present. I have found I can fix this by running '/etc/init.d/network restart' and '/etc/init.d/firewall restart'. However, I would like to have my router be bootable without having to do this every time. Does anyone know how to do this? I have looked around a bit in the logs using logread. The main problem seems to be this: Nov 27 14:04:09 kakkerlak daemon.err pppd[835]: Fatal signal 11 Nov 27 14:04:09 kakkerlak daemon.err pppd[835]: ioctl (SIOCGIFFLAGS): Bad file descriptor (line 2367) Nov 27 14:04:09 kakkerlak daemon.err pppd[835]: default route ioctl(SIOCDELRT): Bad file descriptor Nov 27 14:04:09 kakkerlak daemon.info pppd[835]: Exit. This seems to break the network connection in an obscure way. The router itself still has internet access, though. I'm not really sure what's causing this. Chronologically, this is after the filesystem has been mounted under /mnt/usb (as confirmed in the log). I get an error when I restart the network, but it succeeds anyway: root@kakkerlak:~# /etc/init.d/network restart command failed: No such device (-19) Configuration file: /var/run/hostapd-phy0.conf Using interface wlan0 with hwaddr 90:f6:52:20:35:2a and ssid 'over9000' With regard to the firewall, I think this is the cause: Nov 27 14:04:13 kakkerlak user.info sysinit: firewall already loaded I think this is because using the 'reboot' command doesn't properly clean out the firewall state, so the /var/state/firewall file still contains some lines that make 'uci' think that it's loaded. Not sure what the correct fix for this would be. AFAIK, simply hard-powering the router off is a valid shutdown method, so there would be no way to clean it out on reboot, although '/etc/init.d/firewall stop' does successfully clean the state. Full logs available on request. [1] http://www2.kaufmanfamily.net:8080/blog/2009/08/persistent-var-for-openwrt Cheers, Dave _______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-users
