On Sunday 18 July 2004 16:08, ghrt wrote:
> intel eepro100
Puteam sa fac pariu :)
Cu alea mai vechi care stiau pxe 1.xx am avut si eu problema sa nu se
identifice corect .... cu alea 2.xx nu mai erau probleme.
>
> > Poate eu am deja facut pt. el...
>
> si etherboot-ul a facut un eepro100.zpxe care se paer (conform
> tcpdump) ca e ok
>
> problema este in dhcpd.conf: nu face corect indentificarea lui
> vendor-class nu stiu cum:
>
> if substring (option vendor-class-identifier,1,9) = "Etherboot" {
> filename "/tftpboot/ghrt.01";
> }
> else { filename "/tftpboot/eepro100.zpxe";}
>
> tot timpul furnizeaza eepro... desi VC: in tcpdump arata corect, prima
> data "PXEClient..." si a doua oara "Etherboot-5.3...."
io pt aste folosesc pxeboot dar ma rog ...
uite cum e la mine:
option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
class "pxeclients" {
match if substring (option vendor-class-identifier, 0, 9) =
"PXEClient";
option vendor-class-identifier "PXEClient";
option PXE.mtftp-ip 0.0.0.0;
vendor-option-space PXE;
#SETTING DEFAULT BOOTROM FOR PXE CARDS
filename "pxe/eb-5.0.9-eepro100.lzpxe";
}
Sper sa te ajuta, daca nu mai sapa dupa pxeboot, acuma depinde si de distro
folosit.
--
Enexis
Keresztely-Krall Gyula
---
Detalii despre listele noastre de mail: http://www.lug.ro/
