20.01.2014 Views

Lectures notes for 2010 - KTH

Lectures notes for 2010 - KTH

Lectures notes for 2010 - KTH

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

BOOTP: Bootstrap Protocol (RFC 951)<br />

Although you can figure out who you are, i.e., your IP address, via RARP - many<br />

machines want more in<strong>for</strong>mation.<br />

BOOTP requests and answer are sent via UDP (port 67 server; port 68 client)<br />

• so it is easy to make a user space server<br />

• the client (who wants the answer) need not have a full TCP/IP, it can simply send what looks<br />

like a UDP datagram with a BOOTP request 1 .<br />

Opcode (1=request,<br />

2=reply)<br />

hardware type<br />

(1=ethernet)<br />

number of seconds<br />

hardware address length hop count<br />

(6 <strong>for</strong> ethernet)<br />

transaction ID<br />

unused<br />

client IP address<br />

your IP address<br />

server IP address<br />

gateway IP address<br />

client hardware address (16 bytes of space)<br />

server hostname (64 bytes)<br />

Boot file name (128 bytes)<br />

Vendor specific in<strong>for</strong>mation (64 bytes)<br />

1. see Stevens, Vol. 1, figure 16.2, pg. 216<br />

Maguire BOOTP: Bootstrap Protocol (RFC 951) 4: 30 of 74<br />

maguire@kth.se <strong>2010</strong>.03.21 Internetworking/Internetteknik

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!