Thank you for all the suggestions. Not that I solved this problem on the 
command line, but it really is great to find out where the configuration 
files are, what they do and how to manually edit them.

Here is what I did and the results I got, using the gui network 
configuration tool provided by Redhat.

1. unconfigured both the built in broadcom nic and the linksys wireless nic.
2. physically removed the wireless nic
3. rebooted the computer.
4. configured the broadcom as ETH0, setting it to use DHCP, setting it 
not to activate upon boot and setting it so that any user can activate 
or deactivate it as needed.
5. Inserted the wireless card, with the computer logged in, configured 
the wireless card using the provided Orinoco PrismII driver, setting it 
to use DHCP, setting it not to activate upn boot and allowing any user 
to activate or deactivate it.
6. Connected a cable, activiated the broadcom and had connectivity.
7. deactivated the broadcom.
8. Activated the wireless (the encryption problems were my poor typing) 
and had connectivity.
9. removed the wireless card and rebooted.
10. activated the broadcon, had connectivity.
11. rebooted, this time with the wireless card inserted.
12. Oddly had immediate connectivity. THe gui network config tool showed 
the wireless card as inactive, but ifconfig showed it as active and it 
was infact active.
13. removed the wireless card and activated the broad com, which then 
gave connectivity.

I can't think of any other tests to run or scenarios to try out except 
having both the wireless card and the broadcom active at the same time, 
but I don't need that. I might try it later, but as for now I'm using 
the box in production and can't afford the time to mess with it right now.

Charlie