On 3/27/2013 5:22 PM, m.roth at 5-cent.us wrote: > Les Mikesell wrote: >> On Wed, Mar 27, 2013 at 3:53 PM, Robert Benjamin <benjie1 at cox.net> wrote: >>>> 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. >> I think he meant port 53 instead of 50 to catch the DNS exchange - >> which now sounds like it is working anyway. When you start, does >> gnome eventually work normally now?. I'd do a 'yum update' on >> general principles if you at least have the network running. >> > Thanks, Les, that was what I meant. I've been snowed under all week, and > more so today: it's not one thing after another, it's three things all at > the same time.... > > mark tcpdump with port 53 was no different than with port 50. Waited an hour after startup and still had that same blue screen. Is that the gnome desktop screen? So no it doesn't eventually work. An hour is eventually right? :-) yum update installed 23 packages successfully. Should I re-instal again? It will be the 3rd time. > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >