From owner-freebsd-current Mon Dec 14 01:44:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03332 for freebsd-current-outgoing; Mon, 14 Dec 1998 01:44:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hsw.generalresources.com ([203.79.17.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03254 for ; Mon, 14 Dec 1998 01:43:47 -0800 (PST) (envelope-from hsw@email.generalresources.com) Received: from hsw.generalresources.com (localhost [127.0.0.1]) by hsw.generalresources.com (8.9.1/8.9.1) with ESMTP id RAA04244 for ; Mon, 14 Dec 1998 17:42:48 +0800 (CST) (envelope-from hsw@hsw.generalresources.com) Message-Id: <199812140942.RAA04244@hsw.generalresources.com> To: freebsd-current@FreeBSD.ORG From: Christopher Hall Reply-to: Christopher Hall Subject: ppp tunnelling X-Operating-System: FreeBSD 3.0 X-Mailer: exmh 2.0 Date: Mon, 14 Dec 1998 17:42:48 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a fairly recent make world (cvsup about 12 hours ago) I rebuilt the kernel with two tunnel devices to try to use the ppp.conf "loopback". (from ppp.conf.sample file version 1.33) I tried the following: When I run the client ppp, the server ppp seems to hang, and kill is needed to stop the server. Telnet to server ppp also hangs, there is no output from the server. Running ppp -direct loop-in prints 5 blocks of binary data. Replacing the server with a simple C program to output a couple of lines of text and running the client interactive mode; the text shows up when the "term" command is used. Here is the run: [hsw:/etc/ppp]# ppp -background loop Working in background mode Using interface: tun0 Child failed (errdead). [hsw:/etc/ppp]# >From ps -ax: 698 ?? Is 0:00.04 ppp -direct loop-in It looks to me like the server ppp is not doing any I/O once it has been started by inetd. Just added the Async log flag and I can see the data is only received by the server ppp _after_ it receives the signal 15 from the kill. Might this suggest that it has not set the socket to non-blocking? --- Christopher Hall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message