user472292's questions

I have a client connecting to my Azure Virtual Network Gateway (Gateway1) that sits in a Virtual Network (ClientVNet1: 10.13.0.0/16). I want the client to be able to connect to my DB (10.4.2.5) in a different Virtual Network (InternalVnet1: 10.4.0.0/16). I have the VNets successfully peered and connecting to the DB works fine from the client.

I want to add a layer of indirection and have the client connect to 10.13.2.5 (which will forward traffic to 10.4.2.5). I tried to setup a Route Table (for the GatewaySubnet in the ClientVNet1) that forwards all source traffic from 10.13.2.5 to a firewall (Firewall1) in the InternalVnet1. Then in the firewall I tried to setup a DNAT to redirect to 10.4.2.5. This doesn't seem to work. Is this the correct way to go about doing this?

Or do I need to setup a private IP (network interface) with IP Forwarding Enabled, then associate to a VM that acts as a NVA (Network Virtual Appliance)?

I have the following parties:

Org1 - The owner of the application that is being built
Vendor1 - The 3rd party that build the application
Client1 - A consumer of the application
Clinet2 - A consumer of the application

Our application is set up as "multi-tenancy via infrastructure" (i.e. every client gets their own set of servers, DBs, etc. One requirement is that each client has direct access to their database and the database is only accessible over VPN.

To support this we have set up the following VNets:

Clinet1_Internal_VNet - The database lives in this VNet
Clinet2_Internal_VNet - The database lives in this VNet
Vendor1_VNet - Vendor1's VPN connects to a Virtual Network Gateway in this VNET
Clinet1_VPN_VNet - Client1's VPN connects to a Virtual Network Gateway in this VNET
Clinet2_VPN_VNet - Client2's VPN connects to a Virtual Network Gateway in this VNET

Peerings are as follows:

Clinet1_VPN_VNet -> Connects to Clinet1_Internal_VNet
Clinet2_VPN_VNet -> Connects to Clinet2_Internal_VNet
Vendor1_VNet -> Connects to Clinet1_Internal_VNet and Clinet2_Internal_VNet

If I set Clinet1_Internal_VNet to use the (remote) gateway in Clinet1_VPN_VNet connections work.

If I then set Clinet1_Internal_VNet to use the (remote) gateway in Vendor1_VNet I get an error (as you can only have 1 remote gateway per VNet).

I tried to manually add the route (Clinet1_Internal_VNet -> Vendor1_VNet) in a Route Table but the UI doesn't allow that. If I look at traffic I see traffic flow between VNets but it does not go outside (through the gateway).

Is there a way I can accomplish this, keeping the vnet segregation (I understand I can set up a multi site to site VPN in a hub and spoke model, but I'm concerned with Client1 getting access to Client2's VNet).

I have a site-to-site network setup in Azure to allow my servers in Azure connect to some local resources. The gateway is setup with static routing (policy based). If the connection is inactive for 5 minutes, Azure will bring down the connection automatically. This is fine, but for some reason Azure won't bring back up the connection if it has any attempted traffic from Azure -> Local. The only way to bring the connection back up is to generate traffic from Local -> Azure.

When the connection goes down I can't ping or telnet to my local servers from Azure.

Has anyone experienced this before?

Disclaimer: I am not a network engineer, so I apologize for any improper use of terms.

I configured an AWS Load Balancer. It is working find on HTTP, but when I try over HTTPS I get a 504 Gateway Timeout Error. I tried all the suggestions on AWS's help page (increase idle timeout), but no luck. Any ideas why it wouldn't work over HTTPS, but still work over HTTP?

Both the Instance and Load Balancer security groups have HTTP and HTTPS enabled

The load balancer has HTTP and HTTPS listeners (note the LB does not terminate the SSL cert, it has 443 on front and back end port)

If I change it to be 443/80 (front/back) it works.

I do want it to be 443/443. But when I set it up this way I get the 504 error.