Re: [Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
On Thu, 2008-02-21 at 19:22 +, 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 +, 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 +, 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 > > > > __
Re: [Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
On Thu, Feb 21, 2008 at 04:00:17PM +0100, Bill Maas wrote: > > > > >> OpenBSD/i386 PXEBOOT 2.02 > > > > booting tftp:bsd.rd: | > > > > booting tftp:bsd.rd: 4733076read text: Unknown error: code 60 > > > > failed(60). will try /bsd Try a tcpdump on the server, e.g. tcpdump -i XXX -s1500 -n -X host x.x.x.x where XXX is the interface name, x.x.x.x is the client's IP address. (Unfortunately you can't filter on the UDP port, as after the first packet the source and destination ports are both dynamic) Clearly at least *some* tftp packets are getting through, and the protocol is sufficiently simple that it may not be hard to work out where the problem lies, just from the dump. Relevant documents: [RFC 1350] TFTP [RFC 2347] Options negotiation [RFC 2348] Blocksize option [RFC 2349] Timeout and transfer size options Perhaps there is some problem with the client asking for a particular extension (e.g. block size) but the server not implementing it properly. Or there might be a problem with firewalling on the server side. Regards, Brian. ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
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 :-) 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 +, 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 +, 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 > -- Adam Retter Software Pimp Extraordinaire ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
> "[...]. Also note that TFTP uses UDP as its transport. [...] > [This] also means that TFTP supports broadcasts, meaning you don't > have to configure the TFTP client with the IP address of a particular > TFTP server." While it's not terribly relevant to the problem at hand, this is somewhat inaccurate. Using UDP does not mean that TFTP supports broadcasts; it means that TFTP can support broadcasts if it chooses - as it happens, TFTP did choose to. And while the broadcast support may mean that some particular TFTP client at hand need not be configured with a server address (and thus may not be inaccurate in a "booting FreeBSD" context), that is a property of the particular TFTP client in question; there are TFTP clients that require a server name/address. /~\ The ASCII der Mouse \ / Ribbon Campaign X Against HTML [EMAIL PROTECTED] / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
On Thu, Feb 21, 2008 at 03:28:52PM +, Adam Retter wrote: > Erm sorry im a bit confused now! Where does NFS come into this? I was under the impression that OpenBSD is using NFS as FreeBSD does. FreeBSD uses TFTP to fetch the loader and the loader is using NFS for loading the FORTH scripts, kernel, modules, etc... > If I understand the process then pxeboot is sent by TFTP which then > request bsd.rd from the same TFTP source and then bootstraps bsd.rd > once it is downloaded... > > Or am I missing something? pretty sure NFS is not involved. Sorry for the confusion. > On Thu, Feb 21, 2008 at 1:47 PM, Bernd Walter <[EMAIL PROTECTED]> wrote: > > > > On Wed, Feb 20, 2008 at 11:30:30PM +, Adam Retter wrote: > > > On Wed, Feb 20, 2008 at 11:18 PM, Stuart Henderson <[EMAIL PROTECTED]> > > wrote: > > > > On 2008/02/20 23:08, Adam Retter wrote: > > > > > The console output over COM0 from the net4801 is below, but > > basically > > > > > I have no idea what "Unknown error: code 60" (from pxeboot?) means? > > > > > > > > 60 is ETIMEDOUT, according to OpenBSD's intro(2). iirc the normal OS > > > > error codes are used in the boot loader. are you aware of any network > > > > problems, bad cables or duplex mismatch maybe? > > > > > > Erm nope im not aware of any problems, the cables are all new and work > > > for network traffic otherwise. The net4801 is connected to a Netgear > > > 8-port 10/100/1000Mbit switch and the FreeBSD machine is also > > > connected to the switch. Using the same physical setup with its > > > current OpenBSD 3.7 operating system, I am able to SSH into the > > > net4801 and browse the web etc (its used as a F/W and Router). > > > > > > Hmm, anything I can do to find out why its timing out? > > > > You already tftp'ed the loader and just NFS is failing, so you have to > > search for NFS related problems. > > Is is correct that your nfs path is named tftp:/bsd ? > > I don't know if the OpenBSD loader can handle DNS requests, so you > > might want to try with an IP address as well. -- B.Walterhttp://www.bwct.de http://www.fizon.de [EMAIL PROTECTED] [EMAIL PROTECTED][EMAIL PROTECTED] ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
Hi Adam, >From http://www.onlamp.com/pub/a/bsd/2003/06/05/FreeBSD_Basics.html: "You'll note that FreeBSD supports both IPv4 and IPv6, so its inetd is capable of listening for both types of requests. Also note that TFTP uses UDP as its transport. This means it is not as reliable as FTP (which uses TCP). It also means that TFTP supports broadcasts, meaning you don't have to configure the TFTP client with the IP address of a particular TFTP server." >From http://www.javvin.com/protocolTFTP.html: "Each data packet contains one block of data, and must be acknowledged by an acknowledgment packet before the next packet can be sent. A data packet of less than 512 bytes signals termination of a transfer. If a packet gets lost in the network, the intended recipient will timeout [...]" Together with "server 0.0.0.0" this might hold a clue. Looks like requests are getting through, but ACKs aren't. Were there changes on the FreeBSD (or OpenBSD) front since you last succesfully did this? Bill On Thu, 2008-02-21 at 10:51 +, 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 +, 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 :-) > > > 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
Re: [Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
Erm sorry im a bit confused now! Where does NFS come into this? If I understand the process then pxeboot is sent by TFTP which then request bsd.rd from the same TFTP source and then bootstraps bsd.rd once it is downloaded... Or am I missing something? pretty sure NFS is not involved. On Thu, Feb 21, 2008 at 1:47 PM, Bernd Walter <[EMAIL PROTECTED]> wrote: > > On Wed, Feb 20, 2008 at 11:30:30PM +, Adam Retter wrote: > > On Wed, Feb 20, 2008 at 11:18 PM, Stuart Henderson <[EMAIL PROTECTED]> > wrote: > > > On 2008/02/20 23:08, Adam Retter wrote: > > > > The console output over COM0 from the net4801 is below, but basically > > > > I have no idea what "Unknown error: code 60" (from pxeboot?) means? > > > > > > 60 is ETIMEDOUT, according to OpenBSD's intro(2). iirc the normal OS > > > error codes are used in the boot loader. are you aware of any network > > > problems, bad cables or duplex mismatch maybe? > > > > Erm nope im not aware of any problems, the cables are all new and work > > for network traffic otherwise. The net4801 is connected to a Netgear > > 8-port 10/100/1000Mbit switch and the FreeBSD machine is also > > connected to the switch. Using the same physical setup with its > > current OpenBSD 3.7 operating system, I am able to SSH into the > > net4801 and browse the web etc (its used as a F/W and Router). > > > > Hmm, anything I can do to find out why its timing out? > > You already tftp'ed the loader and just NFS is failing, so you have to > search for NFS related problems. > Is is correct that your nfs path is named tftp:/bsd ? > I don't know if the OpenBSD loader can handle DNS requests, so you > might want to try with an IP address as well. > > -- > B.Walterhttp://www.bwct.de http://www.fizon.de > [EMAIL PROTECTED] [EMAIL PROTECTED][EMAIL PROTECTED] > -- Adam Retter Software Pimp Extraordinaire ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
Hi Adam, [apologies for off-list reply, Reply To All is only a Shift away here] On Thu, 2008-02-21 at 10:51 +, 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 +, 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
Re: [Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
On 2008/02/21 14:47, Bernd Walter wrote: > On Wed, Feb 20, 2008 at 11:30:30PM +, Adam Retter wrote: > > On Wed, Feb 20, 2008 at 11:18 PM, Stuart Henderson <[EMAIL PROTECTED]> > > wrote: > > > On 2008/02/20 23:08, Adam Retter wrote: > > > > The console output over COM0 from the net4801 is below, but basically > > > > I have no idea what "Unknown error: code 60" (from pxeboot?) means? > > > > > > 60 is ETIMEDOUT, according to OpenBSD's intro(2). iirc the normal OS > > > error codes are used in the boot loader. are you aware of any network > > > problems, bad cables or duplex mismatch maybe? > > > > Erm nope im not aware of any problems, the cables are all new and work > > for network traffic otherwise. The net4801 is connected to a Netgear > > 8-port 10/100/1000Mbit switch and the FreeBSD machine is also > > connected to the switch. Using the same physical setup with its > > current OpenBSD 3.7 operating system, I am able to SSH into the > > net4801 and browse the web etc (its used as a F/W and Router). > > > > Hmm, anything I can do to find out why its timing out? > > You already tftp'ed the loader and just NFS is failing, so you have to > search for NFS related problems. OpenBSD pxeboot doesn't do NFS, only tftp. It's easily-configured and normally very effective. switching console to com0 >> OpenBSD/i386 PXEBOOT 2.02 booting tftp:bsd.rd: | booting tftp:bsd.rd: 4733076read text: Unknown error: code 60 failed(60). will try /bsd ...it has loaded most of the file, but fails somewhere near the end. Adam can you successfully get this file using tftp(1) on another machine? Just to double-check, did you note what I said about duplex settings? (No offense meant if you did). If the switch and the installed OS are forced to full-duplex, things would work OK for the installed OS, but you might expect to have some problems if pxeboot auto-detects the duplex setting but the switch is forced. For the upgrade you could just skip pxebooting and copy bsd.rd into / on the running system, then choose it at the boot loader, but it's strange that it should be failing like this. It should just work. I haven't tried with FreeBSD as a tftp server but PXE is my normal way to install OpenBSD, even on normal PCs, and I've not seen this happen before (between temporary installations for testing, permanent installations, and upgrades, I've done this quite often). ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
On Wed, Feb 20, 2008 at 11:30:30PM +, Adam Retter wrote: > On Wed, Feb 20, 2008 at 11:18 PM, Stuart Henderson <[EMAIL PROTECTED]> wrote: > > On 2008/02/20 23:08, Adam Retter wrote: > > > The console output over COM0 from the net4801 is below, but basically > > > I have no idea what "Unknown error: code 60" (from pxeboot?) means? > > > > 60 is ETIMEDOUT, according to OpenBSD's intro(2). iirc the normal OS > > error codes are used in the boot loader. are you aware of any network > > problems, bad cables or duplex mismatch maybe? > > Erm nope im not aware of any problems, the cables are all new and work > for network traffic otherwise. The net4801 is connected to a Netgear > 8-port 10/100/1000Mbit switch and the FreeBSD machine is also > connected to the switch. Using the same physical setup with its > current OpenBSD 3.7 operating system, I am able to SSH into the > net4801 and browse the web etc (its used as a F/W and Router). > > Hmm, anything I can do to find out why its timing out? You already tftp'ed the loader and just NFS is failing, so you have to search for NFS related problems. Is is correct that your nfs path is named tftp:/bsd ? I don't know if the OpenBSD loader can handle DNS requests, so you might want to try with an IP address as well. -- B.Walterhttp://www.bwct.de http://www.fizon.de [EMAIL PROTECTED] [EMAIL PROTECTED][EMAIL PROTECTED] ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
Hi Adam, On Wed, 2008-02-20 at 23:08 +, 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 Maybe the first IP is what you meant, but it might as well indicate a typo in the "next-server" field in dhcpd.conf(!). > 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. 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 ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
On Wed, Feb 20, 2008 at 11:18 PM, Stuart Henderson <[EMAIL PROTECTED]> wrote: > On 2008/02/20 23:08, Adam Retter wrote: > > The console output over COM0 from the net4801 is below, but basically > > I have no idea what "Unknown error: code 60" (from pxeboot?) means? > > 60 is ETIMEDOUT, according to OpenBSD's intro(2). iirc the normal OS > error codes are used in the boot loader. are you aware of any network > problems, bad cables or duplex mismatch maybe? Erm nope im not aware of any problems, the cables are all new and work for network traffic otherwise. The net4801 is connected to a Netgear 8-port 10/100/1000Mbit switch and the FreeBSD machine is also connected to the switch. Using the same physical setup with its current OpenBSD 3.7 operating system, I am able to SSH into the net4801 and browse the web etc (its used as a F/W and Router). Hmm, anything I can do to find out why its timing out? -- Adam Retter Software Pimp Extraordinaire ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
On 2008/02/20 23:08, Adam Retter wrote: > The console output over COM0 from the net4801 is below, but basically > I have no idea what "Unknown error: code 60" (from pxeboot?) means? 60 is ETIMEDOUT, according to OpenBSD's intro(2). iirc the normal OS error codes are used in the boot loader. are you aware of any network problems, bad cables or duplex mismatch maybe? ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
