[Openswan dev] Additional patch prob required post 2.6.29 :(
harald at a-little-linux-box.at
Tue Sep 28 18:45:59 EDT 2010
On Tue, Sep 28, 2010 at 01:18:50PM -0400, Paul Wouters wrote:
> On Tue, 28 Sep 2010, Avesh Agarwal wrote:
> >>Both above things are under "CISCO". Is there any other place
> >>where resolve.conf is being updated? I do not think so.
> >When NM is used, then resolv.conf is updated/restored by NM not by Openswan.
> That could be signaled via a variable on the single updown call? I am just now
> looking at this, and wondering why updown is called twice. It was never meant
> to be called in different ways, and I think it can be done in one pass?
> Perhaps a global (config setup) option that says whether or not to update
> resolv.conf. The current situation is a little odd, as resolv.conf is something
> global, but setting the remote_peer_type=cisco in one conn could change that?
> Anyway, its not as urgent as I originally thought, but we should think about
> it and do some cleanup.
Well I think there should be a general code review of openswan as it seems
there are many issues in the code which are not clean...
More information about the Dev