I have the same issue. Just upgraded a customer to 4.0 MR2 and seeing
these emails now for NTP time adjustments. I can' t imagine why anyone
would want to see these.
They are all 0.0.0.0/0.0.0.0. I believe it' s a routing issue - I can
set up a static route for my client IP on WAN2 and it does work. I think
there' s something I' m not understanding here.
I am having the same issue. Just hooked up WAN2 on a 200A and I cannot
get HTTPS Admin working on that interface. The packets are seen coming
to WAN2 but are not being accepted. fort01 # diag sniffer packet any '
port 443 and host 8.7.25.18' interfac...
