curl
两条命令，而它们之间的区别就是全部价值所在。
curl-host
Section titled “curl-host”在主机网络命名空间中运行 —— 即节点自身的连通性，尚未涉及数据平面。
{"command":["curl-host","-v","cloud.f5.com"]} % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying <public-ip>:80...* Connected to cloud.f5.com (<public-ip>) port 80 (#0)> GET / HTTP/1.1> Host: cloud.f5.com> User-Agent: curl/7.76.1> Accept: */*>* Mark bundle as not supporting multiuse< HTTP/1.1 301 Moved Permanently< location: https://cloud.f5.com/< server: volt-adc< date: Mon, 03 Aug 2026 16:30:24 GMT< connection: close< content-length: 0< 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Closing connection 0curl-vega
Section titled “curl-vega”在 Vega（控制平面）上下文中运行，而非主机上下文。可观察到的差异，也是此处唯一确定的差异，是它所继承的环境：curl-vega 报告的 NO_PROXY 列表涵盖了各私有地址段、int.ves.io、int.volterra.us 以及站点自身的 .tenant.local 域，而 curl-host 则不报告任何内容。这对 DNS 路径意味着什么，并未经过实测。
{"command":["curl-vega","-v","cloud.f5.com"]}* Uses proxy env variable NO_PROXY == '10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,100.127.0.0/18,100.127.192.0/18,169.254.0.0/16,int.ves.io,int.volterra.us,mcn-ce-ha-eastus01.<tenant>.tenant.local' % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying <public-ip>:80...* Connected to cloud.f5.com (<public-ip>) port 80 (#0)> GET / HTTP/1.1> Host: cloud.f5.com> User-Agent: curl/7.76.1> Accept: */*>* Mark bundle as not supporting multiuse< HTTP/1.1 301 Moved Permanently< location: https://cloud.f5.com/< server: volt-adc< date: Mon, 03 Aug 2026 16:30:26 GMT< connection: close< content-length: 0< 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Closing connection 0两者都接受作为独立数组元素传入的常规 curl 参数。值得保留 -v，因为连接与 TLS 握手相关的输出行通常正是故障显现之处。