Christian Güdel wrote:
>On Wed, 2005-10-19 at 17:48 +0200, Pierre Ossman wrote:
>
>
>>Christian Güdel wrote:
>>
>>
>>>On Wed, 2005-10-19 at 13:37 +0200, Pierre Ossman wrote:
>>>
>>>
>>>
>>>>I've been
Christian Güdel wrote:
On Wed, 2005-10-19 at 13:37 +0200, Pierre Ossman wrote:
I've been meaning to get OpenVPN support up and running. Haven't really
been able to find the time for it though. But I will hopefully get it
done eventually. :)
Haven't seen anything abo
Christian Güdel wrote:
Hello,
What about OpenVPN support in Networkmanager? This would be too cool. I
don't know what is possible for IPSec VPNs in Networkmanager, but maybe
we could integrate some configuration dialog too.
Is this already in development?
I've been meaning to get OpenVPN sup
Boris Hayete wrote:
> I'm not sure this is a well-defined issue, but here's what happened.
> Having installed the Network manager, I decided to clean up my panel and
> delete an applet neighboring the NM icon in the gnome panel. As soon as
> I cliked on 'Remove from menu', *both* icons disappeare
David Zeuthen wrote:
>I think the problem is that how you want to do routing differs a lot
>from backend to backend (think openswan vs. vpnc). Dan would know more I
>guess.
>
>
>From what I know of IPsec I don't see how it differs much from a
"normal" VPN. I see two routing scenarios used by us
Pierre Ossman wrote:
>
> Come to think of it, I actually have a couple right now: :)
>
> * Wouldn't it be better to move routing settings out from the plugins.
> This is a common setting for most VPN usage so it seems like a lot of
> code duplication for each plugin. No
Is there a special reason that the VPN plugins are located in /usr/bin?
It seems more correct to have them in /usr/libexec since they are only
called by NetworkManager.
Rgds
Pierre
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http:/
Pierre Ossman wrote:
> David Zeuthen wrote:
>
>
>>I've now added some stuff here
>>
>>http://cvs.gnome.org/viewcvs/NetworkManager/vpn-daemons/README?rev=1.2&view=markup
>>
>>
>>though the backend parts still needs to be documented; w
David Zeuthen wrote:
>
>I've now added some stuff here
>
> http://cvs.gnome.org/viewcvs/NetworkManager/vpn-daemons/README?rev=1.2&view=markup
>
>
>though the backend parts still needs to be documented; will do that
>later unless Dan or Colin beats me to it. Patches welcome.
>
>
>
>
Great! I'l
Dan Williams wrote:
>This is actually a glib bug that will be fixed in a new glib rev that was
>supposed to happen either today or early next week. So I think we should wait
>until that happens and see if that fixes it.
>
>
>
This together with the -Werror made it a bit difficult to build NM
David Zeuthen wrote:
>Cool, that sounds very good. As Dan mentioned, I did look at this but I
>didn't write any code at all for it. I've been meaning to fill out
>
> http://cvs.gnome.org/viewcvs/NetworkManager/vpn-daemons/README?rev=1.1&view=markup
>
>at some point, right now it only says "The AP
GCC caught a missing sentinel hint for g_object_new in
nm-netlink-monitor.c:266.
Change
instance = g_object_new (NM_TYPE_NETLINK_MONITOR, NULL);
to
instance = g_object_new (NM_TYPE_NETLINK_MONITOR, NULL, NULL);
to solve the problem.
Rgds
Pierre
Dan Williams wrote:
>Feel free to go right ahead and see what you can do. What we really want to
>know is whether or not we need to change the VPN API to adapt to other
>clients,
>and whether or not we need to change how NetworkManager sets up the IP/tunnel
>stuff. If OpenVPN doesn't use the
Is anyone working on adding OpenVPN support to NetworkManager? Otherwise
I thought I'd take a stab at it.
Rgds
Pierre
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Neal Becker wrote:
> I have NetworkManager-0.4-18.FC4 on Fedora FC4. I usually use the Fedora
> profiles to switch manually between wired at work, and wireless at home,
> but it would be nice have this be automatic.
>
> Last night I tried NetworkManager (again). I doesn't seem to work in my
> ho
Dan Williams wrote:
>On Mon, 2005-07-04 at 20:46 +0200, Pierre Ossman wrote:
>
>
>>Some devices need to be up to be able to detect link. The sleep function
>>brings interfaces down but the wake function doesn't bring them back up.
>>
>>Signed-o
The reference counting for the devices seems a bit strange. Seeing how
it never reaches zero upon exit something is either not freeing up its
references or the initial count is too high.
The initial count seems to include a reference from the worker thread
(judging by the comment). But that create
Some devices need to be up to be able to detect link. The sleep function
brings interfaces down but the wake function doesn't bring them back up.
Signed-off-by: Pierre Ossman <[EMAIL PROTECTED]>
--- NetworkManager-0.4.orig/src/nm-dbus-nm.c 2005-06-30 02:29:36.0 +0200
+++ Net
Dan Williams wrote:
On Sat, 5 Mar 2005, Pierre Ossman wrote:
I've been playing around with swsusp2 and I have noticed that
NetworkManager doesn't work as nice as one could hope. After a resume
NetworkManager still believes that it is connected just fine. It doesn't
even notice
I've been playing around with swsusp2 and I have noticed that
NetworkManager doesn't work as nice as one could hope. After a resume
NetworkManager still believes that it is connected just fine. It doesn't
even notice that the cable isn't connected anymore.
What would be needed is some way of te
20 matches
Mail list logo
