Hello all,
There is something I don't understand, I don't know if it is normal or normal or not.
I have started my AW instance with opnsense. There is only one interface so far, I will add the LAN interface later.
I can login to opnsense.
Then I assign an elastic IP to my instance, then on opensene, as soon as I assign this public IP to the WAN interface, after I click on apply change, opnsense becomes unreachable. Even with SSH.
Even if I restart the instances.
WAN interface should have the elastic public IP, not the 172.* gave by AWS right?
Quote from: veptune on September 06, 2024, 03:45:12 PM
WAN interface should have the elastic public IP, not the 172.* gave by AWS right?
Sorry, I've never used an Opnsense on AWS, but if it helps you, 172.16.0.0/12 (172.16.0.0 - 172.31.255.255) are private IPs - very unusual for WAN interfaces.
Therefore the WAN-Interface normally needs a
public routeable IP from the LB - "elastic IP" called on AWS?