Return to BSD News archive
#! rnews 2407 bsd
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!spool.mu.edu!howland.erols.net!newsfeed.internetmci.com!uunet!in3.uu.net!news.artisoft.com!usenet
From: Terry Lambert <terry@lambert.org>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: PPP Setup
Date: Mon, 14 Oct 1996 12:03:39 -0700
Organization: Me
Lines: 47
Message-ID: <32628E8B.274B86C@lambert.org>
References: <01bbb95e$bc4937c0$df6d04c7@zellion.cyberwind.com>
NNTP-Posting-Host: hecate.artisoft.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 2.01 (X11; I; Linux 1.1.76 i486)
Jeffery T. White wrote:
]
] I am trying to setup our FreeBSD box at work (2.1.5 RELEASE) to
] allow a dial in connection. This connection will be used by
] Windows 95 clients to obtain access to Lotus Notes via TCP/IP.
] I have tried both pppd and user ppp. With limited success (user
] ppp) and no success (pppd). I have several questions and also
] a request for opinions (everyone's got those<g>).
[ ... opinions ... ]
] Any opinions, bits of info, pointers to docs/faqs would be greatly
] appreciated.
Configuring a FreeBSD box as a scriptless Windows95 server was
recently discussed on the FreeBSD-current list. Patches were
provided. You should access the -current list archives on the
WWW server at http://www.freebsd.org to obtain the patches.
Unfortunately, the patches are required because Microsoft has
chosen to implement their proprietary compression and configuration
exchange in violation of IETF recommendations and rulings.
Any time a company (even Microsoft) destroys standards conformance
for a product, there are interoperability problems which result.
This problem is *definitely* Microsoft's fault.
The patches make the FreeBSD connection negotiation non-RFC
conformant in the same way as Microsoft's implementation.
Go into this *knowing* that the correct fix is to get Microsoft
to conform to IETF approved methods for PPP vendor options
negotiation.
Again, this is Microsoft's fault. Everyone with any influence
should browbeat them back into line, if at all possible.
Regards,
Terry Lambert
terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.