Before I send-pr, some more notes:

On Tue, 11 Oct 2005, Greg Troxel wrote:

>  Check outgoing traffic via tcpdump on another machine.  Probably
>  it's there, but if not that's interesting.

tcpdump on another machine shows traffic going both ways even when
network appears to be down:

13:09:57.479987 IP rainier > pilchuck: icmp 64: echo request seq 59
13:09:57.480170 IP pilchuck > rainier: icmp 64: echo reply seq 59

(rainier is the host with the problem.)

>  Run 'netstat -ain' to see what multicast groups are joined.

No change whether I am running tcpdump or not.

netstat -ain output (but just tlp):

Name  Mtu   Network       Address              Ipkts Ierrs    Opkts Oerrs 
Colls
tlp0  1500  <Link>        00:a0:cc:24:2d:40  1750619     0   638304     1  5512
tlp0  1500  fe80::/64     fe80::2a0:ccff:fe
                           ff02::202%tlp0
                           ff02::2:51:3495%t
                           ff02::1%tlp0
                           ff02::1:ff24:2d40  1750619     0   638304     1 
5512
tlp0  1500  192.168/24    192.168.0.2        1750619     0   638304     1  5512


>  With the system in the broken state, try tcpdump (instead of
>  trafshow) w/o -p.  capture ifconfig; it should show PROMISCOUS but
>  not ALLMULTI. capture netstat -ain.

netstat -ain doesn't change.

With tcpdump not running (and my networking is down):

tlp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500

With tcpdump running (and now my networking works again):

tlp0: flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST> mtu 1500

>  Reboot, but don't power cycle.  Don't start trafshow or ntcpdump.
>  Does it work, or is it still in the no-packets-received state?
...

I didn't get to the rest of this yet. I didn't reboot yet as I am using 
the system :)

  Jeremy C. Reed

  	  	 	 BSD News, BSD tutorials, BSD links
 	  	 	 http://www.bsdnewsletter.com/