Skip to main content
Information Security

Return to Answer

deleted 4 characters in body
Source Link
schroeder ♦
schroeder ♦
  • 132.1k
  • 55
  • 307
  • 348

youYou can use netstat nmap for this; read my answer here:

https://serverfault.com/questions/993783/how-can-i-check-my-pxe-server-configuration/

gatheringGathering the different answers and filtering by e.g. macMAC address, you can easily pinpoint the presence of a rogue PXE server.

It should be considered that PXE information (NBP and TFTP server IP) can be located either at the body of the DHCPOFFER packet (file and next-server fields) or as the corresponding DHCP options.

you can use netstat nmap for this; read my answer here:

https://serverfault.com/questions/993783/how-can-i-check-my-pxe-server-configuration/

gathering the different answers and filtering by e.g. mac address you can easily pinpoint the presence of a rogue

It should be considered that PXE information (NBP and TFTP server IP) can be located either at the body of the DHCPOFFER packet (file and next-server fields) or as the corresponding DHCP options.

You can use nmap for this; read my answer here:

https://serverfault.com/questions/993783/how-can-i-check-my-pxe-server-configuration/

Gathering the different answers and filtering by e.g. MAC address, you can easily pinpoint the presence of a rogue PXE server.

It should be considered that PXE information (NBP and TFTP server IP) can be located either at the body of the DHCPOFFER packet (file and next-server fields) or as the corresponding DHCP options.

added 203 characters in body
Source Link
Pat
Pat
  • 111
  • 2

you can use netstat nmap for this; read my answer here:

https://serverfault.com/questions/993783/how-can-i-check-my-pxe-server-configuration/

gathering the different answers and filtering by e.g. mac address you can easily pinpoint the presence of a rogue

It should be considered that PXE information (NBP and TFTP server IP) can be located either at the body of the DHCPOFFER packet (file and next-server fields) or as the corresponding DHCP options.

you can use netstat nmap for this; read my answer here:

https://serverfault.com/questions/993783/how-can-i-check-my-pxe-server-configuration/

gathering the different answers and filtering by e.g. mac address you can easily pinpoint the presence of a rogue

you can use netstat nmap for this; read my answer here:

https://serverfault.com/questions/993783/how-can-i-check-my-pxe-server-configuration/

gathering the different answers and filtering by e.g. mac address you can easily pinpoint the presence of a rogue

It should be considered that PXE information (NBP and TFTP server IP) can be located either at the body of the DHCPOFFER packet (file and next-server fields) or as the corresponding DHCP options.

added 13 characters in body
Source Link
Pat
Pat
  • 111
  • 2

you can use netstat fornetstat nmap for this; read my answer here:

https://serverfault.com/questions/993783/how-can-i-check-my-pxe-server-configuration/

gathering the different answers and filtering by e.g. mac address you can easily pinpoint the presence of a rogue

you can use netstat for this; read my answer here:

https://serverfault.com/questions/993783/how-can-i-check-my-pxe-server-configuration/

gathering the different answers and filtering by e.g. mac address you can easily pinpoint the presence of a rogue

you can use netstat nmap for this; read my answer here:

https://serverfault.com/questions/993783/how-can-i-check-my-pxe-server-configuration/

gathering the different answers and filtering by e.g. mac address you can easily pinpoint the presence of a rogue

Source Link
Pat
Pat
  • 111
  • 2