I posted to newbie. Maybe it belongs here. I got an Airlink wireless router, and configuring it isn't transparent. Something about my server Linus doesn't like it. At first I thought it was dependent on the configuration of the router, but my other machines could do name resolution and the server couldn't.
I've gone back to my Coyote/Shorewall firewall mostly because the laptop I was trying to tie in wirelessly needs to go back to the shop (yet again) for a bad CD drive. That's another woe between me and CompUSA/Toshiba. Is there anything that might have been left behind (not in the superstitious sense) in an upgrade from RH9 to FC3? That's the only difference on the server that I can think of, other than its being a SCSI box, which have zero to do with networking. This from my previous post. As I said above, I now believe my diagnosis below is in error, but the symptoms may help. Subject: Help with Airlink router To: Kplug Newbie <[email protected]> The manual is six 4" x 3.5" pages on how to M$. It reads like a 70s Japanese camera manual. There are some tech writers in Asia who are definitely pumping their resumes. Under routing, I have static and dynamic. Under dynamic, I have three choices, NAT (on/off), receive (Dis, RIP1, RIP2) and transmit (Dis, RIP1, RIP2). Without NAT on I can't resolve IP addresses. Selecting NT takes "transmit" to "disabled" and blocks outgoing email. I figure the secret sauce is to select NAT and then add a static outgoing route to my mail server at Cox. Am I on the right track? -- Lan Barnes [EMAIL PROTECTED] Linux Guy, SCM Specialist 858-354-0616 -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
