Hey Jason,

Bad News:  there's some logging as vtun walks over its state machine, 
but it's all but random and it's not well-organized.  Patch 2951972 is a 
very early attempt to move some of the chatter below the water mark, but 
it's not in yet.

I can't see a switch in the code that allows any more detail during the 
conversation than we can see now.  We can debug the build, and if we set 
a DEFINE we'll get hints as the encryption sets up.  Additionally, there 
are 110 syslog-type statements in the code.  The vast bulk of them log 
to LOG_ERR, and exactly one logs to LOG_DEBUG (a hint as to the 
configuration the vtund server enforces).

Ultimately, though, none of this can be used to give *more* info 
specifically about the status of the connection than it's giving now. 
The chatter around patch 2951972 dealt with making vtun quieter where it 
was needed, but the question was raised whether VTun is logging what it 
needs to log and to the right channels for simple consumption.  That was 
only a week or so back.

It seems a hot issue.  Should we be asking ourselves what and where it 
should be logging, and when?

I had a Connection Denied issue not so long ago.  I used tcpdump and 
discovered it was a simple firewall issue.  Try that?

  - bish

Jason Antman wrote:
> Hello,
>
> I can't find anything in the docs, but I was wondering if vtun has a
> debugging/verbose output switch?
>
> I have an installation of a central vtun/tap server and a number of
> remote tunneling bridges. I'm trying to build a new server, as the
> current one is quite aged. I've setup a new server and test tunneling
> bridge in a lab environment, but am only getting "Denied connection from
> x.x.x.x" log output.
>
> Is there any way to enable more verbose logging, or a debugging mode, so
> I can figure out the root cause of this error?
>
> Thanks,
> Jason Antman
> Rutgers University
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Vtun-Users mailing list
> Vtun-Users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/vtun-users

-- 
        I would go postal, but I have such bad aim.
                                Neil Bateman, 20090720, GTalk

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Vtun-Users mailing list
Vtun-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vtun-users

Reply via email to