Debugging bootparamd configuration
My great and good friends, I am using setting up diskless(8). I want to test the communication with bootparamd. How do I do the following? 1. Check what the client is sending to the server and what the server responds with 2. Construct a different request for bootparamd (so I can test how the server responds to a different client name) And I ask because I suspect the bootparamd configuration to explain the remaining problem with my diskless setup. I will send more context if it seems that would help. With the best compliments, Ibsen S Ripsbusker
Re: bootparamd and non-default subnet masks
On Thu, 17 Sep 2015 09:24:16 + (UTC) Stuart Henderson wrote: > RARP (RFC 903) d Hi Stuart, thank you for the information. Would there be some bad consequences if OpenBSD changed its diskless booting process so it respects DHCP's root path option? Regards, -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
Re: bootparamd and non-default subnet masks
On 2015-09-17, Marko Cupać wrote: > On Mon, 14 Sep 2015 13:59:15 +0200 > Marko Cupać wrote: > >> Hi, >> >> I am trying to implement diskless setup in VLAN-segmented network. >> Server which hosts dhcpd, tftpd, nfsd, rarpd and bootparamd is on >> 10.30.7.38/27, on separate vlan from client which should be on >> 10.30.7.51/27. >> >> Client obtains IP address, executes pxeboot and boots bsd from tftp >> successfully. However, after that I get messages: >> nfs_boot: using interface rl0, with revarp & bootparams >> nfs_boot: client_addr=10.30.7.51 >> RPC timeout for server 10.255.255.255 (0xaff) prog 10 >> >> The problem is apparently with non-standard subnet mask for class A >> network, but AFAIK rarpd does not supply subnet mask information. How >> can I make this work? >> >> Regards, > > Guys, > > is this really so irrelevant? Or should I interpret silence on topic > somewhere along the lines of "None of the great masters who wrote and > understood this are no longer with us" :P > RARP (RFC 903) does not support CIDR.
Re: bootparamd and non-default subnet masks
On Mon, 14 Sep 2015 13:59:15 +0200 Marko Cupać wrote: > Hi, > > I am trying to implement diskless setup in VLAN-segmented network. > Server which hosts dhcpd, tftpd, nfsd, rarpd and bootparamd is on > 10.30.7.38/27, on separate vlan from client which should be on > 10.30.7.51/27. > > Client obtains IP address, executes pxeboot and boots bsd from tftp > successfully. However, after that I get messages: > nfs_boot: using interface rl0, with revarp & bootparams > nfs_boot: client_addr=10.30.7.51 > RPC timeout for server 10.255.255.255 (0xaff) prog 10 > > The problem is apparently with non-standard subnet mask for class A > network, but AFAIK rarpd does not supply subnet mask information. How > can I make this work? > > Regards, Guys, is this really so irrelevant? Or should I interpret silence on topic somewhere along the lines of "None of the great masters who wrote and understood this are no longer with us" :P -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
bootparamd and non-default subnet masks
Hi, I am trying to implement diskless setup in VLAN-segmented network. Server which hosts dhcpd, tftpd, nfsd, rarpd and bootparamd is on 10.30.7.38/27, on separate vlan from client which should be on 10.30.7.51/27. Client obtains IP address, executes pxeboot and boots bsd from tftp successfully. However, after that I get messages: nfs_boot: using interface rl0, with revarp & bootparams nfs_boot: client_addr=10.30.7.51 RPC timeout for server 10.255.255.255 (0xaff) prog 10 The problem is apparently with non-standard subnet mask for class A network, but AFAIK rarpd does not supply subnet mask information. How can I make this work? Regards, -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
Re: Bootparamd
On Thu, Sep 12, 2013 at 08:17:56PM +, hru...@gmail.com wrote: > Miod Vallat wrote: > > Thanks for the good tips! > > > I think the bootparams swap file information will be used correctly (I > > remember seeing a fix in this area some time ago). It doesn't hurt > > anyway to mention it in /etc/fstab with the nfsmntpt option. > > OK, both, swap and rootfs, again in /etc/fstab. > > I think my configuration is correct, because during booting I get > the messages: > > nfs_boot: root on 10.0.0.1:/export/geode0/root > nfs_boot: swap on 10.0.0.1:/export/geode0/swap > > But if I give the commando "swapctl -l" after booting, I see no > mounted swap, unless I mention it in /etc/fstab. This will be fixed in 5.4: http://marc.info/?l=openbsd-cvs&m=136621575806608&w=2 > > Rodrigo. > -- I'm not entirely sure you are real.
Re: Bootparamd
Miod Vallat wrote: Thanks for the good tips! > I think the bootparams swap file information will be used correctly (I > remember seeing a fix in this area some time ago). It doesn't hurt > anyway to mention it in /etc/fstab with the nfsmntpt option. OK, both, swap and rootfs, again in /etc/fstab. I think my configuration is correct, because during booting I get the messages: nfs_boot: root on 10.0.0.1:/export/geode0/root nfs_boot: swap on 10.0.0.1:/export/geode0/swap But if I give the commando "swapctl -l" after booting, I see no mounted swap, unless I mention it in /etc/fstab. Rodrigo.
Re: Bootparamd
> Who uses bootparam? Only the Kernel? bootparam is used by network boot blocks on several machines, as well as by the kernel when booting with root on nfs. > Is Bootparamd a standard? FreeBSD has it with the same author, > there is also a Bootparamd in SunOS. I think this is important > to know for booting from other operating systems, but I dont > find this info in the man pages. It is a Sun (now Oracle) standard. Its is a very simple protocol, described in /usr/include/rpcsvc/bootparam_prot.x . > After it boots, I have the root file I gave in /etc/bootparam, > I dont need to mount it with /etc/fstab. Should I give the > root file in /etc/bootparam and leave the kernel mount the > root again? It's preferrable, especially if you want to use different mount options than the default NFS options. Also, I'd suggest, whenever possible, to add the `alldirs' option to the NFS server, and put, in the diskless client, explicit entries for /tmp, /usr and /var, so that these can get mounted as NFSv3. Otherwise, the whole / hierarchy is mounted as NFSv2 by the kernel. > The above does not happen with the swap file. To have a swap > file I have to give it in /etc/fstab. Is this due to an error > in my configuration? I think the bootparams swap file information will be used correctly (I remember seeing a fix in this area some time ago). It doesn't hurt anyway to mention it in /etc/fstab with the nfsmntpt option. Miod
Bootparamd
Dear Sirs! I managed to boot OpenBSD 5.3 in a Fujitsu Siemens Futro A220 (AMD Geode LX800) thin client from a Celeron Machine running OpenBSD 4.8. I followed what I read in DISKLESS(8) and PXEBOOT(8) almost blindly, without understandig very much. Perhaps the pages could be more understandable. I have a lot of questions. I begin with some. Who uses bootparam? Only the Kernel? Is Bootparamd a standard? FreeBSD has it with the same author, there is also a Bootparamd in SunOS. I think this is important to know for booting from other operating systems, but I dont find this info in the man pages. After it boots, I have the root file I gave in /etc/bootparam, I dont need to mount it with /etc/fstab. Should I give the root file in /etc/bootparam and leave the kernel mount the root again? The above does not happen with the swap file. To have a swap file I have to give it in /etc/fstab. Is this due to an error in my configuration? Thanks Rodrigo.
