[ https://issues.apache.org/jira/browse/NET-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182154#comment-13182154 ]
Sebb commented on NET-320: -------------------------- Note that the TFTPServer is only currently intended for use by test code. > Allow TFTPServer.java to bind to a specific network adapter > ----------------------------------------------------------- > > Key: NET-320 > URL: https://issues.apache.org/jira/browse/NET-320 > Project: Commons Net > Issue Type: Improvement > Components: TFTP > Affects Versions: 2.0 > Reporter: Kevin > Labels: NetworkInterface, TFTP, TFTPServer > Attachments: tftp-bind.diff > > Original Estimate: 24h > Remaining Estimate: 24h > > It would be very nice to specify exactly which network interface you would > like to bind the TFTP server listening port to. In some cases it's only > necessary to open up loopback, in other cases you may only want to bind to a > management network. I would like to see one of two things happen to satisfy > this requirement. > > 1) You could allow me to get a handle to the socket such that I can make > modifications to it on my own. > or > 2) Add a constructor and/or method that allows me to pass a NetworkInterface > instance to specify which nic to bind the server to. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira