Cisco RV320 - Problemi Timeout

Tutto ciò che ha a che fare con la configurazione di apparati Cisco (e non rientra nelle altre categorie)

Moderatore: Federico.Lagni

Rispondi
lucav
n00b
Messaggi: 1
Iscritto il: sab 07 giu , 2014 6:46 pm

Ciao a tutti,
ho appena acquistato il router in oggetto in quanto a giorni mi attivano una nuova linea adsl e dando accesso internet tramite hotspot ai clienti, una linea andava in saturazione, quindi ho deciso di effettuare un load balancing delle 2 linee adsl.

Prima come router utilizzato un NETGEAR e non ha mai dato nessun problema, mentre con questo ogni tanto la linea decide di "cedere" e non funzionare per qualche secondo (approssimativamente 1 minuto) per poi riprendere e questo rende il tutto inusabile :(

La mia rete è configurata in questo modo, per ora ho solo 1 link WAN attivo.

Modem -> ppoe cisco rv320 (192.161.2.1)-> hotspot zyxel n4100 (192.161.2.1 WAN IP e LAN IP 192.161.1.1)-> switch poe (192.161.1.23) - 3 x wireless poe antenna Ubiquiti

Questo è un ping:

Codice: Seleziona tutto

MacBook-Air-di-Luca:~ LV$ ping www.google.com
PING www.google.com (149.3.176.22): 56 data bytes
64 bytes from 149.3.176.22: icmp_seq=0 ttl=56 time=44.115 ms
64 bytes from 149.3.176.22: icmp_seq=1 ttl=56 time=74.773 ms
64 bytes from 149.3.176.22: icmp_seq=2 ttl=56 time=58.397 ms
64 bytes from 149.3.176.22: icmp_seq=3 ttl=56 time=103.889 ms
64 bytes from 149.3.176.22: icmp_seq=4 ttl=56 time=216.906 ms
64 bytes from 149.3.176.22: icmp_seq=5 ttl=56 time=56.474 ms
64 bytes from 149.3.176.22: icmp_seq=6 ttl=56 time=207.755 ms
64 bytes from 149.3.176.22: icmp_seq=7 ttl=56 time=64.326 ms
64 bytes from 149.3.176.22: icmp_seq=8 ttl=56 time=52.341 ms
64 bytes from 149.3.176.22: icmp_seq=9 ttl=56 time=175.903 ms
64 bytes from 149.3.176.22: icmp_seq=10 ttl=56 time=227.868 ms
64 bytes from 149.3.176.22: icmp_seq=11 ttl=56 time=136.094 ms
64 bytes from 149.3.176.22: icmp_seq=12 ttl=56 time=75.252 ms
64 bytes from 149.3.176.22: icmp_seq=13 ttl=56 time=182.221 ms
64 bytes from 149.3.176.22: icmp_seq=14 ttl=56 time=448.326 ms
Request timeout for icmp_seq 15
64 bytes from 149.3.176.22: icmp_seq=16 ttl=56 time=48.658 ms
64 bytes from 149.3.176.22: icmp_seq=17 ttl=56 time=38.991 ms
--- www.google.com ping statistics ---
18 packets transmitted, 17 packets received, 5.6% packet loss
round-trip min/avg/max/stddev = 38.991/130.135/448.326/102.688 ms
traceroute verso il mio sito:

Codice: Seleziona tutto

MacBook-Air-di-Luca:~ LV$ traceroute www.lucavasini.it
traceroute to www.lucavasini.it (188.226.190.148), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  1.925 ms  1.519 ms  1.399 ms
 2  192.168.2.1 (192.168.2.1)  3.282 ms  2.212 ms  2.051 ms
 3  * * *
 4  host153-230-static.44-88-b.business.telecomitalia.it (88.44.230.153)  26.062 ms  28.702 ms  24.144 ms
 5  80.17.209.141 (80.17.209.141)  25.597 ms  26.954 ms  24.408 ms
 6  172.19.242.58 (172.19.242.58)  37.581 ms  39.646 ms  41.300 ms
 7  pos2-8-0-0.milano50.mil.seabone.net (93.186.128.126)  39.033 ms  37.901 ms  42.055 ms
 8  xe-2-3-0.milano51.mil.seabone.net (195.22.192.103)  35.717 ms  36.261 ms *
 9  ntt-verio.milano51.mil.seabone.net (93.186.128.157)  77.357 ms  58.782 ms *
10  ae-20.r03.amstnl02.nl.bb.gin.ntt.net (129.250.4.169)  67.833 ms  68.055 ms  68.245 ms
11  83.231.213.2 (83.231.213.2)  62.632 ms  62.776 ms  63.491 ms
12  95.85.0.238 (95.85.0.238)  69.742 ms  62.714 ms  62.955 ms
13  srv1.lucavasini.it (188.226.190.148)  74.270 ms  73.730 ms  73.891 ms
MacBook-Air-di-Luca:~ LV$
ping sempre verso il mio sito:

Codice: Seleziona tutto

MacBook-Air-di-Luca:~ LV$ ping www.lucavasini.it
PING www.lucavasini.it (188.226.190.148): 56 data bytes
64 bytes from 188.226.190.148: icmp_seq=0 ttl=51 time=79.104 ms
64 bytes from 188.226.190.148: icmp_seq=1 ttl=51 time=86.076 ms
64 bytes from 188.226.190.148: icmp_seq=2 ttl=51 time=153.377 ms
64 bytes from 188.226.190.148: icmp_seq=3 ttl=51 time=87.232 ms
64 bytes from 188.226.190.148: icmp_seq=4 ttl=51 time=76.080 ms
64 bytes from 188.226.190.148: icmp_seq=5 ttl=51 time=67.852 ms
64 bytes from 188.226.190.148: icmp_seq=6 ttl=51 time=73.136 ms
Request timeout for icmp_seq 7
64 bytes from 188.226.190.148: icmp_seq=7 ttl=51 time=1006.756 ms
64 bytes from 188.226.190.148: icmp_seq=8 ttl=51 time=69.359 ms
64 bytes from 188.226.190.148: icmp_seq=9 ttl=51 time=86.434 ms
64 bytes from 188.226.190.148: icmp_seq=10 ttl=51 time=90.863 ms
64 bytes from 188.226.190.148: icmp_seq=11 ttl=51 time=97.732 ms
64 bytes from 188.226.190.148: icmp_seq=12 ttl=51 time=82.909 ms
64 bytes from 188.226.190.148: icmp_seq=13 ttl=51 time=101.086 ms
Request timeout for icmp_seq 15
64 bytes from 188.226.190.148: icmp_seq=16 ttl=51 time=78.514 ms
64 bytes from 188.226.190.148: icmp_seq=17 ttl=51 time=67.852 ms
64 bytes from 188.226.190.148: icmp_seq=18 ttl=51 time=88.371 ms
64 bytes from 188.226.190.148: icmp_seq=19 ttl=51 time=103.850 ms
64 bytes from 188.226.190.148: icmp_seq=20 ttl=51 time=97.550 ms
64 bytes from 188.226.190.148: icmp_seq=21 ttl=51 time=66.642 ms
--- www.lucavasini.it ping statistics ---
22 packets transmitted, 20 packets received, 9.1% packet loss
round-trip min/avg/max/stddev = 66.642/133.039/1006.756/201.322 ms
ping di quando la linea non funziona:

Codice: Seleziona tutto

MacBook-Air-di-Luca:~ LV$ ping www.google.com
PING www.google.com (149.3.177.54): 56 data bytes
64 bytes from 149.3.177.54: icmp_seq=0 ttl=56 time=36.093 ms
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
^XRequest timeout for icmp_seq 12
--- www.google.com ping statistics ---
14 packets transmitted, 1 packets received, 92.9% packet loss
round-trip min/avg/max/stddev = 36.093/36.093/36.093/0.000 ms
log del router, con errori strani che cercandoli su google restituiscono strani errori che non riesco ad interpretare.

Codice: Seleziona tutto

2023-09-13, 19:21:32

Kernel

kernel: i2c i2c-0: Failed to register i2c client rs5c372b at 0x32 (-16)

2023-09-13, 19:21:32

Kernel

kernel: i2c i2c-0: Can't create device at 0x32

2023-09-13, 19:21:32

Kernel

kernel: gre: can't add protocol

2014-06-05, 01:57:56

Kernel

kernel: i2c i2c-0: Failed to register i2c client rs5c372b at 0x32 (-16)

2014-06-05, 01:57:56

Kernel

kernel: i2c i2c-0: Can't create device at 0x32

2014-06-05, 01:57:56

Kernel

kernel: gre: can't add protocol

2014-06-05, 13:26:09

Kernel

kernel: i2c i2c-0: Failed to register i2c client rs5c372b at 0x32 (-16)

2014-06-05, 13:26:09

Kernel

kernel: i2c i2c-0: Can't create device at 0x32

2014-06-05, 13:26:09

Kernel

kernel: gre: can't add protocol

2014-06-05, 15:36:26

Kernel

kernel: i2c i2c-0: Failed to register i2c client rs5c372b at 0x32 (-16)

2014-06-05, 15:36:26

Kernel

kernel: i2c i2c-0: Can't create device at 0x32

2014-06-05, 15:36:26

Kernel

kernel: gre: can't add protocol

2014-06-08, 09:54:15

Kernel

kernel: i2c i2c-0: Failed to register i2c client rs5c372b at 0x32 (-16)

2014-06-08, 09:54:15

Kernel

kernel: i2c i2c-0: Can't create device at 0x32

2014-06-08, 09:54:15

Kernel

kernel: gre: can't add protocol

2014-06-07, 23:56:35

Kernel

kernel: i2c i2c-0: Failed to register i2c client rs5c372b at 0x32 (-16)

2014-06-07, 23:56:35

Kernel

kernel: i2c i2c-0: Can't create device at 0x32

2014-06-07, 23:56:35

Kernel

kernel: gre: can't add protocol

2014-06-08, 00:18:01

Kernel

kernel: i2c i2c-0: Failed to register i2c client rs5c372b at 0x32 (-16)

2014-06-08, 00:18:01

Kernel

kernel: i2c i2c-0: Can't create device at 0x32

2014-06-08, 00:18:01

Kernel

kernel: gre: can't add protocol

Vi allego anche alcuni screenshots!

Immagine

Immagine

Immagine

Immagine

non so come uscirne fuori sinceramente, spero in un vostro aiuto.
Vi ringrazio e vi auguro una
Buona Domenica.

Luca
Rispondi