public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Bambach <eric@cisu.net>
To: haltec@kvinet.com
Cc: chuck gelm <chuck@gelm.net>, linux-newbie@vger.kernel.org
Subject: Re: pppoe * rp-pppoe * pppd?????
Date: Mon, 28 Nov 2005 14:20:11 -0600	[thread overview]
Message-ID: <200511281420.11452.eric@cisu.net> (raw)
In-Reply-To: <20051128161122.GA1398@lnx2.w8mch.ampr.org>

On Monday 28 November 2005 10:11 am, Hal MacArgle wrote:
> On 11-28, chuck gelm wrote:
> > Hal MacArgle wrote:
> > >Greetings: I'm lost in a bewilderment of HOWTO's, Docs, FAQ's, etc
> > >about PPPOE and ADSL Modems.. The more I read the worse it gets.
> > ><grin>
> > >
> > >However, my one query for the list is:
> > >
> > >Using the Roaring Penguin PPPOE client, rp-pppoe; do I really need
> > >PPP support too?? Or does that client include PPP support.. No success
> > >yet I've got to eliminate some parameters..
> > >
> > >Both are legitimate packages in Slackware 10-l and I'll go ahead and
> > >try all the different ways but could use some possible comments..
> > >
> > >Cheers and TIA..
> >
> > Hi, Hal:
> >
> > "...do I really need PPP support too??"
> >
> > Yes!!
> >
> > I use Slackware and I used Roaring Penguin for several years
> > until one year ago (when I switched from aDSL to cable).  I
> > started with Earthlink (which had excellent support) and later
> > switched to Ameritech/SBC/Yahoo (which had horrible support).
> >
> > It seems to me that you did not describe any problem and you
> > asked a very specific question.  I am unwilling to offer further
> > information until you describe your setup.
>
> 	OK, thanks, bear with this old man.. And, thanks Eric for
> your reaffirmation that ppp is needed along with pppoe.. But, does
> rp-pppoe "include" ppp /or/ do I need to setup ppp separately??
> Slackware has a script 'pppsetup' that, first off, asks for a
> telephone number, so that can't be used it seems...
>
> 	Anyway; Chuck here's the, more or less, details.. ( My rings
> to Verizon's tech support, at least the one I got, knew nothing of
> what I was talking about).. The more I read the more I find that the
> ISP's are different as well as the modems, not to mention two
> different encodings; CAP or DMT, neither compatible.. Did your ISP
> use the same as ours; Verizon?? Who knows.. Verizon, a Baby Bell
> Telco uses PPPOE, rather than several other options; all designed to
> confuse even experts... (There was a listing on the Web pertaining to
> this and Verizon, but it's either gone or down now.) Maybe Verizon
> "locks" out anything but M$ access??
>
> 	My neighbour bought the package, paying one year up front and
> received a 'kit' with the modem & cables plus a setup CD and several
> micro filters.. Apparently her username and password plus DNS stuff
> has to be via the software; it's not printed anywhere... I fired up
> her modem and the ready led blinked then stayed steady indicating the
> modem has received the DSLAM signal from the CO, one block away, and,
> IIRC, means the system is in "sync."
>
> 	I fired up her Gateway XP Home version machine and ran the
> install CD that visually and verbally took me thru boo coo minutes of
> really basic stuff about hooking up the microfilters, etc, etc.. It,
> finally, got to the nitty gritty with the terse comment, "This may
> take some time." After a half hour of watching a twirling ziggy I
> turned the machine off.. Back to the drawing board...
>
> 	Since all M$ stuff intimidates me I thought I'd ring it out
> with a Linux box, at her site, to see if, perhaps, her NIC card was
> at fault: Slackware 10.1 w/ both the ppp and rp-pppoe packages
> installed.. Modprobe ne io=0x300; NIC enabled and OK.. modprobe
> pppoe, again OK.. ifconfig 10.0.0.1 eth0 mtu 1492, again OK..
> Invoking adsl-setup, I answered with a guessed username, no firewall,
> making sure eth0 was there, and have to stop here because my notes
> are confusing, except that, since I didn't really connect to the ISP;
> I tried another, same brand but different model modem; one that had
> been used before by another person 500 miles from here and was
> working.. The difference between the modems is that one is marked
> "bridge modem" and the other, in the kit, a "router modem." Don't
> know if that tells anything much in this case.. Neither one
> connected, not that I know what to expect from the ISP, which
> happens, in this case, to be the same as the Telco, viz, Verizon..
>
> 	Am I outliving my welcome?? I've got to keep better notes..
>
> 	Is the above enough for futher comments?? I guess what I
> basically need to know now is the relationship between rp-pppoe and
> ppp with the above lashup.. I can't try what I'm used to: 'pppsetup'
> that Slackware uses because you can't get by the first entry required
> of the telephone number for dialup.. Does installing rp-pppoe take
> care of installing the necessary ppp routines?? Or are both needed,
> separately??

I'd love to chat further but I am amazingly busy. However, with my Earthlink 
DSL connection the only thing required is to run adsl-setup then adsl-start. 
There is no configuring of ppp as that is all done by rp-pppoe.

One thing strikes me as odd about your setup though. Why did you ifconfig 
10.0.0.1 your NIC? The NIC used to connect to the ADSL modem doesn't need an 
IP. Giving one wont hurt, but it may add to your confusion.

The difference between a router modem and bridge modem can be huge. For a 
bridge, you will need rp-pppoe and you will get an IP from your ISP 
45.231.xxx.xxx etc. etc. 

For a router, your modem will receive an IP. After it connects you run 
dhclient or dhcpcd (dont use slackware) and you will get an address like 
192.168.0.100 with a gateway 192.168.0.1. In the latter setup you should NOT 
use rp-pppoe. A router moded will need you to "log-in" to the modem and set 
up your username password there whereas with a bridge its handled by 
rp-pppoe.

HTH!

> 	Appreciate!

-- 
----------------------------------------
--EB

> All is fine except that I can reliably "oops" it simply by trying to read
> from /proc/apm (e.g. cat /proc/apm).
> oops output and ksymoops-2.3.4 output is attached.
> Is there anything else I can contribute?

The latitude and longtitude of the bios writers current position, and
a ballistic missile.

                --Alan Cox LKML-December 08,2000 

----------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2005-11-28 20:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-27 20:03 pppoe * rp-pppoe * pppd????? Hal MacArgle
2005-11-27 21:22 ` Eric Bambach
2005-11-28 13:22 ` chuck gelm
2005-11-28 16:11   ` Hal MacArgle
2005-11-28 20:20     ` Eric Bambach [this message]
2005-11-28 21:57     ` chuck gelm
2005-12-01 21:40       ` Hal MacArgle
2005-12-02  2:51         ` but does Verizon support Unix/Linux; was " chuck gelm
2005-12-02 20:37           ` linuxdevelop linux
2005-12-02 20:44           ` Hal MacArgle
  -- strict thread matches above, loose matches on Subject: below --
2005-12-01 21:51 Hal MacArgle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200511281420.11452.eric@cisu.net \
    --to=eric@cisu.net \
    --cc=chuck@gelm.net \
    --cc=haltec@kvinet.com \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox