AWS 2.3.4 not able to connect

danny-onegini

Hi All,

I want to use pFsense on AWS with a C4 instance type, but i am not able to get 2.3.4 up and running. 2.3.2 is working fine.
It looks like that the network device name changed from XN0 to ixv0. But without network i am not able to get in to the machine…

does anybody have an idee to solve this?


Welcome to pfSense 2.3.4-RELEASE on the 'pfSense' platform...

realpath: /dev/dumpdev: No such file or directory
Dump device does not exist.  Savecore not run.
Creating symlinks......ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/ipsec /usr/local/lib/perl5/5.24/mach/CORE
32-bit compatibility ldconfig path: /usr/lib32
done.
External config loader 1.0 is now starting...
Launching the init system....... done.
Initializing.................. done.
Starting device manager (devd)...done.
Loading configuration......done.
.....Warning: Configuration references interfaces that do not exist: xn0

Network interface mismatch -- Running interface assignment option.

Valid interfaces are:

ixv0   0a:8d:69:ef:4d:56 (down) Intel(R) PRO/10GbE Virtual Function Network Driv

Do VLANs need to be set up first?
If VLANs will not be used, or only for optional interfaces, it is typical to
say no here and use the webConfigurator to configure VLANs later, if required.

Should VLANs be set up now [y|n]? ixv0: link state changed to UP

popenz

I'm having the same problem with the pfSense AMI from the AWS AMI marketplace: http://i.imgur.com/NpXipty.png

Not sure how to get past this interactive prompt during system boot…

masterkorp

This also happens to me, i had to launch a previous version.

Does AWS not have a serial console or VNC console?

masterkorp

@johnkeates:

Does AWS not have a serial console or VNC console?

Hello,

No aws does not offer any kind of serial or VNC console, it only offers a display for system messages. The connect client is a in browser SSH client, but the pfsense images does not boot to that point.

I guess that's where the Amazon Certified thing comes in…

renanwilliam

Still having problem with this in 2020.

renanwilliam

After some hours spent in this problem, finally can solve it. The main problem here is because when you change on EC2 panel to a instance that require enhance networking (and enable it via CLI) from a old one, the AWS system change the network interface names and pfSense can't bring up the network connection and the instance become unavailable.

The workaround is:

SSH on pfSense instance and start a shell session
In this example a use nano as text editor (I'm noob), so it's necessary install via pkg install nano
Edit the pfSense config file: nano /cf/conf/config.xml
Search (Ctrl + W) for <interfaces> (the complete path is pfsense>system>interfaces) and replace the tag if for both wan/lan interfaces with values ena0 and ena1 respectively. Remember to save using Ctrl + X. Example file:

<interfaces>
  <wan>
     ...
     <if>ena0</if>
     ...
   </wan>
   <lan>
      ...
      <if>ena1</if>
      ...
   </lan>
..
</interfaces>

Shutdown the instance on EC2 panel (remember to check if termination protection is enabled)
Execute this command using aws cli on your local machine to enable enhanced networking:
aws ec2 modify-instance-attribute --instance-id I-INSTANCE_ID --ena-support
Go to EC2 console, select the instance and change the instance type according your needs on "Actions > Instance Settings > Change Instance Type" (for me is a t3a.medium)
Turn on your pfSense instance in EC2 panel and everything will be fine