# AAP 2.5 - Proxy settings do not support CIDR notation (/24) in NO\_PROXY

**URL:** <https://forum.ansible.com/t/aap-2-5-proxy-settings-do-not-support-cidr-notation-24-in-no-proxy/40032>\
**Category:** Get Help\
**Tags:** aap-beta, proxy, aap, ansible-project, awx\
**Created:** [February 4, 2025, 9:35am UTC](https://forum.ansible.com/t/aap-2-5-proxy-settings-do-not-support-cidr-notation-24-in-no-proxy/40032 "2025-02-04T09:35:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![selvi](https://avatars.discourse-cdn.com/v4/letter/s/71c47a/32.png) [@selvi](https://forum.ansible.com/u/selvi)\
**Post date:** [February 4, 2025, 9:35am UTC](https://forum.ansible.com/t/aap-2-5-proxy-settings-do-not-support-cidr-notation-24-in-no-proxy/40032/1 "2025-02-04T09:35:43Z")

</div>

**I am trying to define proxy setting in the extra environmental variables in Job settings like below**

```auto
NO_PROXY = { 
    "HTTPS_PROXY": "http://proxy.example.com:3128",
    "HTTP_PROXY": "http://proxy.example.com:3128",
    "NO_PROXY": "127.0.0.1,localhost,.example.com, 172.20.0.0/24" 
} 

```

AAP doesn’t recognize the “/24” format; instead, if I define individual IP addresses, it works fine.

Is it not supported in AAP 2.5, or did I do anything wrong in this context?

Thanks

---

<div class="post-metadata">

**Author:** ![TJuberg](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/tjuberg/32/7958_2.png) [@TJuberg](https://forum.ansible.com/u/TJuberg)\
**Post date:** [March 21, 2025, 8:07pm UTC](https://forum.ansible.com/t/aap-2-5-proxy-settings-do-not-support-cidr-notation-24-in-no-proxy/40032/2 "2025-03-21T20:07:19Z")

</div>

Probably not what you wanted to hear, but NO\_PROXY does not generally support anything but domains/hostnames, domain/hostname wildcards and full IP.

It is also limited by whatever size limitation exists either on OS level or application level for permitted lenght of variables and their content.

[We need to talk: Can we standardize NO\_PROXY?](https://about.gitlab.com/blog/2021/01/27/we-need-to-talk-no-proxy/) while a few years old now gives a good primer on the limitations and frustrations that is NO\_PROXY.

So you really need to know what underlying library will be using the NO\_PROXY env, and on top of it, wildcards do not work on IP’s as standard, and there is no feasible way to fit RFC1819 IP’s explicitly within NO\_PROXY  
All of RFC1819 would take somewhere around 279160KB (~272MB) and the common limits if memory serves is 128KB or 256KB.

The only feasible way is to avoid using IP’s and rather use hostnames which do allow sane NO\_PROXY wildcards unless you know that NO\_PROXY will be used in curl, wget or any other tool that is a new enough version to support CIDR.