On Sun, 24 Dec 2017 13:09:55 -0800
Samuel Sieb wrote:
> Providing the exact message would be helpful in identifying where it's
> coming from.
This is the sort of stuff that showed up on the console
and in dmesg:
IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
but, rfkill did indeed make i
On 12/24/2017 09:53 AM, Tom Horsley wrote:
I'm not using the wi-fi in my Intel NUC, and about once
a minute or so a log message appears saying "Hey! Your
wi-fi interface isn't configured" (not that exact
language, mind you :-).
Any way to convince fedora to ignore this interface
rather than honk
Once upon a time, Sam Varshavchik said:
> I defy anyone to identify a tangible benefit that comes from
> removing a static IP address from a port when it loses carrier, and
> installing one only once a carrier is present.
It is useful for systems with multiple interfaces, for example a desktop
wi
Roberto Ragusa writes:
On 12/21/2017 06:28 PM, Gordon Messmer wrote:
> Because NetworkManager is an event-driven system. If an interface loses
carrier for a defined period of time (5 seconds prior to the commit I've
referenced), NM will remove the IP configuration from that interface.
An
On Mon, 25 Dec 2017 02:43:29 +0800
Ed Greshko wrote:
> What desktop are you using? KDE has a checkbox to turn off wifi. Then
> and/or how
> about using the rfkill command to turn off the interface?
I forgot about rfkill, that could work. Thanks.
I'm not using any "normal" desktop, I'm got a
On 12/25/17 01:53, Tom Horsley wrote:
> I'm not using the wi-fi in my Intel NUC, and about once
> a minute or so a log message appears saying "Hey! Your
> wi-fi interface isn't configured" (not that exact
> language, mind you :-).
>
> Any way to convince fedora to ignore this interface
> rather tha
I'm not using the wi-fi in my Intel NUC, and about once
a minute or so a log message appears saying "Hey! Your
wi-fi interface isn't configured" (not that exact
language, mind you :-).
Any way to convince fedora to ignore this interface
rather than honking about it every minute?
__
On 12/21/2017 06:28 PM, Gordon Messmer wrote:
> Because NetworkManager is an event-driven system. If an interface loses
> carrier for a defined period of time (5 seconds prior to the commit I've
> referenced), NM will remove the IP configuration from that interface.
And this is one of the most
