APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

Best of CUSM: pppoe verizon dsl


What is this stuff?

If this isn't exactly what you wanted, please try our Search (there's a LOT of techy and non-techy stuff here about Linux, Unix, Mac OS X and just computers in general!):



From: "Brian K. White" <brian@aljex.com>
Newsgroups: comp.unix.sco.misc
Subject: Re: ADSL with Unixware
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Date: Sat, 08 Sep 2001 06:18:14 GMT


"Tony Lawrence" <tony@aplawrence.com> wrote in message
news:3B98B424.EDD59A3C@aplawrence.com...
> Han van Capelle wrote:
> >
> > "Alexander Spanke" <ASpanke@mail.isis.de> wrote in message
> > news:9na1ef$qg$03$1@news.t-online.com...
> > > Hi,
> > >
> > > i know it's a silly question, but does anyone know if i can use ADSL with Unixware 2.1.3 ?
> > >
> > > regards
> > > Alex
> > >
> > >
> > Sure you can. ADSL has nothing to do with the make or version Operating  System.
> > Why are you in doubt?
> > It's just a way of sending data over old telephone wire.
>
>
> Well, yeah, but..
>
> His real question might be something like "Can I use ADSL as provided by
> XYZ?" and the answer to that might be "Maybe".
>
> For example, here in Boston, you can get DSL from the wunnerful Verizon
> folks.  It's a dynamic ip address, and just to make it more of a pita it's
> pppoe and even more painful, you can't get the information you need for pppoe
> without running a Windows client that they provide.
>
> So, does Unixware 2 support dhcp and pppoe?  Can you get the needed info from
> installing their Windows client?  If you do, will it all continue to work
> or are they apt to arbitrarily change something later?
>
> I dunno.  I had one client who did this with the intent of using a Linux
> system that could do dhcp and pppoe, but he couldn't get answers that he
> liked so he went elsewhere.  I have another guy who just did this also; we'll
> see how he makes out.
>
> What I love is the patronizing little laugh you get from some of the Windows
> centric support folk: "Ah, Linux? Well,- ha ha-  we don't support that".
> Yeah, "ha ha" to you too :-)



short answer: it's easy, no problem at all, nothing fancy or weird.
actually, verizon is the most difficult example, but only because it takes
extra work to get the account initailly activated, once that's out of the
way it's,

long answer:

I have a few customers with verizon dsl service, same as you describe,
pppoe, dynamic ip, it's no problem.

the key is, just get any one of several readily available "broadband gateway
router", they are available at office-max, office depot, staples, etc, and
of course comp usa. some names I've used with mixed success, linksys,
d-link, netgear.
they are only about $120 to $190 and usually incorporate a 4 or 8 port
switch, and some even include a print server and some now include a wireless
access point too. (with wireless you are getting into the $300 range.

The way I do it, I pop the install CD in my laptop and go through the
gyrations of getting the account registered as if my laptop were the only
PC. This could be done on a PC in the office but I just find it easier to
usemy own. the dsl install cd forces you to install a special version of
netscape from the CD, which it uses to log in to a special account
activation server via the dsl. there is no way around this. it also installs
a pppoe driver called "winpoet" and a vpn virtual network adapter. this is
all needed for the PC to use the dsl directly, but is all unwelcome junk
once the account is activated and and the router is doing the pppoe. You
never need the stuff again, power-cycling the router or the modem, even for
long times like weeks doesn't make a difference.

once the account is activated and working, I put the router in place of my
laptop, and reconfig my laptop network settings to talk to the LAN side of
the router. I give the laptop an ip like 192.168.1.2, then use it to
configure the router by doing http://192.168.1.1/  (LAN ip of the router),
in the router config, you just:
* set "ip is provided by provider" and leave all ip and dns fields emty
* enable pppoe
* fill in the username and password, gleaned from the account activation
process when you installed the verizon CD
* enable "connect on demand" and set a long idle timeout so it mostly just
stays connected.
* in the case of a LAN that includes a unix server, either make the unix
server the "DMZ" or, define some NAT rules to forward incoming traffic on
specific tcp/udp ports in to the unix servers LAN ip (such as
21,22,23,25,80,110)
"DMZ" is just a special NAT rule that means forward all (0-65535) tcp and
udp ports in to one of the LAN ip's.
if there is not a unix box, you would make the NT server, or just pick an
"important" pc, and make that the dmz, and you will be able to install
pcanywhere on that PC and then youcan pcanywhere from your office to theirs
at dsl speeds. you will need to have them tell you their ip each time for
this but, there are a couple things you can set up to make this quick and
simple, and it's worth the bother even for short sessions.
* You may want to change the routers IP to conform to the existing LAN, if
it was already a proper non-routable network (10.x.x.x or 192.168.x.x)
* You may want to do one or more of the following with the dhcp server built
into the router (damn these little miracle boxes do a lot huh?)
  -  turn it off, since it's usually enabled by default, serving about 50 or
100 addresses
  -  redice the range of addresses in its pool so that most PC's on the lan
have static IP's and there is also a few addresses set aside for dhcp so
that you can also have people with laptops just walk in a plug them in and
have them auto-configure.
  -  leave it enabled, maybe increase it's range so it serves almost all 253
available addresses ( be sure to avoide the unix servers IP, which should
remain static) and configure all the PC's for "detect IP automatically) this
way from now on you never have to figure out what is an available IP to use
when installing new pc's or reconfiguring dead/replaced ones.
* since these things are configured via http or telnet or both, sometimes
they include the option to enable or disable the ability to administer the
router from outside the LAN. since the common http and telnet ports are
probably going to be mapped with NAT to be passed off to the unix box,
sometimes there is an option to have the built-in web server and telnetd
listen on non-standard ports. if there is no option to move the built-in
servers to other ports, then you won't be able to administer the router from
your office except by telnetting in to the unix box, and from there
telnetting to the LAN ip of the router, or if the connection is good, and
you have access to a unix console, you can fire up X, open an xterm and set
and export DISPLAY=your-ip:0, run "xhosts +", telnet to the remote unix,
then run netscape on their box, netscape will then display on your screen,
but it'll be running on their box, and you can then use it to http to the
LAN side of their router. I use this sometimes to run "printtool" on remote
linux boxes, and "netscape fast start internet configuration" on remote sco
boxes. It's not too useful for administering the router though, because you
need the router to be doing it's job in order to get to the unixbox, in
order to get to the private side of the router. sometimes you can dial in to
the unix box and run lynx to administer the router if the router is not
working.



also change the default password since everyone knows the default passwords
of all the mass-produced routers.

also, don't wait for the call-backs, simply check the manufacturer web site
and upgrade the router firmware. In this case, do not waste the time with
the usually better practice of only upgrading something if it actually
breaks in some way.

When I say I've had mixed success, I mean, I've used mostly linksys, and
within that group, in most cases the thing went in and started out working
just fine, but turned out to lock up under a little load, or, perform
terribly under a little load. of these, most were fixed by upgrading the
firmware, but some just turned out to be "bad" and getting a warranty
replacement one (even though it's the same model) from the store, (and
upgrading that ones firmware too) fixed it. And even among "good" ones,
usually they need to power-cycled once in a while, varying from once a week
to once in a month or two. I have a d-link at home, a 8-port switch model,
with only a dormant freebsd box, a mostly dormant win2k box, and once in a
while my laptop, and it needs to be power-cycled every couple days.
I had one recently that would lose it's configuration every day or so.
(power-cycling is safe to do normally btw)
If it loses it's config, such as by hitting the tiny reset button, it only
takes a minute to just punch the stuff back in and You can sometimes even
show a user how to do it, and leave them a cheat sheet with the list of
numbers to fill in and check-boxes to hit. There is no more need for the
install cd or the winpoet junk.

I'm sure there are better boxes out there, but the point of the discussion
was that there is no great difficulty using verizon's or anyone elses dsl
with any unix. On possible exception would be those services where the modem
uses only a usb cable and not ethernet, and/or those cable services where
they install a cable-modem card in the PC, and the cable only downloads, and
uploads (even the tiny upload that is the text of URL you typed in to the
address bar to ask for a page) takes place over a regular telephone modem)

that is for the verizon/bell-atlantic modems. many other services use a
modem that actually is also a NAT-capable router and 4 or 8 port hub or
switch itself, and sometimes they offer the option for a "un-managed"
account, which means they let you have the password to the modem and you can
configure the router/dhcp/nat features yourself, but usually you have to ask
them to do it.in these cases you don't have to buy a router. there is
nothing stopping you from just sticking you own router in there as described
above even if the modem has a router, if it is difficult to get the provider
to do what you want or you just don't want to have to call them every time
you want to play with some new service or something.

You *could* install 2 nic's in a pc, install the winpoet crap on the pc,
install wingate, or use windows me/2000 built in connection-sharing driver
instead of installing a router. I think this is an absolutely terrible way
to go, though I have seen it working in a few places. (I didn't set it up. I
have set up wingate once, could not figure out the windows built-in stuff)
maybe these cases were installed before these routers were such a commodity
item.

--
Brian K. White  --  brian@aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani





Got something to add? Send me email.





(OLDER)    <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

-> -> pppoe verizon dsl ––>Re: ADSL with Unixware and Suse Linux



Increase ad revenue 50-250% with Ezoic


---August 12, 2004

I am a new Verizon DSL customer in Texas. I borrowed a Winblows laptop from the office and used the setup CD to initialize my account. I assumed that Verizon ran PPPoE here, too, and set up PPPoE on SUSE without success. After much head banging and a quick call to tech support(Thank you, Georgia. You're a peach.) I learned that Verizon only uses PPPoE in the former Bell Atlantic markets. For those of us in the Western markets, just set up your ethernet card to use DHCP and let all of the settings come from the server---MUCH simpler!! you don't need to configure for a DSL network device in SUSE, just the Ethernet card. The needed information for setting up mail, newsgroups, etc. can be found at http://www.dslstart.verizon.net.

Kerio Samepage


Have you tried Searching this site?

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us





The danger of computers becoming like humans is not as great as the danger of humans becoming like computers. (Konrad Zuse)





This post tagged: