[
https://issues.apache.org/jira/browse/NET-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bogdan Drozdowski updated NET-320:
----------------------------------
Attachment: tftp-bind.diff
You probably only need to bind to a particular IP address, not to the whole
interface (there's no method of doing this, as far as I know).
This small patch adds two constructors: one taking an InetAddress to bind to
and the other taking a NetworkInterface. The first InetAddress of the given
interface will be the address the DatagramSocket will be bound to.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
