Thanks for the suggestion I did eliminate the second nic altogether and it didn't seem to make a difference
I'm guessing this is easily replicated for others... what I'm most unsure of is why the dhcp conversation isn't "normal" -- is it a NetworkManager conversation in the shipping image or an ISC client that runs? I'm just not experienced with how the in-memory image is built... I can investigate there if somebody can give me a clue on the image generation...
Appreciate it!
On Fri, Jan 25, 2019, 4:00 PM James Pearson <james-p@moving-picture.com wrote:
John Cole wrote:
Once I've got this particular problem solved, I'm looking to boot up and bond BOTH NICs together, something I know should be possible, but I've
not
done myself yet. I believe that'd be handled in the append line as well.
If your diskless client has 2 NICs - could that be confusing things?
You could try adding the line:
IPAPPEND 2
to your PXE config file - this will append the MAC address of the PXEboot NIC as an option to the boot cmdline to be used by dhclient when the OS boots
No idea if this is the issue here ...
James Pearson _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos