Site-to-site VPN tunnel shows up but traffic returns through wrong route
Field Summary
Site-to-site VPN tunnel shows up but traffic returns through wrong route is a Firewalls & Routing ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
Published app works internally but external redirect loop persists
Field Summary
Published app works internally but external redirect loop persists is a Firewalls & Routing ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
Static route added but traceroute still follows default path
Field Summary
Static route added but traceroute still follows default path is a Firewalls & Routing ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
Geo block enabled but approved vendor traffic also blocked
Field Summary
Geo block enabled but approved vendor traffic also blocked is a Firewalls & Routing ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
Application publish rule works by IP not FQDN
Field Summary
Application publish rule works by IP not FQDN is a Firewalls & Routing ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
- Read more about Application publish rule works by IP not FQDN
- Log in to post comments
New ISP circuit installed but outbound policy still uses old WAN
Field Summary
New ISP circuit installed but outbound policy still uses old WAN is a Firewalls & Routing ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
Firewall HA pair syncs config but not session state
Field Summary
Firewall HA pair syncs config but not session state is a Firewalls & Routing ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
Site to site tunnel up but only one subnet passes traffic
Field Summary
Site to site tunnel up but only one subnet passes traffic is a Firewalls & Routing ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
Router rebooted and static routes disappeared
Field Summary
Router rebooted and static routes disappeared is a Firewalls & Routing ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
- Read more about Router rebooted and static routes disappeared
- Log in to post comments
Firewall rules present but traffic still blocked
Field Summary
Firewall rules present but traffic still blocked is a Firewalls & Routing ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.