Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 28 subscribers
  • Views 10352 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

How do I specify the TFTP server IP under DHCP Options?

MichaelGale

I have specified the value via the console for TFTP_Server_Name(66) for my internal DHCP scope however according to TCPDUMP. The client is attempting to make a TFTP connection against my Sophos XF firewall and NOT the TFTP server I specified:

I need the client to make the TFTP request against 192.168.1.3, which is my tftp server.

console> system dhcp dhcp-options binding show dhcpname internal_192_168_1
Options Configured from GUI
---------------------------
Domain_Name mydomain.com
Subnetmask 255.255.255.0
Default_Gateway 192.168.1.1
Domain_Name_Servers 192.168.1.1
Options Configured from CLI
---------------------------
TFTP_Server_Name(66) "192.168.1.3"
Bootfile_Name(67) "pxelinux.0"


Is there another option I need to change?

Michael



This thread was automatically locked due to age.
  • 0

    Hi Michael,

    Just wondering if you ever managed to resolve this issue?

    Cheers

    Brett

  • 0 in reply to ToowoombaRC

    Hello,

        No, I ended up working around it using the following, I left the XG firewall DHCP options along so it provided the normal DHCP service to my LAN clients. I then setup a Linux box with my tftp server, web server, etc to handle the network installations. On the Linux box I then setup DHCP to provide addresses for BOOTP requests only, so it wouldn't interfere with the XG firewall DHCP.

     

    Michael

  • 0 in reply to MichaelGale

    Hey Michael, you might try this again but set the Bootfile_Name(67) as this: tftp://<server's_IP_address>/<filename> instead of just the filename. I was using just the filename and it worked with one type of VM. I figured this was because that VM client would assemble the path on-the-fly but I've found that's not the case with all devices. I've been testing it using another VM and a hardware netbook. I have found that one VM worked with just 'pxelinux.0' as Bootfile_Name(67) but the other VM and netbook would not. I just tried changing it to a network path 'tftp://<my server's IP>/pxelinux.0' and all of them work!!

     

    I also posted this in another thread because I just figured it out this morning.