Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 16940 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DHCP option (66)

JonWestgate

Hello All,

I'm trying to see if a bug that was present in Cyberoam has been fixed.

This would be the one where option 66 (next-server on isc-dhcp and many others) its TFTP_Server_Name(66) in the world of Cyberoam / Sophos XG is totally ignored and a value of 0.0.0.0 is sent to the client.


So far I have been unable to prove this because then I do a tcpdump filedump 'proto UDP and port 67'

because https://<appliance ip>/documents/filedump.pcap returns a 404 error as does https://<appliance ip>/documents/tcpdump.pcap

So its 2 questions really.

Is the DHCP option 66 thing going to get fixed?

Has /documents been removed it was a very useful feature, if its been removed that means a real pain faffing about with port mirroring on switches and notebooks with wireshark.



This thread was automatically locked due to age.
Parents
  • 0

    I can confirm that DHCP Option 66 doesn't work properly. I was attempting to PXE boot via Stratodesk and the client timed out. I fired up Windows Server DHCP server and the client booted.

    DHCP Option 67 (image/file name) may also fail, but until 66 is working, that cannot be validated.

    In the command line, the IP address is displayed with quotes around it, could those quotes be getting sent to the client?

    I'll be moving my DHCP scopes to Windows server to get this working for now.

    Tim

Reply
  • 0

    I can confirm that DHCP Option 66 doesn't work properly. I was attempting to PXE boot via Stratodesk and the client timed out. I fired up Windows Server DHCP server and the client booted.

    DHCP Option 67 (image/file name) may also fail, but until 66 is working, that cannot be validated.

    In the command line, the IP address is displayed with quotes around it, could those quotes be getting sent to the client?

    I'll be moving my DHCP scopes to Windows server to get this working for now.

    Tim

Children
No Data