[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: NM fails to connect when booting ?? -[SOLVED]



Aaron Konstam wrote:

> And the latest NM can be configured to connect on boot.

1. What do you mean by the "latest" NM?
I get
----------------------------------------------------
[tim mary ~]$ grep NetworkManager /var/log/rpmpkgs
NetworkManager-0.7.0.99-3.fc10.i386.rpm
NetworkManager-glib-0.7.0.99-3.fc10.i386.rpm
NetworkManager-gnome-0.7.0.99-3.fc10.i386.rpm
NetworkManager-openvpn-0.7.0.99-1.fc10.i386.rpm
NetworkManager-vpnc-0.7.0.99-1.fc10.i386.rpm
----------------------------------------------------

2. Are you using KDE or Gnome (or something else)?
(I am running KDE.)

3. I have checked-in "Activate device when computer starts"
in f=>Applications=>Administration=>Network Configuration,
on highlighting the device in question (eth1) and clicking on Edit.
In fact all the check-boxes on this page are ticked.


I notice incidentally that if I go to
f=>Applications=>Administration=>Network Device Control,
I see that nothing is listed under
"The following network interfaces are configured in the active profile".
Does one need to change the "active profile"?
If so, how?



-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]