On Mon, Apr 04, 2005 at 11:45:34AM -0700, Gus Wirth wrote: > > Have you tried using direct IP address? For example, can you ping a known > machine on the outside? If not, the problem is deeper than just DNS and may > indicate a routing problem in Linus. >
Always something I try. IIRC that worked, name resolution didn'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. > > Yea Coyote! Boo Toshiba! Yea cheap, not-so-bad Toshiba. It damned thing worked perfectly at the tech desk, so I took it home and threw FC3 on it w/o a hitch. I _hate_ when that happens. > > >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. > > The firewall may have been changed. One thing I did on my box was to make > eth0 a trusted interface so it would pass everything. Have you tried > totally disabling the firewall on Linus to make sure it's not blocking > anything? > In fact, I never enable any firewall rules internally, preferring to depend on my firewall defending me from the outside. lokkit and other RH stuff set off. hosts.[allow|deny] blank. > > > >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? > > I don't think you need to add a route to the firewall. Just set up NAT and > leave it. When you send mail it should resolve for the machines inside your > LAN and just go to the right place. > I'm not interested in mail inside the LAN. I want it to send email to the Cox mail server and find my various accounts with fetchmail. Without name resolution, that fails. > This may be a chore for ethereal. Try turning off everything else on the > LAN except the Airlink and Linus, then run ethereal, start the packet > capture and then try to contact a website. Observe the IP conversation and > it may give you some ideas where things are blocking. > Oooo, goodie ... a new tool. I'll alert my wife that I won't seem to be at home for the next few evenings ;-) Actually, Airlink TS has returned my call and scheduled a call at home at 7 PM tonight. I'm quite impressed with that level of support. Thanks, Gus. I'll post the resolution. -- Lan Barnes [EMAIL PROTECTED] Linux Guy, SCM Specialist 858-354-0616 -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
