Results 1 to 2 of 2

Thread: Setting up atftpd or tftpd on a server, specific eth port

Threaded View

  1. #1

    Setting up atftpd or tftpd on a server, specific eth port

    I need to set up a tftp service on a server in a LAN so that it listens only on a specific network in a vLAN, via a dedicated network interface.

    My workstations are in a 192.168.x network in the default vLAN. They do not do bootP and I do not want them to try. DHCP in this LAN is set up to answer requests from MITEL IP PHONES by sending them to a vLAN 5, and specifying a bootP server at 172.16.x.222. The phones have everything they need, assuming TFTP provides the files they need in order to boot up.

    The second NIC is configured with a static IP 172.16.2.222 in this LAN. It is plugged into a switch on a port configured to vLAN 5, untagged.

    I would like the tftp deamon to listen only on this second NIC. We do have ZENworks imaging, and occasionally we start proxy-dhcp services in order to restore a Windows image to a workstation. I do not want to interfere with this service.

    I have been using atftpd on a dedicated Ubuntu box and know how to configure it for this purpose. I would now like to do this on my Branch servers with SLES11, as I have a free NIC with which to do it.

    I see that atftpd, novell-tftp, tftp, and yast2-tftp-server are all available. What do you recommend? Is there a way to configure the service to listen only to requests from the 172.16.x ethernet interface?
    Last edited by tkindig; 05-Mar-2014 at 19:03. Reason: Additional point.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •