Folks, let me try and explain this as best I can. THis will take some additional testing on my part, but either there's a really serious issue here or all the events ironically happen at the same time. My configuration is like this. I have my dsl modem on the wan port of the Extreme, my Linux box on the lan port, and I have three Macs, an Intel IMac, G5 IMac, and a G4 Mac Mini which are all wireless. I turned my Linux box on lastnight and noticed I couldn't ping the Macs on the network and I couldn't get out of my network at all. I checked my Intel Mac since I was sitting at it and noticed I had no signal, but even more odd was a message on the screen that stated something along the lines of a kernel panic and it wanted to send the info to Apple. Well I ende up just turning off the machine with no real means to make the problem go away, but upon reboot, the AirPort was no longer being detected by any of the other machines on the network. I finally reset the AirPort and had to set everything back up. I can't imagine what the hell went wrong and will perform more testing to determine if the Linux box which is a pc had anything to do with this. Now here's a few more bits of info.

My Macs are all dhcp, but I configured the Extreme to give one static ip to the Linux box because I wanted to forward some ports to it for Speakfreely. Maybe that isn't a good idea and maybe I don't need to forward those ports so as a side note, maybe someone can let me know if this is even necessary. I also use an AirPort Express to extend the range into the basement, but doubt this would really impact the situation. I for the grins of it called Apple to see if they've heard anything along these lines and I got some stuff from a tech who might have known his stuff to some degree, but surely his explanation that there was some sort of feedback that hosed the code on the Intel Mac sounds a little hard to believe. I guess the ip stack could get trashed and perhaps cause some really wild stuff, but if what I have explained turns out to be true, Apple has a really ugly bug on their hands, but how a pc or any hardwired box cause this is beyond me. Now I did use the default 10.0.1.X range so gave the Linux box 10.0.1.201 ip. One other little bit of info that I didn't think of until now and may or may not have anything to do with this situation is my ISP uses the 10.0.1.X ip I believe for its dsl service. I think its more that we generally get a 68.X address, but the 10.X is reserved for how the modem comes up to talk to the pppoe server, but don't quote me on this, I need to research this a bit more.
Any thoughts appreciated and yeah, this all sounds completely crazy.

Scott




Reply via email to