I updated to the latest stable (18.06.4). What's really strange: I can't perform a firstboot from the CLI! It says it will do all the stuff but it doesn't reboot from itself.
root@OpenWrt:~# firstboot
This will erase all settings and remove any installed packages. Are you sure? [N/y]
y
/dev/mtdblock14 is mounted as /overlay, only erasing files
After it I can reboot the device and perform a factory reset with Luci. Strange!
And here are the default settings on the device:
BusyBox v1.28.4 () built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 18.06.4, r7808-ef686b7292
-----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@OpenWrt:~# cat /etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd09:910b:372e::/48'
config interface 'lan'
option type 'bridge'
option ifname 'eth0'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
root@OpenWrt:~#
I think the most robust is to boot into failsafe, don't mount the overlay and then re-init the volume, truncating it with double check this first!!
root@OpenWrt:/# ubinfo /dev/ubi0_1
Volume ID: 1 (on ubi0)
Type: dynamic
Alignment: 1
Size: 953 LEBs (121008128 bytes, 115.4 MiB)
State: OK
Name: rootfs_data
Character device major/minor: 252:2
Once you're sure of the proper volume
ubiupdatevol /dev/ubi0_1 -t
root@OpenWrt:/# ubiupdatevol --help
ubiupdatevol version 2.0.2 - a tool to write data to UBI volumes.
Usage: ubiupdatevol <UBI volume node file name> [-t] [-s <size>] [-h] [-V] [--truncate]
[--size=<size>] [--help] [--version] <image file>
Example 1: ubiupdatevol /dev/ubi0_1 fs.img - write file "fs.img" to UBI volume /dev/ubi0_1
Example 2: ubiupdatevol /dev/ubi0_1 -t - wipe out UBI volume /dev/ubi0_1
-t, --truncate truncate volume (wipe it out)
-s, --size=<bytes> bytes to read from input
--skip=<bytes> leading bytes to skip from input
-h, --help print help message
-V, --version print program version
Thank you! I think it's better for me to wait for tomorrow and try it with a fresh mind. Before I have to figure out which button I can use as failsafe-button and how to perform the boot into failsafe mode.
Thanks @Pilot6. I will try it today. Something for my understanding:
Normally the CPU-port on the switch should always be tagged, shall it? In every OpenWRT router I have there is the CPU port of the switch always tagged even if the physical lan ports are untagged.
Not always. The default vlan 1 config for my NBG6617 is with port 0 untagged. That means that all traffic by default goes to vlan 1 no matter is it tagged or not. It is hardcoded in dts.
You may be correct for the case when eth0 is used for both lan and wan. Change it fo 0t.
Thanks for pointing out! I was just wondering why my try to factory reset in Luci seems to work. I can see the LEDs of the router are blinking and the device is rebooting by itself. I would expect a password and old configs in the webinterface if the factory reset isn't working but it looks like a fresh install.
Are you still advice to do a factory reset with the failsafe method or can I just trust the webinterface. Just asking for timesavings!
PS: You guys are great, so helpful and fast answers! Thanks a lot!
I don't trust something named jffs2reset with UBIFS, especially what I have seen of it so far. If I really need a "factory reset" on a NAND-based device I'll either manually "reformat" the overlay, or, more likely, reflash the device.
Very seldom do I need a full, factory reset -- if I need to revert a file or two that is auto-generated, I delete the file, then reboot.
Reflash using sysupgrade, as long as you specify -n, should work as well.
There are good reasons to prefer ubiupdatevol (which sysupgrade typically eventually calls) over writing a raw image with NAND, such as a U-Boot flash would do.
Is ubiupdatevol /dev/<right_ubi_device> /tmp/netgear_ex6150v2-squashfs-sysupgrade.bin the right way to go? The sysupgrade firmwares are the correct one for the ubiupdatevol? What's the name of the ubi-partition i have to look for?
And running the command from a normal booted device is ok, no need for failsafe mode?
Thank you! This worked, I only additionally added the '0t' to the VLAN1 tagging!
I performed the sysupgrade like @jeff described and went through the configuration. So it's possible to use VLAN-tagging on the EX6150v2. Thank you so much!
