We have two RV320 in separate offices with separate fibre connecions (via FTC converters) to our ISP.
Both are upgraded to the latest firmware.
I am constantly beng called with a problem report "the network's gone again".
What seems to happen is the RV320 crashes, and needs a power cycle to reset it.
Restart from the management interface isn'ts ufficient.
Today I see new errors in the log:
| 2015-04-23, 08:34:38 | Kernel | kernel: Start Check Reg ( 0, 16, 0 ) |
| 2015-04-23, 08:40:38 | Kernel | kernel: WARNING: no highest common denominator or auto-negotiation not complete |
| 2015-04-23, 08:40:39 | Kernel | last message repeated 2 times |
| 2015-04-23, 08:57:00 | Kernel | kernel: wrong ip[1],not_list[0] |
which appeared after after a power cycle at 08:34, but the router hasn't crashed again yet
I see this error often: Kernel kernel: wrong ip[1],not_list[0] ... and it seems to be related to an action in the web managment UI.
As if the web managment is causing that log entry.
These seem to be the relevant entries from before the crash:
| 2015-04-23, 07:44:36 | Kernel | kernel: Set: GPIO[5] Value[LO] |
| 2015-04-23, 07:44:41 | Kernel | kernel: Set: GPIO[5] Value[HI] |
| 2015-04-23, 07:52:49 | Kernel | kernel: WARNING: cant get external phy status |
| 2015-04-23, 08:01:40 | Kernel | kernel: WARNING: no highest common denominator or auto-negotiation not complete |
| 2015-04-23, 08:01:40 | Kernel | last message repeated 2 times |
| 2015-04-23, 08:01:40 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[0], duplex[0] |
| 2015-04-23, 08:01:41 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] |
| 2015-04-23, 08:02:01 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[0], duplex[0] |
| 2015-04-23, 08:02:01 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] |
Another odd set of messages is appearing:
| 2015-04-23, 08:57:42 | Kernel | kernel: WAN [2] UP |
| 2015-04-23, 08:57:42 | Kernel | kernel: [eth0] lanip=192.168.1.1, mask=255.255.255.0 |
| 2015-04-23, 08:57:42 | Kernel | kernel: ip[135.196.23.124] mask[0.0.0.0] |
| 2015-04-23, 08:57:42 | Kernel | kernel: ip[0.0.0.0] mask[0.0.0.0] |
| 2015-04-23, 08:57:43 | Kernel | kernel: [eth0] lanip=192.168.1.1, mask=255.255.255.0 |
| 2015-04-23, 08:57:43 | Kernel | kernel: ip[135.196.23.124] mask[0.0.0.0] |
| 2015-04-23, 08:57:43 | Kernel | kernel: ip[0.0.0.0] mask[0.0.0.0] |
| 2015-04-23, 08:57:43 | Kernel | kernel: wrong ip[1],not_list[0] |
| 2015-04-23, 08:57:43 | Kernel | kernel: upnp idx=202, ip=192.168.1.63, eport=61113, iport=61113 |
| 2015-04-23, 08:57:43 | Kernel | kernel: upnp idx=243, ip=192.168.1.85, eport=55266, iport=55266 |
| 2015-04-23, 08:57:43 | Kernel | kernel: WAN [2] DOWN |
Seemingly indicating that WAN2 is up - even though it is disabled (DMZ mode) and nothing is conected to the port.
Any ideas for fixing the router welcome !
