Date: Wed, 8 Sep 1999 00:22:37 -0000 From: "Doug Young" <dougy@gargoyle.apana.org.au> To: <freebsd-questions@freebsd.org> Subject: Dialin Setup Message-ID: <055c01bef990$4311cf00$827e03cb@apana.org.au>
next in thread | raw e-mail | index | archive | help
Would someone please enlighten me on dialin issues The relevant part of the Handbook seems to suggest that kernel-ppp is used http://www.freebsd.org/handbook/dialup.html instead of the user-ppp that I have for dialout to ISP. Is this likely to cause a conflict due to two different sorts of processes accessing the ppp component at the same time ?? I've been some stuff called PPP-KIT that apparently was prepared by a guy "danny@freebsd.org" who appears to come from Melbourne Australia thats supposed to help with setting this stuff up so it works without the user having to be an expert (see the ReadMe file from the PPP-KIT below). Since there have been a few changes in the way FreeBSD does things over the past year or so, and as I understand 3.3 is coming very shortly, I'd appreciate any comments as to (1) Are there are conflicts using user-ppp & kernel-ppp at same time (2) Is it possible to tell if the PPP-KIT is relevant to present versions (3) Is there an advantage in using mgetty instead of getty .... and if so is it simply a matter of replacing references to getty or is there other stuff that needs to be done to use mgetty +++++++++++++++++++++++++++++++++++++++++++++++++++++ PPPKIT - A kit for using FreeBSD as a PPP terminal server. This kit provides all you need to make a FreeBSD box into a PAP login terminal server using the system password file for authentication. Its home is <ftp://ftp.hilink.com.au/pub/FreeBSD/pppkit.tgz>; Comments to <danny@freebsd.org> Useful stuff for everyone: 1. /bin/ppplogin.sh (should go in /usr/local/bin) which is a login shell for ppp users, and a pppd starter for getty. 2. /etc/gettytab - note the 'pp=' field in std.57600 & co. 3. /etc/ppp/ppp.ports - ports and IP addresses for ppplogin.sh 4. /etc/ppp/ppp.users - IP addresses for users with static IP addresses 5. /etc/ppp/ppp.deny - unames of users not allowed to use PPP 6. /etc/ppp/ppp.shells - allowed shells for a ppp session Installation ------------ * Make sure you have built a kernel with the appropriate number of ppp interfaces. * copy etc/ppp/ppp.* to /etc/ppp and edit appropriately (see below) * Edit /etc/ppp/options to include your local DNS server IP address, and the keyword 'proxyarp' if you need it. You need proxyarp if the IP addresses you have assigned to the modem ports really belong on your ethernet as defined by the IP address/netmask of your ethernet interface. * Install bin/ppplogin.sh into /usr/local/bin/ppplogin.sh. Edit the entries for std.57600, std.115200 and others in /etc/gettytab to have a tag pp=/usr/local/bin/ppplogin.sh. See the supplied gettytab for an example. * You should read ppplogin.sh to see what it does, and make any changes you feel you want to. * /etc/ppp/ppp.shells - this file defines which user shells are acceptable shells for PAP ppp logins using the system password file. It works in a similar manner to /etc/shells for ftp. If a user's shell is not listed in /etc/ppp/ppp.shells, pppd access is denied. You'll need to list at least /usr/local/bin/ppplogin.sh in this file. * /etc/ppp/ppp.deny lists the names of users who are not permitted to use pppd via PAP authentication using the system password file. * If you want users to be able to log in using a login script and normal Unix Login:/Password: prompts, give them a shell of /usr/local/bin/ppplogin.sh, otherwise, give them a shell of /pppok and list /pppok in /etc/ppp/ppp.shells. /pppok need not actually exist. /usr/local/bin/ppplogin.sh does not give the user shell access to the system, it simply starts pppd appropriately for the user when they log in. * /etc/ppp/ppp.users is used by /usr/local/bin/ppplogin.sh to give static IP addresses to some users when they log in via Login:/Password:, but not when they log in via PAP. To assign a static IP via PAP login, use /etc/ppp/pap-secrets Configuring Clients ------------------- Win95 * Turn off "Bring up terminal window" switch in "Dial Up Networking". The TCP/IP protocol must be installed. The "Client for Microsoft Networks" must be installed. In Control Panel:Network:TCP/IP:Bindings there *must* be an entry for "Client for Microsoft Networks" and this must be checked on. When dialling, enter your username and password at the "Connect To" info box and dial. Everything should work fine. Under FreeBSD, you might want to run "tail -f /var/log/messages" while you test things. Things work best for 95 if you turn off "Log on to Network", NetBEUI and IPX/SPX Macintosh FreePPP * Choose 'Direct' connection rather than 'Connection script'; enter the username and password information into the appropriate boxes, and PAP login will be performed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?055c01bef990$4311cf00$827e03cb>