if you fixed the hard coded IP addresses and it helped, you should have a different default gateway and be able to ping it by IP address. Where in that list I posted previously do you get stuck now?

hint:
Can't ping default gateway/router is usually a network problem. These would be either a setup with a bad IP for you or the gateway or subtle physical layer problems, which for wireless I guess that would be bad signal quality. It's possible that some driver call or something is missing between the two versions and that warning you see explains why this part doesn't work?

Can't ping DNS servers: if you can ping the gateway then these are just set up wrong, either by you in your config or by the ISP or whoever set up the DHCP server.

Can't ping an Internet IP (that number above is LQ's webserver.) If everything to here is working then it's likely a routing or access restriction (firewall?) issue somewhere upstream from your system (meaning with the network you are connected to.)

Darin,

The hard-coded IP addresses were in the ifcfg-eth0 file. So when I fixed that file, it only really fixed what was going on with the ethernet controller (that whole thing was just a mistake on my part). I don't think anything I did to the ifcfg-eth0 file changes any of the issues I'm having with wireless card, however. Thus, I get stuck at the same part in the list (can't ping the gateway).

I think that, if this isn't a routing issue, then it might be some intricacy between the wireless driver and the Linux networking layer. Perhaps these "Wireless Extensions" come in to play here? I'm not sure since I don't have that intimate a knowlege of how these things work together (honestly, I thought the wireless driver essentially made the wirelss card behave just like any other ethernet card in Linux).

What still gets me is that my wireless card works just fine at home. Both the T-Mobile Hotspots and my home network are setup with DHCP, so the only part I should have to change in the ifcfg-ath0 file is the network ID (which I have done).

I am running into the exact same problem on my DELL CPi laptop with Xircom cardbus 10/100 card. This is a new installation of Fedora Core 1. The laptop will get an IP and than it won't ping the gateway or anything elso but itself. I installed it twice and tried different Xircom card, tried static IP. All with the same results..

All led on the Xircom card indicates it's connected to the network and there is also traffic when I try to ping. It look like it got assigned an IP by the DHCP and then disconnected. I checked on my router with DHCP and it's showing any record that the IP was assigned to the linux laptop.

Is it possible that my Netgear WGR614v5 router does not like linux?

This is a separate problem and as such, should get its own thread.

Welp, here's the latest:

I'm writing this on my laptop while connected to my school's wireless network. Thus, my wirless configuration:

1. Works on my home wireless network (802.11g; DHCP)
2. Works on my school's wireless network (802.11b; DHCP)
3. Does *not* work on T-Mobile Hotspots (802.11b; DHCP)

This pretty much narrows it down to an issue at Hotspots. I'm wondering if it's just something that T-Mobile changed on their end?

I was just about to get ready to call T-Mobile to see if they changed anything on their end (since I narrowed the problem down to just T-Mobile). Before I called, I decided to try out the laptop at a Starbucks just one more time to see exactly what it did/didn't do (for the support rep) and, wouldn't ya know, it worked with no problems.

No idea...

Great. Now please tell us what you have changed to make it work (wireless at school etc)! I have similar routing problems from one fc3 machine to a netgear router, another fc3 machine just works.

Thanks!

loony