FC5 and Wireless Configuration

I did a Fedora Core 5 install on a notebook, then plugged in a Cisco
Aironet PC card. The card is recognized, but I can't keep my essid and
key in the machine after a reboot. I set the essid and key via iwconfig
and the "Network" GUI located under System|Administration.

I see that my essid is stored in
/etc/sysconfig/network-scripts/ifcfg-eth1 and my key is in
/etc/sysconfig/networking/devices/ifcfg-eth1. Both values are correct,
however, when the machine comes up, the card default of essid "tsunami"
and "keyff" are set...

How do I keep my essid and key persistent? Thanks!

(E-Mail Removed) writes:

>I did a Fedora Core 5 install on a notebook, then plugged in a Cisco
>Aironet PC card. The card is recognized, but I can't keep my essid and
>key in the machine after a reboot. I set the essid and key via iwconfig
>and the "Network" GUI located under System|Administration.

/etc/sysconfig/network-scripts/ifcfg-eth1
Assuming your wireless is eth1
Put in ESSID=whatever
KEY=whatever


>I see that my essid is stored in
>/etc/sysconfig/network-scripts/ifcfg-eth1 and my key is in
>/etc/sysconfig/networking/devices/ifcfg-eth1. Both values are correct,
>however, when the machine comes up, the card default of essid "tsunami"
>and "keyff" are set...

If those are the ESSID in the above network scripts then change them.
Make sure that your system actually uses eth1



>How do I keep my essid and key persistent? Thanks!

(E-Mail Removed) wrote:
> I did a Fedora Core 5 install on a notebook, then plugged in a Cisco
> Aironet PC card. The card is recognized, but I can't keep my essid and
> key in the machine after a reboot. I set the essid and key via iwconfig
> and the "Network" GUI located under System|Administration.
>
> I see that my essid is stored in
> /etc/sysconfig/network-scripts/ifcfg-eth1 and my key is in
> /etc/sysconfig/networking/devices/ifcfg-eth1. Both values are correct,
> however, when the machine comes up, the card default of essid "tsunami"
> and "keyff" are set...

They have problems assigning names to network devices, so that your
wireless adapter may end up assigned anything else then eth1.
http://article.gmane.org/gmane.linux...100.devel/7521

You might like to try using NetworkManager for configuring your
wireless adapter which works quite well and does not suffer from the
problem. The only problem is that it's a GUI tool.

> >I did a Fedora Core 5 install on a notebook, then plugged in a Cisco
> >Aironet PC card. The card is recognized, but I can't keep my essid and
> >key in the machine after a reboot. I set the essid and key via iwconfig
> >and the "Network" GUI located under System|Administration.
>
> /etc/sysconfig/network-scripts/ifcfg-eth1
> Assuming your wireless is eth1
> Put in ESSID=whatever
> KEY=whatever
>
>
> >I see that my essid is stored in
> >/etc/sysconfig/network-scripts/ifcfg-eth1 and my key is in
> >/etc/sysconfig/networking/devices/ifcfg-eth1. Both values are correct,
> >however, when the machine comes up, the card default of essid "tsunami"
> >and "keyff" are set...
>
> If those are the ESSID in the above network scripts then change them.

Change them to what?

> Make sure that your system actually uses eth1

When I look at "iwconfig", I get wireless stuff for "eth1" and "wifi0".
I think wifi0 is bridged to eth1 since I can up and down my wireless
interface on another notebook using eth1.

>
> >How do I keep my essid and key persistent? Thanks!

> > I did a Fedora Core 5 install on a notebook, then plugged in a Cisco
> > Aironet PC card. The card is recognized, but I can't keep my essid and
> > key in the machine after a reboot. I set the essid and key via iwconfig
> > and the "Network" GUI located under System|Administration.
> >
> > I see that my essid is stored in
> > /etc/sysconfig/network-scripts/ifcfg-eth1 and my key is in
> > /etc/sysconfig/networking/devices/ifcfg-eth1. Both values are correct,
> > however, when the machine comes up, the card default of essid "tsunami"
> > and "keyff" are set...
>
> They have problems assigning names to network devices, so that your
> wireless adapter may end up assigned anything else then eth1.
> http://article.gmane.org/gmane.linux...100.devel/7521
>
> You might like to try using NetworkManager for configuring your
> wireless adapter which works quite well and does not suffer from the
> problem. The only problem is that it's a GUI tool.

I tried NetworkManager and it worked once, but I can't connect to
wireless after a reboot even when I plug in the essid and key to
NetworkManager. I can't even get the command line stuff to work when
using iwconfig. When I issue: "iwconfig eth1 essid essidvalue key
keyvalue;dhclient eth1", I get no connection. This worked like a charm
before...

Any idea how I can get rid of the files/settings NetworkManager created
so I can get iwconfig/dhclient to work?

I have a different notebook that I upgraded from FC4 to FC5, uses a
different wireless chip, and it works like a charm. Even with the essid
in /etc/sysconfig/network-scripts/ifcfg-eth1 and the key in
/etc/sysconfig/networking/devices/ifcfg-eth1...

(E-Mail Removed) wrote:

[]

> Any idea how I can get rid of the files/settings NetworkManager created
> so I can get iwconfig/dhclient to work?

Just stop NetworkManager and NetworkManagerDispatcher daemons.

Hi,

I observed a strange behavior with the minisocks in the linux-2.6.16 kernel.

Here is the scenario:

- The server creates a socket, bind, listen and wait indefinitly.

- The client creates a socket, does a bind, connects to the server,
sends data and closes the connection. It waits 61 seconds and does the
same again (with same bind address).

Since this moment, any client trying to connect to the server (eg.
telnet) receives the SYN|ACK from the server but the ACK is lost by the
server and the connection stays in the SYN_RECV state in the server side.

It seems that there are two sockets in the req queue which are
<SS_FREE,TCP_CLOSE_WAIT> and <SS_FREE,TCP_CLOSE> with the same tuple
(src_addr, src_port, dst_addr, dst_port)

What is the expected behavior for a minisock if several connections are
coming from the same source (ip,addr), should they be enqueued, dropped,
refused ? What about the backlog in this case ?

Thanks in advance.

--Daniel

> I did a Fedora Core 5 install on a notebook, then plugged in a Cisco
> Aironet PC card. The card is recognized, but I can't keep my essid and
> key in the machine after a reboot. I set the essid and key via iwconfig
> and the "Network" GUI located under System|Administration.
>
> I see that my essid is stored in
> /etc/sysconfig/network-scripts/ifcfg-eth1 and my key is in
> /etc/sysconfig/networking/devices/ifcfg-eth1. Both values are correct,
> however, when the machine comes up, the card default of essid "tsunami"
> and "keyff" are set...
>
> How do I keep my essid and key persistent? Thanks!

Note typo above: /etc/sysconfig/networking/devices/ifcfg-eth1 should
have been /etc/sysconfig/networking/devices/keys-eth1. I was
referencing the wrong "keys-eth1" file...

I finally got it... I overlooked the file
/etc/sysconfig/network-scripts/keys-eth1. With FC4 and previous the key
was stored in /etc/sysconfig/network-scripts/ifcfg-eth1 (change "eth1"
to whatever the actual interface is). FC5 now appears to put the key in
/etc/sysconfig/network-scripts/keys-eth1 with rw------- permissions.
FC5 will also work with the key in
/etc/sysconfig/network-scripts/ifcfg-eth1, but I like the way it was
changed to use /etc/sysconfig/network-scripts/keys-eth1.

By the by, for some reason my system got dorked and my interface would
not light up after I had /etc/sysconfig/network-scripts/ifcfg-eth1 and
/etc/sysconfig/network-scripts/keys-eth1 in place. Frustration led to a
system rebuild and all is well now.