From: Linda K. <lin...@hp...> - 2012-01-26 22:54:50
|
Eduard (or anyone else who wants to answer), The README.netwk_svr file says that the network server needs a profile.bash file to export the PASSWD environment variable. At some point I ended up added more variables to that file, including RHOST, RHOST6, LBLNET_* and LOCAL_IPV4. I don't recall when/why I added them and I can't say for sure that they're all necessary but I do see references to LOCAL_IPV4 and LBLNET_SVR_IPV4 in the audit-remote/tests/remote_call.bash. Will someone please clarify the expected contents of the profile.bash file and update the REMOTE.netwk_svr file? Thanks, -- ljk |
From: Eduard B. <eb...@re...> - 2012-01-27 09:49:33
|
Hello Linda, you should need just the PASSWD in profile.bash on network server (NS). There are no other variables expected in remote_call.bash. The file remote_call.bash is never used on TOE and serves for NS only. I've checked the README.netwk_svr and step 9. seems to be correct and sufficient for requirements of audit-remote tests run on NS side. The only possible point of confusion are two comments in the code referring to LOCAL_IPV4 varible but not using it. This comments will be updated. Also there is a function call_ns_connection_check() which is not required and serves for troubleshooting connection between NS and TOE. I've asked Ondrej to double-check it and send out a patch for possible code enhancements. The summary is, only PASSWD has to be in profile.bash on NS for audit remote tests. No updates of README.netwrk_srv are necessary. Thanks, Eduard On 01/26/2012 11:58 PM, Linda Knippers wrote: > Eduard (or anyone else who wants to answer), > > The README.netwk_svr file says that the network server > needs a profile.bash file to export the PASSWD environment > variable. > > At some point I ended up added more variables to that file, > including RHOST, RHOST6, LBLNET_* and LOCAL_IPV4. I don't > recall when/why I added them and I can't say for sure that > they're all necessary but I do see references to LOCAL_IPV4 > and LBLNET_SVR_IPV4 in the audit-remote/tests/remote_call.bash. > > Will someone please clarify the expected contents of the profile.bash > file and update the REMOTE.netwk_svr file? > > Thanks, > > -- ljk |
From: Linda K. <lin...@hp...> - 2012-01-27 13:53:35
|
Thanks Eduard, I'll remove the extra variables from my file and retest. -- ljk Eduard Benes wrote: > Hello Linda, > > you should need just the PASSWD in profile.bash on network server (NS). > There are no other variables expected in remote_call.bash. The file > remote_call.bash is never used on TOE and serves for NS only. I've checked > the README.netwk_svr and step 9. seems to be correct and sufficient > for requirements of audit-remote tests run on NS side. The only possible > point of confusion are two comments in the code referring to LOCAL_IPV4 > varible but not using it. This comments will be updated. Also there is > a function call_ns_connection_check() which is not required and serves > for troubleshooting connection between NS and TOE. I've asked Ondrej to > double-check it and send out a patch for possible code enhancements. > > The summary is, only PASSWD has to be in profile.bash on NS for audit > remote tests. No updates of README.netwrk_srv are necessary. > > Thanks, > > Eduard > > > On 01/26/2012 11:58 PM, Linda Knippers wrote: >> Eduard (or anyone else who wants to answer), >> >> The README.netwk_svr file says that the network server >> needs a profile.bash file to export the PASSWD environment >> variable. >> >> At some point I ended up added more variables to that file, >> including RHOST, RHOST6, LBLNET_* and LOCAL_IPV4. I don't >> recall when/why I added them and I can't say for sure that >> they're all necessary but I do see references to LOCAL_IPV4 >> and LBLNET_SVR_IPV4 in the audit-remote/tests/remote_call.bash. >> >> Will someone please clarify the expected contents of the profile.bash >> file and update the REMOTE.netwk_svr file? >> >> Thanks, >> >> -- ljk > |
From: Linda K. <lin...@hp...> - 2012-01-27 14:49:27
|
And as expected, the tests still pass. I don't know why I had those extra lines in there. I'll pull in Ondrej's patch too. Thanks guys! -- ljk Linda Knippers wrote: > Thanks Eduard, > > I'll remove the extra variables from my file and retest. > > -- ljk > > Eduard Benes wrote: >> Hello Linda, >> >> you should need just the PASSWD in profile.bash on network server (NS). >> There are no other variables expected in remote_call.bash. The file >> remote_call.bash is never used on TOE and serves for NS only. I've checked >> the README.netwk_svr and step 9. seems to be correct and sufficient >> for requirements of audit-remote tests run on NS side. The only possible >> point of confusion are two comments in the code referring to LOCAL_IPV4 >> varible but not using it. This comments will be updated. Also there is >> a function call_ns_connection_check() which is not required and serves >> for troubleshooting connection between NS and TOE. I've asked Ondrej to >> double-check it and send out a patch for possible code enhancements. >> >> The summary is, only PASSWD has to be in profile.bash on NS for audit >> remote tests. No updates of README.netwrk_srv are necessary. >> >> Thanks, >> >> Eduard >> >> >> On 01/26/2012 11:58 PM, Linda Knippers wrote: >>> Eduard (or anyone else who wants to answer), >>> >>> The README.netwk_svr file says that the network server >>> needs a profile.bash file to export the PASSWD environment >>> variable. >>> >>> At some point I ended up added more variables to that file, >>> including RHOST, RHOST6, LBLNET_* and LOCAL_IPV4. I don't >>> recall when/why I added them and I can't say for sure that >>> they're all necessary but I do see references to LOCAL_IPV4 >>> and LBLNET_SVR_IPV4 in the audit-remote/tests/remote_call.bash. >>> >>> Will someone please clarify the expected contents of the profile.bash >>> file and update the REMOTE.netwk_svr file? >>> >>> Thanks, >>> >>> -- ljk > > > ------------------------------------------------------------------------------ > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > _______________________________________________ > Audit-test-developer mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audit-test-developer |