Separate out the concept of "hardware maximum supported frame length" and "configured link MTU", and limit the latter according to the former. In networks where the DHCP-supplied link MTU is inconsistent with the hardware or driver capabilities (e.g. a network using jumbo frames), this will result in iPXE advertising a TCP MSS consistent with a size that can actually be received. Note that the term "MTU" is typically used to refer to the maximum length excluding the link-layer headers; we adopt this usage. Signed-off-by: Michael Brown <mcb30@ipxe.org>tags/v1.20.1
|
||
397 | 397 |
|
398 | 398 |
|
399 | 399 |
|
400 |
|
|
400 |
|
|
401 |
|
|
401 | 402 |
|
402 | 403 |
|
404 |
|
|
405 |
|
|
406 |
|
|
407 |
|
|
408 |
|
|
409 |
|
|
403 | 410 |
|
404 | 411 |
|
405 | 412 |
|
|
||
323 | 323 |
|
324 | 324 |
|
325 | 325 |
|
326 |
|
|
326 | 327 |
|
327 | 328 |
|
328 | 329 |
|
|
||
393 | 393 |
|
394 | 394 |
|
395 | 395 |
|
396 |
|
|
396 |
|
|
397 |
|
|
397 | 398 |
|
398 | 399 |
|
399 | 400 |
|
|
||
410 | 411 |
|
411 | 412 |
|
412 | 413 |
|
413 |
|
|
414 |
|
|
414 | 415 |
|
415 |
|
|
416 |
|
|
417 |
|
|
416 |
|
|
417 |
|
|
418 |
|
|
419 |
|
|
420 |
|
|
421 |
|
|
422 |
|
|
423 |
|
|
424 |
|
|
425 |
|
|
426 |
|
|
418 | 427 |
|
419 | 428 |
|
420 | 429 |
|
421 | 430 |
|
422 | 431 |
|
423 |
|
|
424 |
|
|
432 |
|
|
425 | 433 |
|
426 | 434 |
|
427 | 435 |
|
|
||
663 | 663 |
|
664 | 664 |
|
665 | 665 |
|
666 |
|
|
667 |
|
|
668 |
|
|
669 |
|
|
670 |
|
|
671 |
|
|
666 | 672 |
|
667 | 673 |
|
668 | 674 |
|
|
||
144 | 144 |
|
145 | 145 |
|
146 | 146 |
|
147 |
|
|
148 |
|
|
147 |
|
|
149 | 148 |
|
150 | 149 |
|
151 | 150 |
|