sherfu deen wrote:
> 
> dear jacques,
> 
> * Send me the full dhcpd.conf file...
> 
> * ANd try to change the server ip that was wrong..
> change server ip to 192.168.0.1..
> 
> * And boot the workstation...
> 
> Regards,
> sherfudeen M

Dear Sherfu,

OK I did what you asked for:

--- dhcpd.conf file: 

# Sample configuration file for ISCD dhcpd
#
# Don't forget to set run_dhcpd=1 in /etc/init.d/dhcpd
# once you adjusted this file and copied it to /etc/dhcpd.conf.
#

default-lease-time            86400;
max-lease-time                86400;

#option subnet-mask            255.255.255.0;
#option broadcast-address      192.168.0.255;
#option routers                192.168.0.254;
option routers                192.168.1.1;
#option domain-name-servers    192.168.0.254;
option domain-name-servers    192.168.1.1;
option domain-name            "lutecium.org";
option root-path              "/tftpboot/lts/ltsroot";

subnet 10.0.0.0 netmask 255.0.0.0 {
        range 10.0.0.0 10.0.0.255;
}

shared-network LUTECIUM {
    subnet 192.168.1.0 netmask 255.255.255.240 {
        range 192.168.1.1 192.168.1.15;
    }
    subnet 192.168.0.0 netmask 255.255.255.0 {
        range 192.168.0.5 192.168.0.253;
    }
}

group   {
    use-host-decl-names       on;
    option log-servers        192.168.1.1;
#    next-server        192.168.0.1;

    host cluster3 {
        hardware ethernet     0:40:5:e3:79:fc;
        fixed-address         192.168.0.3;
        filename              "/tftpboot/lts/vmlinuz.ne2000";
    }
}

--- I put server to 192.168.0.1 (namely eth1:0)


after boot ping 192.168.0.1 works
ping 192.168.0.1 works

--- I boot ws:

here is the end of boot message on ws:

IP-Config: Gateway not on directly connected network
Looking up port of RPC 100003/2 on 192.168.0.1
Looking up port of RPC 100005/1 on 192.168.0.1
VFS: Mounted Root (NFS filesystem)
Freeing unused kernel memory: 56k freed
nfs: Server 192.168.0.1 not responding, timed out
nfs: Server 192.168.0.1 not responding, still trying

as you see in this case I get the "Gateway not on directly connected network"
and then server is not responding. 

Here is the result of tcpdump for eth1:


09:44:58.801728 < 192.168.0.3.800 > 192.168.0.1.1027: udp 68
09:45:03.792602 < 192.168.0.3.800 > 192.168.0.1.1027: udp 68
09:45:03.793869 > arp who-has 192.168.0.3 tell 192.168.0.1 (0:80:ad:84:b1:7d)
09:45:03.794368 < arp reply 192.168.0.3 is-at 0:40:5:e3:79:fc
(0:80:ad:84:b1:7d)
09:45:07.636372 > 192.168.0.1.1027 > 192.168.0.3.800: udp 60
09:45:07.637268 < 192.168.0.3.57707121 > 192.168.0.1.2049: 100 getattr fh
Unknown/1
09:45:07.639345 > 192.168.0.1.2049 > 192.168.0.3.57707121: reply ok 96 getattr
DIR 40755 ids 0/0 sz 1024 
09:45:07.640187 < 192.168.0.3.74484337 > 192.168.0.1.2049: 100 statfs fh
Unknown/1
09:45:07.641148 > 192.168.0.1.2049 > 192.168.0.3.74484337: reply ok 48 statfs
tsize 8192 bsize 1024 blocks 1740759 bfree 874497 bavail 784533
09:45:07.642019 < 192.168.0.3.91261553 > 192.168.0.1.2049: 108 lookup fh
Unknown/1 "dev"
09:45:07.646169 > 192.168.0.1.2049 > 192.168.0.3.91261553: reply ok 128 lookup
fh Unknown/1
09:45:07.647039 < 192.168.0.3.108038769 > 192.168.0.1.2049: 112 lookup fh
Unknown/1 "console"
09:45:07.647574 > 192.168.0.1.2049 > 192.168.0.3.108038769: reply ok 128
lookup fh Unknown/1
09:45:07.648580 < 192.168.0.3.124815985 > 192.168.0.1.2049: 108 lookup fh
Unknown/1  [|nfs]
09:45:07.651540 > 192.168.0.1.2049 > 192.168.0.3.124815985: reply ok 128
lookup fh Unknown/1
09:45:07.652393 < 192.168.0.3.141593201 > 192.168.0.1.2049: 108 lookup fh
Unknown/1  [|nfs]
09:45:07.653619 > 192.168.0.1.2049 > 192.168.0.3.141593201: reply ok 128
lookup fh Unknown/1
09:45:07.654574 < 192.168.0.3.158370417 > 192.168.0.1.2049: 112 read fh
Unknown/1 4096 bytes @ 0
09:45:08.352493 < 192.168.0.3.158370417 > 192.168.0.1.2049: 112 read fh
Unknown/1 4096 bytes @ 0
09:45:09.752432 < 192.168.0.3.158370417 > 192.168.0.1.2049: 112 read fh
Unknown/1 4096 bytes @ 0
09:45:12.552322 < 192.168.0.3.158370417 > 192.168.0.1.2049: 112 read fh
Unknown/1 4096 bytes @ 0

--- here is the ipconfig:

eth1      Link encap:Ethernet  HWaddr 00:80:AD:84:B1:7D  
          inet addr:192.168.1.1  Bcast:192.168.1.15  Mask:255.255.255.240
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:49348 errors:0 dropped:0 overruns:0 frame:0
          TX packets:59281 errors:0 dropped:0 overruns:0 carrier:0
          collisions:4 txqueuelen:100 
          Interrupt:9 Base address:0x340 

eth1:0    Link encap:Ethernet  HWaddr 00:80:AD:84:B1:7D  
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:9 Base address:0x340 

Thanks for helping me

Jacques


-- 
Dr. Jacques B. Siboni mailto:[EMAIL PROTECTED]
8 pass. Charles Albert, F75018 Paris, France
Tel. & Fax: 33 (0) 1 42 28 76 78
Home Page: http://www.lutecium.org/jacsib/

_____________________________________________________________________
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

Reply via email to