Tom Chen writes: > If I ping this Solaris PC's dummy address from another test PC(Linux), it > looks fine, but if I ping from Solaris PC to Linux PC, ping gets stuck for > one minute or two, however, snoop (running on Solaris PC) shows quite a lot > of packets exchange between them. I am not sure where is wrong, or is Solaris > trying to figure out where that 192.168.0.10 is? I see Solaris sends > (broadcasts) packet to the internal network and Linux PC responds.
Is there any way you could reveal the contents of those packets? It's hard to diagnose a problem without knowing what's going on. Have you tried "ping -n" instead, to rule out name service problems? It _might_ be important to know here that snoop isn't exactly an unbiased observer. It requires the driver to send packets up a separate stream, and thus requires the cooperation of the driver. It's entirely possible that packets you see "transmitted" in snoop never actually make it onto the wire, and that (depending on the driver design) there are some received packets that are not seen. If you need an unbiased observer (and you often do when designing network drivers, as opposed to ordinary applications), then you'd be best off using some neutral third system as an observer. There are some expensive devices available that make this easy, but one relatively inexpensive one is called "PacketView." (Please include some context in your replies; it's hard to tell what you're replying to without it.) -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
