On 08/12/09 21:49, Dan Williams wrote:
Hopefully I'll have the fix committed by tomorrow :) The fix passes all
my testcases, but I need to go back and make sure the old code fails
them, and also have another double-check just to be sure.
Thanks. In the meantime, I can confirm adding my user
On 08/12/09 21:30, Dan Williams wrote:
Hi, It's plain PEM, first few lines attached.
I did try this yesterday with a WPA Enterprise TLS configuration and
could reproduce the issue. But there's a bug I'm tracking that could
have an effect on it if you are using separate private key and client
On 30/11/09 08:00, Dan Williams wrote:
On Thu, 2009-11-26 at 08:46 +, Jon Escombe wrote:
On 26/11/09 03:44, Dan Williams wrote:
On Wed, 2009-11-25 at 15:49 +, Jon Escombe wrote:
Hi,
After upgrading to F12, I can no longer configure my WPA2 Enterprise
(EAP-TLS) network. nm-applet
On 26/11/09 03:44, Dan Williams wrote:
On Wed, 2009-11-25 at 15:49 +, Jon Escombe wrote:
Hi,
After upgrading to F12, I can no longer configure my WPA2 Enterprise
(EAP-TLS) network. nm-applet produces the following output when I enter
the private key file
Any chance you can try what's
Hi,
After upgrading to F12, I can no longer configure my WPA2 Enterprise
(EAP-TLS) network. nm-applet produces the following output when I enter
the private key file
** (nm-applet:4378): CRITICAL **: crypto_md5_hash: assertion
`password_len 0' failed
Any ideas how to troubleshoot this
On 12/05/09 19:15, Dan Williams wrote:
On Tue, 2009-05-12 at 13:31 -0400, Wei Weng wrote:
Hi. I am using
ii network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2
ii network-manager-gnome 0.7.1~rc4.1-0ubuntu2
ii network-manager-openvpn
On 12/05/09 23:06, Wei Weng wrote:
On 5/12/2009 6:01 PM, Jon Escombe wrote:
On 12/05/09 19:15, Dan Williams wrote:
On Tue, 2009-05-12 at 13:31 -0400, Wei Weng wrote:
google openVPN there were no valid VPN secrets. There should be quite
a few solutions out there. :)
Thanks
Dan Williams wrote:
On Thu, 2009-03-19 at 15:45 +, li...@dresco.co.uk wrote:
Hi,
Have recently got access to one of these devices, and having some issues
connecting with NM. Am using F10 with NetworkManager-0.7.0.99-3.fc10.i386
The symptom is that a connection will fail and then the
Jim Popovitch wrote:
See, there you go again. Injecting a perceived feature request that
no one in this thread has requested. You really must come back to
ground level and understand that NO ONE is asking you or NM for
fine-grained name resolution control. Nope, no one.The only
feature
- Vasiliy G Tolstov [EMAIL PROTECTED] wrote:
There is problem because NM add
g_ptr_array_add (openvpn_argv, (gpointer) --ns-cert-type);
g_ptr_array_add (openvpn_argv, (gpointer) server);
The NM openvpn plugin requires that the remote certificate is created with a
server certificate
Valentine Sinitsyn wrote:
I've came across an interesting misbehavior while trying to connect my
NM 0.6.5 on Arch Linux box to OpenVPN (2.0.9) server and thought it
may be useful to raise this question in the mailing list.
Hi,
There was some discussion around this last December, if you
Christoph Brill wrote:
Was the question to complicated? Is noone interested in OpenVPN? Or is
everyone on holidays?
Am Donnerstag, den 27.12.2007, 11:52 +0100 schrieb Christoph Brill:
Hi list,
I'm trying to connect to a openvpn server. This server is set up to use
the companies DHCP
Casey Harkins wrote:
Jon Escombe wrote:
5) Helper expects ifconfig_remote which isn't provided by a TAP
connection.
Attached patch should make this optional from openvpn's perspective. I
haven't tested it, but it looks like NM will just issue a warning if
it the ptp address is unset
- Casey Harkins [EMAIL PROTECTED] wrote:
Can we get the attached two patches applied? One fixes an off by one bug
in parsing the dns servers (only accepting cases where more than one dns
server is listed on a single line). The other passes the --route-noexec
option to openvpn to ensure
Casey Harkins wrote:
Casey Harkins wrote:
Jon Escombe wrote:
4) Mandatory check for a secret that fails with a x509 certs only.
Can you try out the attached patch?
-casey
Forgot to include a file in that diff, here's an updated patch.
-casey
Yes, that's done the trick. Thanks
Casey Harkins wrote:
Also, I'm not getting a route added for the VPN subnet.
Are you talking about the Only use VPN connection for these
addresses option, or it's not setting your default route to your TAP
device?
I'll provide some examples to be clearer. I'm not using the only use
for
- Dan Williams [EMAIL PROTECTED] wrote:
-- Initiating the openvpn connection through NM gives me this:
# ip route
default dev tap0 scope link
so it changes the default route from ppp0 to tap0, but doesn't retain a
specific route to the VPN server over ppp0 - so the tunnel
- Jon Escombe [EMAIL PROTECTED] wrote:
I'll try to debug the ppp case further, see what's different
there that it's not liking..
Appears that openvpn just doesn't like the way the default route is set up by
the ppp connection
# ip route
default dev ppp0 scope link
If I supply
- Dan Williams [EMAIL PROTECTED] wrote:
On Thu, 2007-12-06 at 13:25 +, Jon Escombe wrote:
- Jon Escombe [EMAIL PROTECTED] wrote:
I'll try to debug the ppp case further, see what's different
there that it's not liking..
Appears that openvpn just doesn't like the way
- Casey Harkins [EMAIL PROTECTED] wrote:
I don't think openvpn should be trying to setup routes unless specific
options are being passed (--route, --route-gateway), but I could be
wrong. Either way, there's no harm in passing that option.
Could be, my gateway etc is pushed from the
Casey Harkins wrote:
Jon Escombe wrote:
- Casey Harkins [EMAIL PROTECTED] wrote:
I don't think openvpn should be trying to setup routes unless specific
options are being passed (--route, --route-gateway), but I could be
wrong. Either way, there's no harm in passing that option.
Could
Dan Williams wrote:
On Wed, 2007-12-05 at 09:28 +, Jon Escombe wrote:
Casey Harkins wrote:
If you're interested, the attached patch fixes the glade issue as well
as an improper key being used in a hash table. I just started looking
into the auth dialog which is also failing
Tambet Ingo wrote:
On Dec 4, 2007 4:17 PM, Jon Escombe [EMAIL PROTECTED] wrote:
Good stuff, got connected first time ;)
Only issues were that it didn't set up resolv.conf, and also added three
entries to the applet menu (as the card presents three ports).
Both of these issues
Casey Harkins wrote:
Dan Williams wrote:
On Wed, 2007-12-05 at 14:56 -0600, Casey Harkins wrote:
Attached is a patch with a number of fixes for openvpn against svn
revision 3138. I'm still having some crashes creating/editing
properties, but can consistently create new working settings by
- Tambet Ingo [EMAIL PROTECTED] wrote:
On Nov 28, 2007 5:01 PM, Dan Williams [EMAIL PROTECTED] wrote:
Yes, that'll work; though for secrets you might need to write some C
bits to push the PIN or whatever into the keyring. But if you don't
have a PIN and since most networks don't care
- Tambet Ingo [EMAIL PROTECTED] wrote:
On Dec 4, 2007 3:28 PM, Jon Escombe [EMAIL PROTECTED] wrote:
I've just built from the latest SVN keen to give the UMTS support a try.
Do you have a list of the gconf entries needed to get up and running?
nm-applet creates the gconf entries
- Tambet Ingo [EMAIL PROTECTED] wrote:
On Dec 4, 2007 4:58 PM, Darren Albers [EMAIL PROTECTED] wrote:
Just out of curiosity what cards have you tested with?
As I said, I don't know of anyone else other than Jon who has
successfully tried it. I don't know what card he has, but mine is
Casey Harkins wrote:
Dan Williams wrote:
On Tue, 2007-12-04 at 15:03 -0600, Casey Harkins wrote:
vpnc is; and upstream openvpn has already been fixed up to conform to
the new API bits. Nobody's been around to test it yet. What we
probably should do is to build what's upstream for Fedora,
- Tambet Ingo [EMAIL PROTECTED] wrote:
As Dan already said, I have code to drive gsm data cards and we hope
to get it to SVN later this week, even if it means there's no way to
configure it yet from the UI (the currently missing part).
Thanks, looking forward to trying it out..
Not sure if the devs want any feedback on the 0.7 code from latest Fedora 8 yet?
Appreciate it's still work in progress, but on the off chance you do... ;)
- OpenVPN configuration dialog crashes when entering text
- WPA2 dialog doesn't enable connect button correctly
Other than that, 0.7 is
Peter Davoust wrote:
I just wanted to see if anyone got my e-mail about PEAP support with
NetworkManager. I sent it a few days ago, but got no response and I
wanted to check if I was signed up for this list. My question was
about how to enable PEAP/wpa enterprise support in NetworkManager.
Casey Harkins wrote:
Casey Harkins wrote:
When using NetworkManager-openvpn with the Only use VPN connection for
these addresses option, NetworkManager leaves me with no default route
after the VPN connection is established. I would expect the default
route to remain unchanged (same as
Ryan Novosielski wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jon Escombe wrote:
- Aaron Konstam [EMAIL PROTECTED] wrote:
Now we are really getting into black magic. I changed the lines:
%prep
%setup -q
%patch0 -p1 -b .startup-dhcdbd
%patch2 -p1 -b .linkdebug
Aaron Konstam wrote:
Well it looks like your patch for the LEAP authentication now works.
And it works as I predicted it should. That is, when you try to
reconnect to the access point the program asks you for your keyring
passwd and connects.
If you also want to avoid the prompt for your
Ryan Novosielski wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jon Escombe wrote:
Aaron Konstam wrote:
Well it looks like your patch for the LEAP authentication now works.
And it works as I predicted it should. That is, when you try to
reconnect to the access point
Dan Williams wrote:
On Thu, 2007-07-12 at 16:36 +0100, Jon Escombe wrote:
Aaron Konstam wrote:
Well it looks like your patch for the LEAP authentication now works.
And it works as I predicted it should. That is, when you try to
reconnect to the access point the program asks you for your
- Aaron Konstam [EMAIL PROTECTED] wrote:
On Wed, 2007-07-11 at 18:06 +0100, Jon Escombe wrote:
- Derek Atkins [EMAIL PROTECTED] wrote:
Aaron Konstam [EMAIL PROTECTED] writes:
That is exactly what I did.
In the %prep section did you add the appropriate %patchN (where
- Aaron Konstam [EMAIL PROTECTED] wrote:
Now I am in trouble when I added the line:
%patch4 -p1 -b .LEAP_passwd
What am I supposed to enter here or have I gone really astray?
No, I must have ;)
Looks like the patch I posted doesn't apply against the latest source RPM.
I'll generate
- Aaron Konstam [EMAIL PROTECTED] wrote:
Now we are really getting into black magic. I changed the lines:
%prep
%setup -q
%patch0 -p1 -b .startup-dhcdbd
%patch2 -p1 -b .linkdebug
%patch3 -p1 -b .no-killswitch-fix
%patch4 -p1 -b .LEAP_passwd
# unpack the applet
tar -xjf
Aaron Konstam wrote:
I took the src rpm :NetworkManager-0.6.5-7.fc7.src.rpm and recompiled it
using the LEAP patch NetworkManager-0.6.5-LEAP_passwd.patch developed by
Jon Escombe. Nothing improved. The behavior is the same.
The first time I can configure the LEAP authentication. After reboot
Dan Williams wrote:
On Thu, 2007-07-05 at 15:14 -0500, Aaron Konstam wrote:
On Thu, 2007-07-05 at 13:23 -0400, Darren Albers wrote:
On 7/5/07, Aaron Konstam [EMAIL PROTECTED] wrote:
On Mon, 2007-07-02 at 15:18 -0500, Aaron Konstam wrote:
I am using
Hmm, that patch shouldn't have changed the logic for LEAP authentication..
Do we know what version was last working ok for Aaron (6.4 / 6.5)?
Regards,
Jon.
Looking at the applet code, I'm suspicious that the 6.5 changes that
broke some WPA2 configs have done the same to LEAP. So we
- Aaron Konstam [EMAIL PROTECTED] wrote:
Looking at the applet code, I'm suspicious that the 6.5 changes that
broke some WPA2 configs have done the same to LEAP. So we might just
need to extend that last patch to include LEAP networks.
Aaron, does your LEAP passphrase get stored
Aaron Konstam wrote:
Attached is the syslog messages generated for my machine being attached
to a hard wired connection to attempting to connect to an access point
using LEAP authentication. I gzipped the file.
Maybe I am naive but the problem seems clear. The system requests a key
for
- Giovanni Lovato [EMAIL PROTECTED] wrote:
Jon Escombe wrote:
- Giovanni Lovato [EMAIL PROTECTED] wrote:
While `openvpn --config client.conf' starts up VPN connection
properly,
NM won't:
OpenVPN 2.0.9 i486-pc-linux-gnu [SSL] [LZO] [EPOLL] built on Mar 2
2007
LZO
- Giovanni Lovato [EMAIL PROTECTED] wrote:
While `openvpn --config client.conf' starts up VPN connection
properly,
NM won't:
OpenVPN 2.0.9 i486-pc-linux-gnu [SSL] [LZO] [EPOLL] built on Mar 2
2007
LZO compression initialized
UDPv4 link local: [undef]
UDPv4 link remote:
Dan Williams wrote:
On Tue, 2007-06-26 at 12:45 -0400, Matthew Saltzman wrote:
I updated to NetworkManager-0.6.5-6.fc7 last night. Now, when I
right-click on the nm-applet icon, the Enable Wireless checkbox is
greyed out and I can't set or unset the check mark.
This was not the case
- Jon Nettleton [EMAIL PROTECTED] wrote:
On Thu, 2007-06-07 at 12:08 -0400, Dan Williams wrote:
On Thu, 2007-06-07 at 16:42 +0100, Jon Escombe wrote:
Any thoughts on applying the device-link-race patch to 0.6.x?
Working on that now; I'd rather figure out why nm_device_is_up doesn't
Tomáš Hnyk wrote:
So out of interest, what fields do you use in the configuration
dialog? I am using identity, private key file, and private key
password.
Regards,
Jon.
The config windows should look like this:
http://eduroam.fjfi.cvut.cz/images/eduroam_linux2.png
i.e.
- Dan Williams [EMAIL PROTECTED] wrote:
Attaching a new version of my patch, this checks whether a private
key file is configured for the connection before attempting to read a
password from the keyring. I believe this should suit both of the
above 802.1X configuration types..
- Dan Williams [EMAIL PROTECTED] wrote:
I believe Tomas is using 6.4, which doesn't work (for him) because
it always tries to get a password from the keyring. 6.5 includes a
patch to never get a password from the keyring (which I'm assuming
would work for Tomas - but breaks the private
- Jon Escombe [EMAIL PROTECTED] wrote:
Symptom now is that on a first connection it works fine, dialog is
presented for the credentials and connects fine. However, once the
details for the network are in gconf, reconnecting to that network
just results in a endless loop of trying
- Jon Escombe [EMAIL PROTECTED] wrote:
- Jon Escombe [EMAIL PROTECTED] wrote:
Symptom now is that on a first connection it works fine, dialog is
presented for the credentials and connects fine. However, once the
details for the network are in gconf, reconnecting to that network
Tomáš Hnyk wrote:
Hi,
I tried to apply your patch but it failed. After I investigated it a
little, I found out you are probably using a distro-specific source.
Could you please try this against the current svn? I am using Ubuntu
with network manager 0.6.4 and there the patch fails as well.
With the syslog buffer overflow fixed (thanks!), I've been able to test my WPA2
connection some more. Unfortunately it wasn't long before hitting another
problem.
Symptom now is that on a first connection it works fine, dialog is presented
for the credentials and connects fine. However, once
- dragoran [EMAIL PROTECTED] wrote:
I have seen the same... have you already filled a bug or should I do
it?
Just filed it..
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242455
Regards,
Jon
___
NetworkManager-list mailing list
Whilst not strictly a NM problem, am posting here as (a) Dan's follows
this list and (b) I'd expect this to hit other NM users.
After upgrading from FC6 to F7, I noticed that I was unable to connect
to my office WPA2 network. With some digging, I traced the problem to
wpa_supplicant
- Jon Nettleton [EMAIL PROTECTED] wrote:
On Thu, 2007-05-24 at 14:21 -0400, Dan Williams wrote:
On Wed, 2007-05-23 at 15:20 +0100, John Spray wrote:
Hi,
I'm connecting to a VPN using NetworkManager 0.6.4 on ubuntu 7.04, but
it's not picking up the gateway correctly -- after NM
Jon Escombe wrote:
Patton Echols wrote:
I pointed network manager at the AP, it asked for the WEP pass-phrase,
which I gave, no connection. The network monitor icons seemed to show
signal being exchanged, and showed signal strength, but the no actual
communication was going on. Am
If you just want to avoid entering the password after logon, you could also
look at pam_keyring which will silently give it the logon password..
Regards,
Jon.
- Original Message -
That's excellent -- all I want is not to be futzing with entering a
password in that keyring, however
Nathaniel McCallum wrote:
On Thu, 2007-03-15 at 14:16 +, Jon Escombe wrote:
If you just want to avoid entering the password after logon, you could also
look at pam_keyring which will silently give it the logon password..
Which doesn't work if you are using a non-password based login
Jon Nettleton wrote:
On Thu, 2007-03-15 at 14:50 -0400, Nathaniel McCallum wrote:
On Thu, 2007-03-15 at 14:16 +, Jon Escombe wrote:
If you just want to avoid entering the password after logon, you could also
look at pam_keyring which will silently give it the logon password..
Which
Yeah, it's actually udev that's swapping the device names (happens to me
too), depending on the order they get initialised. Guess the 'usual'
network scripts may already have had some magic to deal with this...
I've not tried it myself, but you can create new udev rules to lock the
mac
Robert Love wrote:
On Thu, 2006-05-11 at 18:24 +0100, Jon Escombe wrote:
That said, my private key password (for a WPA2 network) is stored in the
xml file rather than the keyring ;), but doubtless it'll be stored
somewhere better in due course..
I just fixed this in CVS, a few days ago
Zach Tibbitts wrote:
I'm using networkmanager 0.62 on Ubuntu Dapper, and am having trouble
to connect to my school's wireless network, which uses WPA encryption.
I cannot get NM to connect solely via gui, but running wpa_supplicant
at the commandline made the network appear in the NM applet,
Bo Lorentsen wrote:
Hi ...
I have build a debian package for the nm-0.6.2 release and it works
out nice but, I an only able to enable the 3 WEP encryptions but I
find no WPA encryption.
I know there is a reference to the wpasupplicant and I have included
this at the configure process, but
R S Gill rsgill at purdue.edu writes:
Hi,
Running Ubuntu Dapper Flight 6 with network-manager 0.6 installed.
I just got network-manager to connect to the WPA-TKIP with PEAP network
on my university's campus.
Each time I get disconnected, I have to manually setup the connection to
Nil Gradisnik wrote:
Ups, I apologize for that...
I'm running FedoraCore5 which comes with NetworkManager 0.6.0. I
compiled and installed NetworkManager 0.6.2 today and it was not
working for me ok. He didn't wanted to connect to my wired LAN
network. So I put the old 0.6.0 on from Fedora.
My
Jon Escombe lists at dresco.co.uk writes:
Patch follows inline (can't post as an attachment from here - so can only
apologise if the formatting gets messed up)
Grr, let me try that again...
diff -urN NetworkManager.orig/gnome/applet/nm-gconf-wso.c
NetworkManager.patched/gnome/applet/nm-gconf
Firstly, would just like to say thanks to all the developers,
NetworkManager is turning into a really useful tool.
I've just rebuilt NM from source* on an FC5 machine and run
into a couple of issues:
1) WPA2 Enterprise connection works fine when all the credentials
are entered (using TLS a
70 matches
Mail list logo
