pfSense Gold Subscription

Author Topic: AWS 2.3.4 not able to connect  (Read 345 times)

0 Members and 1 Guest are viewing this topic.

Offline danny-onegini

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
AWS 2.3.4 not able to connect
« on: July 02, 2017, 04:00:47 am »
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?


Code: [Select]
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

Offline popenz

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: AWS 2.3.4 not able to connect
« Reply #1 on: July 07, 2017, 02:59:32 pm »
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...

Offline masterkorp

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: AWS 2.3.4 not able to connect
« Reply #2 on: August 18, 2017, 06:32:52 am »
This also happens to me, i had to launch a previous version.

Offline johnkeates

  • Sr. Member
  • ****
  • Posts: 399
  • Karma: +35/-0
    • View Profile
Re: AWS 2.3.4 not able to connect
« Reply #3 on: September 12, 2017, 11:31:31 pm »
Does AWS not have a serial console or VNC console?

Offline masterkorp

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: AWS 2.3.4 not able to connect
« Reply #4 on: September 13, 2017, 02:56:37 pm »
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.


Offline johnkeates

  • Sr. Member
  • ****
  • Posts: 399
  • Karma: +35/-0
    • View Profile
Re: AWS 2.3.4 not able to connect
« Reply #5 on: September 13, 2017, 03:00:24 pm »
I guess that's where the Amazon Certified thing comes in...