Details
-
Bug
-
Resolution: Fixed
-
Low
-
3.0.3, 3.1.3, 3.1.4
-
None
Description
Scenario/symptoms
- You want to specify a single IP bind for FishEye, instead of listening on all available addresses under Windows, but FishEye will bind to a different address than the one specified in the configuration.
- Your network interface has multiple addresses defined and FishEye will only bind to the primary (first) address of that interface if any other IP on that interface is specified.
Steps to reproduce
- Add a second IP address to the existing interface: http://www.oclc.org/support/services/ezproxy/documentation/technote/2w.en.html
- Open FishEye on both configured IPs in a browser, while having only the port specified in HTTP bind (example: :8060)
- Result: FishEye works on both IPs, as expected
- Configure FishEye to bind to the second IP address that was added (example: 192.168.1.5:8060, while the first IP is 192.168.1.2)
- Restart FishEye for the settings to be picked up
- Once again, open FishEye on both configured IPs in a browser
- Result: FishEye listens only on the first IP (in the example above 192.168.1.2), however the second was defined (in the example 192.168.1.5)
Workaround
Reconfigure the network interface so that the desired IP will be the primary (first) address on that interface.
Notes
The same scenario does not happen under Unix/Linux.
Attachments
Issue Links
- relates to
-
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-