Re: vpnc and determining correct routes

[Derek Atkins <warlord MIT EDU>]

Quoting Dan Williams <dcbw redhat com>:

> Yeah, sorry, we'll need a few more bits here.  The current code (which I
> just looked) just uses strings for the moment.

Strings work, too..  And if you leave it as strings it gives you
the flexibility to add IPv6 support down the road without changing
your APIs.  :)


> > Which is unfortunate -- I wish vpnc would export more of the VPN
> > configuration.  I couldn't even figure out how to get NM to call VPNC
> > in such a way to actually dump the full configuration debug info to
> > syslog!  Either that or the nm-vpnc-service is eating the vpnc debug
> > output..  :(
>
> stdout/stderr should be directed to syslog.  In actuality, the vpnc's
> stdout/stderr are redirected to nm-vpnc-service's stdout/stderr, which
> in turn are redirected to NM's stdout/stderr, which is syslog.

Hmm...  Well I modified the nm-vpnc-service to call vpnc with "--debug 99"
but I still wasn't getting any additional output.

> If you want to get the full config,
> replace /usr/bin/nm-vpnc-service-helper with a script that dumps the
> environment to a file, then calls the actual nm-vpnc-service-helper with
> the same command line and environment.

Been there.  Done that.  Looking for more information.  I think the
problem is that vpnc isn't dumping the whole "VPN State" to the
environment.   I want to see the whole configuration that the server
pushed to vpnc; not just what was pushed into the environment by vpnc.
I think vpnc is skipping some variables...   Or at least I'd like to
see if they are.

> dan

-derek

--
      Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
      Member, MIT Student Information Processing Board  (SIPB)
      URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
      warlord MIT EDU                        PGP key available