Connect. Communicate. Collaborate. Securely.

Domů » Česky » Kerio Control » KC DHCP a PXE
  •  
sheriff6241 je nyní offline sheriff6241

Příspěvky: 110
Odeslat poštu tomuto uživateli
Zdravim,

vo firme pouzivame PXE server (na stroji s KC) pre bootovanie cez LAN na instalaciu OS na klientoch. Zaciname nasadzovat Windows 7 ale nedari sa spustat instalacne prostredie WinPE 3.0
Ine utility cez PXE funguju.

Zistil som dovod:

Mnohe PXE implementacie v sietovych kartach vyzaduju od DHCP servera hodnotu "next-server" (inde som ju videl nazvanu ako ServerIP alebo siaddr).

Nestaci im DHCP option 66 a 67.

Tu je vypis z network monitora na klientovi:

Frame: Number = 131, Captured Frame Length = 365, MediaType = ETHERNET
+ Ethernet: Etype = Internet IP (IPv4),DestinationAddress:[FF-FF-FF-FF-FF-FF],SourceAddress:[00-11-25-22-32-1B]
+ Ipv4: Src = 192.168.64.1, Dest = 255.255.255.255, Next Protocol = UDP, Packet ID = 29967, Total IP Length = 351
+ Udp: SrcPort = BOOTP server(67), DstPort = BOOTP client(68), Length = 331
- Dhcp: Reply, MsgType = ACK, TransactionID = 0x2A87C5FE
    OpCode: Reply, 2(0x02)
    Hardwaretype: Ethernet
    HardwareAddressLength: 6 (0x6)
    HopCount: 0 (0x0)
    TransactionID: 713541118 (0x2A87C5FE)
    Seconds: 0 (0x0)
  - Flags: 32768 (0x8000)
     Broadcast: (1...............) Broadcast
     Reserved: (.000000000000000)
    ClientIP: 0.0.0.0
    YourIP: 192.168.65.120
    ServerIP: 0.0.0.0
    RelayAgentIP: 0.0.0.0
  - ClientHardwareAddress: 08-00-27-87-C5-FE
     EthernetAddress: 08-00-27-87-C5-FE
    ServerHostName: 
    BootFileName: 
    MagicCookie: 99.130.83.99
  + MessageType: ACK - Type 53
  + ServerIdentifier: 192.168.64.1 - Type 54
  + IPAddressLeaseTime: Subnet Mask: 1 day(s),0 hour(s) 0 minute(s) 0 second(s) - Type 51
  + SubnetMask: 255.255.240.0 - Type 1
  + Router: 192.168.64.1 - Type 3
  - DomainNameServer: 0.3232251909.3232251907.3232251905 - Type 6
     Code: Domain Name Server, 6(0x06)
     Length: 12 UINT8(s)
   + IpAddress: 
  - TFTPServerName: 192.168.64.1 - Type 66
     Code: TFTP Server Name, 66(0x42)
     Length: 13 UINT8(s)
     Name: 192.168.64.1
  - Bootfilename: pxelinux.0 - Type 67
     Code: Bootfile Name, 67(0x43)
     Length: 11 UINT8(s)
     Name: pxelinux.0
  - End: 
     Code: End of Options, 255(0xFF)


Ako vidiet, ServerIP je 0.0.0.0, mala by tam byt IP adresa servera poskytujuceho bootstrap.

Problem je, ze PXE klient potom sa snazi bootmgr.exe nacitat z IP adresy 0.0.0.0, co samozrejme nedopadne dobre Sad

  Frame: Number = 497, Captured Frame Length = 75, MediaType = ETHERNET
+ Ethernet: Etype = Internet IP (IPv4),DestinationAddress:[FF-FF-FF-FF-FF-FF],SourceAddress:[08-00-27-87-C5-FE]
- Ipv4: Src = 192.168.65.120, Dest = 0.0.0.0, Next Protocol = UDP, Packet ID = 140, Total IP Length = 61
  + Versions: IPv4, Internet Protocol; Header Length = 20
  + DifferentiatedServicesField: DSCP: 0, ECN: 0
    TotalLength: 61 (0x3D)
    Identification: 140 (0x8C)
  + FragmentFlags: 0 (0x0)
    TimeToLive: 20 (0x14)
    NextProtocol: UDP, 17(0x11)
    Checksum: 41988 (0xA404)
    SourceAddress: 192.168.65.120
    DestinationAddress: 0.0.0.0
+ Udp: SrcPort = 2072, DstPort = TFTP, Trivial File Transfer Protocol(69), Length = 41
+ Tftp:  Read Request - File: bootmgr.exe, Transfer Mode: octet blksize: 1456 


Ako dalej? Je mozne konfigurovat server v DHCP aby posielal "next-server" resp "siaddr" podla RFC2131? Napriklad totoznu s Option 66 ?

DHCP server na linuxoch podporuje tuto moznost.

RFC2131 hovori:
Citát:
DHCP clarifies the interpretation of the 'siaddr' field as the
address of the server to use in the next step of the client's
bootstrap process. A DHCP server may return its own address in the
'siaddr' field, if the server is prepared to supply the next
bootstrap service (e.g., delivery of an operating system executable
image).

[Aktualizováno: Út, 25 leden 2011 17:12]

Předchozí téma: Kerio VPN vs DNS
Další téma: Vlastní DNS
Jít na fórum:
  


Disclaimer:
Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Aktuální čas: Čt srp 17 19:13:26 CEST 2017

Celkový čas potřebný k vygenerování této stránky: 0.00320 vteřin
.:: Kontakt :: Domů ::.
Běží na: FUDforum 3.0.4.