Cloud VPN 터널 또는 VLAN 연결을 관리하는 Cloud Router의 BGP 세션이 외부 네트워크에서 특정 프리픽스(대상)를 수신했는지 확인합니다. 네트워크에 자체 로컬 기본 경로가 있으므로 기본 경로(대상 0.0.0.0/0)를 Cloud Data Fusion VPC 네트워크로 가져올 수 없습니다. 대상의 로컬 경로는 Cloud Data Fusion 피어링이 VPC 네트워크에서 커스텀 경로를 가져오도록 구성되어 있더라도 항상 사용됩니다.
비공개 서비스 연결에서 생성한 피어링 연결을 식별합니다. 서비스에 따라 비공개 서비스 연결에서 다음 피어링 연결 중 하나 이상을 만들 수 있지만 반드시 모든 피어링 연결을 구성할 필요는 없습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eCloud Data Fusion instances must be connected through the same VPC network as the external network they are accessing.\u003c/p\u003e\n"],["\u003cp\u003eConnecting an external network requires using Cloud VPN tunnels or VLAN attachments, with the VPC network connected to the external network via these methods.\u003c/p\u003e\n"],["\u003cp\u003eBGP sessions managing Cloud VPN tunnels or VLAN attachments must receive specific prefixes from the external network, and default routes are not allowed.\u003c/p\u003e\n"],["\u003cp\u003ePeering connections generated by the private services connection must be identified and updated to allow the export of custom routes.\u003c/p\u003e\n"],["\u003cp\u003eA Cloud Router custom advertised route must be created for the allocated IP range on the Cloud Routers managing BGP sessions.\u003c/p\u003e\n"]]],[],null,["# Connect to an external network\n\nTo connect to a resource in an external network (an on-premises network or\nanother Virtual Private Cloud (VPC) network), the external network and\nCloud Data Fusion instance must be connected through the same\nVPC network.\n\nTo connect an external network to the Cloud Data Fusion VPC\nnetwork using Cloud VPN tunnels with border gateway protocol (BGP) routing or\nVLAN attachments, do the following:\n\n- Ensure your VPC network is connected to the external network using a [Cloud VPN tunnel](/network-connectivity/docs/vpn/concepts/overview) or a VLAN attachment for [Dedicated Interconnect](/network-connectivity/docs/interconnect/how-to/dedicated/provisioning-overview) or [Partner Interconnect](/network-connectivity/docs/interconnect/how-to/partner/provisioning-overview).\n- Ensure the BGP sessions on the Cloud Router managing your Cloud VPN tunnels or VLAN attachments have received specific prefixes (destinations) from your external network. Default routes (destination 0.0.0.0/0) cannot be imported into the Cloud Data Fusion VPC network because that network has its own local default route. Local routes for a destination are always used, even though the Cloud Data Fusion peering is configured to import custom routes from your VPC network.\n- [Identify the peering connections](/vpc/docs/configure-private-services-access#listing-connections) produced by the private services connection. Depending on the service, the private services connection might create one or more of the following peering connections, but not necessarily all of them:\n - `datafusion-googleapis-com`\n - `servicenetworking-googleapis-com`\n- [Update all of the peering connections](/vpc/docs/using-vpc-peering#update-peer-connection) to enable Export custom routes.\n- [Identify the allocated range](/vpc/docs/configure-private-services-access#listing_allocated_ip_address_ranges) used by the private services connection.\n- [Create a Cloud Router custom advertised route](/network-connectivity/docs/router/how-to/advertising-custom-ip) for the allocated range on the Cloud Routers managing BGP sessions for your Cloud VPN tunnels or VLAN attachments.\n\nWhat's next\n-----------\n\n- Learn how to [create a private instance in Cloud Data Fusion](/data-fusion/docs/how-to/create-private-ip)."]]
