I'm in Frederick, MD, currently also work in Germantown (and beyond). How's Richmond treating you? Is it as crowded as No.Va.? I tell ya, this area is getting so freakin' crowded I dream about moving to Montana whilst I'm sitting in backups on 270/495.

It's empty down here. I feel like I'm in the middle of nowhere. Once you're used to NoVa, I'm assuming most places feel that way, though.

I have quite a few friends in Fredrick. Seems like 90% of my old team at DOE lived there.

Assuming you've seen my previous posts: no change

I am so confused.

If you get lonely, you can join me and my 10,000,000 friends on 270 tomorrow, say 8'ish? It'll be fun, we'll inhale CO and see colors...

I gotta tell ya, almost all of my posts here have been in the wireless area and this is the weirdest issue I've yet encountered with a wireless card, and this includes the emails from my howto's as well.

So far, all we know is that it responds to broadcast pings, but nothing else, so what is it about those packets that's different from normal packets? *as we grasp at straws here* does ifconfig show both tx and rx packets/bytes? is there a discrepancy between the two? Maybe it's time to try something else, how about an ssh -C to this box from another box? I know it sounds weird, but ssh has gone where other things have not for me before.

One last thought occurs to me (before I do the semi-controlled passing out that I pathetically refer to as sleeping) this *is* the only interface in the machine that's "up", right? I'll check this tomorrow, you'll probably have figured it all out by then.

Dude, I did Sterling -> Germantown for 2 years. No more 495 or 270 for me for a little while atleast.

Here is some interesting stuff:

*START TCPDUMP SESSION*
*ATTEMPT TO SSH*
01:34:20.655273 arp who-has 192.168.1.103 tell 192.168.1.101
01:34:21.655265 arp who-has 192.168.1.103 tell 192.168.1.101
01:34:22.655265 arp who-has 192.168.1.103 tell 192.168.1.101
01:34:23.655273 arp who-has 192.168.1.103 tell 192.168.1.101
01:34:23.658306 arp reply 192.168.1.103 is-at 0:9:5b:74:6e:fe
01:34:23.659076 arp reply 192.168.1.103 is-at 0:9:5b:74:6e:fe
01:35:03.655294 192.168.1.101.35761 > 192.168.1.103.ssh: S 456584736:456584736(0) win 5840 <mss 1460,sackOK,timestamp 859467 0,nop,wscale 0> (DF)
*AFTER SSH TIMES OUT I TRY A PING*
01:37:25.434697 192.168.1.101 > 192.168.1.103: icmp: echo request (DF)
01:37:26.445305 192.168.1.101 > 192.168.1.103: icmp: echo request (DF)
01:37:27.445316 192.168.1.101 > 192.168.1.103: icmp: echo request (DF)
01:37:28.446358 192.168.1.101 > 192.168.1.103: icmp: echo request (DF)
01:37:29.466592 192.168.1.101 > 192.168.1.103: icmp: echo request (DF)
*END TCPDUMP*


It responded to an ARP! That ALMOST makes me happy... Except, it doens't really solve anything....

And, yes. It's the only one. I went as far as disabling my on-board NIC in BIOS to make sure. I had those same thoughts too.

Have fun on 270 tomorrow!

In the mean time... Anyone else out there have any ideas?

WOOHOO!

Just so everyone knows, and for people looking through this topic in the future:

I finally got it working.


The ONLY thing I can figure is that I needed 2.4.22 for some obscure reason. I tried Slackware 9.1 today. Although it didn't fully autodetect, a few insmods, a few modprobes, a few iwconfig commands and a few ifconfig commands, and I was up with no problems.

Actually, I've been up for *check up time* more than 5 hours without a single problem with my connection!

I am now guru on MA311 problems after these last two weeks, so feel free to find me if you need me for that.

Excellent work, I *knew* you would do it.

Uptime now more than a day, and not a single problem. Rock on!

akaBeaVis: Thanks for the vote of confidence.


I think I kinda like it around here. I think I'll start hanging out and answering questions (like I have been doing while waiting to figure this out). You guys are a good bunch.