Difference between site local inside and site local outside ?
Hi all, While reading the F5 distributed cloud documents for virtual network I got lost. Can someone please help me to clarify that what is the difference between the "site local inside" and "site local outside" virtual network. What I read the difference comes in when you configure network connectors, for connecting site local inside and site local outside we will have one additional option in this case and that is the SNAT option, is there any other difference exist between two virtual networks. Secondly when you read F5 networks it says that there could be only one network of this type at particular site (as mentioned in the snapshot below). What does this mean, cant we configure two local-inside type virtual network at one site and if yes then I don't understand why there is an option to configure virtual network of this type ?Distributed Cloud customers: Earn $25 for writing a review
TrustRadius is offering a $25 gift card (or charitable donation) to anyone who writes a review about their experience with F5 Distributed Cloud products. If you’re using one of the products below, we would love to have you write a review. Not only will our product teams and future customers learn from your experience, but you’ll also help us qualify for the 2024 TrustRadius Top Rated awards. Simply click on the links for your product(s) and look for the “write a review” button at the top of the page. WAF Bot Defense API Security Network Connect It takes 10-15 minutes and you can choose to stay anonymous. We’re really hoping to get a few new reviews before March 27 th . Your help will be greatly appreciated! If you you want to earn another $25, head on over and wright a review on Gartner Peer Insights. A review on any F5 product is eligible for the $25 gift card or charitable donation.
Is there a list of the F5 XC API protections OpenAPI/Swagger custom supported extensions ?
Hello to Everyone, After my investigation of the OpenAPI/Swagger options for AWAF/ASM that I have questions underF5 AWAF/ASM support for wildcard url and parameter... - DevCentralthat I have still have questions now I have the same questions for XC Swagger/OpenAPI supported custom options and if there is a list? I see that XC supports Regex for wildcard in the path as shown below but what about parameters with wildcard names or if there could be a wildcard support for methods as to not have to specify each method under an http path or using custom word like "any" ? Other than that it will be nice if there is support for parameters to be specified as in any location not query or request body. Any help will appreciated. }, "servers": [ { "url": "/" } ], "paths": { "/niki.*": { "parameters": [ { "in": "query", "name": "userId", "schema": { "type": "integer" }, "required": true, "description": "Numeric ID of the user to get" }ProTip - Step away from your bias
Posted this on the socials, but wanted to document here as well... #ProTip- Constant struggle when learning new tech: stepping back and analyzing what is, rather than what is perceived. It's super easy to point finger at what is new and unknown and thus delay finding the real problem is in the stuff you already know. Today's example: I was trying to get anF5 Distributed Cloud (F5XC)service on a virtual k8s site to work outside the pod. Still learning the nuances of F5XC services, so my focus on the problem was squarely in what I was probably doing wrong there, but COMPLETELY ignored that the workload I was trying to service was built on the default http port, and my service was set up as 8080, and thus rejected my requests. Thanks toMichaelatF5for talking me off the ledge... 🙂
