SRX5308 e DHCP - no free leases

[tomasigioielli]

Buonasera,

da qualche mese *sembrerebbe* che il firewall non rilasci piu' indirizzi (???) senza motivazione apparente. Inizialmente erano stati introdotti "abusivamente" (senza avvisarmi) un repeater wifi e un sw di videosorveglianza che avevano un servizio DHCP abilitato verso la lan. Disabilitati codesti servizi, il problema inizialmente e' scomparso, salvo ritornare dopo qialche settimana. Non ne vengo a capo.

Il servizio DHCP e' abilitato solo per un determinato range, esclusivamente per venire in contro a periferiche che litigano con gli IP fissi (stendiamo un pietoso velo), altrimenti ne farei volentieri a meno.... Ma tant'e'

Ho riavviato tutto, piu' volte, aggiornato il firmware, cercato sulla community.

Non ne vengo a capo :'(

Modello: SRX5308

FW1: 4.3.4-2 (appena aggiornato)

FW2: 4.2.1-2

subnet: 192.168.66.0/24

DHCP abilitato per il range 192.168.66.144-198

Log del DHCP:

Apr 18 16:36:51 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from 28:a0:2b:3b:cb:29 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:36:42 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from 28:a0:2b:3b:cb:29 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:36:38 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from 28:a0:2b:3b:cb:29 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:36:35 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from 28:a0:2b:3b:cb:29 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:36:33 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from 28:a0:2b:3b:cb:29 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:33:36 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:33:31 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:33:14 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:33:06 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:33:03 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:32:58 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:32:46 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:32:38 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:32:33 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:32:28 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:32:24 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:32:16 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:32:11 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:32:06 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:32:03 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:31:47 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:31:39 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:31:34 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:31:29 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:30:58 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:30:50 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:30:45 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:30:40 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:30:36 [SRX5308] local7.info [DHCPD]: Sending on   Socket/fallback/fallback-net
Apr 18 16:30:36 [SRX5308] local7.err [DHCPD]:
Apr 18 16:30:36 [SRX5308] local7.err [DHCPD]:    to which interface eth0.4092 is attached. **
Apr 18 16:30:36 [SRX5308] local7.err [DHCPD]:    in your dhcpd.conf file for the network segment
Apr 18 16:30:36 [SRX5308] local7.err [DHCPD]:    you want, please write a subnet declaration
Apr 18 16:30:36 [SRX5308] local7.err [DHCPD]: ** Ignoring requests on eth0.4092.  If this is not what
Apr 18 16:30:36 [SRX5308] local7.err [DHCPD]: No subnet declaration for eth0.4092 (10.70.121.2).
Apr 18 16:30:36 [SRX5308] local7.err [DHCPD]:
Apr 18 16:30:36 [SRX5308] local7.info [DHCPD]: Sending on   LPF/eth0.1/28:c6:8e:f5:aa:c6/192.168.66.0/24
Apr 18 16:30:36 [SRX5308] local7.info [DHCPD]: Listening on LPF/eth0.1/28:c6:8e:f5:aa:c6/192.168.66.0/24
Apr 18 16:30:36 [SRX5308] local7.info [DHCPD]: Wrote 55 leases to leases file.
Apr 18 16:30:27 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:30:22 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:30:17 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:30:14 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from bc:ee:7b:8b:65:bd via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:29:58 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:29:57 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from bc:ee:7b:8b:65:bd via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:29:49 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:29:48 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from bc:ee:7b:8b:65:bd via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:29:45 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from bc:ee:7b:8b:65:bd via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:29:44 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:29:39 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:29:35 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:29:18 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:29:12 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from bc:ee:7b:8b:65:bd via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:29:11 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:29:07 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:29:01 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:28:58 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:28:57 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from bc:ee:7b:8b:65:bd via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:28:49 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from bc:ee:7b:8b:65:bd via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:28:45 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from bc:ee:7b:8b:65:bd via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:28:42 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:28:40 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from bc:ee:7b:8b:65:bd via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:28:39 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from bc:ee:7b:8b:65:bd via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:28:33 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:28:28 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:28:23 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:28:19 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:28:04 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:27:56 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:27:51 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:27:46 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:27:36 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:27:20 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:27:12 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:27:08 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:27:06 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:22:12 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:21:57 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:21:48 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:21:43 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:21:38 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:21:34 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:21:19 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:21:10 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:21:06 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:21:00 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:20:56 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:20:40 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:20:32 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:20:28 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:20:23 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:19:05 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:19:00 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:18:54 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:18:39 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:18:32 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:18:27 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Apr 18 16:18:22 [SRX5308] local7.err [DHCPD]: DHCPDISCOVER from a0:8d:16:0f:17:75 via eth0.1: network 192.168.66.0/24: no free leases
Jan  1 01:02:04 [SRX5308] local7.info [DHCPD]: Sending on   Socket/fallback/fallback-net
Jan  1 01:02:04 [SRX5308] local7.err [DHCPD]:
Jan  1 01:02:04 [SRX5308] local7.err [DHCPD]:    to which interface eth0.4092 is attached. **
Jan  1 01:02:04 [SRX5308] local7.err [DHCPD]:    in your dhcpd.conf file for the network segment
Jan  1 01:02:04 [SRX5308] local7.err [DHCPD]:    you want, please write a subnet declaration
Jan  1 01:02:04 [SRX5308] local7.err [DHCPD]: ** Ignoring requests on eth0.4092.  If this is not what
Jan  1 01:02:04 [SRX5308] local7.err [DHCPD]: No subnet declaration for eth0.4092 (10.70.121.2).
Jan  1 01:02:04 [SRX5308] local7.err [DHCPD]:
Jan  1 01:02:04 [SRX5308] local7.info [DHCPD]: Sending on   LPF/eth0.1/28:c6:8e:f5:aa:c6/192.168.66.0/24
Jan  1 01:02:04 [SRX5308] local7.info [DHCPD]: Listening on LPF/eth0.1/28:c6:8e:f5:aa:c6/192.168.66.0/24
Jan  1 01:02:04 [SRX5308] local7.info [DHCPD]: Wrote 55 leases to leases file.
Jan  1 01:01:46 [SRX5308] local7.info [DHCPD]: DHCPACK to 192.168.66.30 (e0:3f:49:be:22:58) via eth0.1
Jan  1 00:01:46 [SRX5308] local7.info [DHCPD]: DHCPINFORM from 192.168.66.30 via eth0.1
Jan  1 00:00:41 [SRX5308] local7.info [DHCPD]: Sending on   Socket/fallback/fallback-net
Jan  1 00:00:41 [SRX5308] local7.info [DHCPD]: Sending on   LPF/eth0.1/28:c6:8e:f5:aa:c6/192.168.66.0/24
Jan  1 00:00:41 [SRX5308] local7.info [DHCPD]: Listening on LPF/eth0.1/28:c6:8e:f5:aa:c6/192.168.66.0/24
Jan  1 00:00:41 [SRX5308] local7.info [DHCPD]: Wrote 55 leases to leases file.

Idee?... 😕

[EvelinaS]

Salve @tomasigioielli, 

complimenti per il suo primo post e Benvenuto nella Community!

Esattamente quanti host ci sono nella rete? Potrebbe gentilmente allegare la schermata dalla pagina con le impostazioni DHCP del firewall?

Cordiali Saluti, 

Evelina

Team NETGEAR 

[tomasigioielli]

Salve @EvelinaS,

con ritardo ecco i dati 😉

- Tra PC e altre periferiche (stampanti, Sonos, AP wireless, cellulari vari...) siamo intorno ai 25 host

- di seguito la schermata delle impostazioni LAN

[EvelinaS]

Buongiorno @tomasigioielli, 

grazie per lo screenshot 🙂

Provi a:

1. Aggiornare la versione del firmware per 4.3.5-3, 

2. Aumentare il range del DHCP 

3. Reset

Cordiali Saluti, 

Evelina

Team NETGEAR 

[Redento]

Bè, dall'errore si direbbe un problema legato al fatto che il pool del DHCP è pieno, strano perchè su una rete da 25 host hai settato quasi 50 IP nel pool, non è che c'è un Access Point aperto che rilascia Ip a smartphone o altro?
Prova a diminuire il lease da 24H a 2H

[tomasigioielli]

---

Redento dixit:

Bè, dall'errore si direbbe un problema legato al fatto che il pool del DHCP è pieno, strano perchè su una rete da 25 host hai settato quasi 50 IP nel pool, non è che c'è un Access Point aperto che rilascia Ip a smartphone o altro?

---

Sicuro al 100% no... Non ho idea di come verificarlo. Diciamo che lo sono al 99 😉

Prova a diminuire il lease da 24H a 2H

Provo a fare questa modifica intanto, grazie.

La cosa che mi perplime, la noto solo ora, e' che la pagina Lan Groups e' vuota. Totalmente vuota.... O.o (ho un po' paura)

[tomasigioielli]

---

EvelinaS ha scritto:

Provi a:

1. Aggiornare la versione del firmware per 4.3.5-3, 

2. Aumentare il range del DHCP 

3. Reset

---

Sto lasciando questa soluzione come ultima spiaggia, perche' al momento il sistema "funziona" (dhcp a parte) e procedere con un aggiornamento + reset vorrebbe dire 1. bloccare l'attivita' del cliente (non ho un apparecchio di rimpiazzo) e 2. correre il rischio, dopo il reset, di perdere tutti i lease dhcp assegnati precedentemente al problema (ci sono diverse periferiche che possono funzionare solo in dhcp) e cio' significherebbe "guai".

Insomma, stro procrastinando, nella speranza che un utente con un problema simile faccia capolino 🙂

[tomasigioielli]

---

EvelinaS ha scritto:

Provi a:

1. Aggiornare la versione del firmware per 4.3.5-3, 

2. Aumentare il range del DHCP 

3. Reset

---

Ri-salve, lo step 1 non ha portato risultati, mentre lo step 2 si'. Al momento il firewall rilascia IP quando delle periferiche lo richiedono.
C'e' una cosa che non torna pero': la pagina "LAN Groups" rimane vuota, mentre prima riportava tutti i client collegati (in DHCP o meno).

Come e' possibile?....

[EvelinaS]

Salve @tomasigioielli,

Ha per caso abilitato la trasmissione ARP in Configurazione di rete -> Impostazioni LAN -> Avanzate -> Advanced IPv4 LAN?

Cordiali Saluti,

Evelina 

Team NETGEAR 

[tomasigioielli]

Affermative, ARP flaggato.

[EvelinaS]

Ha provato ad aggiornare la lista tramite il bottone 'Refresh'? La lista si aggiorna?

Saluti,

Evelina 

Team NETGEAR

[tomasigioielli]

Sì certo, ho provato: la lista rimane vuota....

[EvelinaS]

Grazie per la conferma. Se prova a collegare un dispositivo direttamente al SRX5308 esso viene visualizzato sulla lista? Quale è la topologia della sua rete? 

Saluti,

Evelina 

Team NETGEAR

[tomasigioielli]

Appena ripasso dal cliente faccio una prova collegando un pc direttamente al firewall.

La rete:
Modem fibra dell'ISP > SRX5308.
La LAN è composta da 2 switch GS116 collegati al fw in cascata e 3 AP wifi D-Link (non ricordo il modello esatto).
Poi le varie periferiche, circa 25 tra pc, smartphone, POS, stampanti e videosorveglianza.

[EvelinaS]

Grazie per la celere risposta e altre informazioni.

Rimaniamo in attesa di sue notizie circa il risultato delle prove.

Buona giornata.

Evelina

Team NETGEAR 

[tomasigioielli]

@EvelinaSgrazie per i riscontri.

Ho fatto un test usando un laptop che normalmente ha un IP fisso, mettendolo in dhcp e allacciandolo alla porta del firewall che normalmente ospita il cavo dello switch (l'unica attiva al momento), qundi quest'ultimo era di fatto isolato dalla LAN. Di seguito il log dhcp:

Oct 19 15:13:03 [SRX5308] local7.info [DHCPD]: Wrote 10 leases to leases file.

Oct 19 15:13:02 [SRX5308] local7.info [DHCPD]: DHCPOFFER on 192.168.66.198 to e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:13:01 [SRX5308] local7.info [DHCPD]: DHCPDISCOVER from e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:08:33 [SRX5308] local7.info [DHCPD]: DHCPOFFER on 192.168.66.198 to e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:08:33 [SRX5308] local7.info [DHCPD]: DHCPDISCOVER from e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:08:17 [SRX5308] local7.info [DHCPD]: DHCPOFFER on 192.168.66.198 to e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:08:17 [SRX5308] local7.info [DHCPD]: DHCPDISCOVER from e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:08:08 [SRX5308] local7.info [DHCPD]: DHCPOFFER on 192.168.66.198 to e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:08:08 [SRX5308] local7.info [DHCPD]: DHCPDISCOVER from e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:08:04 [SRX5308] local7.info [DHCPD]: DHCPOFFER on 192.168.66.198 to e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:08:04 [SRX5308] local7.info [DHCPD]: DHCPDISCOVER from e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:07:32 [SRX5308] local7.info [DHCPD]: DHCPOFFER on 192.168.66.198 to e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:07:32 [SRX5308] local7.info [DHCPD]: DHCPDISCOVER from e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:07:16 [SRX5308] local7.info [DHCPD]: DHCPOFFER on 192.168.66.198 to e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:07:16 [SRX5308] local7.info [DHCPD]: DHCPDISCOVER from e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:07:09 [SRX5308] local7.info [DHCPD]: DHCPOFFER on 192.168.66.198 to e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:07:09 [SRX5308] local7.info [DHCPD]: DHCPDISCOVER from e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:07:05 [SRX5308] local7.info [DHCPD]: DHCPOFFER on 192.168.66.198 to e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:07:05 [SRX5308] local7.info [DHCPD]: DHCPDISCOVER from e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:07:02 [SRX5308] local7.info [DHCPD]: DHCPOFFER on 192.168.66.198 to e0:3f:49:be:9f:0f (PIETRO2014bz) via eth0.1
Oct 19 15:07:01 [SRX5308] local7.info [DHCPD]: DHCPDISCOVER from e0:3f:49:be:9f:0f via eth0.1

Ho controllato dal laptop la pagina "Lan Grops" appena ottenuto l'IP e l'ho trovata sempre vuota.

[tomasigioielli]

Gentile @EvelinaS

e' la quarta volta che inserisco questa risposta, non capisco perche' dopo 2 minuti sparisce dal thread... O.o

Provo a re-inserirla, questa volta metto il log DHCP come immagine anziche' come testo.

Ho fatto un test usando un laptop che ha sempre un IP fisso. Una volta messo in dhcp l'ho collegato al firewall usando la stessa porta a cui e' collegato lo switch (e' l'unica abilitata al momento), isolandolo di fatto il fw dalla lan. Log DHCP in allegato.

Appena ottenuto l'IP (come mai tanti tentativi?...) ho controllato la pagina Lan Grous e l'ho trovata di nuovo vuota.

[EvelinaS]

Gentile @tomasigioielli,

grazie per la risposta e gli screen shot.  

A questo punto suggerirei di resettare il Firewall. Tuttavia prima di resettarlo salvi una copia della configurazione. In seguito prima di ripristinare la configurazione salvata esegua nuovamente la prova con il laptop. In questo modo isoleremo la problematica, se è legata alla configurazione.

Saluti, 

Evelina

Team NETGEAR ​​​​​​​