OpenWrt 安装后常见问题解答

→ 详见walkthrough_login

As you can see here development, there are always two branches which are being actively worked on. OpenWrt trunk, which is bleeding edge, codename 'Attitude Adjustment', and the current stable release. Do

cat /etc/banner

to see the exact revision. Use that information for bug reports and questions in the forum. Also use it, to look up information yourself: https://dev.openwrt.org/browser

→ generic.debrick

安装一个，比如 LuCI露西。

→ user.beginner.cli

→generic.overview

→详见failsafe_and_factory_reset

这里有第三方的Web管理界面WebUIs available. All are FOSS, thus you can adapt each of them to your specific needs and likings.

→ 用opkg来安装的 opkg, but please read about flash.layout

→ 见这里 opkg, but please read about flash.layout

通过卸载一些已安装的软件来达到目的。 after flashing OpenWrt onto your Router. You cannot remove packages on the SquashFS partition!

诚请您将bugs发送给 ticket system团队。TKS！

You can check yourself. The OpenWrt repositories are brows-able by web browser. E.g.

• stable • ar71xx
• trunk • lantiq
• etc.

Possible reasons:

• it makes no sense to have this software in the repositories, because it is too bloated/not suited for embedded environments
• nobody has thought on packaging this software for OpenWrt yet

Possible solutions:

• create the package yourself: Creating a package
• do nothing and wait until package becomes available

That be because the firewall-package comes with a configuration already. Certain user chains are created, and packets put into them. When you then later try to catch packets in the INPUT chain, there won't be any, because they are being put into user chains (maybe something like wan_input, lan_input) before that.

Anytime you can type

iptables -L 

to see how things are currently setup, but best thing is, to always know your own setup.

E.g. so:

cat /tmp/dhcp.leases

Like on any Linux system, you can use crond. Please consult /etc/crontabs/root

Unless you installed some other log daemons OpenWrt uses by default busybox-klogd and busybox-syslogd for logging. Both use the same circular buffer, which can be from to in size. Default is . Access with command

logread