Matrix 21 Max Session Tool Help...

[Meatball]

Hey folks,

I'm working through some testing and I'm trying to create a simple batch file that runs through multiple networking tests and spits the results out into a log file. One of the tools I'd like to use the Max Session Tool here on the site.

http://www.smallnetbuilder.com/mydownloads/max_session_tool.zip

Tool works great, but for the life of me I can't figure out how to pipe the output into a log file. I've figured out that I can dump all the data into a file, but then I get a log full of numbers as it writes every session number into the file.

Does anyone know how I can pipe just the final 'failed' packet line into a log file?

For example, with this command I get a blank log file created:

client 192.168.10.105 12345 192.168.10.20 12345 > test.txt

But if I change it to redirect the Standard Error Stream with the following command:

client 192.168.10.105 12345 192.168.10.20 12345 2> test.txt

I get a huge log file that logs every single open session number. (I cut out all the numbers between 50 and 40890, but they're in the log)

http://matrix21.myweb.hinet.net
Send UDP packets from 192.168.10.105(12345+) to 192.168.10.20(12345)
1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950...4089040891 WinSock Error# function: Bind(), error code:10013

 

[tipstir]

try to send the command to another script file use the call command in your main script file to the second file that going to dump the info into either *.txt or *.bin (bin or any can be use just have to tell OS which app will open it to view)

example: script main: call log dump.xxx in the call log dump you have your image dump > log.log or log.txt or log.bin or log.dat etc.

Make sure your place exit and the end of the second script.

 

[Meatball]

Hmm, not sure if that'll work. I've tried a few ways to deal with it. I'm thinking I can dump the entire thing to another file, and then somehow read through that. I just can't seem to figure out how to rip the last 50 or 60 characters out of the file and then stick them into another log file.

If I can figure that out, I can just do that and delete the large log file. I've attached the actual log if you want to take a look and figure it out. In this case I'd need to grab at least the last 55 characters

37138 WinSock Error# function: Bind(), error code:10013

If you do a 'type test.txt' on the file, you'll actually see what the output looks like when it's run. It appears the whole file is the STDERR stream and it's considered 1 line.