Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have tried multiple kernels, several distros (hoping for auto-detect goodness) and both the orinoco/hermes drivers as well as he wlan-ng drivers.
Every single time, I end up with the same situation (regardless of distro, kernel, drivers, etc)
My card is able to get a DHCP lease, however once I get an IP I cannot communicate with anything, nor can anything else communicate with it.
An iwconfig or similar shows signal strength.
Everything works fine, I just merely have NO TCP/IP connectivity. It THINKS everything is okay, but I get no responses...
If I use another system and send a broadcast ping out, the machine will respond. A direct ping does nothing, however. How weird is THAT?
I can provide however much additional information if you need. I am by no means a newbie: I consider myself well-versed. But I have no idea what to try anymore, and was hoping someone around here might know...
While I have a few different chipsets working under various distros here, I won't get my hands on an orinoco for a few weeks yet. (a netgear ma401 is on it's way), If I remember right doesn't this driver use a proprietary setup program, ie: not iwconfig? I'm almost positive I've seen Finegan tell someone this, maybe it's buried deep in the source directory in an out of the way readme? Maybe I'm wrong on this one, does the device respond to iwconfig's? is there a rather lengthy list of iwpriv's available (weird ones that might indicate a proprietary setup prog)?
Once again, I've gotten it to the point where I can dhclient/dhcpcd my interface, and I get an IP. My card sees the MAC of my AP and everything, so I know it's communicating. My AP DHCP client list shows my machine.
Like I said, everything works, except for TCP/IP traffic itself after getting my lease!
[edit: The problem acts and responds exactly like it would if you had your netmask, broadcast and gw set incorrectly... Except I don't. [It's DHCP anyways] Just thought an analogy may help explain how things are behaving...)
if it only was able to *initiate* a connection, we'd think it was some security issue, but the weirdness is it only *responds* to those packets, now *that's* unusual, one last thought, can you try to ad-hoc it to one of those nicely functional other cards?
I live in MD yes, but I *loathe* aim, (makes me think I'm my 19 year old daughter or something, heh), if we go to aim, all the the google.com/linux'ers out there will be deprived of the solution that I'm sure you will eventually come up with (I have faith...)
one other thing, a long shot: may be a buffer issue(happens to me on 2 other cards, both acx100), try fiddling with mtu on the interface, ratcheting down to 576, maybe an explanation for the icmp packets but nothing else. (rh 9 comes with that firewall, it's not lit up right?)