There is no preset password in OpenWrt! You need to set a password at your first login per telnet or the WebUI. |
→docs
→ follow 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 'Designated Driver', 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
Install one, e.g. LuCI.
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 accessed with the command
logread
There are three WebUIs available. All are FOSS, thus you can adapt each of them to your specific needs and likings.
→ with opkg
→ with opkg
see also OPKG troubleshooting: Out of space
By removing packages you installed after flashing OpenWrt onto your Router. You cannot remove packages on the SquashFS partition, which is included in the image you flashed.
This happens easily with recent firmware on 4MB Flash devices.
You can press-fit an OpenWrt image into this small flash by building your own image, with only the packages you need, tailored for your usecase.
You can build your own image
Please send reproducible bugs to our ticket system.
You can check yourself:
Possible reasons:
Possible solutions:
You will get the message “Cannot satisfy the following dependencies for...” if you are trying to install packages intended for a trunk build of OpenWrt on a different (older) version, i.e. the package in the trunk repository is for a newer kernel version than the kernel version on your flash.
--force-depends
(=Install/remove despite failed dependencies). Mind that this is likely to fail for kernel related packages (kmods).Root cause: ??? See OpenWrt forum and add the root cause here --- tmomas 2015/12/23 21:10
Solution: ??? See OpenWrt forum and add the solution here --- tmomas 2015/12/23 21:10
This scenario: https://forum.openwrt.org/viewtopic.php?pid=204297#p204297 has three solutions:
see above: Howto connect behind another router?
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.
cat /tmp/dhcp.leases
cp -f /rom/etc/config/firewall /etc/config/firewall /etc/init.d/firewall restart
Something is wrong with your network configuration. Check Netmask, Gateway, DNS settings. → https://wiki.openwrt.org/doc/howto/internet.connection
Like on any Linux system, you can use crond
. Please consult /etc/crontabs/root
Busybox-crond
does not support the @reboot directive. The next best place to put @reboot jobs is /etc/rc.local