Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 7 May 2001 11:30:23 +0100 (BST)
From:      Randall Skelton <rhskelto@atm.ox.ac.uk>
To:        freebsd-questions@FreeBSD.ORG
Subject:   Dropped packets...
Message-ID:  <Pine.LNX.4.21.0105071125500.1627-100000@homer.atm.ox.ac.uk>

next in thread | raw e-mail | index | archive | help
Hi all,

I am having a rather strange problem with my network interface in FreeBSD
4.2/4.3.  It is an sis900 card which appears to be fully supported and was
detected on install.  Nothing further has been done to the machine (it is a
brand new *vanilla* install of 4.3).

The problem almost appears to be the machine being sleepy and failing to
reply to network requests until it is rudely awakened. After the machine
has been idle for an hour or so (no logins and little activity) the
ethernet card fails to respond when a connection is attempted via
ssh/ftp/telnet/etc...  To 'wake-up' the interface, I must ping the machine
from within the subnet and I seem to loose the first packet?  (NB: if I
ping the machine from outside the subnet at this point I loose all
packets)

(from within the subnet)
PING tulip... (xxx.1.242.xxx): 56 data bytes
64 bytes from xxx.1.242.xxx: icmp_seq=1 ttl=255 time=0.6 ms
64 bytes from xxx.1.242.xxx: icmp_seq=2 ttl=255 time=0.5 ms
64 bytes from xxx.1.242.xxx: icmp_seq=3 ttl=255 time=0.5 ms

Note that icmp_seq=0 is lost.  Once, the machine 'wakes up' the card
appears fine and I can connect to it both from inside or outside the
subnet with no packet loss.

ifconfig gives the following:
sis0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet xxx.1.242.xxx netmask 0xfffff800 broadcast xxx.1.247.xxx
        inet6 fe80::240:33ff:feab:fd85%sis0 prefixlen 64 scopeid 0x1 
        ether 00:40:33:ab:fd:85 
        media: autoselect (100baseTX <full-duplex>) status: active
        supported media: autoselect 100baseTX <full-duplex> 100baseTX
10baseT/UTP <full-duplex> 10baseT/UTP none  

I have no problems with the card under linux so I don't really suspect the
card itself.  Is it possible it is the driver?  How do I turn up the
debugging level for the interface?  Does anyone have any ideas as to what
is going on here or have any comment on what I should try?

Cheers,
Randall



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.21.0105071125500.1627-100000>