Bugzilla – Full Text Bug Listing
| Summary: | AC blocks connecction from local host if local host is allowed by name | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Bob Duncan <duncan> | ||||
| Component: | TPTP | Assignee: | Igor Alelekov <igor.alelekov> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P1 | CC: | karla.callaghan | ||||
| Version: | unspecified | Keywords: | plan | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | closed460 | ||||||
| Attachments: |
|
||||||
At this stage of 4.3, I expect a normal like this to be targeted to 4.4 or later. Are there multiple network cards in this machine such that it would have two names? When I ping my machine by name locally or from another system, I get the same IP. Also, has this worked in the past? Yes, indeed there are multiple cards on the laptop I was using. I just tried again on a desktop with a single card and the testcase works fine (ie: allows the attempt to profile locally). Additionally, of course, the IP is the same for the desktop whether pinged locally or remotely. It looks like you've diagnosed the cause. :-) As far as working previously, this is the first testpass that I was the one to run this case. I believe that it has worked in the past (no record of failure that I could find) but I also believe that it was probably run previously on a desktop with a single card. This same problem is likely to appear with the RAC, since the code in new AC doing the host name check was taken from the RAC. This has likely been around for awhile and simply not seen because combination of specifying local host by name on a multi-IP system didn't occur. Targetting to 4.4. Added effort estimate: 2 days Transferring bugs with 4.4 target to new owner, Igor. If their priority is not set to P1, then the bug is only a stretch item for that release. Created attachment 74545 [details]
patch
Resolving since the patch is checked into CVS Please change the target to the 4.5 iteration when this Bugzilla was resolved. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. |
When the AC is configued to allow access from a local host by name (eg: <Allow host="xyzMachine") it actually blocks an attempt to profile from a workbench on that local host with the following mesage in the service log: ... msg="Connection refused on socket 1340 on host 169.254.198.66 
" ... <sourceComponentId component="AgentController" componentIdType="TPTPComponent" executionEnvironment="D:\cygwin\home\build\TPTP\4.3.0\TPTP-4.3.0-200611070100\agntctrl\src\transport\TPTPClientCompTL\CCTLServer.c, line 493" instanceId="1004" location="xyzMachine.torolab.ibm.com" locationType="IPV4" processId="1632" subComponent="Client Compatibility TL" The problem may possibly be related to network name lookup. When I ping xyzMachine from other machines, ping shows it as a 9.26.nnnn.xxxx address but when i ping it from itself, ping shows it as 169.254.198.123. This problem occurred with the TPTP-4.3.0-200611070100 driver on Windows XP. The steps to reproduce are: 1. Install the Agent Controller on your own Windows XP machine ("xyzMachine" in these steps) 2. Run SetConfig.bat to configure with xyzMachine as the only allowed host -ie: serviceconfig.xml should contain: <Allow host="xyzMachine"/> 3. Start the AC on xyzMachine 4. Start a workbench on xyzMachine 4. Launch any Java program from the workbench and targetted to run on the xyzMachine machine 5. The launch will fail with an error popup (possibly IWAT0008E with a reason of IWAT0007I) 6. Check the refusal message in servicelog.log