From owner-freebsd-hackers Thu Dec 20 14:14:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from clever.eusc.inter.net (clever.eusc.inter.net [213.73.101.4]) by hub.freebsd.org (Postfix) with ESMTP id 5134B37B405; Thu, 20 Dec 2001 14:14:01 -0800 (PST) Received: from tc04-n65-189.de.inter.net ([213.73.65.189] helo=there) by clever.eusc.inter.net with smtp (Exim 3.22 #3) id 16HBRu-0006Wa-00; Thu, 20 Dec 2001 23:13:59 +0100 Content-Type: text/plain; charset="iso-8859-1" From: Matthias Schuendehuette Reply-To: msch@snafu.de Organization: Micro$oft-free Zone To: freebsd-stable@freebsd.org Subject: isp-device broken in 4.5-PRERELEASE Date: Thu, 20 Dec 2001 23:13:57 +0100 X-Mailer: KMail [version 1.3.1] Cc: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, something's broken with the isp-device (ISDN syncPPP network device). The last working kernel was of dec 8, 2001. I found the problem after my next update at dec 15, 2001. Until today, the 'isdnd' worked with the old kernel of dec 8, but now the new userland doesn't fit anymore. THANK GOD my old modem is still working! :-) What I found out so far: It seems nothing to do with the files in src/sys/i4b that changed between dec 8 and dec 15. I downloaded the files in question via CVSweb and built another kernel but the problems still remain. After that, i played around with 'ping -n' and 'tcpdump -n' and found, that the sppp-part works fine (authentication succeeds), even the ICMP-packets are going forth and back (the dial-out process is triggered and i can see the packets in the tcpdump output) but obviously they never reach the ping process again. 'ping -n 194.64.64.23' reports: PING 194.64.64.23 (194.64.64.23): 56 data bytes ^C --- 194.64.64.23 ping statistics --- 6 packets transmitted, 0 packets received, 100% packet loss but the 'tcpdump -n -i isp0' shows: 22:19:41.194471 IP 88: 213.73.67.35 > 194.64.64.23: icmp: echo request 22:19:41.258523 IP 88: 194.64.64.23 > 213.73.67.35: icmp: echo reply (DF) 22:19:41.258790 IP 88: 194.64.64.23 > 213.73.67.35: icmp: echo reply (DF) 22:19:42.202641 IP 88: 213.73.67.35 > 194.64.64.23: icmp: echo request 22:19:42.264898 IP 88: 194.64.64.23 > 213.73.67.35: icmp: echo reply (DF) 22:19:42.265110 IP 88: 194.64.64.23 > 213.73.67.35: icmp: echo reply (DF) [...] I already mailed with hm on that, but he has no ideas. I also don't believe that an error is in the i4b subsystem (see above). And I'm not the only one with these problems, in the german bsd-newsgroup are at least two other persons with exactly the same problems... Please have a look on that issue. If I can do any further testing, I'll do it ASAP. Ciao/BSD - Matthias -- *************************************************************************** * Matthias Schuendehuette msch@snafu.de * * Solmsstrasse 44 * * D-10961 Berlin Engineering Systems Support and Operation * * Germany (Powered by FreeBSD 4.4-STABLE) * *************************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message