Re: Basic questions [Was: How to monitor NM progress?]
On Mon, 2010-09-20 at 15:58 +0200, Rafal Wojtczuk wrote: > On Wed, Sep 15, 2010 at 02:50:46PM +0100, Marc Herbert wrote: > > > So, the device is not managed if and only if the STATE field == > > > 'unavailable' ? > > > > I do not think so: > > > > LC_ALL=C nmcli dev > > DEVICE TYPE STATE > > eth1 802-3-ethernetunmanaged > > eth0 802-3-ethernetunmanaged > > > > > [I am a bit embarassed to ask such basic questions, but I am unable > > > to find a comprehensive NM documentation, and reading its sources is > > > a bit resource consuming]. > > > > http://live.gnome.org/NetworkManager/SystemSettings > > In this page, I do not see an answer to the following question: is it > possible to tell nm-applet to _not_ display unmanaged interfaces at all ? > > Thanks for all the answers so far btw. No, there is no option for that. We specifically added that functionality because many, many Ubuntu users were highly confused tha their network devices were unknown to NetworkManager, because NM 0.6 did hide them from the UI when they were unmanaged. The mailing list would get at least one "where's my network device?" mail from some Ubuntu user every week, because of how the ifupdown plugin handles unmanaged interfaces. To make the situation clearer, and to show users /why/ their network devices were not handled by NetworkManager, we made nm-applet show unmanaged devices. This alerts users to exactly why things don't necessarily work out of the box on distros that unmanaged devices in more common use-cases. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Basic questions [Was: How to monitor NM progress?]
On Wed, Sep 15, 2010 at 02:50:46PM +0100, Marc Herbert wrote: > > So, the device is not managed if and only if the STATE field == > > 'unavailable' ? > > I do not think so: > > LC_ALL=C nmcli dev > DEVICE TYPE STATE > eth1 802-3-ethernetunmanaged > eth0 802-3-ethernetunmanaged > > > [I am a bit embarassed to ask such basic questions, but I am unable > > to find a comprehensive NM documentation, and reading its sources is > > a bit resource consuming]. > > http://live.gnome.org/NetworkManager/SystemSettings In this page, I do not see an answer to the following question: is it possible to tell nm-applet to _not_ display unmanaged interfaces at all ? Thanks for all the answers so far btw. Regards, Rafal Wojtczuk ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Basic questions [Was: How to monitor NM progress?]
On Wednesday 15 of September 2010 12:46:07 Rafal Wojtczuk wrote: > Another basic question no 1: how can I tell NM to keep its hands off a > particular interface ? I tried adding (in the [main] section of > nm-system-settings.conf) > no-auto-default=FE:FF:FF:FF:FF:FF > > and (in the [keyfile]) > unmanaged-devices=FE:FF:FF:FF:FF:FF > Unmanaged deviced are defined via plugin-specific way. See man NetworkManager.conf For Fedora/RHEL put NM_CONTROLLED=no to /etc/sysconfig/network-scripts/ifcfg- eth0 (eth1, etc.) "no-auto-default" only list interfaces for which a default connection (Auto eth0) shouldn't be created (in case no other connection is available for the device). It has nothing in common with unmanaging interfaces. > Another basic question no 2: > how can I tell NM to keep its hands off /proc/sys/net/ipv4/ip_forward ? > I think NM sets ip_forward just in case the method is "Shared to other computers" to allow forwarding packets. Jirka ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Basic questions [Was: How to monitor NM progress?]
>> {pts/1}% LC_ALL=C nmcli dev
>> DEVICE TYPE STATE
>> wlan0 802-11-wireless connected
>> eth0 802-3-ethernetunavailable
>
> So, the device is not managed if and only if the STATE field ==
> 'unavailable' ?
I do not think so:
LC_ALL=C nmcli dev
DEVICE TYPE STATE
eth1 802-3-ethernetunmanaged
eth0 802-3-ethernetunmanaged
> [I am a bit embarassed to ask such basic questions, but I am unable
> to find a comprehensive NM documentation, and reading its sources is
> a bit resource consuming].
http://live.gnome.org/NetworkManager/SystemSettings
> Another basic question no 1: how can I tell NM to keep its hands off
> a particular interface ?
This does not look like "another" question to me; rather the exact
same "unmanaged" question.
> I tried adding (in the [main] section of nm-system-settings.conf)
This file has been recently renamed to NetworkManager.conf (in 0.8?).
The syntax of "unmanaged-devices=..." has also changed since
NM does not use HAL any more.
It's probably simpler to "unmanage" a device using system-config-network.
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Basic questions [Was: How to monitor NM progress?]
On Tue, Sep 14, 2010 at 07:21:45PM +0400, Andrey Borzenkov wrote:
> On Tuesday 14 of September 2010 16:48:45 Rafal Wojtczuk wrote:
> >
> > Alternatively, is there a way to retrieve all interfaces names that NM
> > is supposed to manage ?
> >
>
> For a start
>
> {pts/1}% LC_ALL=C nmcli dev
> DEVICE TYPE STATE
> wlan0 802-11-wireless connected
> eth0 802-3-ethernetunavailable
So, the device is not managed if and only if the STATE field ==
'unavailable' ?
[I am a bit embarassed to ask such basic questions, but I am unable to find
a comprehensive NM documentation, and reading its sources is a bit resource
consuming].
Another basic question no 1: how can I tell NM to keep its hands off a
particular
interface ? I tried adding (in the [main] section of
nm-system-settings.conf)
no-auto-default=FE:FF:FF:FF:FF:FF
and (in the [keyfile])
unmanaged-devices=FE:FF:FF:FF:FF:FF
FE:FF:FF:FF:FF:FF being the address of Xen vif interface.
But nevetheless,
/usr/lib64/pm-utils/sleep.d/55NetworkManager suspend
still ifconfigs all vif devices down, and this tears down the custom routes
set via these devices; these routes are not restored on resume, which is bad.
Perhaps it is a bug.
Another basic question no 2:
how can I tell NM to keep its hands off /proc/sys/net/ipv4/ip_forward ?
RW
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
