debian-mips na indigo2 - bootp problem

Petr's mailing list lists na seznam.cz
Neděle Duben 11 15:00:03 CEST 2004


Zkusil jsem nastavit 2 pocitace jako point to point. Na strave serveru
jsem nastavil tyto soubory: 

dhcpd.conf:

ddns-update-style none;
#ddns-update-style ad-hoc;  # podle gen2
group {
    next-server 192.168.3.1;
    subnet 192.168.3.0 netmask 255.255.255.0 {
	allow bootp;
	}
    host indy {
	hardware ethernet 08:00:69:07:0d:df;
	fixed-address 192.168.3.4;
	option root-path "/2indigo2";
	}
    }
# end of dhcpd.conf

V root adresari soustim script ./indy.local.sh:

# modul for eth added in /etc/rc.d/rc.local
#modprobe eepro100 
# 
# put ip to eth0
#ifconfig eth0 192.168.3.1 netmask 255.255.255.0
#route add -net default gw 192.168.3.1

# maybe shloud be better point-to-point
ifconfig eth0 192.168.3.1 pointopoint 192.168.3.4
#
# feed ports for bootp from indigo2 PROM
echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc
echo 2048 32767 > /proc/sys/net/ipv4/ip_local_port_range
#
# run dhcpd
dhcpd eth0
# and tftpd
/usr/sbin/in.tftpd -l -vv -s /2indigo2
# is this everything I need?	
# end of script

Predpokladam podle dokumentaci, ze mam vse nastaveno.

A zde jsou log soubory: 
-----------------------------------------------------------------------
Na indigu:
>> unsetenv netaddr
>> init
>> bootp():deb-mips1.img     or
>> boot -f bootp()/2indigo/deb-mips1.img 

/var/log/messages ze serveru
Apr 10 12:08:40 darkstar kernel: device eth0 entered promiscuous mode
Apr 10 12:08:46 darkstar dhcpd: BOOTREQUEST from 08:00:69:07:0d:df via
eth0
Apr 10 12:08:46 darkstar dhcpd: BOOTREPLY for 192.168.3.4 to indy
(08:00:69:07:0d:df) via eth0
Apr 10 12:08:50 darkstar dhcpd: BOOTREQUEST from 08:00:69:07:0d:df via
eth0
Apr 10 12:08:50 darkstar dhcpd: BOOTREPLY for 192.168.3.4 to indy
(08:00:69:07:0d:df) via eth0
Apr 10 12:08:55 darkstar dhcpd: BOOTREQUEST from 08:00:69:07:0d:df via
eth0
Apr 10 12:08:55 darkstar dhcpd: BOOTREPLY for 192.168.3.4 to indy
(08:00:69:07:0d:df) via eth0
Apr 10 12:09:00 darkstar dhcpd: BOOTREQUEST from 08:00:69:07:0d:df via
eth0
Apr 10 12:09:00 darkstar dhcpd: BOOTREPLY for 192.168.3.4 to indy
(08:00:69:07:0d:df) via eth0
Apr 10 12:09:10 darkstar kernel: device eth0 left promiscuous mode

z tcpdump:
1081591726.289647 0.0.0.0.bootpc > 255.255.255.255.bootps: [no cksum] 
xid:0x65f6 secs:5 file ""[|bootp] (ttl 255, id 12, len 328)
1081591726.290025 192.168.3.1.bootps > 255.255.255.255.bootpc: 
xid:0x65f6 secs:5 Y:192.168.3.4 S:192.168.3.1 ether 8:0:69:7:d:df file
""[|bootp] (DF) (ttl 64, id 0, len 328)
1081591730.839410 0.0.0.0.bootpc > 255.255.255.255.bootps: [no cksum] 
xid:0x65f6 secs:10 file ""[|bootp] (ttl 255, id 13, len 328)
1081591730.839743 192.168.3.1.bootps > 255.255.255.255.bootpc: 
xid:0x65f6 secs:10 Y:192.168.3.4 S:192.168.3.1 ether 8:0:69:7:d:df file
""[|bootp] (DF) (ttl 64, id 0, len 328)
1081591735.838591 0.0.0.0.bootpc > 255.255.255.255.bootps: [no cksum] 
xid:0x65f6 secs:15 file ""[|bootp] (ttl 255, id 14, len 328)
1081591735.838912 192.168.3.1.bootps > 255.255.255.255.bootpc: 
xid:0x65f6 secs:15 Y:192.168.3.4 S:192.168.3.1 ether 8:0:69:7:d:df file
""[|bootp] (DF) (ttl 64, id 0, len 328)
1081591740.838402 0.0.0.0.bootpc > 255.255.255.255.bootps: [no cksum] 
xid:0x65f6 secs:20 file ""[|bootp] (ttl 255, id 15, len 328)
1081591740.838731 192.168.3.1.bootps > 255.255.255.255.bootpc: 
xid:0x65f6 secs:20 Y:192.168.3.4 S:192.168.3.1 ether 8:0:69:7:d:df file
""[|bootp] (DF) (ttl 64, id 0, len 328)
-----------------------------------------------------------------------
Dalsi zkouska na indigu, kdyz nastavim ip adresu
>> setenv netaddr 192.168.3.4
>> init
>> bootp():deb-mips1.img   or   
>> boot -f bootp()/2indigo/deb-mips1.img 

/var/log/messages:
1081592432.848547 arp who-has 192.168.3.4 tell 192.168.3.4
1081592432.850799 192.168.3.4.bootpc > 255.255.255.255.bootps: [no
cksum]  xid:0x7c87 secs:5 C:192.168.3.4 file ""[|bootp] (ttl 255, id 0,
len 328)
1081592432.851149 192.168.3.1.bootps > 255.255.255.255.bootpc: 
xid:0x7c87 secs:5 C:192.168.3.4 Y:192.168.3.4 S:192.168.3.1 ether
8:0:69:7:d:df file ""[|bootp] (DF) (ttl 64, id 0, len 328)
1081592437.848463 192.168.3.4.bootpc > 255.255.255.255.bootps: [no
cksum]  xid:0x7c87 secs:10 C:192.168.3.4 file ""[|bootp] (ttl 255, id 1,
len 328)
1081592437.848806 192.168.3.1.bootps > 255.255.255.255.bootpc: 
xid:0x7c87 secs:10 C:192.168.3.4 Y:192.168.3.4 S:192.168.3.1 ether
8:0:69:7:d:df file ""[|bootp] (DF) (ttl 64, id 0, len 328)
1081592442.848258 192.168.3.4.bootpc > 255.255.255.255.bootps: [no
cksum]  xid:0x7c87 secs:15 C:192.168.3.4 file ""[|bootp] (ttl 255, id 2,
len 328)
1081592442.848591 192.168.3.1.bootps > 255.255.255.255.bootpc: 
xid:0x7c87 secs:15 C:192.168.3.4 Y:192.168.3.4 S:192.168.3.1 ether
8:0:69:7:d:df file ""[|bootp] (DF) (ttl 64, id 0, len 328)
1081592447.847977 192.168.3.4.bootpc > 255.255.255.255.bootps: [no
cksum]  xid:0x7c87 secs:20 C:192.168.3.4 file ""[|bootp] (ttl 255, id 3,
len 328)
1081592447.848320 192.168.3.1.bootps > 255.255.255.255.bootpc: 
xid:0x7c87 secs:20 C:192.168.3.4 Y:192.168.3.4 S:192.168.3.1 ether
8:0:69:7:d:df file ""[|bootp] (DF) (ttl 64, id 0, len 328)

z tcpdump:
Apr 10 12:20:25 darkstar kernel: device eth0 entered promiscuous mode
Apr 10 12:20:32 darkstar dhcpd: BOOTREQUEST from 08:00:69:07:0d:df via
eth0
Apr 10 12:20:32 darkstar dhcpd: BOOTREPLY for 192.168.3.4 to indy
(08:00:69:07:0d:df) via eth0
Apr 10 12:20:37 darkstar dhcpd: BOOTREQUEST from 08:00:69:07:0d:df via
eth0
Apr 10 12:20:37 darkstar dhcpd: BOOTREPLY for 192.168.3.4 to indy
(08:00:69:07:0d:df) via eth0
Apr 10 12:20:42 darkstar dhcpd: BOOTREQUEST from 08:00:69:07:0d:df via
eth0
Apr 10 12:20:42 darkstar dhcpd: BOOTREPLY for 192.168.3.4 to indy
(08:00:69:07:0d:df) via eth0
Apr 10 12:20:47 darkstar dhcpd: BOOTREQUEST from 08:00:69:07:0d:df via
eth0
Apr 10 12:20:47 darkstar dhcpd: BOOTREPLY for 192.168.3.4 to indy
(08:00:69:07:0d:df) via eth0
Apr 10 12:20:56 darkstar kernel: device eth0 left promiscuous mode

behem bootp(): jsem jeste spustil prikaz:
arping -I eth0 192.168.3.4 # coz je ip adresa indiga

ARPING 192.168.3.4 from 192.168.3.1 eth0
Unicast reply from 192.168.3.4 [08:00:69:07:0D:DF]  0.914ms
Unicast reply from 192.168.3.4 [08:00:69:07:0D:DF]  0.861ms
Unicast reply from 192.168.3.4 [08:00:69:07:0D:DF]  0.810ms
Unicast reply from 192.168.3.4 [08:00:69:07:0D:DF]  0.823ms
Sent 4 probes (1 broadcast(s))
Received 4 response(s)
-----------------------------------------------------------------------
Jeste jsem zkousel bootp():deb-mips1.img root=/dev/ram0 podle gentoo
kucharky a taky bez uspechu.

Petr

On Sun, 11 Apr 2004 12:00:07 +0200
Pavel na Janik.cz (Pavel Janík) wrote:

>    > videt. Presto se mi nedari, aby dhcpd server ip adresu pridelil
>    > natoz, aby se stahnul tftpboot image.
> 
> A co je v logu?


Další informace o konferenci Linux