Re: Disabling wireless networking.

[Dan Williams]

On Thu, 2010-03-18 at 12:00 -0400, Michael H. Warfield wrote:
> On Thu, 2010-03-18 at 11:43 -0300, José Queiroz wrote:
> > Sorry for the naive answer, but, if you're not using wireless, why do
> > you have a wireless adapter in your system?
> 
> It's a laptop (high end developer laptop) with built in bluetooth and
> 802.11 a/b/g/n wifi.  Why do I have it?  I am using it.  Sometimes when
> I don't have hard wired.  It's build-in so removing it is non-trivial
> and sort of senseless if you think about it.
> 
> > Is this some kind of mobile device, like a noteboot/netbook? Doesn't
> > it have some kind of "rfkill" button???
> 
> It does but it only controls the bluetooth for some reason.  My previous
> laptop, it controlled both but not this one for some reason.  It's my
> understanding that the switch is a soft switch, in any case, which does
> not physically or electrically disable the device itself and depends on
> the OS and drivers to do the right thing.  So it may be a driver issue
> at that.  But should it be in the kernel drivers or handled by NM?  I
> don't see the Wifi antenna symbol light up until NM is active.

The other alternative is blacklisting the kernel module that controls
the wifi device.

Dan


> Regardless, it should be possible to configure NM to do what I want, not
> arbitrarily always what it thinks it should in spite of what I've set it
> to.  That's been my perpetual complaint about NM.  I concur with the
> idea that things should just work out of the box, but then it should
> obey what I want it to do, if I don't want it to do what it's doing.
> It's a vast improvement over the bad old days where almost nothing was
> properly configurable and I'm glad to see that this, at least, has been
> already addressed in a newer release and that I'm not the only one with
> this annoyance.  That's progress.
> 
> Mike
> 
> > 2010/3/15 Michael H. Warfield 
> > Hey all,
> > 
> > Pop question.  This is one of my burning annoyances with
> > NetworkManager
> > and maybe there's an easy way to do this and I just can't find
> > it.
> > But...  How do I disable wireless networking by default.  I
> > can disable
> > it but, the next time I log in, it's enabled again.  I want it
> > stone
> > cold dead unless I overtly and explicitly choose to enabled it
> > and then
> > I want it off if I log out and log back in again.
> > 
> > The problem is that I work in an environment that is very rich
> > in IPv6
> > support, at home and at work and on the road and at my
> > colocation
> > facility.  I have v6 everywhere.  The problem is that NM
> > brings up wlan0
> > long after eth0 has been up and then the wlan0 interface gets
> > hit with a
> > new RA (router advertisement) which then causes all the v6
> > traffic to be
> > routed out through the wireless WHICH I DO NOT WANT even
> > though the v4
> > default route is out eth0.  Because wlan0 gets the RA later
> > than the
> > eth0 address in response to its RD (router discovery) request,
> > it has a
> > later expiration time on the routes so it gets preference over
> > the eth0
> > interface.  This is by design.  It's the way v6 is suppose to
> > work and
> > is how you renumber autoconfed v6 networks.  But is screws me
> > over
> > royally when I'm in a situation where I've got a hard wired
> > network
> > connection and the wireless is less than stable and keeps
> > screwing up
> > all my v6 connections.  Disabling it after logging in is
> > useless because
> > it has already brought it up and loaded the v6 routes with a
> > new default
> > and that then just breaks things.
> > 
> > I want wireless off and to STAY OFF unless I want it on and
> > know that I
> > want it on.  But I can't find a sticky setting that basically
> > tells it
> > to play dead and STAY DEAD.  (The wireless "switch" on my
> > laptop only
> > switches the bluetooth, unfortunately).
> > 
> > Mike
> > --
> > Michael H. Warfield (AI4NB) | (770) 985-6132 |
> >  m...@wittsend.com
> >   /\/\|=mhw=|\/\/  | (678) 463-0932 |
> >  http://www.wittsend.com/mhw/
> >   NIC whois: MHW9  | An optimist believes we live in
> > the best of all
> >  PGP Key: 0x674627FF| possible worlds.  A pessimist is
> > sure of it!
> > 
> > ___
> > NetworkManager-list mailing list
> > NetworkManager-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > 
> > 
> > 

Re: Disabling wireless networking.

[Michael H. Warfield]

On Thu, 2010-03-18 at 11:43 -0300, José Queiroz wrote:
> Sorry for the naive answer, but, if you're not using wireless, why do
> you have a wireless adapter in your system?

It's a laptop (high end developer laptop) with built in bluetooth and
802.11 a/b/g/n wifi.  Why do I have it?  I am using it.  Sometimes when
I don't have hard wired.  It's build-in so removing it is non-trivial
and sort of senseless if you think about it.

> Is this some kind of mobile device, like a noteboot/netbook? Doesn't
> it have some kind of "rfkill" button???

It does but it only controls the bluetooth for some reason.  My previous
laptop, it controlled both but not this one for some reason.  It's my
understanding that the switch is a soft switch, in any case, which does
not physically or electrically disable the device itself and depends on
the OS and drivers to do the right thing.  So it may be a driver issue
at that.  But should it be in the kernel drivers or handled by NM?  I
don't see the Wifi antenna symbol light up until NM is active.

Regardless, it should be possible to configure NM to do what I want, not
arbitrarily always what it thinks it should in spite of what I've set it
to.  That's been my perpetual complaint about NM.  I concur with the
idea that things should just work out of the box, but then it should
obey what I want it to do, if I don't want it to do what it's doing.
It's a vast improvement over the bad old days where almost nothing was
properly configurable and I'm glad to see that this, at least, has been
already addressed in a newer release and that I'm not the only one with
this annoyance.  That's progress.

Mike

> 2010/3/15 Michael H. Warfield 
> Hey all,
> 
> Pop question.  This is one of my burning annoyances with
> NetworkManager
> and maybe there's an easy way to do this and I just can't find
> it.
> But...  How do I disable wireless networking by default.  I
> can disable
> it but, the next time I log in, it's enabled again.  I want it
> stone
> cold dead unless I overtly and explicitly choose to enabled it
> and then
> I want it off if I log out and log back in again.
> 
> The problem is that I work in an environment that is very rich
> in IPv6
> support, at home and at work and on the road and at my
> colocation
> facility.  I have v6 everywhere.  The problem is that NM
> brings up wlan0
> long after eth0 has been up and then the wlan0 interface gets
> hit with a
> new RA (router advertisement) which then causes all the v6
> traffic to be
> routed out through the wireless WHICH I DO NOT WANT even
> though the v4
> default route is out eth0.  Because wlan0 gets the RA later
> than the
> eth0 address in response to its RD (router discovery) request,
> it has a
> later expiration time on the routes so it gets preference over
> the eth0
> interface.  This is by design.  It's the way v6 is suppose to
> work and
> is how you renumber autoconfed v6 networks.  But is screws me
> over
> royally when I'm in a situation where I've got a hard wired
> network
> connection and the wireless is less than stable and keeps
> screwing up
> all my v6 connections.  Disabling it after logging in is
> useless because
> it has already brought it up and loaded the v6 routes with a
> new default
> and that then just breaks things.
> 
> I want wireless off and to STAY OFF unless I want it on and
> know that I
> want it on.  But I can't find a sticky setting that basically
> tells it
> to play dead and STAY DEAD.  (The wireless "switch" on my
> laptop only
> switches the bluetooth, unfortunately).
> 
> Mike
> --
> Michael H. Warfield (AI4NB) | (770) 985-6132 |
>  m...@wittsend.com
>   /\/\|=mhw=|\/\/  | (678) 463-0932 |
>  http://www.wittsend.com/mhw/
>   NIC whois: MHW9  | An optimist believes we live in
> the best of all
>  PGP Key: 0x674627FF| possible worlds.  A pessimist is
> sure of it!
> 
> ___
> 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

-- 
Michael H. Warfield (AI4NB) | (770) 985-6132 |  m...@wittsend.com
   /\/\|=mhw=|\/\/  | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9  | An optimist believes w

Re: Disabling wireless networking.

[José Queiroz]

Sorry for the naive answer, but, if you're not using wireless, why do you
have a wireless adapter in your system?

Is this some kind of mobile device, like a noteboot/netbook? Doesn't it have
some kind of "rfkill" button???

2010/3/15 Michael H. Warfield 

> Hey all,
>
> Pop question.  This is one of my burning annoyances with NetworkManager
> and maybe there's an easy way to do this and I just can't find it.
> But...  How do I disable wireless networking by default.  I can disable
> it but, the next time I log in, it's enabled again.  I want it stone
> cold dead unless I overtly and explicitly choose to enabled it and then
> I want it off if I log out and log back in again.
>
> The problem is that I work in an environment that is very rich in IPv6
> support, at home and at work and on the road and at my colocation
> facility.  I have v6 everywhere.  The problem is that NM brings up wlan0
> long after eth0 has been up and then the wlan0 interface gets hit with a
> new RA (router advertisement) which then causes all the v6 traffic to be
> routed out through the wireless WHICH I DO NOT WANT even though the v4
> default route is out eth0.  Because wlan0 gets the RA later than the
> eth0 address in response to its RD (router discovery) request, it has a
> later expiration time on the routes so it gets preference over the eth0
> interface.  This is by design.  It's the way v6 is suppose to work and
> is how you renumber autoconfed v6 networks.  But is screws me over
> royally when I'm in a situation where I've got a hard wired network
> connection and the wireless is less than stable and keeps screwing up
> all my v6 connections.  Disabling it after logging in is useless because
> it has already brought it up and loaded the v6 routes with a new default
> and that then just breaks things.
>
> I want wireless off and to STAY OFF unless I want it on and know that I
> want it on.  But I can't find a sticky setting that basically tells it
> to play dead and STAY DEAD.  (The wireless "switch" on my laptop only
> switches the bluetooth, unfortunately).
>
> Mike
> --
> Michael H. Warfield (AI4NB) | (770) 985-6132 |  m...@wittsend.com
>   /\/\|=mhw=|\/\/  | (678) 463-0932 |
> http://www.wittsend.com/mhw/
>   NIC whois: MHW9  | An optimist believes we live in the best of
> all
>  PGP Key: 0x674627FF| possible worlds.  A pessimist is sure of it!
>
> ___
> 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

Re: Disabling wireless networking.

[Eugene Crosser]

Dan Williams wrote:

>>> Second is that NM 0.8.x has IPv6 support, and if you're running that
>>> version you can set your wifi connection's IPv6 method to "ignore", and
>>> NM will not start IPv6 on that interface.
...
>> I *am* getting RA IPv6 address.
...
> For backwards compatibility reasons, NM won't suppress the kernel's
> automatic IPv6 ability if it's been enabled via /proc by your
> distribution's init scripts.  What we probably should do is add a
> "disabled" method that will actually turn stuff off.

I was not complaining :) Just wanted to point out the 'ignore' does not mean
that you will have IPv6 disabled on the interface.

> I'll have to check out your original problem again and make sure that
> what we expect to happen does happen.

That was probably some problem in keyfile plugin which is unable to edit
system-wide ipv6 settings, but I did not investigate further yet.

>> About the original question: isn't there any way to specify metric on the 
>> routes
>> that would make the kernel always "prefer" the Ethernet interface?
> 
> It should do that already; the priority order that controls how NM
> assigns the default route is (unless you've checked "Only use this
> connection for resources on its network" in the Routes dialog of the
> connection editor):
> 
> 1. Ethernet
> 2. Wifi
> 3. 3G/Bluetooth

This may be the solution for the guy who asked the original question (if NM does
all of the above right for IPv6).

> But you can also set a metric on routes you add yourself through the
> "Routes" dialog in the connection editor.

As was pointed out, apparently the kernel ignores metric value nowdays.

Eugene



signature.asc
Description: OpenPGP digital signature
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Disabling wireless networking.

[Dan Williams]

On Tue, 2010-03-16 at 10:04 +0300, Eugene Crosser wrote:
> Dan Williams wrote:
> 
> > Second is that NM 0.8.x has IPv6 support, and if you're running that
> > version you can set your wifi connection's IPv6 method to "ignore", and
> > NM will not start IPv6 on that interface.
> 
> network-manager:
>   Installed: 0.8~a~git.20091013t193206.679d548-0ubuntu1
> 
> IPv6 set to "ignore" in the connection editor.
> The router is running radvd.
> 
> I *am* getting RA IPv6 address. As far as I understand, this is done by the
> kernel without the help of networkmanager or any other userspace. Actually, it
> works quite well *unless* I try to configure anything IPv6 related in the
> connection editor, as I have posted earlier ("Additional IPv6 address").

For backwards compatibility reasons, NM won't suppress the kernel's
automatic IPv6 ability if it's been enabled via /proc by your
distribution's init scripts.  What we probably should do is add a
"disabled" method that will actually turn stuff off.

Ignore means NM won't touch IPv6 on the interface, just like NM 0.7
didn't.

I'll have to check out your original problem again and make sure that
what we expect to happen does happen.

> About the original question: isn't there any way to specify metric on the 
> routes
> that would make the kernel always "prefer" the Ethernet interface?

It should do that already; the priority order that controls how NM
assigns the default route is (unless you've checked "Only use this
connection for resources on its network" in the Routes dialog of the
connection editor):

1. Ethernet
2. Wifi
3. 3G/Bluetooth

But you can also set a metric on routes you add yourself through the
"Routes" dialog in the connection editor.

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Disabling wireless networking.

[Michael H. Warfield]

On Tue, 2010-03-16 at 10:04 +0300, Eugene Crosser wrote: 
> Dan Williams wrote:

> > Second is that NM 0.8.x has IPv6 support, and if you're running that
> > version you can set your wifi connection's IPv6 method to "ignore", and
> > NM will not start IPv6 on that interface.

> network-manager:
>   Installed: 0.8~a~git.20091013t193206.679d548-0ubuntu1

> IPv6 set to "ignore" in the connection editor.
> The router is running radvd.

> I *am* getting RA IPv6 address. As far as I understand, this is done by the
> kernel without the help of networkmanager or any other userspace. Actually, it
> works quite well *unless* I try to configure anything IPv6 related in the
> connection editor, as I have posted earlier ("Additional IPv6 address").

That is correct.  You can not simply "ignore" RA's.  If you have IPv6
forwarding disabled in the kernel, you have a whole pile of settings
in /proc/sys/net/ipv6/conf/{interface} you have to switch and have
correct in order to disable that.  There are like 5 accept_ra_* settings
for accepting various things from the router advertisement and you've
got some stuff with router_probe and router_solicitation that have to be
set right.  If you have IPv6 forwarding enabled both autoconf and RA/RD
are automatically disabled (but ND is enabled any time IPv6 is enabled).

> About the original question: isn't there any way to specify metric on the 
> routes
> that would make the kernel always "prefer" the Ethernet interface?

IIRC...  The "metric" settings are ignored by modern Linux kernels.  At
least that's what's claimed by the ifconfig man page.  The man page on
"route" indicates it's used by router daemons.  As far as the kernel
preferences go, it says Metric is "The ’distance’ to the target (usually
counted in hops). It is not used by recent kernels, but may be needed by
routing daemons."  I know the value is there when you do an "ip -6 route
ls".  The man page on the "ip" command is terrible to begin with and
really says nothing about metric other than that it's a number.

> Eugene

Regards,
Mike
-- 
Michael H. Warfield (AI4NB) | (770) 985-6132 |  m...@wittsend.com
   /\/\|=mhw=|\/\/  | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9  | An optimist believes we live in the best of all
 PGP Key: 0x674627FF| possible worlds.  A pessimist is sure of it!


signature.asc
Description: This is a digitally signed message part
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Disabling wireless networking.

[Eugene Crosser]

Dan Williams wrote:

> Second is that NM 0.8.x has IPv6 support, and if you're running that
> version you can set your wifi connection's IPv6 method to "ignore", and
> NM will not start IPv6 on that interface.

network-manager:
  Installed: 0.8~a~git.20091013t193206.679d548-0ubuntu1

IPv6 set to "ignore" in the connection editor.
The router is running radvd.

I *am* getting RA IPv6 address. As far as I understand, this is done by the
kernel without the help of networkmanager or any other userspace. Actually, it
works quite well *unless* I try to configure anything IPv6 related in the
connection editor, as I have posted earlier ("Additional IPv6 address").

About the original question: isn't there any way to specify metric on the routes
that would make the kernel always "prefer" the Ethernet interface?

Eugene



signature.asc
Description: OpenPGP digital signature
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Disabling wireless networking.

[Dan Williams]

On Mon, 2010-03-15 at 19:03 -0400, Michael H. Warfield wrote:
> On Mon, 2010-03-15 at 15:59 -0700, Dan Williams wrote: 
> > On Mon, 2010-03-15 at 16:39 -0400, Michael H. Warfield wrote:
> > > Hey all,
> > > 
> > > Pop question.  This is one of my burning annoyances with NetworkManager
> > > and maybe there's an easy way to do this and I just can't find it.
> > > But...  How do I disable wireless networking by default.  I can disable
> > > it but, the next time I log in, it's enabled again.  I want it stone
> > > cold dead unless I overtly and explicitly choose to enabled it and then
> > > I want it off if I log out and log back in again.
> 
> > There are two solutions to your problem; first is that NM 0.8.0 and NM
> > 0.7.3 (not yet released) will save the wifi state and restore it when
> > you restart.
> 
> > Second is that NM 0.8.x has IPv6 support, and if you're running that
> > version you can set your wifi connection's IPv6 method to "ignore", and
> > NM will not start IPv6 on that interface.
> 
> Ooo...  Very interesting.  Shame that NM is so far behind the curve on
> IPv6 support that this is only just now coming out.  I've been on v6 for
> just about a decade and it's been mandatory for me for years (and I'm
> even in the US where we've been the slowest).  I will definitely be
> checking that out.

Certainly let the list know if something doesn't quite work like you
expect it with IPv6.  There's support for both straight autoconf, and
autoconf + DHCPv6 (triggered by the RA's content) and plain DHCPv6.

Dan

> > Dan
> 
> Regards,
> Mike
> 
> > > The problem is that I work in an environment that is very rich in IPv6
> > > support, at home and at work and on the road and at my colocation
> > > facility.  I have v6 everywhere.  The problem is that NM brings up wlan0
> > > long after eth0 has been up and then the wlan0 interface gets hit with a
> > > new RA (router advertisement) which then causes all the v6 traffic to be
> > > routed out through the wireless WHICH I DO NOT WANT even though the v4
> > > default route is out eth0.  Because wlan0 gets the RA later than the
> > > eth0 address in response to its RD (router discovery) request, it has a
> > > later expiration time on the routes so it gets preference over the eth0
> > > interface.  This is by design.  It's the way v6 is suppose to work and
> > > is how you renumber autoconfed v6 networks.  But is screws me over
> > > royally when I'm in a situation where I've got a hard wired network
> > > connection and the wireless is less than stable and keeps screwing up
> > > all my v6 connections.  Disabling it after logging in is useless because
> > > it has already brought it up and loaded the v6 routes with a new default
> > > and that then just breaks things.
> > > 
> > > I want wireless off and to STAY OFF unless I want it on and know that I
> > > want it on.  But I can't find a sticky setting that basically tells it
> > > to play dead and STAY DEAD.  (The wireless "switch" on my laptop only
> > > switches the bluetooth, unfortunately).
> > > 
> > > Mike
> > > ___
> > > 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

Re: Disabling wireless networking.

[Michael H. Warfield]

On Mon, 2010-03-15 at 15:59 -0700, Dan Williams wrote: 
> On Mon, 2010-03-15 at 16:39 -0400, Michael H. Warfield wrote:
> > Hey all,
> > 
> > Pop question.  This is one of my burning annoyances with NetworkManager
> > and maybe there's an easy way to do this and I just can't find it.
> > But...  How do I disable wireless networking by default.  I can disable
> > it but, the next time I log in, it's enabled again.  I want it stone
> > cold dead unless I overtly and explicitly choose to enabled it and then
> > I want it off if I log out and log back in again.

> There are two solutions to your problem; first is that NM 0.8.0 and NM
> 0.7.3 (not yet released) will save the wifi state and restore it when
> you restart.

> Second is that NM 0.8.x has IPv6 support, and if you're running that
> version you can set your wifi connection's IPv6 method to "ignore", and
> NM will not start IPv6 on that interface.

Ooo...  Very interesting.  Shame that NM is so far behind the curve on
IPv6 support that this is only just now coming out.  I've been on v6 for
just about a decade and it's been mandatory for me for years (and I'm
even in the US where we've been the slowest).  I will definitely be
checking that out.

> Dan

Regards,
Mike

> > The problem is that I work in an environment that is very rich in IPv6
> > support, at home and at work and on the road and at my colocation
> > facility.  I have v6 everywhere.  The problem is that NM brings up wlan0
> > long after eth0 has been up and then the wlan0 interface gets hit with a
> > new RA (router advertisement) which then causes all the v6 traffic to be
> > routed out through the wireless WHICH I DO NOT WANT even though the v4
> > default route is out eth0.  Because wlan0 gets the RA later than the
> > eth0 address in response to its RD (router discovery) request, it has a
> > later expiration time on the routes so it gets preference over the eth0
> > interface.  This is by design.  It's the way v6 is suppose to work and
> > is how you renumber autoconfed v6 networks.  But is screws me over
> > royally when I'm in a situation where I've got a hard wired network
> > connection and the wireless is less than stable and keeps screwing up
> > all my v6 connections.  Disabling it after logging in is useless because
> > it has already brought it up and loaded the v6 routes with a new default
> > and that then just breaks things.
> > 
> > I want wireless off and to STAY OFF unless I want it on and know that I
> > want it on.  But I can't find a sticky setting that basically tells it
> > to play dead and STAY DEAD.  (The wireless "switch" on my laptop only
> > switches the bluetooth, unfortunately).
> > 
> > Mike
> > ___
> > NetworkManager-list mailing list
> > NetworkManager-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> 
> 

-- 
Michael H. Warfield (AI4NB) | (770) 985-6132 |  m...@wittsend.com
   /\/\|=mhw=|\/\/  | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9  | An optimist believes we live in the best of all
 PGP Key: 0x674627FF| possible worlds.  A pessimist is sure of it!


signature.asc
Description: This is a digitally signed message part
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Disabling wireless networking.

[Michael H. Warfield]

On Mon, 2010-03-15 at 17:32 -0400, John Mahoney wrote:
> It has already been fixed, but most distos have not picked up the
> change yet.  Read this thread for a better understanding and a
> workaround which sends a dbus command to nm during init.
> 
> 
> http://old.nabble.com/nm-applet-to25936866.html#a25936866
> 
PERFECT!

I don't even want it to remember my last setting.  I want it OFF when it
comes up.  I stuffed that dbus trick into my profile so we shall see.
Seems to work, but I'm already logged in.

> Hopefully,  It will be standard soon.
> 
Concur.

> --
> John

Many thanks!

Regards,
Mike

> On Mon, Mar 15, 2010 at 4:39 PM, Michael H. Warfield
>  wrote:
> Hey all,
> 
> Pop question.  This is one of my burning annoyances with
> NetworkManager
> and maybe there's an easy way to do this and I just can't find
> it.
> But...  How do I disable wireless networking by default.  I
> can disable
> it but, the next time I log in, it's enabled again.  I want it
> stone
> cold dead unless I overtly and explicitly choose to enabled it
> and then
> I want it off if I log out and log back in again.
> 
> The problem is that I work in an environment that is very rich
> in IPv6
> support, at home and at work and on the road and at my
> colocation
> facility.  I have v6 everywhere.  The problem is that NM
> brings up wlan0
> long after eth0 has been up and then the wlan0 interface gets
> hit with a
> new RA (router advertisement) which then causes all the v6
> traffic to be
> routed out through the wireless WHICH I DO NOT WANT even
> though the v4
> default route is out eth0.  Because wlan0 gets the RA later
> than the
> eth0 address in response to its RD (router discovery) request,
> it has a
> later expiration time on the routes so it gets preference over
> the eth0
> interface.  This is by design.  It's the way v6 is suppose to
> work and
> is how you renumber autoconfed v6 networks.  But is screws me
> over
> royally when I'm in a situation where I've got a hard wired
> network
> connection and the wireless is less than stable and keeps
> screwing up
> all my v6 connections.  Disabling it after logging in is
> useless because
> it has already brought it up and loaded the v6 routes with a
> new default
> and that then just breaks things.
> 
> I want wireless off and to STAY OFF unless I want it on and
> know that I
> want it on.  But I can't find a sticky setting that basically
> tells it
> to play dead and STAY DEAD.  (The wireless "switch" on my
> laptop only
> switches the bluetooth, unfortunately).
> 
> Mike
> --
> Michael H. Warfield (AI4NB) | (770) 985-6132 |
>  m...@wittsend.com
>   /\/\|=mhw=|\/\/  | (678) 463-0932 |
>  http://www.wittsend.com/mhw/
>   NIC whois: MHW9  | An optimist believes we live in
> the best of all
>  PGP Key: 0x674627FF| possible worlds.  A pessimist is
> sure of it!
> 
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
> 
> 
> 

-- 
Michael H. Warfield (AI4NB) | (770) 985-6132 |  m...@wittsend.com
   /\/\|=mhw=|\/\/  | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9  | An optimist believes we live in the best of all
 PGP Key: 0x674627FF| possible worlds.  A pessimist is sure of it!


signature.asc
Description: This is a digitally signed message part
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Disabling wireless networking.

[Dan Williams]

On Mon, 2010-03-15 at 16:39 -0400, Michael H. Warfield wrote:
> Hey all,
> 
> Pop question.  This is one of my burning annoyances with NetworkManager
> and maybe there's an easy way to do this and I just can't find it.
> But...  How do I disable wireless networking by default.  I can disable
> it but, the next time I log in, it's enabled again.  I want it stone
> cold dead unless I overtly and explicitly choose to enabled it and then
> I want it off if I log out and log back in again.

There are two solutions to your problem; first is that NM 0.8.0 and NM
0.7.3 (not yet released) will save the wifi state and restore it when
you restart.

Second is that NM 0.8.x has IPv6 support, and if you're running that
version you can set your wifi connection's IPv6 method to "ignore", and
NM will not start IPv6 on that interface.

Dan

> The problem is that I work in an environment that is very rich in IPv6
> support, at home and at work and on the road and at my colocation
> facility.  I have v6 everywhere.  The problem is that NM brings up wlan0
> long after eth0 has been up and then the wlan0 interface gets hit with a
> new RA (router advertisement) which then causes all the v6 traffic to be
> routed out through the wireless WHICH I DO NOT WANT even though the v4
> default route is out eth0.  Because wlan0 gets the RA later than the
> eth0 address in response to its RD (router discovery) request, it has a
> later expiration time on the routes so it gets preference over the eth0
> interface.  This is by design.  It's the way v6 is suppose to work and
> is how you renumber autoconfed v6 networks.  But is screws me over
> royally when I'm in a situation where I've got a hard wired network
> connection and the wireless is less than stable and keeps screwing up
> all my v6 connections.  Disabling it after logging in is useless because
> it has already brought it up and loaded the v6 routes with a new default
> and that then just breaks things.
> 
> I want wireless off and to STAY OFF unless I want it on and know that I
> want it on.  But I can't find a sticky setting that basically tells it
> to play dead and STAY DEAD.  (The wireless "switch" on my laptop only
> switches the bluetooth, unfortunately).
> 
> Mike
> ___
> 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

Re: Disabling wireless networking.

[John Mahoney]

It has already been fixed, but most distos have not picked up the change
yet.  Read this thread for a better understanding and a workaround which
sends a dbus command to nm during init.

http://old.nabble.com/nm-applet-to25936866.html#a25936866

Hopefully,  It
will be standard soon.

--
John

On Mon, Mar 15, 2010 at 4:39 PM, Michael H. Warfield wrote:

> Hey all,
>
> Pop question.  This is one of my burning annoyances with NetworkManager
> and maybe there's an easy way to do this and I just can't find it.
> But...  How do I disable wireless networking by default.  I can disable
> it but, the next time I log in, it's enabled again.  I want it stone
> cold dead unless I overtly and explicitly choose to enabled it and then
> I want it off if I log out and log back in again.
>
> The problem is that I work in an environment that is very rich in IPv6
> support, at home and at work and on the road and at my colocation
> facility.  I have v6 everywhere.  The problem is that NM brings up wlan0
> long after eth0 has been up and then the wlan0 interface gets hit with a
> new RA (router advertisement) which then causes all the v6 traffic to be
> routed out through the wireless WHICH I DO NOT WANT even though the v4
> default route is out eth0.  Because wlan0 gets the RA later than the
> eth0 address in response to its RD (router discovery) request, it has a
> later expiration time on the routes so it gets preference over the eth0
> interface.  This is by design.  It's the way v6 is suppose to work and
> is how you renumber autoconfed v6 networks.  But is screws me over
> royally when I'm in a situation where I've got a hard wired network
> connection and the wireless is less than stable and keeps screwing up
> all my v6 connections.  Disabling it after logging in is useless because
> it has already brought it up and loaded the v6 routes with a new default
> and that then just breaks things.
>
> I want wireless off and to STAY OFF unless I want it on and know that I
> want it on.  But I can't find a sticky setting that basically tells it
> to play dead and STAY DEAD.  (The wireless "switch" on my laptop only
> switches the bluetooth, unfortunately).
>
> Mike
> --
> Michael H. Warfield (AI4NB) | (770) 985-6132 |  m...@wittsend.com
>   /\/\|=mhw=|\/\/  | (678) 463-0932 |
> http://www.wittsend.com/mhw/
>   NIC whois: MHW9  | An optimist believes we live in the best of
> all
>  PGP Key: 0x674627FF| possible worlds.  A pessimist is sure of it!
>
> ___
> 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