NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
rugene
Dec 20, 2014Guide
Final 6.2.1 update causing LAN instability/sluggishness
After upgrading to 6.2.1 on an RN314, the network adapters no longer appear in the UI. In general it looks like the network parameters were reset. I can only recover the device by letting my router ...
dsnpevl
Dec 21, 2014Virtuoso
OK, seems you must definitely disable all portforwarding as well. Then I managed to re-install the OS and have the web admin and SSH connection back.
One other weird thing I noticed, is while I only connected on LAN1, the NIC for LAN2 also show up in the router. This seems to be related to an an observation made here:
One other weird thing I noticed, is while I only connected on LAN1, the NIC for LAN2 also show up in the router. This seems to be related to an an observation made here:
Anyway, I can now try some stuff to get it to work. Logged into SSH and followed this procedure to check for connman packages (command line version).
mountaindude wrote: After restarting connamn (or the entire NAS) I have THREE IPs responding to pings: 192.168.1.16, 192.168.17 and 192.168.106
What??
root@nas-XX-XX-XX:~# apt-cache showpkg connmanSo this means I can try to downgrade to the 1.26-netgear1 version, hoping it doesn't have the flaw of the 1.27.
Package: connman
Versions:
1.27-netgear1 (/var/lib/apt/lists/apt.readynas.com_packages_readynasos_dists_6.2.1_main_binary-amd64_Packages) (/var/lib/dpkg/status)
Description Language:
File: /var/lib/apt/lists/apt.readynas.com_packages_readynasos_dists_6.2.1_updates_binary-amd64_Packages
MD5: cb5a9cf686ae7cfd884a7a436fa64503
1.26-netgear1 (/var/lib/apt/lists/apt.readynas.com_packages_readynasos_dists_6.2.1_updates_binary-amd64_Packages)
Description Language:
File: /var/lib/apt/lists/apt.readynas.com_packages_readynasos_dists_6.2.1_updates_binary-amd64_Packages
MD5: cb5a9cf686ae7cfd884a7a436fa64503
1.0-1.1+wheezy1+b1 (/var/lib/apt/lists/mirrors.kernel.org_debian_dists_wheezy_main_binary-amd64_Packages)
Description Language:
File: /var/lib/apt/lists/apt.readynas.com_packages_readynasos_dists_6.2.1_updates_binary-amd64_Packages
MD5: cb5a9cf686ae7cfd884a7a436fa64503
Reverse Depends:
connman-dbg,connman 1.27-netgear1
connman-dbg,connman 1.26-netgear1
Dependencies:
1.27-netgear1 - iptables (0 (null)) libc6 (2 2.15) libdbus-1-3 (2 1.1.1) libglib2.0-0 (2 2.31.8) libreadline6 (2 6.0) libxtables7 (0 (null)) dbus (0 (null)) lsb-base (0 (null)) bluez (0 (null)) wpasupplicant (0 (null))
1.26-netgear1 - iptables (0 (null)) libc6 (2 2.15) libdbus-1-3 (2 1.1.1) libglib2.0-0 (2 2.31.8) libreadline6 (2 6.0) libxtables7 (0 (null)) dbus (0 (null)) lsb-base (0 (null)) bluez (0 (null)) wpasupplicant (0 (null))
1.0-1.1+wheezy1+b1 - iptables (0 (null)) libc6 (2 2.9) libdbus-1-3 (2 1.1.1) libglib2.0-0 (2 2.28.0) libgnutls26 (2 2.12.17-0) libxtables7 (0 (null)) dbus (0 (null)) lsb-base (0 (null)) bluez (0 (null)) wpasupplicant (0 (null))
Provides:
1.27-netgear1 -
1.26-netgear1 -
1.0-1.1+wheezy1+b1 -
Reverse Provides:
root@nas-XX-XX-XX:~# sudo apt-get install connman=1.26-netgear1So now the big question: will it still work after restart. Since I have connection still, I used the web admin to restart. Will let you know how this goes.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Recommended packages:
bluez wpasupplicant
The following packages will be DOWNGRADED:
connman
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 51 not upgraded.
Need to get 383 kB of archives.
After this operation, 4,096 B disk space will be freed.
Do you want to continue? [Y/n] Y
Get:1 http://apt.readynas.com/packages/readynasos/ 6.2.1/updates connman amd64 1.26-netgear1 [383 kB]
Fetched 383 kB in 1s (251 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
dpkg: warning: downgrading connman from 1.27-netgear1 to 1.26-netgear1
(Reading database ... 32568 files and directories currently installed.)
Preparing to replace connman 1.27-netgear1 (using .../connman_1.26-netgear1_amd64.deb) ...
Unpacking replacement connman ...
Setting up connman (1.26-netgear1) ...
insserv: warning: current stop runlevel(s) (empty) of script `connman' overrides LSB defaults (0 1 6).
insserv: can not symlink(../init.d/nut-server, ../rc2.d/S03nut-server): File exists
insserv: can not symlink(../init.d/forked-daapd, ../rc2.d/S05forked-daapd): File exists
insserv: can not symlink(../init.d/avahi-daemon, ../rc2.d/S04avahi-daemon): File exists
insserv: can not symlink(../init.d/dbus, ../rc2.d/S03dbus): File exists
insserv: can not symlink(../init.d/apache2, ../rc2.d/S02apache2): File exists
insserv: can not symlink(../init.d/lsyncd, ../rc2.d/S01lsyncd): File exists
insserv: can not symlink(../init.d/mdadm, ../rc2.d/S03mdadm): File exists
insserv: can not symlink(../init.d/connman, ../rc2.d/S04connman): File exists
insserv: can not symlink(../init.d/rsync, ../rc2.d/S03rsync): File exists
insserv: can not symlink(../init.d/cron, ../rc2.d/S03cron): File exists
insserv: can not symlink(../init.d/nut-server, ../rc3.d/S03nut-server): File exists
insserv: can not symlink(../init.d/forked-daapd, ../rc3.d/S05forked-daapd): File exists
insserv: can not symlink(../init.d/avahi-daemon, ../rc3.d/S04avahi-daemon): File exists
insserv: can not symlink(../init.d/dbus, ../rc3.d/S03dbus): File exists
insserv: can not symlink(../init.d/apache2, ../rc3.d/S02apache2): File exists
insserv: can not symlink(../init.d/lsyncd, ../rc3.d/S01lsyncd): File exists
insserv: can not symlink(../init.d/mdadm, ../rc3.d/S03mdadm): File exists
insserv: can not symlink(../init.d/connman, ../rc3.d/S04connman): File exists
insserv: can not symlink(../init.d/rsync, ../rc3.d/S03rsync): File exists
insserv: can not symlink(../init.d/cron, ../rc3.d/S03cron): File exists
insserv: can not symlink(../init.d/nut-server, ../rc4.d/S03nut-server): File exists
insserv: can not symlink(../init.d/forked-daapd, ../rc4.d/S05forked-daapd): File exists
insserv: can not symlink(../init.d/avahi-daemon, ../rc4.d/S04avahi-daemon): File exists
insserv: can not symlink(../init.d/dbus, ../rc4.d/S03dbus): File exists
insserv: can not symlink(../init.d/apache2, ../rc4.d/S02apache2): File exists
insserv: can not symlink(../init.d/lsyncd, ../rc4.d/S01lsyncd): File exists
insserv: can not symlink(../init.d/mdadm, ../rc4.d/S03mdadm): File exists
insserv: can not symlink(../init.d/connman, ../rc4.d/S04connman): File exists
insserv: can not symlink(../init.d/rsync, ../rc4.d/S03rsync): File exists
insserv: can not symlink(../init.d/cron, ../rc4.d/S03cron): File exists
insserv: can not symlink(../init.d/nut-server, ../rc5.d/S03nut-server): File exists
insserv: can not symlink(../init.d/forked-daapd, ../rc5.d/S05forked-daapd): File exists
insserv: can not symlink(../init.d/avahi-daemon, ../rc5.d/S04avahi-daemon): File exists
insserv: can not symlink(../init.d/dbus, ../rc5.d/S03dbus): File exists
insserv: can not symlink(../init.d/apache2, ../rc5.d/S02apache2): File exists
insserv: can not symlink(../init.d/lsyncd, ../rc5.d/S01lsyncd): File exists
insserv: can not symlink(../init.d/mdadm, ../rc5.d/S03mdadm): File exists
insserv: can not symlink(../init.d/connman, ../rc5.d/S04connman): File exists
insserv: can not symlink(../init.d/rsync, ../rc5.d/S03rsync): File exists
insserv: can not symlink(../init.d/cron, ../rc5.d/S03cron): File exists
[ ok ] Restarting connman (via systemctl): connman.service.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!