Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multiple NICs for vsphere-iso - only one NIC with IP-Reachability #11409

Closed
heitmanr opened this issue Nov 22, 2021 · 2 comments
Closed

multiple NICs for vsphere-iso - only one NIC with IP-Reachability #11409

heitmanr opened this issue Nov 22, 2021 · 2 comments

Comments

@heitmanr
Copy link

Building a VM with two NICs mapped to their vSphere-Portgroups works just fine.

Description

In my Setup, only one Portgroup contains a DHCP-Server.

  • the 2nd NIC doesn't get an IP-Address (by design)
  • the 2nd Portgroup would be in an isolated IP-Range
    • so an SSH-Connection to n IP-Address at this 2nd-NIC wouldn't be possible anyway.

Right now, the whole build-process gets stuck, in "Waiting for IP"
=> I assume, the script looks to the "wrong" NIC [which doesn't get an IP]
=> or it wait's, until all NICs got an IP-Address

Use Case(s)

Any dual-homed Server connecting different "network security zones, perimeter networks, etc."

Potential configuration

I'd suggest the possibility, to flag one or more NICs as "management"-Interface usable for packer.
//of course, defaulting to "true" would make sense to avoid changes to standard, single-homed setups.

  network_adapters {
    network_card = "vmxnet3"
    network      = "LAB.Management"
    management = true
  }
 network_adapters {
    network_card = "vmxnet3"
    network      = "isolated LAN without DHCPd"
   management = false
  }

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

@github-actions
Copy link

This issue has been migrated to hashicorp/packer-plugin-vsphere#133 due to the Packer Plugin split.

Please follow the new issue for updates.

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants