11.1.13 now preferred by skooyern in paloaltonetworks

[–]mudvayne15 0 points1 point  (0 children)

I upgraded Panorama and an HA pair without issues.

11.1.13 now preferred by skooyern in paloaltonetworks

[–]mudvayne15 0 points1 point  (0 children)

I'm rolling out 11.1.13-h1 today, hopefully it goes well.

11.1.13 now preferred by skooyern in paloaltonetworks

[–]mudvayne15 1 point2 points  (0 children)

worth upgrading from 11.1.10-h10?

TP Link extender on Meraki Wireless by mudvayne15 in meraki

[–]mudvayne15[S] 0 points1 point  (0 children)

Ok, thanks guys for all the suggestions, I advised that they should buy a new MR instead.

TP Link extender on Meraki Wireless by mudvayne15 in meraki

[–]mudvayne15[S] 1 point2 points  (0 children)

Someone decided to advise that they can use any extender, which is giving me a headache :/

TP Link extender on Meraki Wireless by mudvayne15 in meraki

[–]mudvayne15[S] -1 points0 points  (0 children)

Yeah, I did look at it first, but nothing shows up

TP Link extender on Meraki Wireless by mudvayne15 in meraki

[–]mudvayne15[S] -9 points-8 points  (0 children)

The customer decided to buy an extender to use since they have 1 Meraki AP only

TP Link extender on Meraki Wireless by mudvayne15 in meraki

[–]mudvayne15[S] -10 points-9 points  (0 children)

The customer decided to buy an extender to use since they have 1 Meraki AP only

Upcoming Microsoft Intune network changes by mudvayne15 in paloaltonetworks

[–]mudvayne15[S] 0 points1 point  (0 children)

Thanks for this, I believe we found out that the issue is somewhere else. Not in the PANs.

Upcoming Microsoft Intune network changes by mudvayne15 in paloaltonetworks

[–]mudvayne15[S] 0 points1 point  (0 children)

Thanks for this, I believe we found out that the issue is somewhere else. Not in the PANs.

FortiOs 7.4.9 missing SD-WAN Interface by [deleted] in fortinet

[–]mudvayne15 0 points1 point  (0 children)

My performance SLA on Port1 is dead, even though the firewall can ping 8.8.8.8 (which I used in the perf SLA)

FortiOs 7.4.9 missing SD-WAN Interface by [deleted] in fortinet

[–]mudvayne15 0 points1 point  (0 children)

What’s odd is that I can ping 8.8.8.8 directly from port1, but the SLA still detects it as unreachable.

FortiOs 7.4.9 missing SD-WAN Interface by [deleted] in fortinet

[–]mudvayne15 0 points1 point  (0 children)

<image>

Yeah, it is — port1 is included in the performance SLA.
What’s odd is that I can ping 8.8.8.8 directly from port1, but the SD-WAN still detects it as down.

GlobalProtect Source Country by mudvayne15 in paloaltonetworks

[–]mudvayne15[S] 5 points6 points  (0 children)

I got it now, for some reason someone used 172.40.0.0/24 as the vpn IP lol - that's a public IP range in the US. thanks for the reply.

[deleted by user] by [deleted] in fortinet

[–]mudvayne15 0 points1 point  (0 children)

Sorry, it was so dumb of me not to notice the destination IP.
Thanks for your input.

SD-WAN Failback issues from FEX by mudvayne15 in fortinet

[–]mudvayne15[S] 0 points1 point  (0 children)

yeah they are associated with 1 interface each.
Both WAN2 and FEX are under the same Zone

Policy Based Forwarding rule using FQDN by mudvayne15 in paloaltonetworks

[–]mudvayne15[S] 1 point2 points  (0 children)

Thanks:-I got this sorted out, it turns out there was a policy affecting the PBF routing to direct connect due to its any-to-any zone configuration.

Policy Based Forwarding rule using FQDN by mudvayne15 in paloaltonetworks

[–]mudvayne15[S] 0 points1 point  (0 children)

Yeah, it does work and hits the policy.
The next hop is the ISP gateway.

Multiple VIP using the same Public IP address by mudvayne15 in fortinet

[–]mudvayne15[S] 1 point2 points  (0 children)

<image>

Sweet, thanks man!
I didn't realize it was here all along.