vpnc-plugin

Hi, Sorry if this is a dumb question, but is there an easy way to get the sources for the vpnc-plugin for NM? I see there're are in GNOME CVS, but I there didn't seem to be an easy way to get the entire folder. Thanks, Carlos signature.asc Description: This is a digitally signed message part __

[patch 2/3] array of domains

This patch affects the 9th argument of the IP4 config message (DNS domain) so that it can either be a single STRING or an ARRAY of STRING. Implementation is as follows: - if the argument is a non empty STRING, it will be the only domain in the config, as before; - if the argument is a non empty AR

[patch 3/3] process dhcp-option DOMAIN

This patch brings multiple domain support to nm-openvpn. It extracts domains from the 'dhcp-option DOMAIN' varirables pushed by the openvpn server and put them in the IP4 config message sent to the core nm. Index: NetworkManager-cvs/vpn-daemons/openvpn/src/nm-openvpn-service-openvpn-helper.c

[patch 1/3] multiple named zones

This patch brings support for multiple domains in named configuration. All listed domains in the IP4 config structure are processed as follows: - domain is added to 'search' entry in /etc/resolv.conf, as before; - 'SetForwarders' message is sent to named for each nameserver listed in the IP4 confi

[patch 0/3] Multiple domains and OpenVPN

Hi, I just re-send a serie of patches I had sent a few monthes ago, just in case it makes it to the CVS repository this time. ;) The goal of this serie of patches is to bring support for multiple domains pushed by an OpenVPN server. For this, some work had to be done: - named manager: propagate

NetworkManager questions

Hello all I posted this on the turnpike list by accident. I think the question really belongs here If I recall correctly, connection information (vpn switch ip, username, etc) are shared in an xml file with the name profile_.prf When you connect, you specify the name of the xml file as follows:

Re: RFE: Connection Sharing

On Sun, 2006-08-27 at 20:35 -0400, Saikat Guha wrote: > As for the restrictions themselves, I don't know whether NM is the > best > place to enforce firewalling of the internal network when it doesn't > handle firewalling of the actual internet interface. IMHO, it makes > more > sense for NM to all

Re: Can we make NM automatically handle the need for proxy arp?

On 8/27/06, Ted Lemon <[EMAIL PROTECTED]> wrote: > On Aug 27, 2006, at 11:25 PM, Miles Lane wrote: > > netstat -rn > > Kernel IP routing table > > Destination Gateway Genmask Flags MSS Window > > irtt Iface > > 192.168.21.00.0.0.0 255.255.255.0 U 0 > > 0