Bug #6459: AWS EC2 Instance should skip interface config in setup wizard - pfSense - pfSense bugtracker

Bug #6459

AWS EC2 Instance should skip interface config in setup wizard

Added by Danny Schuh about 4 years ago. Updated over 2 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Renato Botelho

Category:

Interfaces

Target version:

2.4.2

Start date:

06/06/2016

Due date:

% Done:

100%

Estimated time:

Affected Version:

All

Affected Architecture:

Description

AWS EC2 instances should default to DHCP. EC2 instances are assigned IP addresses via DHCP. If you want to give the instance a static address, you will still need to configure the ENI in EC2. No need to configure this twice unless you are running the DHCPd services.

Associated revisions

Revision bff36903 (diff)
Added by Renato Botelho over 2 years ago

Fix #6459: Skip interfaces config in AWS EC2 wizard

History

#1 Updated by Chris Buechler about 4 years ago

Subject changed from AWS EC2 Instance interfaces should default to DHCP to AWS EC2 Instance should skip interface config in setup wizard
Status changed from New to Confirmed
Target version changed from 2.3.1-p2 to 2.3.2
Affected Version changed from 2.3.1 to All

I presume updated subject is what you're referring to, as it does default to DHCP. It ought to not prompt users in the setup wizard to avoid confusing them.

#2 Updated by Danny Schuh about 4 years ago

Actually, I had skipped the initial setup wizard. I'm looking to eventually deploy this AMI w/o user interaction.

#3 Updated by Chris Buechler about 4 years ago

Danny Schuh wrote:

Actually, I had skipped the initial setup wizard.

Then your WAN would be DHCP, that's the only possible config out of the box.

#4 Updated by Danny Schuh about 4 years ago

I believe that that was the case. I think that when I manually created the LAN interface, the addressing method was set to none for both v4 and v6, which is why I created this ticket. This is no doubt a side-effect of me not running the setup wizard. Perhaps a userdata-supplied array mentioned in feature request #6457 will help AWS users by not having to manually configure them post-launch.

I would normally close this bug at this point, but it seems that it can be better served to improve the setup wizard as you have pointed out.