1:39 p.m.
Hello,
Updated from F17 to F19 with a fresh install, and have hit a few
problems. The main one is that my wireless interface does not come up
(it is an Atheros AR9170 device).
I configured it in F17 without NetworkManager by modifying
the /etc/wpa_supplicant/wpa_supplicant.conf
and /etc/sysconfig/network-scripts/ifcfg-wlan0 (with NM_CONTROLLED=no)
and /etc/sysconfig/wpa_supplicant files. This worked fine, no problems
at all.
With F19, after making the same changes, the wlan0 interface appears but
is not assigned an IP address. It seems that wpa_supplicant works okay,
as does the general startup of the network (the loopback interface
appears okay), but running dhclient to get an IP address either does not
happen or fails. 'ps auxww' does not show dhclient as running. I can
find no errors in the log files.
If I run 'ifdown wlan0 && ifup wlan0' then the interface comes up with
an IP address (and this is recorded in the log file and ps shows
dhclient as now running).
Anyone any ideas why dhclient might not be running? I'll keep working on
this (obviously), but have already spent most of the day on it and got
nowhere.
Thanks,
John.
--
John Horne, Plymouth University, UK
Tel: +44 (0)1752 587287 Fax: +44 (0)1752 587001
3:46 p.m.
hello john,
On 08/26/2013 01:39 PM, John Horne wrote:
Hello,
Updated from F17 to F19 with a fresh install, and have hit a few
problems. The main one is that my wireless interface does not come up
(it is an Atheros AR9170 device).
i do not recall exactly when something similar was 'threaded', but it
was a problem of timing as to just what starts when.
awairc, solution was to start wlan last to give time for networking
time to finish configuring.
sound reasonable?
hth.
--
peace out.
in a world with out fences, who needs gates.
sl6.3 linux
tc.hago.
g
.
2:18 a.m.
On 08/26/2013 05:14 PM, John Horne wrote:
On Mon, 2013-08-26 at 15:46 -0500, g wrote:
> hello john,
>
> On 08/26/2013 01:39 PM, John Horne wrote:
>> Hello,
>>
>> Updated from F17 to F19 with a fresh install, and have hit a few
>> problems. The main one is that my wireless interface does not come up
>> (it is an Atheros AR9170 device).
>
> i do not recall exactly when something similar was 'threaded', but it
> was a problem of timing as to just what starts when.
>
> awairc, solution was to start wlan last to give time for networking
> time to finish configuring.
>
> sound reasonable?
>
Other way round I would say :-)
wpa_supplicant must finish before the network starts, if it doesn't then
the wireless interface won't come up. This was a problem years ago
(Fedora 7 or so?) when the SYSV scripts started networking first, and
then wireless. The fix was, as said, to start wpa_supplicant first.
so you are saying that one has to have wireless networking before any
networking can be?
does that not seem senseless for non wi-fi systems.
--
peace out.
in a world with out fences, who needs gates.
sl6.3 linux
tc.hago.
g
.
8:34 a.m.
On Tue, 2013-08-27 at 15:03 +0200, Mihai T. Lazarescu wrote:
Check also if the MAC and name of the WiFi interface in the user
configuration of NetworkManager matches that of the hardware.
NetworkManager is not being used.
John.
--
John Horne, Plymouth University, UK
Tel: +44 (0)1752 587287 Fax: +44 (0)1752 587001
10:57 a.m.
On Tue, 2013-08-27 at 11:18 -0400, Jared K. Smith wrote:
On Tue, Aug 27, 2013 at 9:03 AM, Mihai T. Lazarescu
<mtlagm(a)gmail.com>
wrote:
Check also if the MAC and name of the WiFi interface in the
user
configuration of NetworkManager matches that of the hardware.
I too would suggest that you double-check that the MAC address -- just
last week I got the same symptoms from a system where the config files
thought that the MAC should be one thing, and the actual MAC address
was different.
The wireless adapter hasn't changed, and the same config files
(wpa_supplicant.conf, ifcfg-wlan0) are being used that worked with F17.
As said, if I run 'ifdown wlan0 && ifup wlan0' then the interface comes
up. That wouldn't happen if the MAC address was wrong.
John.
--
John Horne, Plymouth University, UK
Tel: +44 (0)1752 587287 Fax: +44 (0)1752 587001
10:18 a.m.
On Tue, Aug 27, 2013 at 9:03 AM, Mihai T. Lazarescu <mtlagm(a)gmail.com>wrote:
Check also if the MAC and name of the WiFi interface in the user
configuration of NetworkManager matches that of the hardware.
I too would suggest that you double-check that the MAC address -- just last
week I got the same symptoms from a system where the config files thought
that the MAC should be one thing, and the actual MAC address was different.
-Jared
12:36 p.m.
On 08/27/2013 10:57 AM, John Horne wrote:
<>
The wireless adapter hasn't changed, and the same config files
(wpa_supplicant.conf, ifcfg-wlan0) are being used that worked with F17.
As said, if I run 'ifdown wlan0 && ifup wlan0' then the interface comes
up. That wouldn't happen if the MAC address was wrong.
obviously, wpa_supplicant is not getting started during startup.
as a workaround until you can come up with answer, at end of start up script,
[and there is/was a personal start up script, do not recall name] try
adding;
wpa_supplicant -B -d -f (outputfile) -c/etc/wpa_supplicant.conf -iwlan0
sleep 10 s
ifcfg-wland0
if it works, it will save you trouble of entering it yourself and let you
play until you find time to delve into problem more.
read, reread;
man wpa_supplicant
man sleep
--
peace out.
in a world with out fences, who needs gates.
sl6.3 linux
tc.hago.
g
.
12:11 p.m.
On Tue, 2013-08-27 at 18:16 +0200, Mihai T. Lazarescu wrote:
On Tue, Aug 27, 2013 at 04:57:04PM +0100, John Horne wrote:
> On Tue, 2013-08-27 at 11:18 -0400, Jared K. Smith wrote:
> > On Tue, Aug 27, 2013 at 9:03 AM, Mihai T. Lazarescu <mtlagm(a)gmail.com>
> > wrote:
> > Check also if the MAC and name of the WiFi interface in the
> > user
> > configuration of NetworkManager matches that of the hardware.
> >
> >
> > I too would suggest that you double-check that the MAC address -- just
> > last week I got the same symptoms from a system where the config files
> > thought that the MAC should be one thing, and the actual MAC address
> > was different.
> >
> The wireless adapter hasn't changed, and the same config files
> (wpa_supplicant.conf, ifcfg-wlan0) are being used that worked with F17.
>
> As said, if I run 'ifdown wlan0 && ifup wlan0' then the interface
comes
> up. That wouldn't happen if the MAC address was wrong.
MAC is stored in system filed (/etc/...) and user files
($HOME/...). Check the latter.
Why?
John.
--
John Horne, Plymouth University, UK
Tel: +44 (0)1752 587287 Fax: +44 (0)1752 587001
8:40 a.m.
On 08/28/2013 08:21 AM, John Horne wrote:
On Mon, 2013-08-26 at 19:39 +0100, John Horne wrote:
> Hello,
>
> Updated from F17 to F19 with a fresh install, and have hit a few
> problems. The main one is that my wireless interface does not come up
> (it is an Atheros AR9170 device).
>
Seems the problem is that the SYSV 'network' must be started. I have to
admit that I had assumed this had gone by now. There were very few SYSV
services in F17, and I just didn't check in F19. Once I had set that to
start, then the network comes up after every reboot.
ha. mountains to mole hills. :=)
congrats.
--
peace out.
in a world with out fences, who needs gates.
sl6.3 linux
tc.hago.
g
.
10:19 a.m.
On 28.08.2013 15:21, John Horne wrote:
On Mon, 2013-08-26 at 19:39 +0100, John Horne wrote:
> Hello,
>
> Updated from F17 to F19 with a fresh install, and have hit a few
> problems. The main one is that my wireless interface does not come up
> (it is an Atheros AR9170 device).
>
Seems the problem is that the SYSV 'network' must be started. I have to
admit that I had assumed this had gone by now. There were very few SYSV
services in F17, and I just didn't check in F19. Once I had set that to
start, then the network comes up after every reboot.
We expect you with the same question, on Fedora 40 - Quantum Chicken.
poma
8:21 a.m.
On Mon, 2013-08-26 at 19:39 +0100, John Horne wrote:
Hello,
Updated from F17 to F19 with a fresh install, and have hit a few
problems. The main one is that my wireless interface does not come up
(it is an Atheros AR9170 device).
Seems the problem is that the SYSV 'network' must be started. I have to
admit that I had assumed this had gone by now. There were very few SYSV
services in F17, and I just didn't check in F19. Once I had set that to
start, then the network comes up after every reboot.
John.
--
John Horne, Plymouth University, UK
Tel: +44 (0)1752 587287 Fax: +44 (0)1752 587001
4:56 p.m.
On Tue, Aug 27, 2013 at 06:11:35PM +0100, John Horne wrote:
On Tue, 2013-08-27 at 18:16 +0200, Mihai T. Lazarescu wrote:
> On Tue, Aug 27, 2013 at 04:57:04PM +0100, John Horne wrote:
>
> > On Tue, 2013-08-27 at 11:18 -0400, Jared K. Smith wrote:
> > > On Tue, Aug 27, 2013 at 9:03 AM, Mihai T. Lazarescu
<mtlagm(a)gmail.com>
> > > wrote:
> > > Check also if the MAC and name of the WiFi interface in the
> > > user
> > > configuration of NetworkManager matches that of the hardware.
> > >
> > >
> > > I too would suggest that you double-check that the MAC address -- just
> > > last week I got the same symptoms from a system where the config files
> > > thought that the MAC should be one thing, and the actual MAC address
> > > was different.
> > >
> > The wireless adapter hasn't changed, and the same config files
> > (wpa_supplicant.conf, ifcfg-wlan0) are being used that worked with F17.
> >
> > As said, if I run 'ifdown wlan0 && ifup wlan0' then the
interface comes
> > up. That wouldn't happen if the MAC address was wrong.
>
> MAC is stored in system filed (/etc/...) and user files
> ($HOME/...). Check the latter.
Why?
Because the F19 fresh installation you made aligns the system
files, not user's.
Even if the MAC did not changed, F19 changed interface names:
https://fedoraproject.org/wiki/Features/SystemdPredictableNetworkInterfac...
Since you preserved the user configuration from F17, that is
set for the "old" interface names. Thus, your network manager
is not finding the new ones, unless you manually check for
and fix the mismatches.
Mihai
9:23 a.m.
On Tue, Aug 27, 2013 at 02:34:29PM +0100, John Horne wrote:
On Tue, 2013-08-27 at 15:03 +0200, Mihai T. Lazarescu wrote:
> Check also if the MAC and name of the WiFi interface in the user
> configuration of NetworkManager matches that of the hardware.
>
NetworkManager is not being used.
Regardless, other managers may have similar settings.
Mihai
1:37 p.m.
On 08/27/2013 01:02 PM, John Horne wrote:
On Tue, 2013-08-27 at 12:36 -0500, g wrote:
> obviously, wpa_supplicant is not getting started during startup.
>
Yes it is. The log file, /var/log/wpa_supplicant.log, shows this. If it
wasn't started then 'ifup wlan0' wouldn't work. What isn't happening
during startup - it seems - is dhclient running. And I can find no
mention of that in the log files. It does run though when I use 'ifup'
after startup. Hence running 'ifdown wlan0 && ifup wlan0' works.
I'll
need to see where dhclient gets started and see if I can crank up the
logging/debugging.
ok. my bad.
so instead of adding a script with wpa_supplicant, add script with;
ifdown wlan0
sleep 10 s
ifup wlan0
run;
man dhclient
note the "-p -d -v" options
have you checked 'ifconfig" before and after you manually start wlan0?
--
peace out.
in a world with out fences, who needs gates.
sl6.3 linux
tc.hago.
g
.
1:02 p.m.
On Tue, 2013-08-27 at 12:36 -0500, g wrote:
On 08/27/2013 10:57 AM, John Horne wrote:
<>
> The wireless adapter hasn't changed, and the same config files
> (wpa_supplicant.conf, ifcfg-wlan0) are being used that worked with F17.
>
> As said, if I run 'ifdown wlan0 && ifup wlan0' then the interface
comes
> up. That wouldn't happen if the MAC address was wrong.
obviously, wpa_supplicant is not getting started during startup.
Yes it is. The log file, /var/log/wpa_supplicant.log, shows this. If it
wasn't started then 'ifup wlan0' wouldn't work. What isn't happening
during startup - it seems - is dhclient running. And I can find no
mention of that in the log files. It does run though when I use 'ifup'
after startup. Hence running 'ifdown wlan0 && ifup wlan0' works. I'll
need to see where dhclient gets started and see if I can crank up the
logging/debugging.
John.
--
John Horne, Plymouth University, UK
Tel: +44 (0)1752 587287 Fax: +44 (0)1752 587001
11:16 a.m.
On Tue, Aug 27, 2013 at 04:57:04PM +0100, John Horne wrote:
On Tue, 2013-08-27 at 11:18 -0400, Jared K. Smith wrote:
> On Tue, Aug 27, 2013 at 9:03 AM, Mihai T. Lazarescu <mtlagm(a)gmail.com>
> wrote:
> Check also if the MAC and name of the WiFi interface in the
> user
> configuration of NetworkManager matches that of the hardware.
>
>
> I too would suggest that you double-check that the MAC address -- just
> last week I got the same symptoms from a system where the config files
> thought that the MAC should be one thing, and the actual MAC address
> was different.
>
The wireless adapter hasn't changed, and the same config files
(wpa_supplicant.conf, ifcfg-wlan0) are being used that worked with F17.
As said, if I run 'ifdown wlan0 && ifup wlan0' then the interface comes
up. That wouldn't happen if the MAC address was wrong.
MAC is stored in system filed (/etc/...) and user files
($HOME/...). Check the latter.
Mihai
8:03 a.m.
Check also if the MAC and name of the WiFi interface in the user
configuration of NetworkManager matches that of the hardware.
Mihai
7:22 a.m.
On 08/27/2013 04:32 AM, John Horne wrote:
On Tue, 2013-08-27 at 02:18 -0500, g wrote:
>
> On 08/26/2013 05:14 PM, John Horne wrote:
>> On Mon, 2013-08-26 at 15:46 -0500, g wrote:
>>> hello john,
>>>
>>> On 08/26/2013 01:39 PM, John Horne wrote:
>>>> Hello,
>>>>
>>>> Updated from F17 to F19 with a fresh install, and have hit a few
>>>> problems. The main one is that my wireless interface does not come up
>>>> (it is an Atheros AR9170 device).
>>>
>>> i do not recall exactly when something similar was 'threaded', but
it
>>> was a problem of timing as to just what starts when.
>>>
>>> awairc, solution was to start wlan last to give time for networking
>>> time to finish configuring.
>>>
>>> sound reasonable?
>>>
>> Other way round I would say :-)
>>
>> wpa_supplicant must finish before the network starts, if it doesn't then
>> the wireless interface won't come up. This was a problem years ago
>> (Fedora 7 or so?) when the SYSV scripts started networking first, and
>> then wireless. The fix was, as said, to start wpa_supplicant first.
>
> so you are saying that one has to have wireless networking before any
> networking can be?
>
The association of the wifi network card with the router, yes. After
that networking can then set the interface as up or down. It cannot do
that before the association though (hence wpa_supplicant must run before
the network is started).
Obviously for wired networks, wpa_supplicant isn't going to do anything,
so networking will start up as usual (bringing interfaces up or leaving
them down).
so that _all_ point of confusion are clarified;
1 - networking working
/etc/sysconfig/
network
2 - wpa_supplicant [if using w-fi]
/etc/sysconfig/
wpa_supplicant
3a - wired [if using wired]
/etc/sysconfig/network-scripts/
ifup-eth
3b - wi-fi [if using wi-fi]
/etc/sysconfig/network-scripts/
ifcfg-wlanx
iirc, all 4 is how i go about it. ;=)
--
peace out.
in a world with out fences, who needs gates.
sl6.3 linux
tc.hago.
g
.
4:32 a.m.
On Tue, 2013-08-27 at 02:18 -0500, g wrote:
On 08/26/2013 05:14 PM, John Horne wrote:
> On Mon, 2013-08-26 at 15:46 -0500, g wrote:
>> hello john,
>>
>> On 08/26/2013 01:39 PM, John Horne wrote:
>>> Hello,
>>>
>>> Updated from F17 to F19 with a fresh install, and have hit a few
>>> problems. The main one is that my wireless interface does not come up
>>> (it is an Atheros AR9170 device).
>>
>> i do not recall exactly when something similar was 'threaded', but it
>> was a problem of timing as to just what starts when.
>>
>> awairc, solution was to start wlan last to give time for networking
>> time to finish configuring.
>>
>> sound reasonable?
>>
> Other way round I would say :-)
>
> wpa_supplicant must finish before the network starts, if it doesn't then
> the wireless interface won't come up. This was a problem years ago
> (Fedora 7 or so?) when the SYSV scripts started networking first, and
> then wireless. The fix was, as said, to start wpa_supplicant first.
so you are saying that one has to have wireless networking before any
networking can be?
The association of the wifi network card with the router, yes. After
that networking can then set the interface as up or down. It cannot do
that before the association though (hence wpa_supplicant must run before
the network is started).
Obviously for wired networks, wpa_supplicant isn't going to do anything,
so networking will start up as usual (bringing interfaces up or leaving
them down).
John.
--
John Horne Tel: +44 (0)1752 587287
Plymouth University, UK Fax: +44 (0)1752 587001
5:14 p.m.
On Mon, 2013-08-26 at 15:46 -0500, g wrote:
hello john,
On 08/26/2013 01:39 PM, John Horne wrote:
> Hello,
>
> Updated from F17 to F19 with a fresh install, and have hit a few
> problems. The main one is that my wireless interface does not come up
> (it is an Atheros AR9170 device).
i do not recall exactly when something similar was 'threaded', but it
was a problem of timing as to just what starts when.
awairc, solution was to start wlan last to give time for networking
time to finish configuring.
sound reasonable?
Other way round I would say :-)
wpa_supplicant must finish before the network starts, if it doesn't then
the wireless interface won't come up. This was a problem years ago
(Fedora 7 or so?) when the SYSV scripts started networking first, and
then wireless. The fix was, as said, to start wpa_supplicant first.
However, this all worked fine with F17 (and systemd) and the starting
order was sorted out a long time ago.
John.
--
John Horne, Plymouth University, UK
Tel: +44 (0)1752 587287 Fax: +44 (0)1752 587001
10:51 a.m.
On 8/28/2013 11:19 AM, poma wrote:
On 28.08.2013 15:21, John Horne wrote:
> On Mon, 2013-08-26 at 19:39 +0100, John Horne wrote:
>> Hello,
>>
>> Updated from F17 to F19 with a fresh install, and have hit a few
>> problems. The main one is that my wireless interface does not come up
>> (it is an Atheros AR9170 device).
>>
> Seems the problem is that the SYSV 'network' must be started. I have to
> admit that I had assumed this had gone by now. There were very few SYSV
> services in F17, and I just didn't check in F19. Once I had set that to
> start, then the network comes up after every reboot.
>
We expect you with the same question, on Fedora 40 - Quantum Chicken.
poma
Love the name. :-)
--
David
3901
days inactive
3903
days old
20 comments
6 participants
participants (6)
-
David -
g -
Jared K. Smith -
John Horne -
Mihai T. Lazarescu -
poma