7:16 p.m.
IIRC, Fedora - and other distributions -
tried to bring up the interface <xyz>
if there was a file /etc/sysconfig/network-scripts/ifcfg-<xyz>.
But this no longer seems to be the case -
I have an ifcfg-eth0 which is completely ignored
by "service network restart" and even "ifup eth0".
How does Fedora now decide what interfaces to try to bring up?
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
7:42 a.m.
On 02/01/2008, Timothy Murphy <tim(a)birdsnest.maths.tcd.ie> wrote:
I just want a good WiFi program.
You might have a look at wicd:
http://wicd.sourceforge.net/
4:02 a.m.
Mr.Scrooge wrote:
> > Thanks for the response.
> > But I always have NM off, as it does not work with all my devices,
> > and I ran "service network restart" anyway without finding eth0.
> >
shouldn't a wireless interface come up as wlan0,ath0 not eth0? or does it
depend on the driver? iwconfig should show you something, me thinks.
I think the interface does depend on the driver, as you suggest.
I was using orinoco_cs , and this brings up the interface eth?.
Also iwconfig would not show anything if eth0 did not come up.
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
2:30 p.m.
On 01/01/2008, Timothy Murphy <tim(a)birdsnest.maths.tcd.ie> wrote:
My claim is: when the laptop booted (without NM)
it did not try to bring eth0 up,
even though there was a file /etc/sysconfig/network-scripts/ifcfg-eth0 .
Perhaps you forgot to turn on the "network" service - in F8 it is off
by default because NM is on by default. You need to turn NM off and
chkconfig network on.
8:06 a.m.
On Tue, 2008-01-01 at 14:01 +0100, Timothy Murphy wrote:
My claim is: when the laptop booted (without NM)
it did not try to bring eth0 up,
even though there was a
file /etc/sysconfig/network-scripts/ifcfg-eth0 .
There mere presence of that file doesn't mean it will be brought up, you
also have to have the configuration set to bring it up at boot up.
Do you?
--
(This computer runs FC7, my others run FC4, FC5 & FC6, in case that's
important to the thread.)
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
4:06 p.m.
On Dec 31, 2007 4:24 AM, Timothy Murphy <tim(a)birdsnest.maths.tcd.ie> wrote:
Tod Merley wrote:
---------------------------------->8
>> How does Fedora now decide what interfaces to try to bring
up?
> I believe they are using an automated environment overseen by
> NetworkManager.
>
> To play in a bit more static environment (from gnome desktop):
>
------------------------------------>8
Actually, I'm almost certain I wasn't running NetworkManager
(NM)
on the computer in question.
Hi Timothy Murphy!
Easy to find out:
------------------------
[tod@localhost ~]$ ps aux | grep Net ; ps aux | grep nm
root 2139 0.0 0.3 14680 1668 ? Ssl 12:39 0:00
NetworkManager --pid-file=/var/run/NetworkManager/NetworkManager.pid
tod 3412 0.0 0.1 4008 716 pts/0 S+ 13:54 0:00 grep Net
tod 2520 0.1 5.0 58744 25804 ? S 12:40 0:06
nm-applet --sm-disable
tod 3414 0.0 0.1 4008 716 pts/0 S+ 13:54 0:00 grep nm
--------------------------
Have Fun!
Tod
7:01 a.m.
Tod Merley wrote:
> Actually, I'm almost certain I wasn't running
NetworkManager (NM)
> on the computer in question.
Hi Timothy Murphy!
Easy to find out:
I don't actually have access to the laptop I was talking about
at this moment.
However, if I did I would have no difficulty telling if NM was running,
or turning it off if it was.
My claim is: when the laptop booted (without NM)
it did not try to bring eth0 up,
even though there was a file /etc/sysconfig/network-scripts/ifcfg-eth0 .
As I said, I am only 99% sure of the setup at the time.
But I'd be interested to know if anyone else has had this experience
(with Fedora-8).
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
6:38 a.m.
Jonathan Underwood wrote:
> My claim is: when the laptop booted (without NM)
> it did not try to bring eth0 up,
> even though there was a file /etc/sysconfig/network-scripts/ifcfg-eth0 .
>
Perhaps you forgot to turn on the "network" service - in F8 it is off
by default because NM is on by default. You need to turn NM off and
chkconfig network on.
Thanks for the response.
But I always have NM off, as it does not work with all my devices,
and I ran "service network restart" anyway without finding eth0.
I had brief access to the laptop last night.
It did bring up eth0 this time,
but it did not find the access point.
I am fairly baffled by WiFi -
I often find that device 1 will connect to access point A
but not to access point B
while device 2 does the opposite,
although they have identical settings (except for MAC address).
What I'd really like is some tool that would tell me
what is happening at the lowest level,
explicitly listing the packets that are exchanged.
In the present case, for example, the light on the access point
flashes when I run "service network restart",
so there is clearly some exchange of packets.
But /var/log/messages on the laptop simply reports
that no link was established.
(I don't have that laptop with me, so cannot give the exact message.)
I've never seen a good WiFi trouble-shooter.
Most writers seem to assume that what works for them
is bound to work for everyone else in the world.
In my view, the Linux "wireless tools" were very good when they came out,
but there does not seem to have been any attempt to improve them
over the years.
The system-config-network variants are almost useless, in my experience,
while NetworkManager just tries to do too much, in my opinion.
I have never had any problems with ethernet or bluetooth,
so don't feel the need for a program that tries to deal with them
as well as WiFi.
I just want a good WiFi program.
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
8:16 p.m.
--- Jonathan Underwood <jonathan.underwood(a)gmail.com> wrote:
On 02/01/2008, Timothy Murphy <tim(a)birdsnest.maths.tcd.ie>
wrote:
> Thanks for the response.
> But I always have NM off, as it does not work with all my devices,
> and I ran "service network restart" anyway without finding eth0.
>
shouldn't a wireless interface come up as wlan0,ath0 not eth0? or does it
depend on the driver?
iwconfig should show you something, me thinks.
> I had brief access to the laptop last night.
> It did bring up eth0 this time,
> but it did not find the access point.
>
[...]
To help you further I think we'll need more information about the
access point )eg. what encryption scheme is being used, if any), the
wireless card type etc.
other things you can try for information include /sbin/iwlist scan and
/sbin/iwlconfig.
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
8:13 p.m.
On 03/01/2008, Jonathan Underwood <jonathan.underwood(a)gmail.com> wrote:
To help you further I think we'll need more information about
the
access point )eg. what encryption scheme is being used, if any), the
wireless card type etc.
other things you can try for information include /sbin/iwlist scan and
/sbin/iwlconfig.
Sorry, that was a bit brief. Things to report back:
1) What wireless card are you using, and with which kernel?
2) What is the output of /sbin/iwlist scan?
3) What encryption is being used by the AP?
4) If you were to enable NM (and disable/shutdown the network service)
what is the output of nm-tool?
8:11 p.m.
On 02/01/2008, Timothy Murphy <tim(a)birdsnest.maths.tcd.ie> wrote:
Thanks for the response.
But I always have NM off, as it does not work with all my devices,
and I ran "service network restart" anyway without finding eth0.
I had brief access to the laptop last night.
It did bring up eth0 this time,
but it did not find the access point.
[...]
To help you further I think we'll need more information about the
access point )eg. what encryption scheme is being used, if any), the
wireless card type etc.
other things you can try for information include /sbin/iwlist scan and
/sbin/iwlconfig.
1:51 p.m.
Tim wrote:
On Tue, 2008-01-01 at 14:01 +0100, Timothy Murphy wrote:
> My claim is: when the laptop booted (without NM)
> it did not try to bring eth0 up,
> even though there was a
> file /etc/sysconfig/network-scripts/ifcfg-eth0 .
There mere presence of that file doesn't mean it will be brought up, you
also have to have the configuration set to bring it up at boot up.
Do you?
ifcfg-eth0 did say "ONBOOT=yes".
I always set this.
I may have access to the laptop again soon.
I'll see exactly what the settings are.
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
1:33 p.m.
Rick Stevens wrote:
> >> IIRC, Fedora - and other distributions -
> >> tried to bring up the interface <xyz>
> >> if there was a file /etc/sysconfig/network-scripts/ifcfg-<xyz>.
> >>
> >> But this no longer seems to be the case -
> >> I have an ifcfg-eth0 which is completely ignored
> >> by "service network restart" and even "ifup eth0".
> >>
> >> How does Fedora now decide what interfaces to try to bring up?
"service network start|restart" depends on having an
"ONBOOT=yes" line
in the ifcfg-eth0 file. If you can type in "ifup eth0" and the card
comes up, then you probably have "ONBOOT=no" or no line in the file.
I'm pretty sure I tried "ifup eth0" in this case,
and it didn't work.
One of the many annoying things about WiFi
is the way several programs modify ifcfg-<xyz>.
I don't mind programs like system-config-<whatever> doing this,
after all you are asking for it in such a case,
but I'd really prefer if anyone wants to alter my /etc/files
if they would ask me first, or at least tell me what they have done ...
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
10:58 a.m.
On Mon, 2007-12-31 at 13:24 +0100, Timothy Murphy wrote:
Tod Merley wrote:
>> IIRC, Fedora - and other distributions -
>> tried to bring up the interface <xyz>
>> if there was a file /etc/sysconfig/network-scripts/ifcfg-<xyz>.
>>
>> But this no longer seems to be the case -
>> I have an ifcfg-eth0 which is completely ignored
>> by "service network restart" and even "ifup eth0".
>>
>> How does Fedora now decide what interfaces to try to bring up?
> I believe they are using an automated environment overseen by
> NetworkManager.
>
> To play in a bit more static environment (from gnome desktop):
>
> System > Administration > Services
> Un-check NetworkManager
> Checki Network (about 2/3 down the list)
> Save!
> Reboot or restart service.
Actually, I'm almost certain I wasn't running NetworkManager (NM)
on the computer in question.
I don't normally run NM, because it does not work
with all the WiFi cards I use -
in particular it does not work with my Orinoco PCMCIA cards,
which I am reluctant to throw away as they have very good antennae -
and I like to run as near as possible the same system
on all my machines.
I've also found that "alias eth0 xyz" in /etc/modprobe.conf
also seems to be often ignored.
"service network start|restart" depends on having an "ONBOOT=yes"
line
in the ifcfg-eth0 file. If you can type in "ifup eth0" and the card
comes up, then you probably have "ONBOOT=no" or no line in the file.
----------------------------------------------------------------------
- Rick Stevens, Principal Engineer rstevens(a)internap.com -
- CDN Systems, Internap, Inc. http://www.internap.com -
- -
- Diplomacy: The art of saying "Nice doggy!" until you can find a -
- big enough rock. -
----------------------------------------------------------------------
6:24 a.m.
Tod Merley wrote:
> IIRC, Fedora - and other distributions -
> tried to bring up the interface <xyz>
> if there was a file /etc/sysconfig/network-scripts/ifcfg-<xyz>.
>
> But this no longer seems to be the case -
> I have an ifcfg-eth0 which is completely ignored
> by "service network restart" and even "ifup eth0".
>
> How does Fedora now decide what interfaces to try to bring up?
I believe they are using an automated environment overseen by
NetworkManager.
To play in a bit more static environment (from gnome desktop):
System > Administration > Services
Un-check NetworkManager
Checki Network (about 2/3 down the list)
Save!
Reboot or restart service.
Actually, I'm almost certain I wasn't running NetworkManager (NM)
on the computer in question.
I don't normally run NM, because it does not work
with all the WiFi cards I use -
in particular it does not work with my Orinoco PCMCIA cards,
which I am reluctant to throw away as they have very good antennae -
and I like to run as near as possible the same system
on all my machines.
I've also found that "alias eth0 xyz" in /etc/modprobe.conf
also seems to be often ignored.
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
9:44 p.m.
On Dec 30, 2007 5:16 PM, Timothy Murphy <tim(a)birdsnest.maths.tcd.ie> wrote:
IIRC, Fedora - and other distributions -
tried to bring up the interface <xyz>
if there was a file /etc/sysconfig/network-scripts/ifcfg-<xyz>.
But this no longer seems to be the case -
I have an ifcfg-eth0 which is completely ignored
by "service network restart" and even "ifup eth0".
How does Fedora now decide what interfaces to try to bring up?
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Hi Timothy Murphy!
I believe they are using an automated environment overseen by NetworkManager.
To play in a bit more static environment (from gnome desktop):
System > Administration > Services
Un-check NetworkManager
Checki Network (about 2/3 down the list)
Save!
Reboot or restart service.
Enjoy!
Tod
5972
days inactive
5975
days old
15 comments
6 participants
participants (6)
-
Jonathan Underwood -
Max -
Rick Stevens -
Tim -
Timothy Murphy -
Tod Merley