Hi;

Last week I was messing around with my network and Internet connections
and managed to break NeteworkManager. See thread "Messed up my
ISP/Networkmanager connection !?" Aug 5. Since I couldn't get it fixed,
I stopped and disabled the NetworkManager service. I now find that many
of my gnome services are somehow dependant on it.

Will 'yum remove NetworkMangaer' remove it or will I end up in
dependency hell? I would prefer to fix it but I am a fish out of water
when it comes to anymore than rudimentary network stuff.

My current ~/.xsession-errors. I moved the
previous file aside before logging out and back in so it is absolutely
current.

xrdb: colon missing on line 18, ignoring line
SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/3565,unix/unix:/tmp/.ICE-unix/3565
seahorse nautilus module initialized

** (nautilus:3654): WARNING **: Unable to add monitor: Not supported
Failure: Module initalization failed
** Message: failed to load session
from /home/bill/.nautilus/saved-session-0E9JFU

** (nm-applet:3708): WARNING **: nm_object_get_property: Error getting
'WirelessHardwareEnabled' for /org/freedesktop/NetworkManager: The name
org.freedesktop.NetworkManager was not provided by any .service files


** (nm-applet:3708): WARNING **: No connections defined
evolution-alarm-notify-Message: Setting timeout for 47486 1218600000
1218552514
evolution-alarm-notify-Message: Wed Aug 13 00:00:00 2008

evolution-alarm-notify-Message: Tue Aug 12 10:48:34 2008

CalDAV Eplugin starting up ...
connect: Operation now in progress
Unable to open desktop file /home/bill/Desktop/alacarte-made.desktop for
panel launcher: No such file or directory
** (evolution:3669): DEBUG: mailto URL command: evolution
--component=mail %s
** (evolution:3669): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
(org.freedesktop.DBus.Error.ServiceUnknown) The name
org.freedesktop.NetworkManager was not provided by any .service files

** (nm-applet:3708): WARNING **: nm_object_get_property: Error getting
'ActiveConnections' for /org/freedesktop/NetworkManager: The name
org.freedesktop.NetworkManager was not provided by any .service files

BBDB spinning up...

Shouldn't I be able to make commandline adjustments to network
configurations (for ill or good) and still get NetworkManager to
continue to operate, on my machine at least? If I made mistakes,
shouldn't I, none-the-less, be able to correct them through the
NetworkManager gui?

--
Regards Bill;
Fedora 9, Gnome 2.22.3
Evo.2.22.3.1, Emacs 22.2.1

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Tue, Aug 12, 2008 at 7:55 AM, William Case <billlinux@rogers.com> wrote:

Shouldn't I be able to make commandline adjustments to network

configurations (for ill or good) and still get NetworkManager to

continue to operate, on my machine at least? *If I made mistakes,

shouldn't I, none-the-less, be able to correct them through the

NetworkManager gui?


I missed the original thread detailing how you munched your NM config..ill need to go back and read it.* But quick answer for now on how you can work around this until i understand how you screwed up your NM config:


system-config-network can be used in F9 if needed to configure devices using the legacy sysconfig network scripts. iit has a new setting to turn NM control of the device on or off per device. This gui toggle sets a new variable in the legacy networking scripts which get written down below /etc/sysconfig.* The legacy network service..appropriately named 'network' must be turned on...for these configs to be parsed...the legacy service its off by default.* If you have set the configs correct NM will ignore those devices and let the legacy service handle them.



-jef

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Tue, Aug 12, 2008 at 2:45 PM, Jeff Spaleta <jspaleta@gmail.com> wrote:

I missed the original thread detailing how you munched your NM config..ill need to go back and read it.* But quick answer for now on how you can work around this until i understand how you screwed up your NM config:



Okay I've caught up.

NM does NOT make use of most of the information set through system-config-network usage nor any information you manually set in the ifcfg-* scripts.* These are legacy network controls and there are provided explicitly because the developers of NM know..full well..that NM is not feature complete for all network needs. The are working on it.* My gut feeling is you are primarily confused because you are expecting NM to read the legacy network configs..and they don't.* It's not clear to me that you made any changes to NM's configs..i saw you attempting to edit the legacy configs and resulting confusion.


Before we get into specifics as to what you should or should not be doing to configure to make NM useful for you again.. I need to understand what your network topology and a succint and completely english-with no numbers or urls-description of what you are trying to do with your network set up.


For example... NM works perfectly fine for my very mundane network topologies I have to work with.* At home I have an off-the-shelf lan router which acts as both dns and dhcp... NM works just fine there wired and wireless.* I even vpn into work no problems.* At work I have another dhcp server configuration to deal with, nothing fancy..things just work..wired and wireless.


So I need to understand what inspired you to make manual changes at all..before I can attempt to direct you on what to do.

I'm also probably going to need to review several of your network related scripts down in /etc/sysconfig


And no..you can't just remove NM..dont even try..you'll just get into deep deep trouble.

-jef

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Hi Jeff;

I would appreciate the help getting things back to normal.

On Tue, 2008-08-12 at 15:05 -0800, Jeff Spaleta wrote:
>
>
> On Tue, Aug 12, 2008 at 2:45 PM, Jeff Spaleta <jspaleta@gmail.com>
> wrote:
> I missed the original thread detailing how you munched your NM
> config..ill need to go back and read it. But quick answer for
> now on how you can work around this until i understand how you
> screwed up your NM config:
>
>
> Okay I've caught up.
>
> NM does NOT make use of most of the information set through
> system-config-network usage nor any information you manually set in
> the ifcfg-* scripts. These are legacy network controls and there are
> provided explicitly because the developers of NM know..full well..that
> NM is not feature complete for all network needs. The are working on
> it.


> My gut feeling is you are primarily confused because you are expecting
> NM to read the legacy network configs..and they don't. It's not clear
> to me that you made any changes to NM's configs..i saw you attempting
> to edit the legacy configs and resulting confusion.

Yes, that is what happened.
>
> Before we get into specifics as to what you should or should not be
> doing to configure to make NM useful for you again.. I need to
> understand what your network topology and a succint and completely
> english-with no numbers or urls-description of what you are trying to
> do with your network set up.

> For example... NM works perfectly fine for my very mundane network
> topologies I have to work with. At home I have an off-the-shelf lan
> router which acts as both dns and dhcp... NM works just fine there
> wired and wireless. I even vpn into work no problems. At work I have
> another dhcp server configuration to deal with, nothing fancy..things
> just work..wired and wireless.
>

Your description fits mine. I have a three computer home LAN; 1 dual
boot running Fedora 9 + WindowsXP; 2nd running Ubuntu + WindowsXP and a
3rd running WindowsXp. The house was purchased completely wired with
cat5 leading to a central router in the basement which in turn is
connected to a cable modem leading out of the house.

> So I need to understand what inspired you to make manual changes at
> all..before I can attempt to direct you on what to do.
>

What *inspired* me was that the time had come to learn about networking,
from top to bottom; inside out. In the past, including the Fedora 9
installation, I understood only the rudiments of network setup and
Internet connecting. I basically let whatever front ends that existed
set the networks up for me. Anaconda seemed to have correctly installed
NetworkManager for me when I did a fresh install of F9

A week or so ago I began to read various manuals, texts and tutorials,
all of which dealt with a pre-NetworkManager world. The changes came
about as a result of various experiments, tweaks and tries using the
command line.

This is in fact something I would like to do over the next few weeks
until a understand more than just the basics. If this means
NetworkManager is going to be in the way while I learn then I would like
to temporarily remove it. I would like to end the learning process by
re-introducing NetworkManager but only after learning the wheres and
whyfors about its operation.

> I'm also probably going to need to review several of your network
> related scripts down in /etc/sysconfig
>

ifcfg-eth0:
# nVidia Corporation MCP51 Ethernet Controller
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=00:1a:92:e5:dc:47
ONBOOT=yes
DHCP_HOSTNAME=CASE
NM_CONTROLLED=no
TYPE=Ethernet
#DNS1=192.168.1.1

DEVICE=lo
IPADDR=127.0.0.1
NETMASK=255.0.0.0
NETWORK=127.0.0.0
# If you're having problems with gated making 127.0.0.0/8 a martian,
# you can change this to something else (255.255.255.255, for example)
BROADCAST=127.255.255.255
ONBOOT=yes
NAME=loopback

For various ifup-xx and ifdown-xx scripts let me know which ones you
need.

I will be happy to post any other information you need, including router
data.

> And no..you can't just remove NM..dont even try..you'll just get into
> deep deep trouble.
>
> -jef

>
--
Regards Bill;
Fedora 9, Gnome 2.22.3
Evo.2.22.3.1, Emacs 22.2.1

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Tue, Aug 12, 2008 at 7:20 PM, William Case <billlinux@rogers.com> wrote:

ifcfg-eth0:

# nVidia Corporation MCP51 Ethernet Controller

DEVICE=eth0

BOOTPROTO=dhcp

HWADDR=00:1a:92:e5:dc:47

>
DHCP_HOSTNAME=CASE

NM_CONTROLLED=no

TYPE=Ethernet

#DNS1=192.168.1.1



Number 1 problem...... NM_CONTROLLED=no** informs NM to hide this device completely. NM will not even show this in its applet interface as being active.* This was added specifically so that NM would not get in the way of people who feel they need to use the legacy network script stack. system-config-network if used to edit a device's config defaults to setting this to no via a radio button selection. The idea being..if you use s-c-network to change the config, then normally you want NM to ignore the device so your configs will work.* At some point s-c-network will go away when NM is feature complete and we'll have less confusion for the average desktop/laptop home system userbase.* We may even think about not including s-c-network by default in F10..but have it available in the repo...if NM's static address support is good enough in F10. Not my call, but something worth thinking about.


So what you need to do is change that to NM_CONTROLLED=yes
stop the legacy network service (keep it from starting at boot too)
start the NetworkManager service (make sure its starting at boot too)

That should be enough to at least make NM's applet appear to function correctly.

If there is still a problem... I need to look at your /etc/hosts and /etc/resolv.conf files and possible the output of route.

-jef

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Wed, 2008-08-13 at 08:13 -0800, Jeff Spaleta wrote:
>
>
> On Tue, Aug 12, 2008 at 7:20 PM, William Case <billlinux@rogers.com>
> wrote:
> ifcfg-eth0:
> # nVidia Corporation MCP51 Ethernet Controller
> DEVICE=eth0
> BOOTPROTO=dhcp
> HWADDR=00:1a:92:e5:dc:47
> ONBOOT=yes
> DHCP_HOSTNAME=CASE
> NM_CONTROLLED=no
> TYPE=Ethernet
> #DNS1=192.168.1.1
>

>
> So what you need to do is change that to NM_CONTROLLED=yes
Done
> stop the legacy network service (keep it from starting at boot too)
network service is disabled but refuses to unplug. Every time I try to
'stop' in either the services 'gui' or by command line I get the
following SELinux warning:

SELinux is preventing ifup-eth (hotplug_t) "append"
to ./dhclient-eth0.conf (etc_t).

[SELinux is in permissive mode, the operation would have been denied but
was permitted due to permissive mode.]

Trying to stop network by the command line:

]# service network stop
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]

]# service network status
Configured devices:
lo eth0
Currently active devices:
eth0

> start the NetworkManager service (make sure its starting at boot too)
Done
]# service NetworkManager status
NetworkManager (pid 2339) is running...


>
> That should be enough to at least make NM's applet appear to function
> correctly.
The applet appear's to function correctly.

> If there is still a problem... I need to look at your /etc/hosts
> and /etc/resolv.conf files and possible the output of route.
>

As additional referrence:
/etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 CASE localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6

/etc/resolv.conf
# generated by NetworkManager, do not edit!

nameserver 192.168.1.1

]$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 * 255.255.255.0 U 0 0 0
eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0
eth0

Does NetworkManager have a separate configuration file? If so, where is
it?


--
Regards Bill;
Fedora 9, Gnome 2.22.3
Evo.2.22.3.1, Emacs 22.2.1

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Wed, Aug 13, 2008 at 10:41 AM, William Case <billlinux@rogers.com> wrote:

> stop the legacy network service (keep it from starting at boot too)

network service is disabled but refuses to unplug. *Every time I try to

'stop' in either the services 'gui' or by command line I get the

following SELinux warning:



SELinux is preventing ifup-eth (hotplug_t) "append"

to ./dhclient-eth0.conf (etc_t).


where is dhclient-eth0.conf* exactly?** I think you should just remove it since I dont think such a file exists for default operation.* Find where it is, and if you want a backup of it to use later.. for more experimenting...just move it to /root/* for now instead of deleting it.

*The applet appear's to function correctly.


So if the applet appears to function correctly...does the network appear to work as expected?

As additional referrence:

/etc/hosts

# Do not remove the following line, or various programs

# that require network functionality will fail.

127.0.0.1 * * * CASE localhost.localdomain * * * localhost

::1 * * * * * * * * *localhost6.localdomain6 * * localhost6



/etc/resolv.conf

# generated by NetworkManager, do not edit!



nameserver 192.168.1.1


i take it 192.168.1.1 is the ip of your router?
*


]$ route

Kernel IP routing table

Destination * * Gateway * * * * Genmask * * * * Flags Metric Ref * *Use

Iface

192.168.1.0 * * * * * * * * * * 255.255.255.0 * U * * 0 * * *0 * * * *0

eth0

default * * * * 192.168.1.1 * * 0.0.0.0 * * * * UG * *0 * * *0 * * * *0

eth0


looks fine as long as 192.168.1.1 is the router.
*

Does NetworkManager have a separate configuration file? *If so, where is

it?

The simplest answer is no... NM doesn't have a single configuration file that can be compared to something like ifcfg-eth0.*

I believe NM makes use of gconf for per-user configs about 'connections' as well as gnome-keyring for network passwords. If you want to explore NM's configs as a user you might want to install gconf-editor and use the gui to explore the network related items you can edit instead of working with the gconf files directly or using the cmdline tools. When you interact with NM via the applet as a logged in user, you are working with the user configs in the user's gconf registry..not a set of system defaults.*


Before you go messing around with gconf stuff I would suggest you back up your user's .gconf and .gconfd directories. If you make a mistake you can just put the backups back into place kill the gconfd service daemon and have things back in order.


The most important thing when poking at your system's configurations directly via the cmdline or advanced ui tools..is to make sure you back things up before you start the 'learning' process. And by back up I mean directory structures you plan to add or remove or edit files under. If you add a file and you don't take notes about what you added.. the only sure way to make sure you remove the files is to refresh the directory entirely to a specific known state.. not just copy in versions of pre-existing files.


There is no automatic 'undo all the changes I shouldn't have made button' when editing configs. Backup...poke your system with a stick till you kill it...reload from the backup..repeat.

-jef

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Thanks very much Jeff;

On Wed, 2008-08-13 at 11:51 -0800, Jeff Spaleta wrote:
[snip]

>
> where is dhclient-eth0.conf exactly?
It is exactly at:
/etc/dhclient-eth0.conf

> I think you should just remove it since I dont think such a file
> exists for default operation. Find where it is, and if you want a
> backup of it to use later.. for more experimenting...just move it
> to /root/ for now instead of deleting it.
I have taken your advice and moved it to
/root/MoveAsides/dhclient-eth0.conf

Should I do the same with
/etc/dhcp6c.conf ?

Currently the file dhcp6c.conf exists but is completely commented out.

>
> The applet appear's to function correctly.
>
>
> So if the applet appears to function correctly...does the network
> appear to work as expected?
>
Not sure. I had a couple of problems with shutdown ( shutdown got stuck
at tomcat5 and I had to turn off the computer manually) and boincmgr
coming up at re-boot but on third try everything worked fine. May or
may not be related to NetworkManager.

> As additional referrence:
> /etc/hosts
> # Do not remove the following line, or various programs
> # that require network functionality will fail.
> 127.0.0.1 CASE localhost.localdomain localhost
> ::1 localhost6.localdomain6 localhost6
>
> /etc/resolv.conf
> # generated by NetworkManager, do not edit!
>
> nameserver 192.168.1.1
>
> i take it 192.168.1.1 is the ip of your router?
>
Yes it is.

>
> ]$ route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric
> Ref Use
> Iface
> 192.168.1.0 * 255.255.255.0 U 0
> 0 0
> eth0
> default 192.168.1.1 0.0.0.0 UG 0
> 0 0
> eth0
>
> looks fine as long as 192.168.1.1 is the router.
>
Then it is fine.

>
> Does NetworkManager have a separate configuration file? If
> so, where is
> it?
> The simplest answer is no... NM doesn't have a single configuration
> file that can be compared to something like ifcfg-eth0.
>
> I believe NM makes use of gconf for per-user configs about
> 'connections' as well as gnome-keyring for network passwords. If you
> want to explore NM's configs as a user you might want to install
> gconf-editor and use the gui to explore the network related items you
> can edit instead of working with the gconf files directly or using the
> cmdline tools.

I have had gconf-editor since I first installed F9. There is no listing
of NetworkManager or anything with network in its name or as a key value
that is related to network or networkmanager or NM or such. Nor is
there any 'connections'.

One entry, /apps/nautilus/desktop/network_icon_visible, is unmarked i.e.
false. That's it.

Double checked ~/.gconf. Nothing there either.

> When you interact with NM via the applet as a logged in user, you are
> working with the user configs in the user's gconf registry..not a set
> of system defaults.
>
Only key found with find "connections"

/apps/gnome-session/options/allow_tcp_connections

Unmarked [false]

> Before you go messing around with gconf stuff I would suggest you back
> up your user's .gconf and .gconfd directories. If you make a mistake
> you can just put the backups back into place kill the gconfd service
> daemon and have things back in order.
>
First I had better find out where my NM stuff is in .gconf. I have
completely eyeballed the file and searched using as many criteria as *I*
can think of and no luck. All suggestions welcome.

> The most important thing when poking at your system's configurations
> directly via the cmdline or advanced ui tools..is to make sure you
> back things up before you start the 'learning' process. And by back up
> I mean directory structures you plan to add or remove or edit files
> under. If you add a file and you don't take notes about what you
> added.. the only sure way to make sure you remove the files is to
> refresh the directory entirely to a specific known state.. not just
> copy in versions of pre-existing files.

Very good advice. But pardon my apparent stupidity, I am not yet sure
where the current gconf configurations are.

By the way; I have been having problems with gnome desktop, nautilus and
friends for a couple of weeks now. The trashcan was removed from my
desktop and re-marking it to be visible does not return it to the
desktop, etc. All minor problems, but annoying -- I hadn't thought of
them being connected to NetworkManager. Perhaps the non-appearance of
NM configuration in gconf-editor and .gconf is related to this problem

>
> There is no automatic 'undo all the changes I shouldn't have made
> button' when editing configs. Backup...poke your system with a stick
> till you kill it...reload from the backup..repeat.
>
Thanks Jeff; I am used to doing that kind of stuff. I have been poking
around Linux for three years now, so I have learnt the hard way.



--
Regards Bill;
Fedora 9, Gnome 2.22.3
Evo.2.22.3.1, Emacs 22.2.1

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list