Updates to Sandbox Reservation Internet Access Policy
Due to changes in our networking policies, we are updating the internet access policy within our sandbox reservation instances.
Hosts will no longer have internet access outbound.
This should not affect the overall functionality or access to the resources within the sandbox instances, connecting via VPN.
DevNet Sandbox Team
I'm trying to use the sandbox from my office but as the VPN runs on a non-standard port it's blocked by default. Please could someone advise the IP & port ranges required to be opened to access the sandboxes.
Rather than raise lots of requests I'd just like to get it all done in one hit.
I had a hunt around but couldn't see this documented anywhere.
Good question .. I would like to know as well if there is a set range of ports used.
Might worth asking the dcloud support team - https://dcloud2-lon.cisco.com/support/
and dcloud community - https://community.cisco.com/t5/cisco-dcloud/ct-p/dcloud
The port range will be anywhere from TCP 20100 through TCP 20354. If that's not working, keep in mind VPNs also use TLS (TCP 443) and DTLS (UDP 443). Though typically these are open in most organizations.
There is more information on the devnet sandbox here https://developer.cisco.com/docs/sandbox/#!getting-started
Thanks @bigevilbeard - any word on the headend IPs? I've been on the SJ one and I've seen an EMEA one mentioned on the forums - any others I need to be aware of?
I know the labs are free but I'd really like to see this documented officially somewhere.. we are networkers after all :)