>
>
> On Mon, 28 Jun 2010, Daniel Braniss wrote:
>
> >>
> >>
> >> On Mon, 28 Jun 2010, al...@ulgsm.ru wrote:
> >>
> >>>
> >>>
> >>> kernel built with:
> >>> options BOOTP # Use BOOTP to obtain IP address/hostname
> >>> options BOOTP_NFSROOT # NFS mount root file system using BO
On Tue, 29 Jun 2010, al...@ulgsm.ru wrote:
Yes. without BOOTPxxx options boot is fine.
Btw, if you feel like helping out with testing it, I have patches for
this case that modify pxeboot to use NFSv3 instead of NFSv2. The more
testing they get the better. They're at:
http://people.freebsd.o
On Mon, 28 Jun 2010, Daniel Braniss wrote:
On Mon, 28 Jun 2010, al...@ulgsm.ru wrote:
kernel built with:
options BOOTP # Use BOOTP to obtain IP address/hostname
options BOOTP_NFSROOT # NFS mount root file system using BOOTP info
options BOOTP_NFSV3
Try building a
On Tue, 29 Jun 2010, al...@ulgsm.ru wrote:
I think using NFS_ROOT but not the BOOTPxxx options will work around this
or you could test the following patch and see if it helps. (Testing the
patch would be appreciated, since I don't have any way to test across
multiple subnets and it would be n
* Rick Macklem [2010-06-28 20:41:17 -0400]:
>
>
> On Mon, 28 Jun 2010, Daniel Braniss wrote:
>
> >>
> >>
> >> On Mon, 28 Jun 2010, al...@ulgsm.ru wrote:
> >>
> >>>
> >>>
> >>> kernel built with:
> >>> options BOOTP # Use BOOTP to obtain IP address/hostname
> >>> options BOOTP_
On Mon, 28 Jun 2010, Daniel Braniss wrote:
On Mon, 28 Jun 2010, al...@ulgsm.ru wrote:
kernel built with:
options BOOTP # Use BOOTP to obtain IP address/hostname
options BOOTP_NFSROOT # NFS mount root file system using BOOTP info
options BOOTP_NFSV3
Try building a
>
>
> On Mon, 28 Jun 2010, al...@ulgsm.ru wrote:
>
> >
> >
> > kernel built with:
> > options BOOTP # Use BOOTP to obtain IP address/hostname
> > options BOOTP_NFSROOT # NFS mount root file system using BOOTP info
> > options BOOTP_NFSV3
> >
> Try building a kernel without
On Mon, 28 Jun 2010, al...@ulgsm.ru wrote:
kernel built with:
options BOOTP # Use BOOTP to obtain IP address/hostname
options BOOTP_NFSROOT # NFS mount root file system using BOOTP info
options BOOTP_NFSV3
Try building a kernel without the above options, but with
opti
* al...@ulgsm.ru [2010-06-28 10:16:01 +0400]:
> I have two subnets:
> 10.144.142.0/22 - here is tftp server and diskless.
> 10.144.130.0/24 - here is nfs server.
>
> in isc-dhcpd.conf:
> next-server 10.144.140.160;
> option root-path "10.144.130.160:/exp/fbsdstable";
>
>
> In this case, pxeboot
* Rick Macklem [2010-06-26 10:24:44 -0400]:
>
>
> On Sat, 26 Jun 2010, al...@ulgsm.ru wrote:
>
> [stuff snipped]
> >
> >
> > dhcp seems ok.
> > [alexs:ul-it13:~]>kenv
> > LINES="24"
> > acpi_load="YES"
> > boot.netif.gateway="10.144.140.1"
> > boot.netif.hwaddr="00:1c:c0:5a:f4:72"
> > boot.net
On Sat, 26 Jun 2010, al...@ulgsm.ru wrote:
[stuff snipped]
dhcp seems ok.
[alexs:ul-it13:~]>kenv
LINES="24"
acpi_load="YES"
boot.netif.gateway="10.144.140.1"
boot.netif.hwaddr="00:1c:c0:5a:f4:72"
boot.netif.ip="10.144.142.78"
boot.netif.netmask="255.255.252.0"
boot.nfsroot.nfshandle="Xbb55e8
* Rick Macklem [2010-06-25 20:11:42 -0400]:
> From a quick glance at the code, I think that the dhcp server must return
> the gateway the client uses to get to the server. (ie. it must be an ip
> addr on the diskless client's network for the gateway to where the server
> is) It looks like this wi
On Fri, 25 Jun 2010, al...@ulgsm.ru wrote:
Hi all.
I tryed setup server for booting diskless hosts from different networks.
In one network booting is ok.
I see thet realtek 8139 pxe can`t load pxeboot file fromi tftp server from
another
network.
By changing options in dhcp server, i resol
Hi all.
I tryed setup server for booting diskless hosts from different networks.
In one network booting is ok.
I see thet realtek 8139 pxe can`t load pxeboot file fromi tftp server from
another
network.
By changing options in dhcp server, i resolve that pxeboot can load kernel
from this server
14 matches
Mail list logo
