---

Fra en ltsp-mallingliste har jeg fået dette råd:

Your dhcpd.conf file shows an IP address of something
like 192.168.0.*, but you don't have an interface
setup with an address in that range.

Where did the '10.0.0.3' address come from ?

Is that address needed to connect to other machines on
the net ?

If you only have one ethernet interface, but you want to
have multiple IP addresses, you can add an aliased interface
like this:

ifconfig eth0:0 192.168.0.254

That will add a 2nd address to your interface.


If you want to make that change permanent, you can
go into the /etc/sysconfig/network-scripts directory
and copy the file called 'ifcfg-eth0' to ifcfg-eth0:0,
and edit the new file and make the appropriate changes
for the new IP address. Then, next time you boot,
the eth0:0 interface will come up automatically.

Er det her ok skrevet? ( jeg har tilføjet nederste linje)

Øhh, det er det ikke. Det giver nemlig en fejlmeddeelse. Så spørgsmålet
skal snarere lyde:

Hvordan gøres det rigtigt?

BOOTPROTO="dhcp"
IPADDR="193.141.17.202"
NETMASK=
BROADCAST=
NETWORK=
STARTMODE=onboot
UNIQUE='_+Pw.GB4ZS2NjMdE'
ifconfig eth0:0 192.168.0.254


hilsen Claus

---

Den Mon, 15 Jul 2002 15:44:38 +0200 skrev claus Christian Larsen:
>Er det her ok skrevet? ( jeg har tilføjet nederste linje)
>
>Øhh, det er det ikke. Det giver nemlig en fejlmeddeelse. Så spørgsmålet
>skal snarere lyde:
>
>Hvordan gøres det rigtigt?
>
>BOOTPROTO="dhcp"
>IPADDR="193.141.17.202"
>NETMASK=
>BROADCAST=
>NETWORK=
>STARTMODE=onboot
>UNIQUE='_+Pw.GB4ZS2NjMdE'
>ifconfig eth0:0 192.168.0.254

Det kan du ikke gøre der. Du er nødt til at vente til efter eth0 er
aktiveret. Enten ved at flytte det til den rigtige opstartsfil, eller
ved at lave en ifconfig eth0 up inden.

Mvh
Kent
--
Hvis man ikke kan lide klassisk musik, er det sandsynligvis fordi
lydkvaliteten er for dårlig. Klassisk musik kræver et godt anlæg.

---

claus Christian Larsen wrote:

> ifconfig eth0:0 192.168.0.254

> If you want to make that change permanent, you can
> go into the /etc/sysconfig/network-scripts directory
> and copy the file called 'ifcfg-eth0' to ifcfg-eth0:0,
> and edit the new file and make the appropriate changes
> for the new IP address. Then, next time you boot,
> the eth0:0 interface will come up automatically.
>
> Er det her ok skrevet? ( jeg har tilføjet nederste linje)

> Hvordan gøres det rigtigt?

> BOOTPROTO="dhcp"
> IPADDR="193.141.17.202"
> NETMASK=
> BROADCAST=
> NETWORK=
> STARTMODE=onboot
> UNIQUE='_+Pw.GB4ZS2NjMdE'
> ifconfig eth0:0 192.168.0.254

Opret ifcfg-eth0:0 med indholdet:

DEVICE="eth0:0"
BOOTPROTO="none"
IPADDR="192.168.0.254"
NETMASK="255.255.255.0"
ONBOOT="yes"

og fjern den tilføjede 'ifconfig'-linje fra ifcfg-eth0.

/Rasmus

--
-- [ Rasmus "Møffe" Bøg Hansen ] ---------------------------------------
I don't suffer from insanity, i enjoy every minute of it!
----------------------------------[ moffe at amagerkollegiet dot dk ] --

---

Rasmus Bøg Hansen wrote:

>
> Opret ifcfg-eth0:0 med indholdet:
>
> DEVICE="eth0:0"
> BOOTPROTO="none"
> IPADDR="192.168.0.254"
> NETMASK="255.255.255.0"
> ONBOOT="yes"
>
> og fjern den tilføjede 'ifconfig'-linje fra ifcfg-eth0.
>
> /Rasmus


Okay, det ser meget bedre ud.

Tak for hjælp.

hilsen Claus.

---

Rasmus Bøg Hansen wrote:

> Opret ifcfg-eth0:0 med indholdet:
>
> DEVICE="eth0:0"
> BOOTPROTO="none"
> IPADDR="192.168.0.254"
> NETMASK="255.255.255.0"
> ONBOOT="yes"

Takker for svar ( lidt forsinket pga. sommerferie ), men det fik startet
dhcp.

Jeg har spurgt en gang til på mallinglisten fordi jeg ikke kan få gang i
et ltsp-netværk. Jeg vil gerne have lidt hjælp ang. dette:

jam@McQuil.Com wrote:

Claus,

I see a couple of problems:

1) The server has an IP address of 0.0.0.0

2) The kernel is defaulting to '/tftpboot/kernel'


This indicates to me that it wasn't a Linux dhcp server
that offered the DHCP info. It should at least have
a valid IP address. And, if your dhcp server is
configured properly on your linux server, the kernel
should be something like: /lts/vmlinuz-2.4.18-ltsp-1


I'm guessing that either a windows NT or 2k system on your
network is offering that info, or you have a router that is
doing dhcp-relay or in fact is a dhcp server.

For testing purposes, you should completely isolate your
workstation and server, so that there is nothing else on
your network. Then, see if you can get your dhcp server
working on the linux server.

And, see if you can figure out which device on your network
is currently offering dhcp replies.

Jim McQuillan
jam@Ltsp.org



On Tue, 30 Jul 2002, claus Christian Larsen wrote:

Jan Humme wrote:


Unless of course you provide some detailed information about eg. the boot
process of your LTSP-terminal, where it gets stuck, what info is on the
screen etc. etc.

okay.

The terminal boots like this:


000021.0000 done
rom segment 0x0800 length 0x4000 reloc 0x9400
a20 enabled via bios
Etherboot 5.0.6 (GPL) Tagged ELF for for [3c5x9]
Boot from (N)etwork or from (L)ocal? N
Probing...[3c5x9]3c5x9 board on isa at 0x0300 - 10baseT
Ethernet address: 00:20:AF:21:6b:D4
Searching for server (DHCP)...
...Me: 10.0.0.2, Server: 0.0.0.0, Gateway 10.0.0.1
Loading 0.0.0.0:/tftpboot/kernel.......

and then nothing more is happening.

I do not have a network but i am sharing and adsl-hubswitsh with a
windows-xp.

I dont know if the windowssystem are the resons to the "funny" ipadress
of the terminal. Or if my windows system are disturbing my linuxsystem?

Suse 8.0



With regards
Claus Larsen










-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.openprojects.net

---

claus Christian Larsen wrote:

> Jeg har spurgt en gang til på mallinglisten fordi jeg ikke kan få gang i
> et ltsp-netværk. Jeg vil gerne have lidt hjælp ang. dette:

> 1) The server has an IP address of 0.0.0.0
>
> 2) The kernel is defaulting to '/tftpboot/kernel'

> 000021.0000 done
> rom segment 0x0800 length 0x4000 reloc 0x9400
> a20 enabled via bios
> Etherboot 5.0.6 (GPL) Tagged ELF for for [3c5x9]
> Boot from (N)etwork or from (L)ocal? N
> Probing...[3c5x9]3c5x9 board on isa at 0x0300 - 10baseT
> Ethernet address: 00:20:AF:21:6b:D4
> Searching for server (DHCP)...
> ..Me: 10.0.0.2, Server: 0.0.0.0, Gateway 10.0.0.1
> Loading 0.0.0.0:/tftpboot/kernel.......

Hvordan ser din dhcpd.conf ud?

/Rasmus

--
-- [ Rasmus "Møffe" Bøg Hansen ] ---------------------------------------
To alcohol!
The cause of - and solution to - all of life's problems!
-- Homer Simpson
----------------------------------[ moffe at amagerkollegiet dot dk ] --

---

Rasmus Bøg Hansen wrote:

> Hvordan ser din dhcpd.conf ud?

linux:/etc # cat dhcpd.conf

ddns-update-style interim;
default-lease-time 21600;
max-lease-time 21600;

option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option routers 192.168.0.254;
option domain-name-servers 192.168.0.254;
option domain-name "yourdomain.com";
option root-path "192.168.0.254:/opt/ltsp/i386";

option option-128 code 128 = string;
option option-129 code 129 = text;

shared-network WORKSTATIONS {
subnet 192.168.0.0 netmask 255.255.255.0 {
}
}

group {
use-host-decl-names on;
option log-servers 192.168.0.254;

host ws001 {
hardware ethernet 00:E0:06:E8:00:84;
fixed-address 192.168.0.1;
filename "/lts/vmlinuz-2.4.9-ltsp-6";
option option-128 e4:45:74:68:00:00;
option option-129 "NIC=eepro100";
}
host ws002 {
hardware ethernet 00:D0:09:30:6A:1C;
fixed-address 192.168.0.2;
filename "/lts/vmlinuz-2.4.9-ltsp-6";
option option-128 e4:45:74:68:00:00;
option option-129 "NIC=tulip";
}
}
linux:/etc #

Hilsen Claus

---

claus Christian Larsen wrote:

> option root-path "192.168.0.254:/opt/ltsp/i386";

Du skal svjh ikke have servernavn eller -IP med i root-path, men angive det
som:

option root-path "/opt/ltsp/i386";
option server-name "192.168.0.254";

/Rasmus

--
-- [ Rasmus "Møffe" Bøg Hansen ] ---------------------------------------
Because I don't want to force you to follow my philosophy, even though
it happens to be the only possible correct philosophy.
-- Ted Lemon
----------------------------------[ moffe at amagerkollegiet dot dk ] --

---

Rasmus Bøg Hansen wrote:
> claus Christian Larsen wrote:
>
>
>>option root-path "192.168.0.254:/opt/ltsp/i386";
>>
>
> Du skal svjh ikke have servernavn eller -IP med i root-path, men angive det
> som:
>
> option root-path "/opt/ltsp/i386";
> option server-name "192.168.0.254";


Efter at jeg har slået dhcp fra i min adslrooter og fået en fast ip,
brokker min dhcpd.conf sig:

linux:/etc # rcdhcpd start
Starting DHCP server Internet Software Consortium DHCP Server V3.0.1rc6
Copyright 1995-2001 Internet Software Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
//etc/dhcpd.conf line 17: unknown option dhcp.server-name
option server-name "192.168.0.254"
^
Configuration file errors encountered -- exiting

If you did not get this software from ftp.isc.org, please
get the latest from ftp.isc.org and install that before
requesting help.

If you did get this software from ftp.isc.org and have not
yet read the README, please read it before requesting help.
If you intend to request help from the dhcp-server@isc.org
mailing list, please read the section on the README about
submitting bug reports and requests for help.

Please do not under any circumstances send requests for
help directly to the authors of this software - please
send them to the appropriate mailing list as described in
the README file.

exiting.
failed
linux:/etc #

linux:/etc # cat dhcpd.conf






ddns-update-style interim;
default-lease-time 21600;
max-lease-time 21600;

option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option routers 192.168.0.254;
option domain-name-servers 192.168.0.254;
option domain-name "yourdomain.com";
option root-path "/opt/ltsp/i386";
option server-name "192.168.0.254";

option option-128 code 128 = string;
option option-129 code 129 = text;

shared-network WORKSTATIONS {
subnet 192.168.0.0 netmask 255.255.255.0 {
}
}

group {
use-host-decl-names on;
option log-servers 192.168.0.254;

host ws001 {
hardware ethernet 00:E0:06:E8:00:84;
fixed-address 192.168.0.1;
filename "/lts/vmlinuz-2.4.9-ltsp-6";
option option-128 e4:45:74:68:00:00;
option option-129 "NIC=eepro100";
}
host ws002 {
hardware ethernet 00:D0:09:30:6A:1C;
fixed-address 192.168.0.2;
filename "/lts/vmlinuz-2.4.9-ltsp-6";
option option-128 e4:45:74:68:00:00;
option option-129 "NIC=tulip";
}
}
linux:/etc #

Hilsen Claus

---

claus Christian Larsen wrote:

> Rasmus Bøg Hansen wrote:
>> claus Christian Larsen wrote:
>>
>>
>>>option root-path "192.168.0.254:/opt/ltsp/i386";
>>>
>>
>> Du skal svjh ikke have servernavn eller -IP med i root-path, men angive
>> det som:
>>
>> option root-path "/opt/ltsp/i386";
>> option server-name "192.168.0.254";

> //etc/dhcpd.conf line 17: unknown option dhcp.server-name
> option server-name "192.168.0.254"
> ^

Ups, det skal være "server-name 192.168.0.254" og ikke en option (den skal
formentlig heller ikke have "'er omkring).

Iøvrigt ser det ud til at man kan bruge begge metoder (med separat root-path
og server-name såvel som begge dele samlet i root-path).

/Rasmus

--
-- [ Rasmus "Møffe" Bøg Hansen ] ---------------------------------------
Those who write "Optimized for Netscape" og "Best viewed with MSIE"
never figured out the difference between the WWW and a Word Perfect
4.2 Document.
----------------------------------[ moffe at amagerkollegiet dot dk ] --

---

Rasmus Bøg Hansen wrote:

>
> Ups, det skal være "server-name 192.168.0.254" og ikke en option (den skal
> formentlig heller ikke have "'er omkring).

Ganske rigtigt. Den er nu oppe og køre, men tak for hjælp.

Hilsen Claus