Routing multiple VNETS in Azure

helmutderhaas

Hi,

Just using PFSENSE as an appliance in azure to route across multiple VNETS since Azure don't have their own product for routing between Peered networks.

Currently it's setup like

ARM VNET - ARM VNET - ASM VNET
Windows VM PFSENSE - Domain Services IP
10.76.28.32/27 10.76.21.0/29 10.76.20.0/29

IP Address of the Windows VM is 10.76.28.51
pfSense is configured with one interface with the Firewall turned off (so it should just route traffic)

It appears to work, but then it intermittently just stops working

Pinging 10.76.20.4 with 32 bytes of data:
Reply from 10.76.20.4: bytes=32 time=4ms TTL=127
Reply from 10.76.20.4: bytes=32 time=1ms TTL=127
Reply from 10.76.20.4: bytes=32 time<1ms TTL=127
Reply from 10.76.20.4: bytes=32 time<1ms TTL=127
Reply from 10.76.20.4: bytes=32 time=1ms TTL=127
Reply from 10.76.20.4: bytes=32 time<1ms TTL=127
Reply from 10.76.20.4: bytes=32 time=1ms TTL=127
Reply from 10.76.20.4: bytes=32 time=1ms TTL=127
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.76.20.4:
Packets: Sent = 13, Received = 8, Lost = 5 (38% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 4ms, Average = 1ms

IP Forwarding is enabled on the pfSense appliance interface.

Any ideas on what the issue might be ?