Re: [gentoo-user] diskless booting

2007-10-02 Thread Roger Mason 
Hello Dan,

Dan Farrell [EMAIL PROTECTED] writes:

 On Mon, 01 Oct 2007 12:57:05 -0230
 Roger Mason [EMAIL PROTECTED] wrote:

 Well, I had it working on Friday but over the weeekend I tinkered some
 more with pixegrub and broke it again.  Now pxelinux won't work
 either.

 I've attached my dhcpd.conf, sans rndc-key.  Please note that this
 configuration has a big block of code that is for dynamic DNS updates.
 I kept it in because I found it hard to figure out for myself, and I
 figured it would be better to put more out on the web rather than refer
 you to sources I don't even know exist.  I don't know if you are
 running BIND or a DNS server that can do static updates, but if you
 can, I highly suggest it for your own sanity.  

As soon as I sat down at the box this morning I spotted the problem,
which was incredibly stupid (but sadly self typical): I had named my
in.tftpd config file without the final d.  Argh!  Now everything
seems to be running again.

I have kept a copy of your dhcpd.conf as a useful reference.

What I'm trying to accomplish is to build a kerrighed system.  Now on
to the next stage.

Thanks again for your help.

Best wishes,
Roger

-- 
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] diskless booting [solved, I hope]

2007-10-01 Thread Neil Bothwick 
Hello Dan Farrell,

 I was going to suggest you avoid pxegrub, but I guess you figured that
 out for yourself.  

What's wrong with pxe grub. I use it and it works, so I haven't tried
pxelinux. Is there a good reason to change if it works?


-- 
Neil Bothwick

Newsflash! Explosion at M$ beta testsite - Infinite number of monkeys
killed.


signature.asc
Description: PGP signature

Re: [gentoo-user] diskless booting [solved, I hope]

2007-10-01 Thread Dan Farrell 
On Mon, 1 Oct 2007 09:41:43 +0100
Neil Bothwick [EMAIL PROTECTED] wrote:

 Hello Dan Farrell,
 
  I was going to suggest you avoid pxegrub, but I guess you figured
  that out for yourself.  
 
 What's wrong with pxe grub. I use it and it works, so I haven't tried
 pxelinux. Is there a good reason to change if it works?
 
 

I never got it to work last January when I set up my first diskless
host.  I got similar strange errors; it just didn't seem to want to do
anything, although it appeared to be properly configured.

PXElinux was a breeze by comparison, I thought, even though the
configuration files are icky.  But most importantly, it worked, so I
stuck with it under the same principle.  
-- 
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] diskless booting [solved, I hope]

2007-10-01 Thread Bertram Scharpf 
Hi,

Am Montag, 01. Okt 2007, 07:51:36 -0500 schrieb Dan Farrell:
 On Mon, 1 Oct 2007 09:41:43 +0100
 Neil Bothwick [EMAIL PROTECTED] wrote:
   I was going to suggest you avoid pxegrub, but I guess you figured
   that out for yourself.  
  
  What's wrong with pxe grub. I use it and it works, so I haven't tried
  pxelinux. Is there a good reason to change if it works?
  
 I never got it to work last January when I set up my first diskless
 host.  I got similar strange errors; it just didn't seem to want to do
 anything, although it appeared to be properly configured.
 
 PXElinux was a breeze by comparison, I thought, even though the
 configuration files are icky.  But most importantly, it worked, so I
 stuck with it under the same principle.  

I set up a CD-less client just for installation last week
and I did not succeed with PXElinux; then I used Pxegrub and
everything was fine. I admit I have not clue how to manage
an initramfs; with Pxegrub you need RootNFS which I finally
installed correctly after bothering this list with some
stupid posts ...

Bertram


-- 
Bertram Scharpf
Stuttgart, Deutschland/Germany
http://www.bertram-scharpf.de
-- 
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] diskless booting [solved, I hope]

2007-10-01 Thread Roger Mason 
Hello Dan,

Dan Farrell [EMAIL PROTECTED] writes:

 I was going to suggest you avoid pxegrub, but I guess you figured that
 out for yourself.  

 
  I'm almost certain to get stuck so I'll
 probably be back asking again.

 Let me know. 

Well, I had it working on Friday but over the weeekend I tinkered some
more with pixegrub and broke it again.  Now pxelinux won't work
either.

I have the following dhcpd.conf on the host (192.168.0.2):

+dhcpd.conf
ddns-update-style none ;

next-server 192.168.0.2;

option domain-name-servers 192.168.0.2;
option routers 192.168.0.2;

option space PXE;
option PXE.mtftp-ip   code 1 = ip-address;
option PXE.mtftp-cportcode 2 = unsigned integer 16;
option PXE.mtftp-sportcode 3 = unsigned integer 16;
option PXE.mtftp-tmoutcode 4 = unsigned integer 8;
option PXE.mtftp-delaycode 5 = unsigned integer 8;
option PXE.discovery-control  code 6 = unsigned integer 8;
option PXE.discovery-mcast-addr   code 7 = ip-address;

# Declare the subnet where our diskless nodes will live
subnet 192.168.0.0 netmask 255.255.255.0 {
  # Provide PXE clients with appropriate information
  class pxeclient {
match if substring(option vendor-class-identifier, 0, 9) = PXEClient;
vendor-option-space PXE;

# At least one of the vendor-specific PXE options must be set in
# order for the client boot ROMs to realize that we are a PXE-compliant
# server.  We set the MCAST IP address to 0.0.0.0 to tell the boot ROM
# that we can't provide multicast TFTP.

option PXE.mtftp-ip 0.0.0.0;

  }

  host cctp {

  hardware ethernet 00:01:03:ce:52:a8;
  fixed-address 192.168.0.3;
# option option-150 /calcite/boot/grub.lst;   
   
  filename pxelinux.0;
  }

}

allow bootp;
allow booting;
+

I have the following in.tftp on the host (192.168.0.2):

+in.tftpd

# /etc/init.d/in.tftpd

INTFTPD_PATH=/diskless
INTFTPD_USER=nobody

INTFTPD_OPTS=-v -s ${INTFTPD_PATH}
+

I have bzImage, pxelinux.0 and pxelinux.cfg/ in /diskless on the
host. pxelinux.cfg/ contains a default file with these contents:

+pxelinux.cfg/default+

DEFAULT /bzImage
APPEND ip=dhcp root=/dev/nfs nfsroot=192.168.0.2:/diskless/calcite



When I try to boot the client, tcpdump -i eth1 prints the following
dialogue:

tcpdump -i eth1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
11:50:39.930039 IP 0.0.0.0.bootpc  255.255.255.255.bootps: BOOTP/DHCP, Request 
from 00:01:03:ce:52:a8 (oui Unknown), length 548
11:50:39.930886 IP lowalbite.private.bootps  255.255.255.255.bootpc: 
BOOTP/DHCP, Reply, length 300
11:50:42.072242 IP 0.0.0.0.bootpc  255.255.255.255.bootps: BOOTP/DHCP, Request 
from 00:01:03:ce:52:a8 (oui Unknown), length 548
11:50:42.073040 IP lowalbite.private.bootps  255.255.255.255.bootpc: 
BOOTP/DHCP, Reply, length 300
11:50:42.077032 arp who-has lowalbite.private tell calcite.private
11:50:42.077088 arp reply lowalbite.private is-at 00:04:75:77:98:4f (oui 
Unknown)
11:50:42.077165 IP calcite.private.2070  lowalbite.private.tftp:  27 RRQ 
pxelinux.0 octet tsize 0 
11:50:42.080043 IP lowalbite.private.32771  calcite.private.2070: UDP, length 
36
11:50:42.081409 IP calcite.private.2071  lowalbite.private.tftp:  32 RRQ 
pxelinux.0 octet blksize 1456 
11:50:42.084147 IP lowalbite.private.32771  calcite.private.2071: UDP, length 
36
11:50:47.077314 arp who-has calcite.private tell lowalbite.private
11:50:48.077397 arp who-has calcite.private tell lowalbite.private
11:50:49.077484 arp who-has calcite.private tell lowalbite.private

If I connect a terminal to the client I see:

Non-system disk or disk error replace and strike any key when ready


 By the way, if you're looking for performance enhancements to your
 diskless hosts, let me know. I have found some, and am also always
 looking for more.  

Right now I'd be happy to have it working, no matter how slowly.

One think I have found by searching the internet is that pxegrub has
history of poor interaction with 3Com cards, which is what I'm using.

Thanks for any help you can offer.

Roger

-- 
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] diskless booting

2007-10-01 Thread Dan Farrell 
On Mon, 01 Oct 2007 12:57:05 -0230
Roger Mason [EMAIL PROTECTED] wrote:

 Well, I had it working on Friday but over the weeekend I tinkered some
 more with pixegrub and broke it again.  Now pxelinux won't work
 either.

I've attached my dhcpd.conf, sans rndc-key.  Please note that this
configuration has a big block of code that is for dynamic DNS updates.
I kept it in because I found it hard to figure out for myself, and I
figured it would be better to put more out on the web rather than refer
you to sources I don't even know exist.  I don't know if you are
running BIND or a DNS server that can do static updates, but if you
can, I highly suggest it for your own sanity.  

For usefulness of online archives, which probably strip attachments,
here is the same info.  I even annotated it a little.

/*===
dhcpd.conf from spore.ath.cx
===*/

key rndc-key { algorithm hmac-md5;
   secret ;
};

server-identifier zeus.pantheon.spore.ath.cx;
authoritative;

option domain-name-servers 192.168.10.1, 192.168.1.87;
ddns-update-style interim;

use-host-decl-names on;
allow client-updates;

# these two lines are important for net booting.. i think...
option oe-key code 159 = string;
option oe-gateway code 160 = ip-address;

on commit {
if (not static and
((config-option server.ddns-updates = null) or
(config-option server.ddns-updates != 0))) {
if exists oe-key {
set ddns-rev-name =
concat (binary-to-ascii (10, 8, .,
reverse (1, leased-address)), .,
pick (config-option server.ddns-rev-domainname,
in-addr.arpa.));
set full-oe-key = option oe-key;
switch (ns-update (delete (IN, 25, ddns-rev-name, null),
add (IN, 25, ddns-rev-name, full-oe-key,
lease-time / 2)))
{
default:
unset ddns-rev-name;
break;
case NOERROR:
on release or expiry {
switch (ns-update (delete (IN, 25, ddns-rev-name, null))) {
case NOERROR:
unset ddns-rev-name;
break;
}
}
}
}
}
}

default-lease-time 609080;
max-lease-time 1218160;

# tftp server, I believe.
next-server 192.168.10.1;

#barge in and take over any lease you hear of, even if
#you don't remember granting it.  
authoritative

# more pxe settings:
option space PXE;
option PXE.mtftp-ip   code 1 = ip-address;
option PXE.mtftp-cportcode 2 = unsigned integer 16;
option PXE.mtftp-sportcode 3 = unsigned integer 16;
option PXE.mtftp-tmoutcode 4 = unsigned integer 8;
option PXE.mtftp-delaycode 5 = unsigned integer 8;
option PXE.discovery-control  code 6 = unsigned integer 8;
option PXE.discovery-mcast-addr   code 7 = ip-address;

# each subdomain should have a zone entry.  

#wireless, g.spore.ath.cx
zone g.spore.ath.cx. {
   primary 192.168.1.87;
   key rndc-key;
}

#you might well need the in-addr.arpa zone too:

zone 2.168.192.in-addr.arpa. {
   primary 192.168.1.87;
   key rndc-key;
}

# this subnet doesn't support diskless booting.  Yuck, doing that 
# over WIFI would be icky.
subnet 192.168.2.0 netmask 255.255.255.0
{
   option domain-name g.spore.ath.cx;
   # the default route for the subdomain.
   option routers 192.168.1.1;
   option domain-name-servers 192.168.1.87;
}

#pantheon 

# another one of those netbooting things
option option-150 code 150 = text ;

# another zone...
zone pantheon.spore.ath.cx. {
   primary 192.168.10.1;
   key rndc-key;
}

#   ...  and reverse ...
zone 10.168.192.in-addr.arpa. {
   primary 192.168.10.1;
   key rndc-key;

#   ... and the subnet information ...
subnet 192.168.10.0 netmask 255.255.255.0 {
  range 192.168.10.101 192.168.10.199;
  option domain-name-servers 192.168.10.1;
  option domain-name pantheon.spore.ath.cx;
  option routers 192.168.10.1;
  option broadcast-address 192.168.10.255;
  one-lease-per-client on;
  option routers 192.168.10.1;
  option domain-name-servers 192.168.10.1;
  update-static-leases on;
  ddns-domainname pantheon.spore.ath.cx;

#the host entry is required for any host that is to be net booted.
 host apollo{
   # some way to identify
   hardware ethernet 00:04:76:e3:3b:95;
   fixed-address 192.168.10.99;
   option host-name apollo;
   DDNS-hostname apollo;
   # analagous to next server , I guess
   option PXE.mtftp-ip 0.0.0.0;
   # file to be served.  In this case, it's the syslinux preboot
   #execution environment binary. 
   filename pxelinux.0;
 }
#more examples of host entries, all pretty much the same idea.  
host aphrodite{
   hardware ethernet 00:01:02:5F:6E:6B;
   fixed-address 192.168.10.96;
   option host-name aphrodite;
   DDNS-hostname aphrodite;
   option PXE.mtftp-ip 0.0.0.0;
   filename pxelinux.0;
}
host artemis {
   hardware ethernet 00:01:02:46:E7:CC;
   fixed-address 192.168.10.97;
   option host-name artemis;
   DDNS-hostname artemis;
   option PXE.mtftp-ip 0.0.0.0;
   filename pxelinux.0;
}
host matty{
hardware ethernet 00:01:03:20:B8:04;
fixed-address

Re: [gentoo-user] diskless booting [solved, I hope]

2007-09-30 Thread Dan Farrell 
On Sat, 29 Sep 2007 09:55:40 -0230
Roger Mason [EMAIL PROTECTED] wrote:

 Well, the configs were the same as the diskless install docs on the
 Gentoo alt-install page, with suitable modifications of the ip and MAC
 addresses in the dhcpd.conf.  I _was using pxegrub but, on a whim, I
 tried syslinux instead as per the Gentoo diskless howto and, without
 any further reconfiguration beyond pointing the client at pxelinix.0,
 it booted first time.  After some tweaking of the client fstab and
 hosts files it now works fine.

I was going to suggest you avoid pxegrub, but I guess you figured that
out for yourself.  

 
 Thanks for the offer.  I'm planning to add some more clients now that
 I have one working system.  I'm almost certain to get stuck so I'll
 probably be back asking again.

Let me know. 

By the way, if you're looking for performance enhancements to your
diskless hosts, let me know. I have found some, and am also always
looking for more.  


-- 
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] diskless booting [solved, I hope]

2007-09-29 Thread Roger Mason 
Hello Dan,

Dan Farrell [EMAIL PROTECTED] writes:

 On Fri, 28 Sep 2007 14:03:59 -0230
 Roger Mason [EMAIL PROTECTED] wrote:

 The client boot process hangs, with the following dialog between the
 server (192.168.0.2, 00:04:75:77:98:4f) and client (192.168.0.3,
 00:01:03:ce:52:a8) repeated three times:
 
 00:04:75:77:98:4f  00:01:03:ce:52:a8, ARP, length 42: arp who-has
 192.168.0.3 tell 192.168.0.2
 

 what's the config for dhcp/tftp  and what are you using for PXE on the
 client?

Well, the configs were the same as the diskless install docs on the
Gentoo alt-install page, with suitable modifications of the ip and MAC
addresses in the dhcpd.conf.  I _was using pxegrub but, on a whim, I
tried syslinux instead as per the Gentoo diskless howto and, without
any further reconfiguration beyond pointing the client at pxelinix.0,
it booted first time.  After some tweaking of the client fstab and
hosts files it now works fine.

 i think I might be able to help you.

Thanks for the offer.  I'm planning to add some more clients now that
I have one working system.  I'm almost certain to get stuck so I'll
probably be back asking again.

Cheers,

Roger

-- 
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] diskless booting

2007-09-28 Thread Dan Farrell 
On Fri, 28 Sep 2007 14:03:59 -0230
Roger Mason [EMAIL PROTECTED] wrote:

 Hello,
 
 I'm trying to boot a diskless machine, using the instructions in the
 alternative installation guide.
 
 The client boot process hangs, with the following dialog between the
 server (192.168.0.2, 00:04:75:77:98:4f) and client (192.168.0.3,
 00:01:03:ce:52:a8) repeated three times:
 
 00:04:75:77:98:4f  00:01:03:ce:52:a8, ARP, length 42: arp who-has
 192.168.0.3 tell 192.168.0.2
 
 I'm not sure what information is needed to help debug this, but if
 anyone is willing to assist I'll provide whatever is required.
 
 Thanks,
 
 Roger Mason
 

what's the config for dhcp/tftp  and what are you using for PXE on the
client?

i think I might be able to help you.
-- 
[EMAIL PROTECTED] mailing list