netbootxyz / netboot.xyz

Your favorite operating systems in one place. A network-based bootable operating system installer based on iPXE.
https://netboot.xyz
Apache License 2.0
8.94k stars 670 forks source link

no network connection after pxe boot of flatcar container linux and/or fedora coreOS #1105

Open joppa27 opened 2 years ago

joppa27 commented 2 years ago

Describe the bug After netbooting into flatcar, an IP address is no longer assigned.No IP address means no network/internet connection. Which causes any attempt to use flatcar-install or coreos-installer script(s) to install the OS to disk to fail, because they are unable to download the required images.

To Reproduce

  1. setup pfsense as a netboot server https://figura.im/posts/2020/01/pfsense-as-a-netboot.xyz-server/
  2. from netboot main menu select live network install
  3. select container linux by flatcar stable
  4. after flatcar boots & at command prompt type flatcar-install -d /dev/sda

Expected behavior

expect required images to download, and be installed on selected disk. Instead script fails because image is unable to be downloaded.

Screenshots image

Additional context When I boot Fedora CoreOS (or Ubuntu) from an ISO, an IP address is assigned and I'm able to connect to the internet or my internal network to download the required images.

antonym commented 2 years ago

I was able to get networking using Proxmox... are you using DHCP and any info about the network/hardware you are using? It sounds like networking may not be getting detected, but it should normally work.

github-actions[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

joppa27 commented 2 years ago

@antonym I am using DHCP, the same config described here: https://figura.im/posts/2020/01/pfsense-as-a-netboot.xyz-server/ I should have mentioned that I am doing a bare metal install on a HP ProDesk 405 G6 Desktop Mini PC The network adapter is a Realtek RTL8111 (when i boot it up with ubuntu) image

I think it may be a driver issue?