From owner-freebsd-isp Sun Jan 4 23:18:45 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA11075 for isp-outgoing; Sun, 4 Jan 1998 23:18:45 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA11067 for ; Sun, 4 Jan 1998 23:18:41 -0800 (PST) (envelope-from danny@panda.hilink.com.au) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id SAA29382; Mon, 5 Jan 1998 18:18:25 +1100 (EST) Date: Mon, 5 Jan 1998 18:18:25 +1100 (EST) From: "Daniel O'Callaghan" To: John Kelly cc: freebsd-isp@FreeBSD.ORG Subject: Re: PPPD terminal server on FreeBSD, NATD In-Reply-To: <34b07d97.643666@mail.cetlink.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I still don't know yet if FreeBSD will scale to a 32 port terminal > server with the SIO driver and cheap multiport serial cards like the > one I use, but with no efficiency loss on 2 ports, it has some hope. I have a 686-200 with 1 16-port cyclades and 2 TC-800 (Byterunners). The main problem I have is with mpd running really hard, taking 6% of CPU, trying to serve 3 downstream small ISPs all at peak time. In other words, for normal use, using kernel pppd, the TC-800 from Byterunner is fine. However, one of those downstream ISPs put his MPD onto two ports of his TC-800 and it would not work. The second TC-800 sio port on the mpd was hardly serviced at all, and data flow was abysmal. Moving his mpd to sio0 and sio1 fixed the problem, and he has users dialling into the TC-800 fine. In other words, TC-800 is fine for transmitting data, but not so good on receiving it. Danny