PaoloFracas  Ally Member

By placing the device to be monitored in a dedicated VLAN could I monitor the traffic between the LAN and the device?! So a Smart Managed Switch would be enough for me. Right?

Thanks Peter, In addition to the type of Firewall (USG FLEX 100 in my case), I assume that one of the prerequisites is a Managed Switch. Which is not my case. Unfortunately.

I'll try. Thanks

Sorry for delay. Unfortunately the solution doesn't work. It doesn't monitor internal LAN traffic, which is what I need. Monitors traffic from LAN to VLAN and vice versa but not LAN to LAN traffic. Thanks anyway

I apologize for the delay in responding but the last two weeks have been particularly intense. I am flattered by the proposal but the answer is somewhat difficult. On the one hand you can test and influence the logic of new devices but on the other, everything will be subordinated to specific tasks provided by you. At the…

Thanks for all. Have a good day too. Paolo Fracas

Bye bye granularity. Thanks for help. Best Regards Paolo Fracas

Between yesterday and today I ran a simulation for an IKEv2 VPN with Client StrongSwan. Once the simulation was completed, I restored the backup of the Configuration performed before carrying out the checks. The restore was successful.

I confirm that the beta firmware works with a different configuration folder than the consolidated firmware. Verification with Customer Backup was successful so the Firewall problem with TCP port 6281 would seem to be solved. So, we suggest you could monitor the USG Flex 100 for a few days. Thanks.I honestly don't…

I had this state only during the first application of the Beta Firmware.After I was able to load it into the Standbye Partition the problem no longer occurred except with the application of the two configurations which are not loaded with either the consolidated firmware or the beta version.Do you need that I collect the…

Hi Jeff,the data transfer rate is absolutely stable.What do you mean when you say "Once this symptom occurs again". I think that the only way to check the symptom is to upload a firmware more updated that the beta one. That at the moment is not available. I think. It seems that the "stable firmware" work with a…

LATEST TESTS Today I tried to reboot starting from the partition with the Beta Firmware (I backed up the active configuration with the consolidated firmware first).Like the last attempt, booting from the "Beta" Partition returned the configuration to the factory condition. As an example I report the screenshot of the…

Hi sandra_sa,From my analysis the problem is not in the Port Forwarding itself but in the "Firewall Rule" that manages it.If I limit communications to the affected Port only (in my case TCP 6281 for Synology Backup) I have problems. If I allow communication to all services ("Any" parameter) and trust the Port Forwarding…

(1).May I know did the device reboot from V5.32(ABUH.0)ITS-22WK41-1125-221101280 to V5.32 automatically? Do that two firmware run on the same partition or different partitions?After about 15 minutes of inactivity, unable to contact the Firewall, I had to disconnect the power and then reconnect it to see if it…

When I wrote "Restore verified" I meant that after integrating the 10/27/2022 backup I could do a backup/restore configuration test, not that I could restore the 11/23/2022 configuration.This means that every time I restart the Firewall with the beta Firmware the configuration is restored to the factory values and…