Package: tcptraceroute
Version: 1.5beta6-1
Severity: important

When used on my laptop (via Ethernet), tcptraceroute fails to
function, and (IIRC) has done so for as long as I've tried it.

Further, while active, the system cannot receive packets on the
Ethernet interface, for *any* application.  tcpdump on other machines
shows that packets are being sent properly, including the
tcptraceroute packets, but the machine now silently ignores the
replies and other incoming packets.

Pings freeze with no error messages (but continue to transmit ICMP
echo-requests) until tcptraceroute is aborted, and incoming pings from
other machines are ignored.

Running tcpdump on the same system while tcptraceroute is active
prevents the network 'freeze', but does not allow tcptraceroute to
receive its own packets.

This occurs both with standard firewalling rules and with all tables
flushed.  Ethernet is a BroadCom, b44 driver.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-686
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)

Versions of packages tcptraceroute depends on:
ii  libc6                       2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  libnet1                     1.1.2.1-2    library for the construction and h
ii  libpcap0.7                  0.7.2-7      System interface for user-level pa

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to