OpenWrt 18.06.0 release

This seems to work. Thank you. Another issue, on the Buffalo WBMR-HP-G300H when the "non-wildcard" option is turned on, dnsmasq fails to start with this message:

"cannot set --bind-interfaces and --bind-dynamic"

It seems to work fine on the BT HomeHub - so I wonder if there are specific compile options that are slightly different here.

Hello, I have problem with new fw version. I cant get automatically default gateway from my provider, but for older version 17.01.4 all work. if i set static router i get internet but it must works automaticle.
Help me pls

DUPLICATE: Default gateway problem

i have the same problem, did you find a fix?

yeah. There is a another topic in the forum but I don't have the link now. What I did is reboot the router from the luci ui. Then everything works well.

So, if what you have done is power off the router or reset the router with the router hardware. Then you can try to reflash openwrt and reboot it from luci this time. The reason is that something is not written to the nand flash when you power off the router.

ok thanks. i did find the other topic: [Solved] Asus RT-AC58U and OpenWrt 18.06 problem

I upgraded to 18.06.0 on Aug 7th and everything was working well. Then on Aug 11th, I upgraded 3 packages and my networking, particularly wifi, has become noticeably less stable from multiple / all devices. The packages are:

Package: mwlwifi-firmware-88w8864
Version: 2018-06-15-8683de8e-1
Depends: libc, kmod-mwlwifi
Status: install user installed
Architecture: arm_cortex-a9_vfpv3
Installed-Time: 1534013771

Package: libuci
Version: 2018-08-11-4c8b4d6e-1
Depends: libc, libubox
Status: install user installed
Architecture: arm_cortex-a9_vfpv3
Installed-Time: 1534013772

Package: uci
Version: 2018-08-11-4c8b4d6e-1
Depends: libc, libuci
Status: install user installed
Architecture: arm_cortex-a9_vfpv3
Installed-Time: 1534013772

Details of my build are:

Model: Linksys WRT1900AC
Architecture: ARMv7 Processor rev 2 (v7l)
Firmware Version: OpenWrt 18.06.0 r7188-b0b5c64c22 / LuCI openwrt-18.06 branch (git-18.219.52706-a49e4e4)
Kernel Version: 4.14.54

I'm wondering -- has anyone else noticed any issue after such an upgrade to those packages? Also, I have been trying to figure out how to downgrade an individual package, and although I understand there's a --force-downgrade option to opkg, I simply can't FIND the previous version(s) available anywhere.

Any help would be appreciated.

1 Like

Just installed OpenWrt 18.06.0 r7188-b0b5c64c22 on my NETGEAR WNDR4300.
It works fine but I can't find iptables-mod-geoip. That module was available in lede.
Will it be available soon in the repository ?
Perhaps, i can try to compile it but I have to learn more how to find the good way for cross compiling.

Should be available for mips_24kc: https://openwrt.org/packages/pkgdata/iptables-mod-geoip

maybe you forgot to opkg update?

18.06.1 appears to being built now (August 16th, 2018) with results appearing under http://downloads.openwrt.org/releases/18.06.1/

Things that caught my eye (this is not an official release note) from git log v18.06.0..v18.06.1 include:

  • openssl 1.0.2p
  • kernel: bump kernel 4.9 to version 4.9.120
  • kernel: bump 4.14 to 4.14.62
  • mwlwifi: update to version 10.3.8.0-20180615
  • wpa_supplicant: fix CVE-2018-14526
  • mbedtls: Update to 2.12.0
  • kernel: backport upstream fix for CVE-2018-5390

and a lot more.

1 Like

I dn't forgot 'opkg update' but the link provided here is for lede version .
iptables-mod-geoip is not available for OpenWrt 18.06.0 but exist for OpenWrt 18.06.1.
I shall wait for openwrt-18.06.1-ar71xx-nand-wndr4300-squashfs-sysupgrade.tar not yet available now.
Then I can upgrade to that version.

Sorry, those pages didn't receive an update in a while. Done so now, updated to 18.06.

If you re-install 18.06.0, any updated packages will be lost (only those includes with that release will be installed)!

Lede version 18.06.0 on the tl-wr841nd v11 as relayd repeater. It seems to work but there are various kernel errors on the log.

This morning, iptables-mod-geoip is available for OpenWrt 18.06.0, so everything is OK for me.

1 Like

Thanks @LHoust -- that's exactly what I did. Let's see if WiFi stabilizes

How did you upgrade it? I tried and got an error. (Upgrade from LEDE 17.01.2 to OpenWRT 18.06.1)

sysupgrade -v openwrt-18.06.1-mvebu-cortexa9-linksys-wrt1900acs-squashfs-sysupgrade.bin
Image metadata not found
Use sysupgrade -F to override this check when downgrading or flashing to vendor firmware
Image check 'fwtool_check_image' failed.

Hello, i have the same error too when i try to upgrade frome 17.0.1, how can we solve this please ?

It seems like when PPPOA is used, it takes a while with the current kernel for the actual pppoa device to come up.

However, 'netifd' thinks that the interface is back up and attempts to trigger the WAN connection setup procedure, this results in a minor load spike and repeats of the following sets of message:

netifd: Interface 'wan' is now down
netifd: Interface 'wan' is setting up now
insmod: module is already loaded - slhc
insmod: module is already loaded - ppp_generic
insmod: module is already loaded - pppox
insmod: module is already loaded - pppoatm
pppd[2548]: Plugin pppoatm.so loaded.
pppd[2548]: PPPoATM plugin_init
pppd[2548]: PPPoATM setdevname_pppoatm - SUCCESS:0.38
pppd[2548]: pppd 2.4.7 started by root, uid 0
pppd[2548]: connect(0.38): No such device
pppd[2548]: Exit.

dnsmasq also tries start and demonstrates various failures, this appears to happen a number of times before the kernel returns after about 40 seconds with:

kernel: [   73.564838] ATM1.0.26    ATM (A1) firmware version 0.24
kernel: [   73.568741] ifxmips_atm: ATM init succeed

and then eventually after another 30-40 seconds:

kernel: [  111.967797] enter showtime, cell rate: 0 - 2346, 1 - 2346, xdata addr: 0xa62d0000
kernel: [  111.975541] enter showtime, cell rate: 0 - 2346, 1 - 2346, xdata addr: 0xa62d0000

At which point pppd proceeds as normal - the entire process taking a lot longer than it does in 17.X. I'm wondering if part of the issue is pppd chewing up cpu

I've been trying to get extroot to work on USB w18.0.6. I can manually mount /dev/sda1 to /overlay, and it shows increased size, but upon reboot it doesn't auto mount. (no .extroot-uuid in ext USB). The auto-mount works on any other target but /overlay.

Appreciate any ideas, thank you!

dmesg Errors

[ 13.034123] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
[ 13.061991] block: extroot: device not present, retrying in 15 seconds
[ 28.083918] block: extroot: cannot find device with UUID ef34e5db-7aff-49d7-8960-b048f482ea5b
[ 28.103240] mount_root: switching to jffs2 overlay'

/etc/config/fstab
'config 'global'
        option  anon_swap       '0'
        option  anon_mount      '0'
        option  auto_swap       '1'
        option  auto_mount      '1'
        option  delay_root      '15'
        option  check_fs        '0'

config 'mount'
        option  target  '/overlay'
        option  uuid    'ef34e5db-7aff-49d7-8960-b048f482ea5b'
        option  fstype  'ext4'
        option  enabled '1'

config 'swap'
        option  uuid    'dcb91081-6dba-473a-8d8e-d8dc03eb1725'
        option  enabled '1'