Very Computer

hi,

i have two unix boxes behind a router which is currently
connected to a cable modem. i nailed down the setup on this
in about 1hr. and it works fine both inside our office and
out to the net. we have shared internet connections, IP
printing, a nice local LAN etc. etc. etc.

DSL modems and PPP is another matter. My chief complaint
is that how-tos start bottom up and explain how to configure
tiny-tiny details like the pap-secrets file and details about
pppd without explaining the basic architecture of the network.
heck, what are the basics for netmasks, IP addresses, both
for the eth0, ppp0, and router? can somebody do that here?

here is what I think is right (but does not work :)

Linksys DSL modem/router
           WAN connect mode: static, manual IP address
                             class B as assigned by ISP
                             in my case 64.xxx.xxx.xxx
                  Netmask  : 255.255.0.0 i.e. not 255.255.255.0
                  DNS      : as assigned by ISP
                  Prim. GW : as assigned by ISP
           LAN parameters
                           : static class C IP address 192.168.1.1
                           : netmask 255.255.255.0

MacOS box: eth0: static class C IP 192.168.1.100
                 netmask 255.255.255.0
           ppp0: static class C IP 192.168.1.101
                 netmask: 255.255.255.0
                 username: per ISP assignment
                 password: per self assignment
           routing:
                 there is, somehow, a static route
                 entry which guides network traffic
                 i.e. non-192.xxx.xxx.xxx traffic
                 to ppp0 where another static route
                 sends it to 192.168.1.1  router
                 and out onto the DSL modem.

Linux box: eth0: static class C IP 192.168.1.102
                 netmask 255.255.255.0
           ppp0: static class C IP 192.168.1.103
                 netmask: 255.255.255.0
                 username: per ISP assignment
                 password: per self assignment
           routing:
                 there is, somehow, a static route
                 entry which guides network traffic
                 i.e. non-192.xxx.xxx.xxx traffic
                 to ppp0 where another static route
                 sends it to 192.168.1.1  router
                 and out onto the DSL modem.

the linux box and macos box have DIFFERENT accounts and
different PASSWORDS which, although the ISP did not tell
me, I assume to be the xxxxxx part in email address

password. So I assume the DSL username/password are the
same as the email accounts. Probably this is WRONG!!!

i have tried other configurations (i.e. WAN connect PPPoE
or WAN connect type PPTP in router but am lost as to the
IP, routes, and netmasks for eth0 and ppp0).

Once I get help here the other stuff like pppd, PPP
support into the kernel, the pap-secrets stuff is easy.
If I need masquarading or some such then I *may* need
some help.

shane

See the Networking HOWTO for the basics.

--
Cameron Kerr

Empowered by Perl!

Mr. Kerr,

where is one which gives the procedure for two unix boxes
behind a router and a dsl (PPPoE) modem? i have not seen
one as yet even under LINUX HOW-TOs pages. again tons of
stuff  on low-end details (also important), how to use the linux
box as a router, how to make a lan, how to use two NICs
to simulate a router, firewalls, etc. etc. etc. there's even
tons of stuff on PPP.

yet it is unclear to me what IPs, netmasks go into what per
above diagram. I am not trying to lazy and will happily
summarize solution to those who ask to offload future
bandwidth.

Regards,
Shane

Well, very obviously, if IPs and netmasks are unclear to You, You
definately want to read the Networking-HowTo as suggested.

But to put You on the right track, in brief:

The idea of having a modem/router like Your LinkSys device is to
use _one_ connection to Your ISP from _multiple_ clients on Your local
net, therefore eliminating the need for some modem or similar device
for each of the clients.

What You should do now is (1) to get rid of the clients' respective
pppN devices, and (2) set the default route via Your LinkSys router,
192.168.1.1. Then, (3), configure Your router to use the account de-
tails of one account of Your choice to connect to Your ISP, and to (4)
allow masquerading for Your 192.168.1/24 local subnet.

That's it, basically. You may want to go through this step by step,
but the most important part is that You use the router _instead_ of
the ppp-devices.

As Cameron said, You should start and get the very basics of networking.
After that, things will be way easier for You to understand.

Cheers, Jack.

--
----------------------------------------------------------------------
My personal reading of the string "MicroSoft" expands to "NanoWeak"...

What you need to do depends on how what the Linksys DSL "modem" does
and what the ISP requires.  If the ISP requires PPPoE then either the
modem (actually a Terminal Adapter, TA) or you must provide PPPoE.

Quote:> here is what I think is right (but does not work :)

"Does not work" isn't enough.  How do you know it does not work, e.g.,
does everything look right but all the Internet applications you've
tried have failed?

Does it work for the MacOS?  If it does then you need to provide PPPoE.

Maybe this link will help:

http://ftp.eenet.ee/LDP/HOWTO/DSL-HOWTO/configure.html

--

PPP-Q&A links, downloads:                      http://ckite.no-ip.net/
/* Emacs vs vi:
   Sort of like a Swiss Army knife versus a rapier. */

Jack,

What you wrote is helping. Thanks.

Quote:> Well, very obviously, if IPs and netmasks are unclear to You, You
> definately want to read the Networking-HowTo as suggested.

it's not so much "what is a netmask? what is a IP address? do you or
don't you use a netmask of 255.255.255.0 for a class B IP address"
it's more of "where do I put the respective IP addresses". Once I
have that then the rest is easy.

Quote:> The idea of having a modem/router like Your LinkSys device is to
> use _one_ connection to Your ISP from _multiple_ clients on Your local
> net, therefore eliminating the need for some modem or similar device
> for each of the clients.

OK! got it. This is precisely what I wrote above for the router part EXCEPT:

(1) you clarify: NO PPP0 devices on the UNIX boxes. Thank you.
(2) must have eth0 devices configured on the UNIX boxes as class C i.e.
    192.168.1.xxx and netmask of 255.255.255.0. Also per my original email.
    OK. got this part: no PPP0 only eth0 to make the local/intranet work.
(3) must have a default route moving all non-192.168.1.xxx traffic
    to the router. OK. I know how to do that.

Quote:> tails of one account of Your choice to connect to Your ISP, and to (4)
> allow masquerading for Your 192.168.1/24 local subnet.

OK. That helps too. I just choose one of the uid/password pairs and
configure it.

What is NOT clear to me is that the linksys router/dsl-modem box has
*three* ways of connecting up to THE static-IP-assigned-by-ISP-address.
Each way poses a problem with my broken understanding:

1. by statically and manually configuring the WAN's TCP-IP params. The ISP
   assigned me an IP address of 64.xxx.xxx.xxx together with DNS, GW, and
   a primary route. Fine! I can plug all that into the router but where
   does the uid/password info go? That's what sent me the PPP0 devs in
   the UNIX boxes (which is wrong).
2. i can choose PPPoE WAN configure mode in the router. That asks me for
   the uid/password but does not give me a place to put in the assigned
   IP address, DNS, GW, or primary route. can it somehow do that by
   "decoding" my phonenumber (i.e. the DSL modem goes through my phone
   line) into the right data? That also sent me back into the UNIX boxes
   trying to configure out the PPP0 devices. But that's wrong.
3. i can choose PPTP WAN configure mode in the router. Now the router asks
   me for uid/password in addition to DNS, GW, and a primary route. This
   *seems* best but I cannot get the router to connect without an error.
   Also I doubt Cavtel (uses Verizon HW) deals with tunneling. Maybe my
   DSL uid/password is not my uid/password for my email.

Shane

Jack

Oops missed this question:

Quote:>tails of one account of Your choice to connect to Your ISP, and to (4)
>allow masquerading for Your 192.168.1/24 local subnet.

I thought the router did this for me? i.e. a packet comes from 192.168.1.100
which is meant for, say, www.google.com. So the router makes it appear
as if the packet really came from the router's WAN IP address (and then
"pops the stack" when the return pack from google comes). This is NAT or
masquerading.

Shane

[...]

Quote:>What is NOT clear to me is that the linksys router/dsl-modem box has
>*three* ways of connecting up to THE static-IP-assigned-by-ISP-address.

Be aware that not all DSL routers are capable of providing all possible
methods of PPPoE implementation.

Quote:>Each way poses a problem with my broken understanding:
>1. by statically and manually configuring the WAN's TCP-IP params. The ISP
>   assigned me an IP address of 64.xxx.xxx.xxx together with DNS, GW, and
>   a primary route. Fine! I can plug all that into the router but where
>   does the uid/password info go? That's what sent me the PPP0 devs in
>   the UNIX boxes (which is wrong).

If there's no option for that in your Linksys' configuration panel,
contact the support at Linksys. There's probably no way to get that
working if the router's firmware isn't providing the required fields.

Quote:>2. i can choose PPPoE WAN configure mode in the router. That asks me for
>   the uid/password but does not give me a place to put in the assigned
>   IP address, DNS, GW, or primary route. can it somehow do that by
>   "decoding" my phonenumber (i.e. the DSL modem goes through my phone
>   line) into the right data? That also sent me back into the UNIX boxes
>   trying to configure out the PPP0 devices. But that's wrong.

Your provider should assign you the defined IP address each time
you login via your userID/password combination, if you have signed
up for a static IP address. Give it a try, and let the IP address be
assigned dynamically by your ISP. I would assume that this will always
be the same IP address in this scenario. If not, ask the tech support
at your ISP to fix it.

Quote:>3. i can choose PPTP WAN configure mode in the router. Now the router asks
>   me for uid/password in addition to DNS, GW, and a primary route. This
>   *seems* best but I cannot get the router to connect without an error.

What errors?

Quote:>   Also I doubt Cavtel (uses Verizon HW) deals with tunneling. Maybe my
>   DSL uid/password is not my uid/password for my email.

This makes no sense. Of course your DSL password isn't your
"email password" (whatever that is).

Michael

Excellent.

But seriously, Your LinkSys should do that for You, correct. It was just
meant as a hint in case it didn't.

As for Your connection scenarioes, see Michaels post. - If You configure
Your router manually, the ISP can identify You by the physical line You
are using, so no need for user/password combo. (BTW, with DSL, there's
no such thing like a phone number; that belongs to the phone service.
The fact that both go over the same pair of copper does not "combine"
them into one...)

If You use the PPPoE way, the LinkSys must be capable of doing pppoe.
It will - most likely - use something very similar to pppd in linux
and will be able to accept a dynamically assigned IP from Your ISP,
along with routing and name service configuration.

In either case, it seems that You _may_ have some means of using the
LinkSys as a DNS proxy. - The routing information that is negotiated
between the LinkSys and Your ISP is of no interest for You: You just
tell Your local clients to use the LinkSys _inside_ IP (192.168.1.1)
as their default gateway. In essence, You needn't even know Your ex-
ternal IP to connect to the outside, but only when You want to reach
Your net _from_ the wild.

Cheers, Jack.

--
----------------------------------------------------------------------
My personal reading of the string "MicroSoft" expands to "NanoWeak"...