Sponsored Content
Full Discussion: PPPoE + ADSL on FreeBSD 4.4
Top Forums UNIX for Dummies Questions & Answers PPPoE + ADSL on FreeBSD 4.4 Post 16901 by killerserv on Friday 8th of March 2002 06:16:15 AM
Old 03-08-2002
modify four lines in the file /etc/ppp/ppp.conf.

You will find the following lines at the end of /etc/ppp/ppp.conf:

papchap:

#
# edit the next three lines and replace the items in caps with
# the values which have been assigned by your ISP:
#

set phone PHONE_NUM
set authname USERNAME
set authkey PASSWORD

Assuming your ISP name is MYISP, your phone # is 123-1212, your username is USER and your password is PASS, you would do the following:

MYISP:

set phone 555-1212
set authname USER
set authkey PASS

Save your changes and from the command line do this:

# ppp -auto MYISP

Now ping an IP or access your network. Your modem should dial your ISP and connect. That's all there is to it.

Note that this assumes your modem is on com1. If not, tweak the beginning of your ppp.conf file under the default: section.
 

9 More Discussions You Might Find Interesting

1. IP Networking

Unix and ADSL

Is ADSL support available for Unix/Linux? If I want to set up a internet server, will it have to be Windows with a seperate unix box? Or can it be a clean unix server? (2 Replies)
Discussion started by: vannie
2 Replies

2. UNIX for Dummies Questions & Answers

ADSL with Darwin 1.41

Hey everyone, just to let you all know "I'm an uber n00b" I'm connected to Telstra Bigpond's (Australian ISP) ADSL network, now I;m running Darwin 1.41 on an Apple Macintosh PPC computer. I don't know how to set up ADSL on this system, can someone please guide me. (3 Replies)
Discussion started by: Syphor
3 Replies

3. UNIX for Dummies Questions & Answers

Four PCs Sharing ADSL

Hello, everyone. I have a little favor to ask. Me and my friends decided sharing an ADSL line with four PCs. PC no.1: Desktop, two netcard (2000 and 8139), Mandrake 9.0 PC no.2: Acer notebook, PC Card, RTL-8139C/8139C+, MS 98 + Win 2000 Pro PC no.3: Desktop, net card 8139, WindowME + Win 2000... (1 Reply)
Discussion started by: HOUSCOUS
1 Replies

4. SCO

pppoe

Greetings... I'm looking for a pppoe client for SCO SYS_V can u guys gimme some help ? a website address or even the program name would be just fine. Thanx (1 Reply)
Discussion started by: nEuRoMaNcEr
1 Replies

5. Solaris

Solaris 10 ADSL USB modem problem

Hi, I have USB Siemens Santis 100 ADSL modem.I need driver for this modem on Solaris 10.Please help me with some info.Platform is x86.Thanks. (2 Replies)
Discussion started by: Upravnik
2 Replies

6. Solaris

Installing USB adsl modem?

Hello all, granted that I am an absolute beginner with Solaris, I'd like to use my adsl modem, t's a Zyxel prestige 630. I managed to install and configure it under Ubuntu using the drivers from Conexant AccessRunner ADSL USB modems with Linux ; is there a chance to do the same under Solaris 10... (0 Replies)
Discussion started by: clalfa
0 Replies

7. IP Networking

Sharing Adsl Link

Hi guyz, got a little bit of a situation here. we are sharing an ADSL link with another organization. so there are 2 networks. network 1: has the adsl router and the whole n/w is on subnet 192.168.0.* the adsl router has its ip as 192.168.0.1 network 2(now us): we have set up a linux... (0 Replies)
Discussion started by: royashoya
0 Replies

8. Shell Programming and Scripting

Using Net::Telnet in Perl to connect to an adsl modem

Hello, First of all, congratulations on this forum! Very mice material! This is my fist thread and it has to do with connecting to an adsl modem and executing some commands. Heres what I do: $username = 'admin'; $passwd = 'admin'; $telnet = new Net::Telnet ( Timeout=>10,... (2 Replies)
Discussion started by: Ravendark
2 Replies

9. IP Networking

authentication of VM's via PPPoE

I have two VM's running on Ubuntu box.Their name and IP addresses are give below. nas 192.168.129.153 home_user 192.168.129.152 I establish a ppp connection between the two machines #nas (server) sudo pppd noauth local lock defaultroute... (0 Replies)
Discussion started by: karthik.sharma
0 Replies
WVDIAL(1)						      General Commands Manual							 WVDIAL(1)

NAME
wvdial - PPP dialer with built-in intelligence. SYNOPSIS
wvdial [ OPTIONS ] [ SECTION ] ... DESCRIPTION
wvdial is an intelligent PPP dialer, which means that it dials a modem and starts PPP in order to connect to the Internet. It is something like the chat(8) program, except that it uses heuristics to guess how to dial and log into your server rather than forcing you to write a login script. When wvdial starts, it first loads its configuration from /etc/wvdial.conf and ~/.wvdialrc which contains basic information about the modem port, speed, and init string, along with information about your Internet Service Provider (ISP), such as the phone number, your username, and your password. Then it initializes your modem and dials the server and waits for a connection (a CONNECT string from the modem). It understands and responds to typical connection problems (like BUSY and NO DIALTONE). Any time after connecting, wvdial will start PPP if it sees a PPP sequence from the server. Otherwise, it tries to convince the server to start PPP by doing the following: o responding to any login/password prompts it sees; o interpreting "choose one of the following"-style menus; o eventually, sending the word "ppp" (a common terminal server command). If all of this fails, wvdial just runs pppd(8) and hopes for the best. It will bring up the connection, and then wait patiently for you to drop the link by pressing CTRL-C. OPTIONS
Several options are recognized by wvdial. -c, --chat Run wvdial as a chat replacement from within pppd, instead of the more normal method of having wvdial negotiate the connection and then call pppd. -C, --config=CONFIGFILE Run wvdial with CONFIGFILE as the configuration file, instead of /etc/wvdial.conf. This is mainly useful only if you want to have per-user configurations, or you want to avoid having dial-up information (usernames, passwords, calling card numbers, etc.) in a system wide configuration file. --remotename Override the Remote Name setting in the dialer configuration section of the configuration file. This is mainly useful when you dial to multiple systems with the same user name and password, and you don't want to use inheritance to override this setting (which is the recommended way to do it). -n, --no-syslog Don't output debug information to the syslog daemon (only useful together with --chat). wvdial is normally run without command line options, in which case it reads its configuration from the [Dialer Defaults] section of /etc/wvdial.conf. (The configuration file is described in more detail in wvdial.conf(5) manual page.) One or more SECTIONs of /etc/wvdial.conf may be specified on the command line. Settings in these sections will override settings in [Dialer Defaults]. For example, the command: wvdial phone2 will read default options from the [Dialer Defaults] section, then override any or all of the options with those found in the [Dialer phone2] section. If more than one section is specified, they are processed in the order they are given. Each section will override all the sections that came before it. For example, the command: wvdial phone2 pulse shh will read default options from the [Dialer Defaults] section, then override any or all of the options with those found in the [Dialer phone2] section, followed by the [Dialer pulse] section, and lastly the [Dialer shh] section. Using this method, it is possible to easily configure wvdial to switch between different internet providers, modem init strings, account names, and so on without specifying the same configuration information over and over. BUGS
"Intelligent" programs are frustrating when they don't work right. This version of wvdial has only minimal support for disabling or over- riding its "intelligence", with the "Stupid Mode", "Login Prompt", and "Password Prompt" options. So, in general if you have a nice ISP, it will probably work, and if you have a weird ISP, it might not. Still, it's not much good if it doesn't work for you, right? Don't be fooled by the fact that wvdial finally made it to version 1.00; it could well contain many bugs and misfeatures. Let us know if you have problems by sending e-mail to <wvdial-list@lists.nit.ca>. You may encounter some error messages if you don't have write access to /etc/ppp/pap-secrets and /etc/ppp/chap-secrets. Unfortunately, there's really no nice way around this yet. FILES
/etc/wvdial.conf Configuration file which contains modem, dialing, and login information. See wvdial.conf(5). /dev/ttyS* Serial port devices. /etc/ppp/peers/wvdial Required for correct authentication in pppd version 2.3.0 or newer. /etc/ppp/{pap,chap}-secrets Contains a list of usernames and passwords used by pppd for authentication. wvdial maintains this list automatically. AUTHORS
Dave Coombs and Avery Pennarun for Net Integration Technologies. We would also like to thank SuSE and RedHat for adding a number of vari- ous cool features to wvdial. Thanks guys! SEE ALSO
wvdial.conf(5), wvdialconf(1), pppd(8), chat(8). WvDial December 2005 WVDIAL(1)
All times are GMT -4. The time now is 11:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy