You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Kevin Bulebush (JIRA)" <ji...@apache.org> on 2010/05/03 20:29:58 UTC
[jira] Created: (NET-320) Allow TFTPServer.java to bind to a
specific network adapter
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
Affects Versions: 2.0
Reporter: Kevin Bulebush
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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (NET-320) Allow TFTPServer.java to bind to a
specific network adapter
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NET-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebb updated NET-320:
---------------------
Component/s: TFTP
> 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 Bulebush
> 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.
-
You can reply to this email to add a comment to the issue online.