I upgraded the 18.06.1 packages with opkg of my Netgear R7800 and now now Luci doesn't show the LAN configuration fields. How can I downgrade to standard 18.06.1?
Wherever you grabbed that from appears someone pasted the & operator from a source with the wrong character set, as it should be: umount /overlay && /sbin/firstboot && reboot
This must be done with care, as Base packages should never be upgraded... if Base packages need to be updated, an updated firmware image must be flashed.
LuCI and any of it's app packages are packages that should never be upgraded with opkg, as they're kernel version dependent
OpenWrt 18.06.1, r7258-5eb055306f
-----------------------------------------------------
root@R7800:~# umount /overlay && firstboot && reboot
This will erase all settings and remove any installed packages. Are you sure? [N/y]
y
/dev/ubi0_1 is not mounted
/dev/ubi0_1 will be erased on next mount
writing /dev/ubi0_1 failed: Bad file descriptor
Or if there is something wrong with the updated core system packages, boot the router to the Openwrt failsafe mode and use "firstboot" there. Failsafe mode skips all your changes in overlay and only used the flashed orginal firmware.
With R7800 you can naturally also use the Netgear TFTP recovery flash mode to flash a new version via TFTP, but likely that is not necessary.
is not a possible way? Sorry to ask again. This was the way to upgrade a 7-8 year old openwrt-router: TP-LINK TL-WR1043ND v1.8 Upgrade. But the difference now is, there is a downgrade of nearly thes same installation.
Ok, so with sysupgrade the sysupgrade-file and with tftp the factory file. I am asking double, because the router has another network (192.168.178.x) and after flashing I cannot access to it with my pc anymore (not easily) and I have to lend a notebook.
Default OpenWrt subnet is 192.168.1.0/24, which is the subnet the router will have once flashed.
For your PC, simply disconnect the ethernet cable for ~5s, then plug in back in... it will generate a new DHCP request and your PC will be assigned an IP in the 192.168.1.0/24 subnet.
If your PC is configured with a static IP on the PC's interface, simply change the IP to an IP in the aforementioned subnet (say .254), netmask to /24, and gateway as 192.168.1.1.
Not so easy with the pc, it is a bridge with 2 NICs, forwarding and firewall-rules and I try not to touch the configuration. I only want to be sure not to flash the wrong file. Thanks! I will give feedback, when it is done.
You can configure a virtual interface with the 192.168.1.0/24 IP assigned.
All Unix based OSes support this
Windows does, but only natively with Windows 10 Pro via Hyper-V.
If a home license, OpenVPN's TAP adapter is required to be installed (simply install OpenVPN), as the Windows TCP/IP stack is entirely different from Unix's, and doesn't support an interface without actual hardware attached to it.