-
Re: After upgrade 12.7.2 or higher, can't not connect gateway on Firebox in internal?
FYI - you can provide full private IP addresses & subnets without any security exposure to you. Verify that the L3 switch has an IP addr from the trusted interface subnet. Check the firewall ARP … (View Post)1 -
Re: smtp connection behind WG?
The policy that you see is an Outgoing policy which allows out all TCP & UDP packets, and will allow out TCP port 587. It is not a TCP-UDP proxy policy. Explain your DMZ setup. Did you have somet… (View Post)1 -
Re: After upgrade 12.7.2 or higher, can't not connect gateway on Firebox in internal?
You will only see denied packets and proxy strip type packets in Traffic Monitor. To see allowed packets, you need to enable Logging on policies of interest. Is your PC getting a an IP addr from the … (View Post)1 -
Re: After upgrade 12.7.2 or higher, can't not connect gateway on Firebox in internal?
Also review this Known Issue: Traffic Monitor fails to show traffic logs after 1 December 2021 https://portal.watchguard.com/wgknowledgebase?type=Known%20Issues&SFDCID=kA16S000000SNhXSAW (View Post)1 -
Re: smtp connection behind WG?
Anything in Traffic Monitor related to this? The default Outgoing policy should allow out all TCP packet types, including TCP port 587. If you have a TCP-UDP proxy in your config, it could be interce… (View Post)1
