cblair

Reactions

0 Promote 0 Like 0 Boom 0 LOL 0 Spam 0 Abuse

Comments

  • Just to close the loop here. I spoke with Tech Support. The issue was with our Ping Policy. It was routing those packets per the SD-WAN policy. After unchecking the Route outbound traffic using SD-WAN Based Routing, we were able to ping sslvpn clients. Thanks again for the help!
    in SSLVPN Routing Comment by cblair March 2020
  • Thanks for your time! I will update when I find a solution.
    in SSLVPN Routing Comment by cblair March 2020
  • I do have those same entries in the status report. Our SSLVPN range is 172.16.13.X. 172.16.10.X is our 'main network'. The following was in the logs - 2020-03-19 10:46:56 Allow src_ip=172.16.10.42 dst_ip=172.16.13.2 pr=icmp src_port= dst_port= src_intf=0-MainNetwork dst_intf=5-FiberWAN msg=Allowed pckt_len=92 ttl=2…
    in SSLVPN Routing Comment by cblair March 2020
  • Bruce - Thanks for the reply. When i run a tracert from the main network to 172.16.13.5, which is a person connected to the SSLVPN, the packet hits the firewall and then is routed out through our Internet service - Tracing route to 172.16.13.5 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 172.16.10.253 2 <1 ms <1 ms <1 ms…
    in SSLVPN Routing Comment by cblair March 2020