qui il log di debug del firewall
DHCP: SDiscover attempt # 6 for entry (xid = 0xb81c72e) at 16:18:20 CEDT Sun Mar 25 2018
DHCP: SDiscover broadcast 306 bytes on interface 2
DHCP Broadcast to 255.255.255.255 from 0.0.0.0 on interface 2
DHCP: SDiscover attempt # 7 for entry (xid = 0xb81c72e) at 16:18:28 CEDT Sun Mar 25 2018
DHCP: SDiscover broadcast 306 bytes on interface 2
DHCP Broadcast to 255.255.255.255 from 0.0.0.0 on interface 2
DHCPC: msg received, fip=ANY, fport=0 on outside interface
DHCPC: msg received, fip=ANY, fport=0 on outside interface
DHCPC: msg received, fip=ANY, fport=0 on outside interface
DHCP: SDiscover attempt # 8 for entry (xid = 0xb81c72e) at 16:18:37 CEDT Sun Mar 25 2018
DHCP: SDiscover broadcast 306 bytes on interface 2
DHCP Broadcast to 255.255.255.255 from 0.0.0.0 on interface 2
DHCP: SDiscover attempt # 1 for entry (xid = 0xb81c72e) at 16:18:47 CEDT Sun Mar 25 2018
DHCP: SDiscover broadcast 306 bytes on interface 2
DHCP Broadcast to 255.255.255.255 from 0.0.0.0 on interface 2
DHCP: SDiscover attempt # 2 for entry (xid = 0xb81c72e) at 16:18:50 CEDT Sun Mar 25 2018
DHCP: SDiscover broadcast 306 bytes on interface 2
DHCP Broadcast to 255.255.255.255 from 0.0.0.0 on interface 2
DHCP: SDiscover attempt # 3 for entry (xid = 0xb81c72e) at 16:18:54 CEDT Sun Mar 25 2018
DHCP: SDiscover broadcast 306 bytes on interface 2
DHCP Broadcast to 255.255.255.255 from 0.0.0.0 on interface 2
sembra che non ci sia risposta alle richieste DHCP, e (non ho screen perchè non compariva sempre) sembra che sia lo stesso modem che raccoglieva le richieste DHCP e rispondeva con no pool available for DHCP. Quindi il firewall non veniva correttamente bridgiato verso la parte DSL e qui screen della parte DSL mentre è in bridge
