On Thu, 2005-10-20 at 23:22 +0200, Joris Vuffray wrote:
> Trying to add a vpn connection produce following error:
> "No suitable VPN software was found on your system. Contact your
> system administrator."
>
> I'm running NetworkManger 0.5.1 on gentoo & vpnc 0.3.2
>
> Is this a problem with the l
On Thu, 2005-10-20 at 14:38 -0400, Peter Jones wrote:
> Both of them should be started by init during boot. I think starting it
> through this mechanism is just incorrect.
Can you elaborate on this? From my point of view, named can either be
controlled through dbus, or it can be a standalone DNS
Matthew Saltzman wrote:
On Thu, 20 Oct 2005, Matthew Saltzman wrote:
On Wed, 19 Oct 2005, Myk Melez wrote:
Matthew Saltzman wrote:
nm-applet starts on login, but never prompts for my keyring
password. It starts showing "no connection". When I enter the
ESSID in the "connect to other wirel
Hi,
I finally got NetworkManager 0.5.0 builded, but dhcp doesn't work for me.
I'm getting the following messages in /var/log/messages:
Oct 19 21:42:34 poseidon
dhcdbd: message_handler: message handler not found under
/com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Oct 19 21:42:36 poseido
What is it?
===
NetworkManager attempts to keep an active network connection available
at all times. The point of NetworkManager is to make networking
configuration and setup as painless and automatic as possible.
NetworkManager 0.5.1 is the latest release in the unstable series
leading
Trying to add a vpn connection produce following error:
"No suitable VPN software was found on your system. Contact your system administrator."
I'm running NetworkManger 0.5.1 on gentoo & vpnc 0.3.2
Is this a problem with the location of the config files?
Regards,
- Joris
--
J
On Thu, 2005-10-20 at 11:13 +0100, D. D. Brierton wrote:
> On Wed, 2005-10-19 at 15:44 -0400, Christopher Aillon wrote:
> > Seems this might be due to error on my part. The package didn't force
> > an update of wireless-tools as it should have. See
> > https://bugzilla.redhat.com/bugzilla/show_
On Thu, 20 Oct 2005, Matthew Saltzman wrote:
On Wed, 19 Oct 2005, Myk Melez wrote:
Matthew Saltzman wrote:
nm-applet starts on login, but never prompts for my keyring password. It
starts showing "no connection". When I enter the ESSID in the "connect to
other wireless" dialog, it eventuall
On Thu, 2005-10-20 at 18:39 +0200, Tomislav Vujec wrote:
> On Tue, 2005-10-18 at 14:41 -0400, Dan Williams wrote:
> > No, NM no longer spawns named directly at any point. If named is
> > already running (we check whether the DBUS service that named provides
> > is active or not) then NM will use i
On Tue, 2005-10-18 at 14:41 -0400, Dan Williams wrote:
> No, NM no longer spawns named directly at any point. If named is
> already running (we check whether the DBUS service that named provides
> is active or not) then NM will use it. If the service is not running,
> NM falls back to writing /et
I was also suffering from this problem. To *really* confirm this, updating
wireless-tools works.
I suffered from one more problem then, I didn't have the dhcdbd package (it
this also listed as a dependency ? Since it didn't install it). After
installing that, it still refused to work. Rebooting wa
On Thu, 2005-10-20 at 11:13 +0100, D. D. Brierton wrote:
> H. I just did that and it appears to have killed NM altogether. I've
> attempted to restart the service to no avail:
>
[snip]
Christopher, I was holding off bugzillaing this in case there was
something simple I was missing, but would
On 10/19/2005 01:12 PM, Nick Atkins wrote:
Hi all,
I saw the announcement about 0.5.0 and decided to upgrade from the
updates-testing repo on Fedora using the command:
*yum --enablerepo=updates-testing update NetworkManager bind dhcdbd*
The announcement also told you to report issues to RH bu
Hi all,
I saw the announcement about 0.5.0 and decided to upgrade from the
updates-testing repo on Fedora using the command:
yum --enablerepo=updates-testing update NetworkManager
bind dhcdbd
The packages installed OK and I even rebooted but NetworkManager just
does not work properly. It fai
I also tried updating those packages and NM just does not work. At one
point it does seem to connect and I see the "blue steps" icon but then
it goes away as NetworkManager crashes.
Myk Melez wrote:
Matthew Saltzman wrote:
nm-applet starts on login, but never prompts for my keyring
password.
On Wed, 19 Oct 2005, Myk Melez wrote:
Matthew Saltzman wrote:
nm-applet starts on login, but never prompts for my keyring password. It
starts showing "no connection". When I enter the ESSID in the "connect to
other wireless" dialog, it eventually prompts me for the key, then fails to
connec
On Wed, 2005-10-19 at 15:44 -0400, Christopher Aillon wrote:
> Seems this might be due to error on my part. The package didn't force
> an update of wireless-tools as it should have. See
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=171195
>
> `yum --enablerepo=updates-testing update w
17 matches
Mail list logo