4/32 are OK. I use it with MR-3040. The image is smaller than 17.01, because LTO is used on some packages.
Issue can be logged in https://bugs.openwrt.org/ ; please provide the used dhcp and network config
I have also an WR1043ND v1 in use.
Usually I have an extroot (+swap) configuration, and there is everything working.
Because of your post I disabled extroot/swap, and I was still able to load opkg softlist and to install packages.
Only, in this configuration I have no luci installed.
Memory after installing some packages:
root@sickbox:~# free total used free shared buffers cached Mem: 27832 19868 7964 668 2020 5000 -/+ buffers/cache: 12848 14984 Swap: 0 0 0
@Azmuth i have luci installed, no extroot or swap or anything weird other than stock lede install
Thanks for the hints! I was reluctant to upgrade the 15.05.01 running TL-WR741ND v4 directly
to 18.06.0, but followed your advice and used LEDE as an intermediary step. Not sure if it's really needed, might work to directly flash 18.06.0 on it .
Success: TP-Link TL-WR741ND v4
- TP-Link TL-WR741ND v4 running openwrt-15.05.1-ar71xx-generic-tl-wr741nd-v4-squashfs-factory.bin (280 KB free space)
- removed the packages libpcap & tcpdump-mini (that I installed) and kept the configuration including a firewall custom script (a few pages of rules)
- LuCI unable to upgrade directly to openwrt-18.06.0-ar71xx-tiny-tl-wr741nd-v4-squashfs-sysupgrade.bin
- LuCI - upgrade to lede-17.01.5-ar71xx-generic-tl-wr741nd-v4-squashfs-sysupgrade.bin (280 KB free space)
- LuCI - upgrade to openwrt-18.06.0-ar71xx-tiny-tl-wr741nd-v4-squashfs-sysupgrade.bin (88 KB free space)
- everything's dandy! Lost the ability to install the very useful tcpdump, running stable and no apparent speed drop on pppoE - 96-98 Mbps on http://www.speedtest.net/
Failure: D-Link DIR-300B1
- D-Link DIR-300B1 running openwrt-15.05.1-ramips-rt305x-dir-300-b1-squashfs-factory.bin (260 KB free space), already "castrated", speed on pppoE won't reach over 30-40Mbps
- removed libpcap & tcpdump-mini and kept the configuration including a firewall custom script (a few pages of rules)
- LuCI unable to upgrade directly to openwrt-18.06.0-ramips-rt305x-dir-300-b1-squashfs-sysupgrade.bin
- LuCI - upgrade to lede-17.01.5-ramips-rt305x-dir-300-b1-squashfs-sysupgrade.bin (280 KB free space), still "castrated" pppoE won't reach over 30-40Mbps
- LuCI - upgrade to openwrt-18.06.0-ramips-rt305x-dir-300-b1-squashfs-sysupgrade.bin - lost configuration, unable to save anything, Free space: 100% (13.70 MB)
- D-Link DIR-300B1 entering flash recovery mode (reset button pressed - interface at 192.168.0.1)
- loading lede-17.01.5-ramips-rt305x-dir-300-b1-squashfs-factory.bin - (300 KB free space)
- applying openwrt-15.05.1 saved configuration, freeze after reboot - worked for a few seconds
- D-Link DIR-300B1 entering flash recovery mode (reset button pressed - interface at 192.168.0.1)
- loading openwrt-18.06.0-ramips-rt305x-dir-300-b1-squashfs-factory.bin -unable to save anything, Free space: 100% (13.70 MB)
Must be something wrong with the D-Link DIR-300B1 images. It runs solid on DD-WRT latest with pppoE at the "normal" speed of 96-98Mbps.
Thanks for this new release. 18.06 runs great on my WR1043ND v1. Because I installed Luci Material design at first I ran out of RAM quickly. Luckily I could still install a few packages with LuCi or ssh after every reboot. I made my way to usb, vfat and swap support.
But for neewbies it might be easier if you divide the package lists into chunks this 32MB RAM device can handle. On the other hand I'm happy that you haven't dropped the support yet.
Keep up that great work.
(Made a swap-file on an existing vfat filesystem with sudo dd if=/dev/zero of=/media/sdb1/swap count=256k and sudo mkswap /media/sdb1/swap on my desktop pc. This is much easier than creating new partition tables on SD cards.)
Pretty happy with how 18.06 behaves on the TL-WR741ND v4, just noticed in the LuCI status page that I'm left with between 1,4-2MB free RAM, even under heavy load, and hope that I won't run into any issues because of this.
There is a small glitch I've noticed in the Network>Interfaces section. I'm cloning my WAN MAC with:
uci set network.wan.macaddr=xx:xx:xx:xx:xx:xx uci commit network ifdown wan ifup wan
and the GUI is displaying the WAN (pppoe-wan) interface details:
Uptime: 0h 5m 43s
The MAC is actually cloned successfully and I can verify that by checking the details of the eth1 interface (ssh to the router - ifconfig).
Thanks to all involved in the development of OpenWRT, it rocks!
Might I suggest opening a bug report at https://bugs.openwrt.org/
so the problem can be tracked.
How many DIR-300B1's do you have? If its only one, why not sell it and then purchase a more recent used router via ebay craigslist or varagesale? I picked up a used TP-Link TL-WDR3600 for a reasonable price and has Gigabit ethernet, dual band, 8m flash, 128m ram, 2 usb ports, and both dd-wrt and Openwrt compatible . Or use 17.01.5 which is smaller and also recently released and I think still supported on your DIR-300.
Flashed a wrt1900ac today, from led 17.01.5 to openwrt 18.06.0
Went good, I still have to tweak a few things
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2018.08.04 13:53:54 =~=~=~=~=~=~=~=~=~=~=~= Using username "root". Authenticating with public key "rsa-key-2e BusyBox v1.25.1 () built-in shell (ash) LEDE Reboot 17.01.5 Security is enabled, and your IP address has been logged. e]0;root@AC1900M: ~aroot@AC1900M:~# cd /tmp e]0;root@AC1900M: /tmparoot@AC1900M:/tmp# sysupgrade -c -v openwrt-18.06.0-mvebu-cortexa9-linksys-wrt19 00ac-squashfs-sysupgrade.bin Saving config files... etc/collectd.conf etc/config/.wireless.uci-AHlfaI etc/config/ddns etc/config/ddns-opkg etc/config/dhcp etc/config/dhcp-opkg etc/config/dnscrypt-proxy etc/config/dnscrypt-proxy-opkg etc/config/dropbear etc/config/firewall etc/config/fstab etc/config/luci etc/config/luci-opkg etc/config/luci_statistics etc/config/luci_statistics-opkg etc/config/network etc/config/openvpn etc/config/openvpn-opkg etc/config/openvpn.old etc/config/openvpn_recipes etc/config/packages.list etc/config/rpcd etc/config/samba etc/config/samba-opkg etc/config/system etc/config/ubootenv etc/config/ucitrack etc/config/ucitrack-opkg etc/config/uhttpd etc/config/uhttpd-opkg etc/config/vnstat etc/config/vnstat-opkg etc/config/wireless etc/crontabs/root etc/dropbear/authorized_keys etc/dropbear/dropbear_rsa_host_key etc/easy-rsa/keys/index.txt etc/easy-rsa/keys/serial etc/firewall.user etc/fw_env.config etc/group etc/hosts etc/init.d/fan_control etc/inittab etc/luci-uploads/.placeholder etc/openvpn/IPredator.auth etc/openvpn/IPredator.se.ca.cer etc/openvpn/IPredator.se.ca.crt etc/openvpn/IPredator.se.ta.key etc/openvpn/ca.cer etc/openvpn/ca.crt etc/openvpn/ca.key etc/openvpn/client.crt etc/openvpn/client.key etc/openvpn/del-client_iptables etc/openvpn/dh2048.pem etc/openvpn/hma.auth etc/openvpn/hmauser.cer etc/openvpn/hmauser.key etc/openvpn/ivpn.auth etc/openvpn/server.crt etc/openvpn/server.key etc/openvpn/set-client_iptables etc/openvpn/ta.key etc/openvpn/tlsauth.key etc/opkg/keys/5151f69420c3f508 etc/opkg/keys/72a57f2191b211e0 etc/opkg/keys/792d9d9b39f180dc etc/opkg/keys/9ef4694208102c43 etc/opkg/keys/b5043e70f9a75cde etc/opkg/keys/dace9d4df16896bf etc/opkg/keys/dd6de0d06bbd3d85 etc/passwd etc/profile etc/rc.local etc/samba/lowcase.dat etc/samba/secrets.tdb etc/samba/smb.conf etc/samba/smb.conf.template etc/samba/smb.conf.template-opkg etc/samba/smbpasswd etc/samba/upcase.dat etc/samba/valid.dat etc/sensors3.conf etc/shadow etc/shells etc/ssh/banner etc/ssh/moduli etc/ssh/ssh_host_dsa_key etc/ssh/ssh_host_dsa_key.pub etc/ssh/ssh_host_ecdsa_key etc/ssh/ssh_host_ecdsa_key.pub etc/ssh/ssh_host_ed25519_key etc/ssh/ssh_host_ed25519_key.pub etc/ssh/ssh_host_rsa_key etc/ssh/ssh_host_rsa_key.pub etc/ssh/sshd_config etc/ssh/sshd_config-opkg etc/ssh/sshd_config.old etc/ssl/openssl.cnf etc/sysctl.conf etc/sysctl.d/local.conf etc/sysupgrade.conf etc/uhttpd.crt etc/uhttpd.key etc/usr/bin/1.sh etc/usr/bin/2..sh etc/usr/bin/3.sh etc/usr/bin/always_up.sh etc/usr/bin/bu_overlay.sh etc/usr/bin/crash_rb.sh etc/usr/bin/dc.sh etc/usr/bin/dl_hosts.sh etc/usr/bin/fancontrol.sh etc/usr/bin/firewall.sh etc/usr/bin/log.sh etc/usr/bin/loginprompt etc/usr/bin/run.sh etc/usr/bin/set-client_iptables.sh etc/usr/bin/sfw.sh etc/usr/bin/start.test.sh etc/usr/bin/trap.sh etc/usr/bin/v6.sh root/.ssh/authorized_keys root/.ssh/authorized_keys2 root/.ssh/ssh_mamba_rsa.key.pub usr/sbin/fan_monitor usr/share/dnscrypt-proxy/dnscrypt-resolvers.csv etc/uhttpd.key etc/uhttpd.crt killall: watchdog: no process killed Sending TERM to remaining processes ... sleep logd rpcd netifd odhcpd crond uhttpd smbd nmbd collectd dnsmasq dnscrypt-proxy ntpd fan_monitor vnstatd ubusd askfirst Sending KILL to remaining processes ... sleep askfirst Switching to ramdisk... Performing system upgrade... Unlocking kernel2 ... Writing from <stdin> to kernel2 ... [ ][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w] UBI device number 2, total 296 LEBs (37584896 bytes, 35.8 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB) Volume ID 0, size 18 LEBs (2285568 bytes, 2.2 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "rootfs", alignment 1 Set volume size to 32251904 Volume ID 1, size 254 LEBs (32251904 bytes, 30.8 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "rootfs_data", alignment 1 sysupgrade successful umount: can't unmount /dev/pts: Resource busy umount: can't unmount /dev: Resource busy umount: can't unmount /tmp: Resource busy
It's only one I have left from a previous installation and I'm using it for tests. These old routers have no value anymore, good for throwing away, nobody needs them. And, as mentioned in a previous post, all OpenWRT images I tried on it are crippling the PPPoE performance and LEDE doesn't seem stable. Running DD-WRT on it now.
I'm basically using a router only for the WAN link, a first stage firewall and for isolating the internal network(s) - Routed AP. OpenWRT has a great value exactly for allowing me to do these and for being secure and updated, unlike the stock firmware.
As for other modern routers, I only played with a few D-Link DIR-860L B1, loading 15.05.1 on them and then upgraded to LEDE. This router model was the only one I found under 50EUR, that was giving pretty good performance under PPPoE (around 300Mbps). WiFi stability on 2.4G is not great, the design (form) is big&ugly and the power consumption high. I'll need to upgrade them on 18.06 soon.
The real gigabit routers, powerful enough to actually run at gigabit speeds, even under PPPoE are very expensive ATM, starting at around 100EUR. I don't really need more than 100Mbit on WAN ATM.
I'm always wondering from were are the manufacturers still getting these tiny flash chips (8/16/32MB) in 2018 and if it's worth the effort in crippling the Linux kernel and the utilities to fit in that tiny space. As an alternative, I rather go for a 30EUR Raspberry board and use it as a router extension.
Will do so.
Why can I not use my forum registration to authenticate also in the bugtrack site? Weird...
The bug at bugs.openwrt.org was closed as it has to do with LuCI and I found my reported issue already recorded, a long time ago, in the LuCI issues list at github:
For those with rb493g routers, I can confirm that a sysupgrade from 17.01.3 to 18.06 works perfectly. I was surprised that after the 18.06 update that my wan6 interface changed from 6rd to dhcpv6. I have att uverse. Apparently I missed the notification that att has rolled out dual stack to its customers.
Keep up the excellent work!
I suggest keeping an eye on classified sites for a used compatible router with more flash and which works well at the speeds you need. But I think a DIR-300 with a current dd-wrt (17.01.05 ) is very valuable as a replacement for any router with old or unsupported proprietary software. Lots of people have connections slower than a gigabit and would greatly benefit from the much better security of Openwrt. Maybe if you don't find a buyer, pass /swap your DIR_300 with openwrt 17.01.05 to someone you know to introduce them to the world of Openwrt and make the internet a safer place.
Something is broken with openvpn.
Looks like it's the TUN/TAP IF
Sun Aug 5 08:55:48 2018 Initialization Sequence Completed Sun Aug 5 08:55:51 2018 write to TUN/TAP : Invalid argument (code=22) Sun Aug 5 08:55:53 2018 write to TUN/TAP : Invalid argument (code=22) Sun Aug 5 08:55:55 2018 write to TUN/TAP : Invalid argument (code=22) Sun Aug 5 08:55:59 2018 write to TUN/TAP : Invalid argument (code=22) Sun Aug 5 08:56:00 2018 event_wait : Interrupted system call (code=4) Sun Aug 5 08:56:00 2018 SIGTERM received, sending exit notification to peer Sun Aug 5 08:56:00 2018 write to TUN/TAP : Invalid argument (code=22) Sun Aug 5 08:56:02 2018 write to TUN/TAP : Invalid argument (code=22) Sun Aug 5 08:56:03 2018 /sbin/route del -net 18.104.22.168 netmask 255.255.255.255 Sun Aug 5 08:56:03 2018 /sbin/route del -net 0.0.0.0 netmask 22.214.171.124 Sun Aug 5 08:56:03 2018 /sbin/route del -net 126.96.36.199 netmask 188.8.131.52 Sun Aug 5 08:56:03 2018 Closing TUN/TAP interface Sun Aug 5 08:56:03 2018 /sbin/ifconfig tun1337 0.0.0.0 Sun Aug 5 08:56:03 2018 SIGTERM[soft,exit-with-notification] received, process exiting
I just upgraded my RouterStation Pro to 18.06.0 (the device is specifically my VPN server), and everything is working perfectly, so I don't think it is the new OpenWRT version specifically (although it could be the result of updates to the OpenVPN version now part of the 18.06 packages).
I'd recommend that you start a new thread to address your problem. In that thread, please post your OpenVPN config files (both client and server, if you're running both sides), OpenVPN log entries (also from both sides, if applicable), as well as your network and firewall files. Sanitize where necessary, of course, to ensure you don't reveal anything personal/sensitive.
EDIT: also worth noting that I upgraded a TP-Link TL-WR902AC to the stable release -- this device is my OpenVPN client in a travel router. It is able to connect to the RouterStation Pro (OVPN server) without issues.
Ubnt ERX - 18.06.0
traceroute -I (Traceroute ICMP option) is still broken and it's using UDP instead of ICMP. Please fix it in the next version.
I'm pretty sure this was due to a hardware issue. The fact that it worked sporadically on 17.01.4 was just a red herring.
good release, my tplink wr841n run quitely stable, everything work fine