Unknown SPI Error
Hi, I received a SPI UNKNOWN error, if try to tunnel on a fedora core 5 maschine. What can I do? /var/log/messages says (XXX'ed vpn concentrater's ip): -- May 14 14:12:36 localhost vpnc: local address for XXX.XXX.99.125 is 192.168.1.10 May 14 14:12:36 localhost vpnc: local address for XXX.XXX.254.150 is 192.168.1.10 May 14 14:12:36 localhost vpnc[2954]: unknown spi 0 May 14 14:12:36 localhost vpnc[2954]: unknown spi from XXX.XXX.254.150 May 14 14:12:36 localhost NetworkManager: information VPN Activation (UniBE) Stage 4 of 4 (IP Config Get) reply received. May 14 14:12:36 localhost NetworkManager: WARNING get_dbus_guint32_helper (): Error: couldn't get MSS from VPN IP Config message. May 14 14:12:36 localhost NetworkManager: WARNING nm_vpn_service_stage4_ip_config_get (): (VPN Service org.freedesktop.NetworkManager.vpnc): did not receive valid IP config information. May 14 14:12:36 localhost NetworkManager: information VPN Activation (UniBE) failed. -- Thank you! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A comment on NetworkManager
On Saturday 13 May 2006 12:26, Gene Heskett wrote: [snip] After a restart, gnome-keyring-daemon is running. Next? You're all set. The nm-applet can now store credentials for encrypted wireless networks in the GNOME keyring. This means that you won't have to keep entering the pass phrases each time you want to associate with an encrypted network. Jon Nettleton also points out that, if you use your login password to lock the GNOME keyring, you can avoid having to explicitly unlock the keyring by adding pam_keyring. It tries the login password and, if successful, automatically unlocks the keyring. No second prompt. Nice. Enjoy. -- Garry T. Williams --- +1 678 656-4579 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
A reconsideration of the list reply configuration.
When I am wrong I an wrong. I have been thinking about it. Despite what
red hat lists do I think that return to message sender is the best
configuration of this list.
With appropriate e-mail clients we can then:
1. reply to the poster of the message. [reply]
2. reply to the list alone {reply to list]
3. reply to both [reply all]
The only bad thing is that some mail clients [mutt for example] do not
have these three options but you can fake it if your clever.
--
Aaron Konstam [EMAIL PROTECTED]
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: D-BUS/Qt3 bindings for knetworkmanager
Hi Chris, On Sun, 2006-05-14 at 12:41 +0100, Chris Jones wrote: whilst trying to build knetworkmanager from KDE svn, on FC5, I get configure: WARNING: You need D-BUS/Qt3 bindings during ./configure I asked on the FC mailing lists about the availability of D-BUS/Qt3 bindings, and got this response Do we have FC5 rpms for these D-BUS/Qt3 bindings ? Could find anything via yum search In short, No. Long story (as I understand it): the dbus-qt3 bindings were recently removed from upsgream dbus due to lack of maintainership. No. They were not removed. The Qt4 bindings were moved in, but the Qt3 bindings were not removed. Additionally, the new Qt4 bindings have been backported to Qt3. They are not part of D-BUS -- they are living somewhere in the KDE SVN as far as I know. So, the version of dbus on fc5 is new enough to not even include those bindings. There is a --disable-qt3 switch which helps if one does not want to build and package the Qt3 bindings. The good news is that there is a new dbus-qt maintainer (for both qt3 and qt4), but the new qt3 bindings aren't binary compatible with the old ones, and aren't distributed with dbus. So the question is, does kentworkmanager need/use the old no-longer-available dbus/qt3 bindings, or is it asking for the new (not-yet-available) dbus/qt3 bindings? So, what bindings does knetworkmanager need ? The Qt3 bindings shipping with D-BUS. I am cc'ing Danny. He might have some pointers wrt availability of the Qt3 bindings on FC5. cheers Chris Timo ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A reconsideration of the list reply configuration.
On Sun, 2006-05-14 at 15:40 -0500, Aaron Konstam wrote:
When I am wrong I an wrong. I have been thinking about it. Despite what
red hat lists do I think that return to message sender is the best
configuration of this list.
With appropriate e-mail clients we can then:
1. reply to the poster of the message. [reply]
2. reply to the list alone {reply to list]
3. reply to both [reply all]
The only bad thing is that some mail clients [mutt for example] do not
have these three options but you can fake it if your clever.
Personally I tend to prefer the 'reply to list, unless the poster
specifically sets the reply-to' option, because most people sending a
msg to a list expect the reply to be sent to the list; but I don't
really see it as a big deal either way.
The only frustrating part is remembering which list is which before
hitting the reply, but with reply to list supported in evo, I guess I
just need to get in the habit of hitting Ctrl-L. :-/
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: latest NM update has broken my VPN
On Sun, 2006-05-14 at 20:16 -0400, Mike Detwiler wrote: Dave Mitchell wrote: Since today's yum update of network manager, my VPN (using NetworkManager-vpnc) no longer works. Here's the output of /var/log/messages when I try to connect: May 14 23:52:45 splatty NetworkManager: information VPN Activation (FDI) Stage 4 of 4 (IP Config Get) reply received. May 14 23:52:45 splatty NetworkManager: WARNING get_dbus_guint32_helper (): Error: couldn't get MSS from VPN IP Config message. May 14 23:52:45 splatty NetworkManager: WARNING nm_vpn_service_stage4_ip_config_get (): (VPN Service org.freedesktop.NetworkManager.vpnc): did not receive valid IP config information. May 14 23:52:45 splatty NetworkManager: information VPN Activation (FDI) failed. Same problem here with the same output in /var/log/messages. Also the same. -- Brian Millett - [ Sheridan (re: Project Lazarus), A Spider in the Web] The theory was to 'hard-wire' the subject's brain with a computer intelligence that kept the brain functional while the body was repaired. Then, using telepathic deep scan, the subject was fixated on the moment of his death, shutting down all conscious thought. The computer takes complete control, while the subject is dying over and over again in his subconscious. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Unknown SPI Error
On Sun, 2006-05-14 at 14:28 +0200, Andreas Zocher wrote: Hi, I received a SPI UNKNOWN error, if try to tunnel on a fedora core 5 maschine. What can I do? That would actually be a question for the vpnc-devel list. I get that sort of message from time to time too, even on Windows or Mac OS X with the Cisco client. Do you know if your VPN has a really short rekey interval? Dan /var/log/messages says (XXX'ed vpn concentrater's ip): -- May 14 14:12:36 localhost vpnc: local address for XXX.XXX.99.125 is 192.168.1.10 May 14 14:12:36 localhost vpnc: local address for XXX.XXX.254.150 is 192.168.1.10 May 14 14:12:36 localhost vpnc[2954]: unknown spi 0 May 14 14:12:36 localhost vpnc[2954]: unknown spi from XXX.XXX.254.150 May 14 14:12:36 localhost NetworkManager: information VPN Activation (UniBE) Stage 4 of 4 (IP Config Get) reply received. May 14 14:12:36 localhost NetworkManager: WARNING get_dbus_guint32_helper (): Error: couldn't get MSS from VPN IP Config message. May 14 14:12:36 localhost NetworkManager: WARNING nm_vpn_service_stage4_ip_config_get (): (VPN Service org.freedesktop.NetworkManager.vpnc): did not receive valid IP config information. May 14 14:12:36 localhost NetworkManager: information VPN Activation (UniBE) failed. -- Thank you! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
