From owner-freebsd-questions Fri Dec 31 13:17: 0 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mail.megsinet.net (mailcluster-b.corecomm.net [216.214.150.11]) by hub.freebsd.org (Postfix) with ESMTP id A795414E6B for ; Fri, 31 Dec 1999 13:16:57 -0800 (PST) (envelope-from cpitzer@megsinet.net) Received: from nightrider (max9-116.columbus.corecomm.net) by mail.megsinet.net (Sun Internet Mail Server sims.3.5.1999.07.30.00.05.p8) with SMTP id <0FNM009ELJ5HBG@mail.megsinet.net> for questions@freebsd.org; Fri, 31 Dec 1999 15:17:43 -0600 (CST) Date: Fri, 31 Dec 1999 16:12:13 -0500 From: Chris Pitzer Subject: PPP services To: questions@freebsd.org Message-id: <002901bf53d3$b6044040$2a640a0a@wasteland.net> MIME-version: 1.0 X-Mailer: Microsoft Outlook Express 5.00.2615.200 Content-type: multipart/alternative; boundary="----=_NextPart_000_0026_01BF53A9.CC7596A0" X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 X-Priority: 3 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0026_01BF53A9.CC7596A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I am trying to connect to IRC using FreeBSD as a proxy. I cannot send = files through DCC. I seem to remember seeing something about having to = enable sockets, but can't seem to find that now. Does anybody have any = suggestions on how to set this up? thanks Chris ------=_NextPart_000_0026_01BF53A9.CC7596A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I am trying to connect to IRC = using FreeBSD=20 as a proxy. I cannot send files through DCC. I seem to remember seeing = something=20 about having to enable sockets, but can't seem to find that now. Does = anybody=20 have any suggestions on how to set this up?

thanks

Chris

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