LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (https://www.linuxquestions.org/questions/fedora-35/)
-   -   Fedora 10 - Wireless issue with RaLink RT2500 and DHCP (https://www.linuxquestions.org/questions/fedora-35/fedora-10-wireless-issue-with-ralink-rt2500-and-dhcp-711374/)

silviap 03-13-2009 11:05 AM
Fedora 10 - Wireless issue with RaLink RT2500 and DHCP
 
Hello,

I have a desktop computer (IBM) and my system administrator added in a wireless network card from MSI; after this I installed Fedora 10. The problem is Fedora recognizes all the hardware [ when I issue a command like lspci I get "Network Controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev-01)". ], but, at first when I tried to use Network Manager I saw my wireless AP but I got disconnected after a few seconds of trying to get an IP address, after this I saw the wireless card received a different IP address than the one my router gave.

Can you help me?
Thank you!

PTrenholme 03-13-2009 02:00 PM
  1. You should address your questions to your system administrator.
  2. The wireless connection is (obviously) connecting to a wireless router. So, why would you expect the IP address range used by that router to be the same as the range used by the wired router? If they were the same, than your network would, almost certainly, not work.

silviap 03-14-2009 10:51 AM
Quote:
Originally Posted by PTrenholme (Post 3474602)
  1. You should address your questions to your system administrator.
  2. The wireless connection is (obviously) connecting to a wireless router. So, why would you expect the IP address range used by that router to be the same as the range used by the wired router? If they were the same, than your network would, almost certainly, not work.
Hello again,

1. My system administrator has a specific requirement to use only wireless in our office (he does not know that much about troubleshooting linux & networking...)

2. We only have one wireless router, I did not mention any other type of router in my post.

So, to make my self a little more clear: at the beginning the system administrator gave me a machine with Windows installed, the network card was working ok. Of course, I wanted to switch to Fedora 10; now my wireless connection is not working as expected (I have tested before two other machines with Fedora 9 and CentOS 5 and I had no issues with the wireless connections).
Regarding the IP address: I checked my router's DHCP client list and I instantly see my MAC in there with a class C IP address, but on my machine I either get a class A IP address or a "network disconnected" error and no IP.

Any other suggestions?
Thank you for your help!

PTrenholme 03-14-2009 02:56 PM
Fedora 10 should have installed the NetworkManager package for you. If you're using the GNOME desktop, check the task bar in the upper right to see if you have a "network" icon displayed. If you do, click on it and select the access point to which you want to connect and let the NetworkManager package do the work. (Use a left-click to set the connection options.)

Note that this assume that your hardware (wireless card) is detected and has a driver loaded for it, but from your description it seems that you have that part working.

Oh, also go to system-config-network and make sure the "Let NetworkManager control this device" check box is checked. (Or, if you really want to do it "by hand" as your comments imply, make sure the box is not checked. It is usually checked by default.)

I suspect that your problem is that the option to use the NetworkManager has been checked, and you're trying to configure the connection the "old fashioned" way (iwconfig, ifup, etc.) which is, basically, incompatible with NM.

silviap 03-16-2009 03:28 AM
Quote:
Originally Posted by PTrenholme (Post 3475556)
Fedora 10 should have installed the NetworkManager package for you. If you're using the GNOME desktop, check the task bar in the upper right to see if you have a "network" icon displayed. If you do, click on it and select the access point to which you want to connect and let the NetworkManager package do the work. (Use a left-click to set the connection options.)

Note that this assume that your hardware (wireless card) is detected and has a driver loaded for it, but from your description it seems that you have that part working.

Oh, also go to system-config-network and make sure the "Let NetworkManager control this device" check box is checked. (Or, if you really want to do it "by hand" as your comments imply, make sure the box is not checked. It is usually checked by default.)

I suspect that your problem is that the option to use the NetworkManager has been checked, and you're trying to configure the connection the "old fashioned" way (iwconfig, ifup, etc.) which is, basically, incompatible with NM.
Hello,

I can't see my wireless card when I type in system-network-config and now I can't see it in lspci either.

PTrenholme 03-16-2009 09:15 AM
If it's not in lspci, it wasn't detected when the kernel scanned the PCI bus. Is it still working in your Windows distribution? If so, try a reboot. In any case, check that the modem card is properly seated and locked inside your computer.

A hardware problem is, I believe, one that your system guy should be able to address since it doesn't have anything to do with the software being used. (The modem card could even be yanked and tried in another box to confirm that it works properly - or not, as the case may be.)

silviap 03-17-2009 04:12 AM
Quote:
Originally Posted by PTrenholme (Post 3477067)
If it's not in lspci, it wasn't detected when the kernel scanned the PCI bus. Is it still working in your Windows distribution? If so, try a reboot. In any case, check that the modem card is properly seated and locked inside your computer.

A hardware problem is, I believe, one that your system guy should be able to address since it doesn't have anything to do with the software being used. (The modem card could even be yanked and tried in another box to confirm that it works properly - or not, as the case may be.)
It works ok under windows, I tested it on another computer. I saw it with lspci the other days, after a reboot it's "gone". I guess the issue comes from Fedora...

PTrenholme 03-17-2009 07:57 AM
Try dmesg | grep -i wifi to list any boot-time messages related to your wifi connection.

If that's not informative, try the command dmesg | less to display almost all the messages generated during the boot. This is a fairly long output, and most of it is of little interest to anyone but a kernel developer, but you may find a clue somewhere in there. (The less command is just a "page-at-a-time" output display formatter. See man less for a description of the various keys you can use - basically <space> for the next page, <up arrow>, <down arrow>, "h" for help, and "q" to quit.)


All times are GMT -5. The time now is 12:05 PM.