On 3/27/2013 3:57 PM, Robert Benjamin wrote: > On 3/27/2013 3:30 PM, m.roth at 5-cent.us wrote: >> Robert Benjamin wrote: >>> On 3/27/2013 1:52 PM, Les Mikesell wrote: >>>> On Wed, Mar 27, 2013 at 12:32 PM, Robert Benjamin <benjie1 at cox.net> >>>> wrote: >>>>>> The reason I think this is the problem is the post where you said you >>>>>> could log in after a very long delay. About the only thing that can >>>>>> cause a very long delay is the system waiting for DNS responses on >> <snip> >>>> The IP address looks like what you would get from a typical home >>>> router, so that's probably OK. A quick test for DNS would be the >>>> 'dig' command. If it quickly returns a screenfull of root >>>> nameservers and addresses, then DNS is not the problem. If it >>>> doesn't, then check what you have in your /etc/resolv.conf file. >>>> >>> dig returned a lot of root nameservers instantly. >> Nasty thought: in one window, run tcpdump -A port 50, and in another, try >> looking something up, say, nytimes.com, something obvious. See what's >> going and coming. >> >> mark > Did you mean ping nytimes.com ? tcpdump -A port 50 output is tcpdump: verbose output suppressed, use -v or -w for all protocol decode listening on eth0, link-type EN10MB (Ethernet), capturing size 65535 bytes, and a blinking cursor which I left for 20 min and re-started, tried with -v got listening on eth0, type EN10MB (Ethernet), capture size 65535 bytes. re-started and meant to use -w but forgot and just typed tcpdump. That gave tons of output which I can't fathom and let it go for 30 minutes. Re-started one more time and pinged nytimes.com That returned screenful of data packets all ok. Then shutdown til tomorrow. Bob >> _______________________________________________ >> CentOS mailing list >> CentOS at centos.org >> http://lists.centos.org/mailman/listinfo/centos >> > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >