Mailinglist Archive: opensuse (1839 mails)

[Anton Aylward <anton.aylward@xxxxxxxxxx>]

Mark Misulich said the following on 09/28/2010 03:18 PM:


> service tftp
>   {
>         disable                 = no
>         socket_type             = dgram
>         wait                    = yes
>         user                    = root
>         server                  = /usr/sbin/in.tftpd
>         server_args             = -v -s /var/lib/tftpboot

that means chroot to /var/lib/tftpboot
so the file "pxelinux.0" should be there.
Yes?

>         only_from               = 192.168.1. 127.0.0.1
>   }

Well there's one problem!
You DHCP is handning out ...

> > subnet 192.168.1.0 netmask 255.255.255.0 {
> >   range dynamic-bootp 192.168.0.1 192.168.1.254;
> > }

Now that looks odd.
Either the "192.168.0.1" is ignoed 'cos of the "subnet 192.168.1.0"
or it isn't.
If it isn't it means you're handing our addresses in "192.169.0.x" until
they are exhausted.

So if the PE machine gets "192.168.0.1" the the "only_from" of the TFTP
isn't going to repsond.

I don't know the code, but I wouldn't go there if I was you.

You may also be clashing with your router's address :-!
If you're starting at 192.168.0.1 ... isn't that the router's address?

Well actually the DHCP server is supposed to check IP addresses to see
if they are in use by sending an ICMP Echo request message to that
address. It expects an response within a second.   You can test this
from the command line of your server to see if the router is presonding
to ping requests.

If I were you I'd use a stanza in the DHCP config like

        host laptop1 {
                        hardware ethernet AB:CD:EF:12:34:56  ;
                        fixed-address 192.168.1.10 ;
        }
and
        host laptop1 {
                        hardware ethernet EF:12:AB:12:34:AB  ;
                        fixed-address 192.168.1.11 ;
        }

Use symbolic names.
This way you can be sure of the address.

If you insist on using the form
> > subnet 192.168.1.0 netmask 255.255.255.0 {
then I'd make sure that the range is ONLY in that subnet.
And I'd use the "range" statement
KISS

subnet 192.168.1.0 netmask 255.255.255.0 {
  range  192.168.1.1 192.168.1.254;
}

I'm aware that there are a number of thigns that DHCP servers can do
with BOOTP clients, but they are not relevant here.  We are not talking
about a mixed pool of BOOTP and non-BOOTP clients, we are talking about
a PXE installation.

I'd suggest a look at
http://www.stanford.edu/~alfw/PXE-Kickstart/PXE-Kickstart-4.html


-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx