Skip to content

W-18670236-Make explicit that TCP traffic is not supported #797

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
luanamulesoft wants to merge 2 commits into
base: latest
Choose a base branch
from
Open

W-18670236-Make explicit that TCP traffic is not supported #797

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
59b7ac0
Make explicit that TCP traffic is not supported
May 30, 2025
d996c4b
Apply suggestion from @bjoson-mulesoft
luanamulesoft Apr 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 1 addition & 7 deletions cloudhub/modules/ROOT/pages/vpc-upgrade.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,13 +53,7 @@ CloudHub VPC doesn't restrict outbound egress traffic, so removing the default f

Non-HTTP/S TCP Traffic::
+
You can send only HTTP and HTTPS traffic to applications in the migrated private space. Upgraded private spaces don't support non-HTTP/S TCP traffic.
+
For in-place migrations with existing network connections (Transit Gateway or VPN), the CloudHub 2.0 private space infrastructure uses an internal IP range (`100.67.x.x`) that differs from the original VPC IP range. This IP range mismatch prevents TCP traffic that requires node-level access from reaching the private space through your on-premise network.
+
To enable TCP traffic for migrated private spaces with network connections, add routes in your on-premise network to reach the private space infrastructure CIDR range, and coordinate with MuleSoft Support for required NAT configuration changes.
+
If you can't add these routes, consider this limitation before starting the in-place migration.
Currently only HTTP and HTTPS traffic can be sent to applications in the migrated Private Space. TCP traffic is not supported at this time.
Comment thread
luanamulesoft marked this conversation as resolved.
Outdated
Copy link
Copy Markdown
Contributor

@bjoson-mulesoft bjoson-mulesoft Apr 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Our standards generally prohibit talking about future possibilities in anything except SF RN. Also, this could be made more concise and AI ready.

Comment thread
luanamulesoft marked this conversation as resolved.
Outdated


== Understand Environment Association
Expand Down
⚡