On Thu, 2008-02-21 at 19:22 +0000, Adam Retter wrote:
> Bill,
> 
> Thanks very very much :-)
> 
> All it needed was the next-server option, then it booted up perfectly
> - im now sending this via. my new OpenBSD 4.2 net4801 router/firewall.
> 
> I guess something must have changed on either the OpenBSD or FreeBSD
> side, I think FreeBSD switched to isc-dhcpd-3 and im not sure whether
> the dhcpd of pxeboot in OpenBSD has changed, but I know that I didnt
> used to have to use next-server to get it to work.
> 
> 
> Thanks again. Im overjoyed :-)

Glad to hear that. Your output might still be of interest to FreeBSD's
dhcpd3 and/or OpenBSD's pxeboot maintainers, since according to dhcpd(8)
V3.0.4 on Ubuntu Linux:

"If no next-server parameter applies to a given client, the DHCP
server’s IP address is used."

Which obviously didn't entirely go according to plan here.. The bug is
most likely in pxeboot, as both dhcpd and tftpd appear to be doing what
they should do and pxeboot's all-zeroes looked suspicious to begin with.

Bill

> On Thu, Feb 21, 2008 at 3:00 PM, Bill Maas <[EMAIL PROTECTED]> wrote:
> > Hi Adam,
> >
> >  [apologies for off-list reply, Reply To All is only a Shift away here]
> >
> >
> >  On Thu, 2008-02-21 at 10:51 +0000, Adam Retter wrote:
> >
> >
> > > On Thu, Feb 21, 2008 at 9:28 AM, Bill Maas <[EMAIL PROTECTED]> wrote:
> >  > > Hi Adam,
> >  > >
> >  > >  On Wed, 2008-02-20 at 23:08 +0000, Adam Retter wrote:
> >  > >  [...]
> >  > >
> >  > > >
> >  > >  > CLIENT MAC ADDR: 00 00 24 C4 2C 6C
> >  > >  > CLIENT IP: 172.16.16.252  MASK: 255.255.255.240  DHCP IP: 
> > 172.16.16.245
> >  > >  > GATEWAY IP: 172.16.16.254
> >  > >
> >  > >  172.16.16.245
> >  > >  172.16.16.254
> >  >
> >  > No this is correct, my router (imaginary, as it will be my net4801
> >  > eventually) is on 172.16.16.254 and the FreeBSD machine issuing the
> >  > DHCP lease is on 172.16.16.245
> >  >
> >  >
> >  > >  Maybe the first IP is what you meant, but it might as well indicate a
> >  > >  typo in the "next-server" field in dhcpd.conf(!).
> >  >
> >  > not sure i have a next-server field in my dhcpd.conf, I am at work at
> >  > the moment and will check this when I get home...
> >  >
> >  > >
> >  > >  > probing: pc0 com0 com1 pci pxe![2.1] mem[639K 127M a20=on]
> >  > >  > disk: hd0+
> >  > >  > net: mac 00:00:24:c4:2c:6c, ip 172.16.16.252, server 0.0.0.0
> >  > >
> >  > >  I would expect a local IP here for "server". This would match
> >  > >  "next-server" in dhcpd.conf on OpenBSD. Apparantly downloading the 
> > boot
> >  > >  loader succeeds (as if "next-server" doesn't apply yet), but the boot
> >  > >  loader apparently fails to get the TFTP server's correct address.
> >  >
> >  > Ah so next-server could definitely be the culprit if I am missing it,
> >  > will take a look tonight. Thanks very much for your help so far :-)
> >  >
> >
> >
> > No, I was being overly imaginative and suspicious about default program
> >  behaviour. The two IPs just looked suspiciously similar to me. The
> >  messages for trivial errors are in fact quite clear (just generated a
> >  few):
> >
> >  Wrong next-server (PXE ROM):
> >  PXE-E11: ARP timeout PXE-E11: ARP timeout
> >  PXE-E38: TFTP cannot open connection
> >  PXE-M0F: Exiting BootManage PXE ROM.
> >
> >  Unreadable bsd.rd (pxeboot):
> >  booting tftp:/bsd.rd: open tftp:/bsd.rd: Operation not permitted
> >   failed(1). will try /bsd
> >
> > boot>
> >  booting tftp:/bsd: open tftp:/bsd: No such file or directory
> >   failed(2). will try /bsd
> >  Turning timeout off.
> >
> >
> > Without a next-server the DHCP IP will be used as it should, but in my
> >  output I do see it after the "server" keyword, and not 0.0.0.0 (which
> >  might indicate ARP trouble, and many error code 60 reports are about
> >  ARP).
> >
> >  But the ARP/next-server theory doesn't hold as well, since pxeboot can
> >  (a) determine bsd.rd's size, and (b) determine that bsd isn't there.
> >
> >  It doesn't look like there is a trivial answer here.
> >
> >  Bill
> >
> >
> >
> > > >  I'm not sure about this, I didn't write dhcpd or pxeboot;), but it 
> > > > looks
> >  > >  to me as if that's what's to be happening here.
> >  > >
> >  > >  Bill
> >  > >
> >  > >
> >  > >  > >> OpenBSD/i386 PXEBOOT 2.02
> >  > >  > booting tftp:bsd.rd: |
> >  > >  > booting tftp:bsd.rd: 4733076read text: Unknown error: code 60
> >  > >  >  failed(60). will try /bsd
> >  > >  > boot>
> >  > >  > booting tftp:/bsd: open tftp:/bsd: No such file or directory
> >  > >  >  failed(2). will try /bsd
> >  > >  > Turning timeout off.
> >  > >  > boot>
> >  > >  > _______________________________________________
> >  > >  > Soekris-tech mailing list
> >  > >  > Soekris-tech@lists.soekris.com
> >  > >  > http://lists.soekris.com/mailman/listinfo/soekris-tech
> >  > >  >
> >  > >  --
> >  > >  "What's a computer?" - MES
> >  > >
> >  > >
> >  >
> >  >
> >  >
> >  --
> >  "What's a computer?" - MES
> >
> >  _______________________________________________
> >  Soekris-tech mailing list
> >  Soekris-tech@lists.soekris.com
> >  http://lists.soekris.com/mailman/listinfo/soekris-tech
> >
> 
> 
> 
-- 
"What's a computer?" - MES

_______________________________________________
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech

Reply via email to