On Mon, 11 Nov 2019 at 21:16, Samuel Sieb <samuel@xxxxxxxx> wrote:
>
> On 11/11/19 10:57 AM, Aaron Gray wrote:
> > On Thu, 7 Nov 2019 at 03:53, Samuel Sieb <samuel@xxxxxxxx> wrote:
> >> On 11/6/19 3:39 PM, Aaron Gray wrote:
> >>> Does anyone have PXE booting working ?
> >>
> >> Yes, for both legacy and EFI modes.
> >
> > Right I am only needing legacy
>
> > I have BOOTP and TFTP working but it seems to be failing on DNS and
> > HTTP or HTTPS.
Samuel,
I was trying to follow this howto :-
https://docs.fedoraproject.org/en-US/fedora/rawhide/install-guide/advanced/Network_based_Installations/
> You need to explain in more detail where the boot process is getting
> stuck. Does the PXE BIOS get an IP address? Does it load the file from
> the tftp server or does it fail there?
PXE BOOT is working fine, the TFTP is working and the kernel is loading.
But the initrd is unable to load the inst.stage2 http(s) loaders
~~~ pxelinux.cfg ~~~
default vesamenu.c32
prompt 1
timeout 600
label linux
menu label ^Install Fedora 30 64-bit
menu default
kernel f30/vmlinuz
append initrd=f30/initrd.img inst.stage2=https://download.fedoraproject.org/pub/fedora/linux/releases/30/Server/x86_64/os/ ip=dhcp
label server30
menu label ^Install Fedora 30 ( Minimal Image )
menu default
kernel f30/vmlinuz
append initrd=f30/initrd.img inst.stage2=https://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/releases/30/Server/x86_64/os ip=dhcp ks=https://example.com/fedora/kickstarts/minimal.ks
label server31
menu label ^Install Fedora 31
menu default
kernel f31/vmlinuz
append initrd=f31/initrd.img inst.stage2=https://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/releases/31/Server/x86_64/os
label local
menu label Boot from ^local drive
localboot 0xffff
~~~
> > Here's my dhcp.conf :-
> > ~~~
> > # dhcpd.conf
> >
> > # option definitions common to all supported networks...
> > option domain-name "aarongray.org";
> > option domain-name-servers ns1.hover.com, ns2.hover.com;
>
> This is incorrect, you have to put IP addresses. You can't resolve the
> names without having a DNS server already. :-)
> > # No service will be given on this subnet, but declaring it helps the
> > # DHCP server to understand the network topology.
>
> I think that's a copy and paste comment that is invalid.
> > subnet 192.168.2.0 netmask 255.255.255.0 {
> > authoritative;
> >
> > range 192.168.2.1 192.168.2.127;
> > option domain-name-servers 8.8.8.8, 8.8.4.4;
> > option routers 192.168.1.111;
>
> Your gateway address is not in this subnet. That won't work.
>
> Do you have a "pxelinux.cfg" directory on the tftp server? That would
> be the next step.
>
> On 11/11/19 10:57 AM, Aaron Gray wrote:
> > On Thu, 7 Nov 2019 at 03:53, Samuel Sieb <samuel@xxxxxxxx> wrote:
> >> On 11/6/19 3:39 PM, Aaron Gray wrote:
> >>> Does anyone have PXE booting working ?
> >>
> >> Yes, for both legacy and EFI modes.
> >
> > Right I am only needing legacy
>
> > I have BOOTP and TFTP working but it seems to be failing on DNS and
> > HTTP or HTTPS.
Samuel,
I was trying to follow this howto :-
https://docs.fedoraproject.org/en-US/fedora/rawhide/install-guide/advanced/Network_based_Installations/
> You need to explain in more detail where the boot process is getting
> stuck. Does the PXE BIOS get an IP address? Does it load the file from
> the tftp server or does it fail there?
PXE BOOT is working fine, the TFTP is working and the kernel is loading.
But the initrd is unable to load the inst.stage2 http(s) loaders
~~~ pxelinux.cfg ~~~
default vesamenu.c32
prompt 1
timeout 600
label linux
menu label ^Install Fedora 30 64-bit
menu default
kernel f30/vmlinuz
append initrd=f30/initrd.img inst.stage2=https://download.fedoraproject.org/pub/fedora/linux/releases/30/Server/x86_64/os/ ip=dhcp
label server30
menu label ^Install Fedora 30 ( Minimal Image )
menu default
kernel f30/vmlinuz
append initrd=f30/initrd.img inst.stage2=https://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/releases/30/Server/x86_64/os ip=dhcp ks=https://example.com/fedora/kickstarts/minimal.ks
label server31
menu label ^Install Fedora 31
menu default
kernel f31/vmlinuz
append initrd=f31/initrd.img inst.stage2=https://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/releases/31/Server/x86_64/os
label local
menu label Boot from ^local drive
localboot 0xffff
~~~
> > Here's my dhcp.conf :-
> > ~~~
> > # dhcpd.conf
> >
> > # option definitions common to all supported networks...
> > option domain-name "aarongray.org";
> > option domain-name-servers ns1.hover.com, ns2.hover.com;
>
> This is incorrect, you have to put IP addresses. You can't resolve the
> names without having a DNS server already. :-)
Oh okay I thought it would use the systems DNS to look up the addresses.
> > # No service will be given on this subnet, but declaring it helps the
> > # DHCP server to understand the network topology.
>
> I think that's a copy and paste comment that is invalid.
Okay that was from the default /etc/dhcp/dhcpd.conf file
> > subnet 192.168.2.0 netmask 255.255.255.0 {
> > authoritative;
> >
> > range 192.168.2.1 192.168.2.127;
> > option domain-name-servers 8.8.8.8, 8.8.4.4;
> > option routers 192.168.1.111;
>
> Your gateway address is not in this subnet. That won't work.
Okay that may well be the issue ! I cannot access stuff off of the internet so that figures !
So that should be 192.168.2.1 or
192.168.2.254 ?
192.168.1.111 is the gateway address of the router my DHCPD server machine is connected to.
I tried using the this DHCPD server on Windows and it was fine and could access the internet for normal operation using the
192.168.1.111
address so thought I had a working configuration.
How do I go about this will the DHCPD server pick up that gate way automattically use itself or do I have to do some further routing ??
> > option broadcast-address 192.168.2.255;
> > # option ip-forwarding off;
> > default-lease-time 600;
> > max-lease-time 7200;
> >
> > option ntp-servers ntp.fedora.org;
> >
> > range dynamic-bootp 192.168.2.128 192.168.2.240;
> > ddns-update-style none;
> > filename "pxelinux.0";
> > }
>
> When you say tftp is working, do you mean the server is running or that
> the clients are getting the boot file? You're missing the info telling
> the clients what tftp server to use. You need a line like:
> > # option ip-forwarding off;
> > default-lease-time 600;
> > max-lease-time 7200;
> >
> > option ntp-servers ntp.fedora.org;
> >
> > range dynamic-bootp 192.168.2.128 192.168.2.240;
> > ddns-update-style none;
> > filename "pxelinux.0";
> > }
>
> When you say tftp is working, do you mean the server is running or that
> the clients are getting the boot file? You're missing the info telling
> the clients what tftp server to use. You need a line like:
The machine is getting the bootfiles and menus from the TFTP server fine.
> next-server 192.168.2.1;
Yes I was wondering about next-server ?
>
> Do you have a "pxelinux.cfg" directory on the tftp server? That would
> be the next step.
Thats working fine, I got menus and stuff its the second stage loader that loads images/install.img from initrd.img which is where its failing !
Thanks for helping !
Aaron
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
