AWS Direct Connect

mcjim2k

I'm working towards connecting our PFSense (2.5.1) box to our AWS Direct Connect we had working with a raw Ubuntu 18.04 and FRR installation.

Unfortunately I'm stuck not being able to ping my Amazon router peer IP.

This is how I have stuff setup so far:

The pfsense box has two NICs configured in a LAGG to the switch (the lagg has multiple VLANs for varying purposes, all of which are working properly).
A VLAN has been created on that LAGG matching our AWS virtual interface and a new IPv4 interface has been created - AWS Interface.
The AWS Interface has an IPv4 address of 10.40.1.1/30 - I did not use the default generated peer IPs because AWS uses 169.254/16 IPs
I've tested the interface and VLAN on another server with the IP 10.40.1.2/30, connectivity was successful - so the vlan tagged traffic is going across the network properly.
Connected the AWS Direct Connection to the same switch and configured the port as a Tagged VLAN port (with the same VLAN as the AWS Interface) - Netgear M4300

So at this point, I should be able to ping the AWS router IP at 10.40.1.2, but I cannot. 10.40.1.2 is the AWS router IP per my AWS console. I'm testing ping using Diagnostics / Ping, selecting the AWS Interface and entering 10.40.1.2. With response:

PING 10.40.1.2 (10.40.1.2) from 10.40.1.1: 56 data bytes

--- 10.40.1.2 ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss

This connection was working through a different switch and router, so I am assuming the upstream is good and hasn't changed - I've also checked with our provider and they've said nothing has changed.

So at this point, I'm thinking I'm missing something silly with pfsense, or I've goof'd something with our switch's VLAN setup. I was hoping to rule out any PFSense related issues here.

Please let me know if any more details could be useful.

Thanks a lot.