network configuration

Rick Stevens rstevens at vitalstream.com
Fri Mar 4 17:21:43 UTC 2005


Ryan Olthof wrote:
> To clarify my configuration, my wireless connection is from my ISP. 
> It just does not seem to use DHCP to obtain my IP, DNS etc.
> automatically.  I have tried the NetworkManager as well with no luck. 
> My network adaptor is an Intel 82801DB Pro/EV(CNR) as reported by FC3.
>  There seems to be some downstream traffic over the connection, but
> upstream is either very slow, or not working (after 1/2 hour I had
> 4kb)

What does "iwconfig -a" report?  Do you have the proper ESSID and WEP
key set?  Channel?  Mode (ad-hoc, managed)?

Oh, and bottom-post from now on, please?

> On Thu, 03 Mar 2005 23:02:28 -0500, Scot L. Harris <webid at cfl.rr.com> wrote:
> 
>>On Thu, 2005-03-03 at 20:00, Ryan Olthof wrote:
>>
>>>I just installed Fedora Core 3 on my system but can't get my fixed
>>>wireless connection configured properly using DHCP.  If I manually set
>>>up the connection, I can activate my network adaptor, but get no
>>>connectivity.  I have a smartbridge powershot for PoE, and an Intel
>>>network adaptor.  The connection itself works fine using winxp, but
>>>DHCP does not work with it either.  I read the FAQ and also tried
>>>using the internet configuration wizard, nothing works.  Any ideas?
>>>
>>>Thanks
>>>Ryan
>>
>>I had similar problems getting wireless working on my Tecra M2 laptop.
>>When I tried the normal methods of configuring the wireless interface it
>>would start up, I could scan and see the available access points but it
>>would never establish a connection.  I tried it using DHCP as well as
>>hard coding the IP address.
>>
>>I finally tried using the NetworkManager program and amazingly it made
>>the wireless connection work.
>>
>>However I am tracking down a problem at the moment that is looking more
>>and more like NetworkManager is the most like suspect.  VPN connections
>>seem to be partially broken when trying to use the wired connection.  It
>>works over wireless.
>>
>>There also appears to be a possible bug where modprobe uses 100% cpu
>>when you switch from interface to interface a couple of times using
>>NetworkManager.
>>
>>I suspect I am going to have to revisit getting the wireless working
>>with out NetworkManager.
>>
>>--
>>Scot L. Harris
>>webid at cfl.rr.com
>>
>>nohup rm -fr /&
>>
>>--
>>fedora-list mailing list
>>fedora-list at redhat.com
>>To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
>>
> 
> 


-- 
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens at vitalstream.com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-  Memory is the second thing to go, but I can't remember the first! -
----------------------------------------------------------------------




More information about the users mailing list