nm-openswan development update
Hi, It's been busy at work and hence development slows down accordingly, but my weekends are free and I've made some big strides this weekend. I also wasted about 5 hours of my time today (not to mention the frustration and head scratching for the past 3 weeks) at why the symbol plugin for Anjuta (my IDE) wasn't working reliably: it sometimes displayed correct data, then other times it wouldn't display that same data at all. The 5 hours today went towards 3 efforts: 1. Try out eclipse (read the docs -- it doesn't support automake build systems) 2. Try out Kdevelop (well.. I'm not developing for KDE and it crashed everytime I tried to import my project or create a new GTK+ project and import my source 3. Try to compile the latest source of the next rev of Anjuta: Too many library version conflicts with my FC6 installation to make a sane build enviornment feisable on my laptop. Then I stumbled across the reason for all my problems: I started with the source to nm-vpnc (FC6 src rpm + redhat patches) and of course, just like copying in school, you get the mistakes as well as the correct answers. Moral of the Story: Don't copy verbatim if you can avoid it. After I fixed the problem ( which had to do with name/type conflicts on typedef struct definitions ) the symbol browser in FC6's default installation of Anjuta started working perfectly. Afterwards, I ran a build of the default vpc source (Just for kicks) and saw warnings about the same thing. Anyway, just wanted to save people time if anyone else is writing a vpn plugin, and started with the source an existing one for reference like I did. Development continues on nm-openswan and I hope to have a complete set of working alpha code for all targets of the plugin in about 2 weeks. At that point I'm going to setup some kind of CVS repository for the dist. There is still one big design question to be answered through testing. If anyone knows openswan well, or cares to help me figure this one out, feel free to offer advice. Here's my dilema: Call out to /usr/libexec/ipsec/whack to initiate/terminate an ipsec connection -OR- integrate the code for whack into my project and link against it at build time (so my code actually talks directly to pluto through a socket). I don't like this idea as my code becomes dependant on a specific version of openswan (it's hard to explain the why of that). Each new major rev of openswan will require an update to my source and a recompile to work again and introducing depenancies doesn't seem to fit with the design goals of NetworkManager. All feedback welcome. I'll send another update once I've got this problem licked and the alpha code compiles (without segfaults at runtime ;) Steve. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Weird nm-applet behavior.
Denis Leroy wrote: > Aaron Konstam wrote: >> What is described below has happened to me at least twice. I asked about >> it on this list and got no real assistance. Can anyone guess why this >> would happen? The person who posted below was using FC6 and I was was >> using FC5 if that is important. >> >> 2/ NetworkManager has started to claim that it has successfully >> connected to a wired network. This is weird as the computer isn't >> connected to a wired network. All network access is through a PCI >> wireless card. Still works fine. It just thinks it's the wrong kind of >> network. > > Ran into a similar issue a few times a well, on FC6. Wifi is a > Atheros-based PCI card. This also happens using the Netgear MA CF card from my PDA (in a PCMCIA carrier adapter). It works, but nm thinks it's eth1 not ath0. ///Peter ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
If WiFi is off during boot I can turn it on afterwards and connect. Otherwise, no go.
I can connect to my wireless router only if I switch off the wifi before I boot linux. Once booted, I switch it on, at which point it prompts me for my keyring password. It takes quite a while but if finally authenticates and connects. If I boot with it switched on it won't authenticate. Switching off and on at this point does no good. Any clue as to why this might be the case? This is a 3 week old Toshiba Laptop running the latest Feisty upgrades. Thanks, Karl ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager and wpa
On Fri, 2007-03-23 at 23:03 -0400, Darren Albers wrote:
> On 3/23/07, Martin Monroe <[EMAIL PROTECTED]> wrote:
> > Just as a preface: I think NetworkManager is great and use it almost
> > exclusively to connect to wired or wireless networks on my Ubuntu Edgy
> > Laptop.
> >
> > Here's one case where it doesn't work and I hope the information I provide
> > can help in solving the problem:
> >
> > I am unable to connect to my university's wifi network through the
> > NetworkManager dialogs. The icon whirls and then 60s are reached and it
> > disconnects for taking too long. I had a look at syslog as it was doing
> > this but to my untrained eye saw nothing of interest.
> >
> > I can however connect with just straight wpa_supplicant and dhclient. My
> > school (thankfully) provided a wpa_supplicant.conf file for Linux users to
> > install with the instructions "After this it should all just work".
> >
> > the file is as follows:
> > /
> > ctrl_interface=/var/run/wpa_supplicant
> > ctrl_interface_group=0
> >
> > eapol_version=1
> > ap_scan=1
> > fast_reauth=1
> >
> > network={
> > ssid="eduroam"
> >
> > key_mgmt=WPA-EAP
> > eap=TTLS
> >
> > ca_cert="/etc/ssl/certs/soas-root-ca.pem"
> > anonymous_identity="@soas.ac.uk"
> > identity=" [EMAIL PROTECTED]"
> > password="password"
> > phase2="auth=PAP"
> >
> > priority=5
> >
> > }
> >
> > ///
> >
> > then by running the command line:
> > wpa_supplicant -Dwext -ieth1 -K -dd -c
> > /etc/wpa_supplicant/wpa_supplicant.conf -B
> >
> > and waiting a few seconds and then running dhclient, I'm connected to the
> > network.
> >
> > I've tried all manner of options in NetworkManager and none seem to work.
> >
> > I thought it might have something to do with the phase2 authentication (the
> > line being: "phase2="auth=PAP"") as I saw no-where to set that in NM.
> >
> > Anyway I hope this case might help improve NetworkManager,
> >
> > Best of luck,
> > -M. Willis Monroe
> >
> > ___
> > NetworkManager-list mailing list
> > NetworkManager-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> >
> >
>
> As you guessed Phase2 auth is not supported in NM yet but I think it
> is slated for .7
There is phase2 functionality in 0.6.5 SVN and should be there when it
gets released.
Dan
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Weird nm-applet behavior.
On Sun, 2007-03-25 at 09:42 +0200, dragoran wrote: > I can confirm that this works fine with 0.6.4 but not with 0.6.5 so its > not a driver issue. Has 0.6.5 been released? I thought it had not. Does 0.6.5 have LEAP authentication, and where can it be found? -- Aaron Konstam <[EMAIL PROTECTED]> ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Weird nm-applet behavior.
Aaron Konstam wrote: > What is described below has happened to me at least twice. I asked about > it on this list and got no real assistance. Can anyone guess why this > would happen? The person who posted below was using FC6 and I was was > using FC5 if that is important. > > 2/ NetworkManager has started to claim that it has successfully > connected to a wired network. This is weird as the computer isn't > connected to a wired network. All network access is through a PCI > wireless card. Still works fine. It just thinks it's the wrong kind of > network. Ran into a similar issue a few times a well, on FC6. Wifi is a Atheros-based PCI card. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=224086 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
