List Info

Thread: Re: trying to configure XAUTH as replacement for working Cisco VPN C




Re: trying to configure XAUTH as replacement for working Cisco VPN C
country flaguser name
Netherlands
2007-03-29 13:00:10
On Thu, 29 Mar 2007, Dirk Nehring wrote:

> That's a known patch which is already applied. Just
changing modprobe to
> insmod. I have also applied a patch where the calls to
ifconfig are
> changed to "ip", which is the standard
network tool under Linux since
> many years. FreeWRT does not support ifconfig any more
and I do not
> really understand why OpenSwan is not going the same
way.

Because the output of "ip" is different on various
systems, and therefor
harder to parse. We in fact tried switching to ip and were
forced to
put back some calls to using ifconfig again.

Also, openswan runs on other platforms, like freebsd, which
do not have
the ip command.

Paul
-- 
Building and integrating Virtual Private Networks with
Openswan:
http://www.amazon.com/gp/product/1904811
256/104-3099591-2946327?n=283155
_______________________________________________
Dev mailing list
Devopenswan.org
http:/
/lists.openswan.org/mailman/listinfo/dev

Re: trying to configure XAUTH as replacement for working Cisco VPN C
user name
2007-03-29 17:55:11
On Thu, Mar 29, 2007 at 08:00:10PM +0200, Paul Wouters
wrote:
> On Thu, 29 Mar 2007, Dirk Nehring wrote:
>
> > That's a known patch which is already applied.
Just changing modprobe to
> > insmod. I have also applied a patch where the
calls to ifconfig are
> > changed to "ip", which is the standard
network tool under Linux since
> > many years. FreeWRT does not support ifconfig any
more and I do not
> > really understand why OpenSwan is not going the
same way.
>
> Because the output of "ip" is different on
various systems, and therefor
> harder to parse. We in fact tried switching to ip and
were forced to
> put back some calls to using ifconfig again.
>
> Also, openswan runs on other platforms, like freebsd,
which do not have
> the ip command.

Mmh, we are doing much more things with "ip",
especially "ip route"
which cannot be done with "route", ie source based
routing and more than
one routing table. Until now, I am using ip on various
plattforms, for
me the output looks very similar. When I provide a small
patch which check
the availability of a recent "ip" and then tries
to use it, would you
consider to take a look onto it?

Cheers,

Dirk
_______________________________________________
Dev mailing list
Devopenswan.org
http:/
/lists.openswan.org/mailman/listinfo/dev

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )