Selective handling of traffic received from on-premises data centers

1. A method comprising:

receiving, by a redirector (RD) in a cloud hosted data center, a packet originating from a source device in an on-premises data center, the packet belonging to a connection and being directed to a particular destination IP address associated with a router located in the cloud hosted data center, wherein a destination address field in a header of the packet is set to the particular destination IP address;

determining, by the RD, whether the packet addressed to be directed to the router is to be forwarded to the router or whether the packet is to be forwarded to a host machine implementing a service host in a virtual cloud network (VCN), the determining being performed based on a pair of IP addresses associated with the connection, the pair of IP addresses including a source IP address of the source device and the particular destination IP address of the router;

responsive to determining by the RD that the packet is to be forwarded to the host machine:

modifying, by the RD, the destination address field to be set to an address associated with the service host; and

causing the packet to be forwarded to the host machine; and

responsive to determining by the RD that the packet is to be forwarded to the router, forwarding, by the RD, the packet to the router.

2. The method of claim 1 , wherein the determining further comprises:

comparing, by the RD, the pair of IP addresses associated with the connection to information associated with a plurality of connections maintained in a database, wherein each of the plurality of connections is associated with a unique pair of IP addresses; and

verifying, by the RD, whether the pair of IP addresses associated with the connection matches any one of the unique pair of IP addresses.

3. The method of claim 1 , wherein responsive to determining by the RD that the packet is to be forwarded to the host machine, the method further comprises:

transmitting, by the RD, the packet to a gateway; and

forwarding, by the gateway, the packet to the host machine.

4. The method of claim 3 , wherein the gateway, the router, and the RD are located in a service enclave of the cloud hosted data center.

5. The method of claim 3 , further comprising:

obtaining, by the RD, route information that is advertised by the router and associated with the particular destination IP address; and

re-advertising, by the RD, the route information to the gateway as preferential route information associated with the particular destination IP address.

6. The method of claim 1 , wherein the service host corresponds to a compute instance implemented in software that is programmed to terminate the connection at a tunnel end-point (TEP).

7. A computing device located in a cloud hosted data center, the computing device comprising:

a processor; and

a memory including instructions that, when executed with the processor, cause the computing device to, at least:

receive a packet originating from a source device in an on-premises data center, the packet belonging to a connection and being directed to a particular destination IP address associated with a router located in the cloud hosted data center, wherein a destination address field in a header of the packet is set to the particular destination IP address;

determine, whether the packet addressed to be directed to the router is to be forwarded to the router or whether the packet is to be forwarded to a host machine implementing a service host in a virtual cloud network (VCN) based on a pair of IP addresses associated with the connection, the pair of IP addresses including a source IP address of the source device and the particular destination IP address of the router;

responsive to determining that the packet is to be forwarded to the host machine:

modify the destination address field to be set to an address associated with the service host; and

cause the packet to be forwarded to the host machine; and

responsive to determining that the packet is to be forwarded to the router, forwarding the packet to the router.

8. The computing device of claim 7 , wherein the instructions when executed with the processor, causes the computing device to further:

compare the pair of IP addresses associated with the connection to information associated with a plurality of connections maintained in a database, wherein each of the plurality of connections is associated with a unique pair of IP addresses; and

verify whether the pair of IP addresses associated with the connection matches any one of the unique pair of IP addresses.

9. The computing device of claim 7 , wherein responsive to determining that the packet is to be forwarded to the host machine, the computing device is further configured to:

transmit the packet to a gateway; and

forward, by the gateway, the packet to the host machine.

10. The computing device of claim 9 , wherein the gateway, the router, and the computing device are located in a service enclave of the cloud hosted data center.

11. The computing device of claim 9 , wherein the instructions when executed with the processor, causes the computing device to further:

obtain route information that is advertised by the router and associated with the particular destination IP address; and

re-advertise the route information to the gateway as preferential route information associated with the particular destination IP address.

12. The computing device of claim 7 , wherein the service host corresponds to a compute instance implemented in software that is programmed to terminate the connection a tunnel end-point (TEP).

13. A non-transitory computer readable medium storing specific computer-executable instructions that, when executed by a processor, cause a computer system to at least:

receive, by a redirector (RD) in a cloud hosted data center, a packet originating from a source device in an on-premises data center, the packet belonging to a connection and being directed to a particular destination IP address associated with a router located in the cloud hosted data center, wherein a destination address field in a header of the packet is set to the particular destination IP address;

determine, by the RD, whether the packet addressed to be directed to the router is to be forwarded to the router or whether the packet is to be forwarded to a host machine implementing a service host in a virtual cloud network (VCN) based on a pair of IP addresses associated with the connection, the pair of IP addresses including a source IP address of the source device and the particular destination IP address of the router;

responsive to determining by the RD that the packet is to be forwarded to the host machine:

modify, by the RD, the destination address field to be set to an address associated with the service host; and

cause the packet to be forwarded to the host machine; and

responsive to determining by the RD that the packet is to be forwarded to the router, forward, by the RD, the packet to the router.

14. The non-transitory computer readable medium of claim 13 , wherein the computer system is further configured to:

compare, by the RD, the pair of IP addresses associated with the connection to information associated with a plurality of connections maintained in a database, wherein each of the plurality of connections is associated with a unique pair of IP addresses; and

verify, by the RD, whether the pair of IP addresses associated with the connection matches any one of the unique pair of IP addresses.

15. The non-transitory computer readable medium of claim 13 , wherein responsive to determining by the RD that the packet is to be forwarded to the host machine, the computer system is further configured to:

transmit, by the RD, the packet to a gateway; and

forward, by the gateway, the packet to the host machine.

16. The non-transitory computer readable medium of claim 15 , wherein the gateway, the router, and the RD are located in a service enclave of the cloud hosted data center.

17. The non-transitory computer readable medium of claim 13 , wherein the service host corresponds to a compute instance implemented in software that is programmed to terminate the connection a tunnel end-point (TEP).