nakaji@jp.freebsd.org wrote:

> bash-3.2# netstat -in -I tlp0 1
>  tlp0 in       tlp0 out              total in      total out            
>  packets  errs  packets  errs colls   packets  errs  packets  errs colls
>  1660378     0   977657     0     0   2651602     0  2601825     0     0
>        0     0        0     0     0         0     0        0     0     0
>        0     0        0     0     0         0     0        0     0     0
>        0     0        0     0     0         0     0        0     0     0
>        0     0        0     0     0         0     0        0     0     0
>        0     0        0     0     0         0     0        0     0     0
> ^C
> bash-3.2# netstat -in -I tlp1 1
>  tlp1 in       tlp1 out              total in      total out            
>  packets  errs  packets  errs colls   packets  errs  packets  errs colls
>   915078     0  1548022     0     0   2651602     0  2601825     0     0
>        0     0        0     0     0         0     0        0     0     0
>        0     0        0     0     0         0     0        0     0     0
>        0     0        0     0     0         0     0        0     0     0
>        0     0        0     0     0         0     0        0     0     0
>        0     0        0     0     0         0     0        0     0     0
> ^C

Hmm, no input/output packets.

> > > I was running "tcpdump -n -i tlp0", "tcpdump -n -i tlp1" and "vmstat
> > > -i -w 5" while downloading.
> 
> > Hmm, how about "tcpdump -env"?
> 
> I recorded with -w option. What is to be checked especially?

Is there any packet at that time?

> When all tlp connections are lost, "vmstat -i" shows

Please check if any interrupts occur during the trouble,
not only rates/numbers. ("systat vmstat" might be better)

> bash-3.2# ping 127.0.0.1
> PING localhost (127.0.0.1): 56 data bytes
> ping: sendto: No buffer space available
> ping: sendto: No buffer space available
> ping: sendto: No buffer space available
> ping: sendto: No buffer space available

Hmm, looks IFF_OACTIVE is set in tlp_start.
Didn't you see any timeout error messages?
How about ping right after "ifconfig tlp[01] up"?

> Ping to 60.32.13.193 and 192.168.1.1 does not start, no output.
> 
> bash-3.2# ping 192.168.1.1
> ^C
> bash-3.2# ping 60.32.13.193
> ^C

I guess it's because DNS lookup. You should try ping -n in such case.

> > > And, tcpdump shows only SNMP, NTP, and SMB now.
> 
> > Hmm, if any packets are handled in upper layer,
> > it shouldn't be a driver problem (nor cobalt specific)
> > but some issue around ipf or other settings, I guess.
> 
> I'm confused very much. I just copied the settings from NetBSD/i386
> (former nat box). What is the next step?

Are you sure that you can see any input packets on tcpdump
but ping fails (or netstat shows no in/out packets)?

Anyway, it's also better to post dmesg (or kernel config
if your kernel is not GENERIC).
---
Izumi Tsutsui