Anton, I believe it should be way #2 below, since eth0 will change less and be less dependent on virtual IPs, etc.
Andy -----Original Message----- From: Anton Pak [mailto:[email protected]] Sent: Tuesday, November 09, 2010 7:45 AM To: OpenHPI-devel Subject: [Openhpi-devel] About feature request #3094859 "Add a possibility to listen only specified network interfaces" Hello! I have some uncertainty about the way it will work. There are several ways: 1) Use IP addresses to which to bind daemon socket ( i.e. introduce OPENHPI_DAEMON_BIND_ADDRESS=192.168.1.1) 2) Use network interface names to which to bind daemon socket (i.e. introduce OPENHPI_DAEMON_INTERFACE=eth0) 3) Way #1 but reuse existing OPENHPI_DAEMON_HOST variable instead of new OPENHPI_DAEMON_BIND_ADDRESS Also there is a question if we should support several bind addresses / interfaces. And there is a question about 127.0.0.1 / lo. Should it be always binded? Should it be configured? Looking forward for your opinions. Anton Pak ------------------------------------------------------------------------ ------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Openhpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openhpi-devel ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Openhpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openhpi-devel
