You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When http proxy is in place to access internet resources containerlab users typically have to set the http_proxy/https_proxy env vars in their topologies to make the applications running in the containers use the proxy:
Note, how every lab node, lab mgmt network and localhost has to be called out in the no_proxy env var to ensure that the nodes when communicating with each other will not try to reach the proxy.
Containerlab should set these values automatically as a default env var set:
all node names as provided in the topology
mgmt network
localhost
127.0.0.1
*.local addresses
The text was updated successfully, but these errors were encountered:
Would really love to see this feature implemented!
Subnet ranges do not work with the no_proxy variable for some OS. Hostname wildcards can be used, but IP addresses should also be added individually not only via CIDR.
Edit: Might deliver a PR myself in the coming days 😄
When http proxy is in place to access internet resources containerlab users typically have to set the http_proxy/https_proxy env vars in their topologies to make the applications running in the containers use the proxy:
Note, how every lab node, lab mgmt network and localhost has to be called out in the
no_proxy
env var to ensure that the nodes when communicating with each other will not try to reach the proxy.Containerlab should set these values automatically as a default env var set:
The text was updated successfully, but these errors were encountered: