[WARP] Added note source ips (#26862)

* added note

* added note to lb

* refined text

* Update src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/warp-connector/tips.mdx

Co-authored-by: ranbel <101146722+ranbel@users.noreply.github.com>

---------

Co-authored-by: ranbel <101146722+ranbel@users.noreply.github.com>

Author: marciocloudflare

src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/warp-connector/tips.mdx

@@ -24,6 +24,10 @@ For Amazon Web Services (AWS) deployments:
 		| ----------- | ------ |
 		| `0.0.0.0/0` | `eni-11223344556677889` |
 
+## Source IPs for Cloudflare services
+
+When Cloudflare services such as [Load Balancing](/load-balancing/) send traffic to your private network through WARP Connector, the traffic originates from a configurable IP range (default `100.64.0.0/12`). You may need to [configure Cloudflare source IPs](/cloudflare-one/networks/connectors/wan-tunnels/configuration/manually/how-to/configure-cloudflare-source-ips/) to avoid IP conflicts or align with your IP address management plan.
+
 ## WARP Connector with cloudflared
 
 WARP Connector and [`cloudflared`](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/) can run together on the same Linux host. This configuration is useful when you want to use WARP Connector as a gateway for your private network, while also using the `cloudflared` daemon to expose specific applications.

src/content/docs/load-balancing/private-network/magic-wan.mdx

@@ -37,7 +37,7 @@ Pools can be created using either the Cloudflare dashboard or the API. Refer to
 After selecting an IP address and completing the setup, you will be redirected to the Load Balancing dashboard. You can locate your load balancer using the search bar or by filtering for **Private** load balancers. Be sure to note the assigned IP address, as it will be required in the following steps.
 
 :::note
-Traffic from your load balancer will appear to originate from one of Cloudflare’s IP addresses. These IP addresses must be whitelisted to ensure proper traffic flow. Ensure your routing is properly configured to return traffic to your Magic WAN tunnels and not the public Internet. Private Load Balancers created with a Cloudflare private IP address will receive an address in the CGNAT range `100.112.0.0`.
+Traffic from your load balancer will appear to originate from one of Cloudflare's IP addresses. These IP addresses must be whitelisted to ensure proper traffic flow. Ensure your routing is properly configured to return traffic to your Magic WAN tunnels and not the public Internet. Private Load Balancers created with a Cloudflare private IP address will receive a default address in the CGNAT range `100.112.0.0`. This IP address is configurable. Refer to [Cloudflare source IP range](/cloudflare-one/networks/connectors/wan-tunnels/configuration/manually/how-to/configure-cloudflare-source-ips/) to learn more.
 :::
 
 ## 3. FQDN override (optional)
@@ -51,6 +51,6 @@ To create the override, follow these steps:
    - The **Selector** equals `Host`
    - The **Operator** equals `is`
    - The **Value** is the hostname you wish to associate with your load balancer.
-3. Set the **Action** to _Override_, and in **Override Hostname**, enter the IP address of your Private Load Balancer. 
+3. Set the **Action** to _Override_, and in **Override Hostname**, enter the IP address of your Private Load Balancer.
 
 Requests to the hostname will now resolve to your private load balancer.