-----Original Message-----
From: Vicky [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 11, 2000 12:34 AM
To: [EMAIL PROTECTED]
Subject: Re: [newbie]I need Modem Help



okay I found drakconf :) right there on my desktop, when I look in
there  nothing is listed for modem. I am so confused , I thought I had
it installed okay , when i ran minicom I got the ok. I called my isp ,
they  said they dont support linux and even though the admin has a BS in
comp sci and is msce ,,etc He doesnt know anything about it and wasnt
sure if it is chap or pap. I havent seen any responses to my pleas for
help , this is the first maling list I have ever been on also. So even
if you cant help me with this problem could someone email me and tell me
if this got sent out to everyone ,   thx Vicky

---

Here's a message I gave to someone else about setting up their internet
connection...
Since this was originally about setting up a cable modem connection, you can
omit all parts related to local ethernet interface (eth0) at 10.0.0.1.

Everything else is the same vis-a-vis ppp...

Your ISP is probably using NT dialups, so you will have to use PAP
authentication... as indicated below...


---

I'm making the assumption that your modem is already correctly working and
you are logged in as root.

If not use the Mandrake control panel to set up the soft link to the modem
or whatever way you want to use...

Fire up an Xterm and run minicom.

If your /dev/modem link is correct, minicom should get back an "OK" from the
modem.

Exit minicom.

Ok, in X-Windows fire up Linuxconf. You can of course do this via the
Mandrake "control panel" if you wish or run it from an Xterm.

Since the most common view for Linuxconf is the non-tree view or non-gnome
view, you might need to turn off tree view so that we stay in sync...

Go into; "Control Files and System" and "Configure Linuxconf Modules".

TURN OFF "treemenu" and turn ON everything else except usermenu, uucp and
xterminals. Then restart Linuxconf.

If you had treemenu on before, it will look far different now.

The first screen that comes up is Linuxconf's "main" control menu.

Click on "Networking".

This brings up a new Submenu. Notice that in the first "Client Tasks" page
you have an entry or two labeled; "PPP or SLIP dialout" and/or
"PPP/SLIP/PLIP".

Since I do not know which you'll see I'll proceed with "PPP/SLIP/PLIP".

Anyway start by clicking on "Basic Host Information".

Make sure the "Host Name" box reads the name of your machines FQDN...

I.E. router.mydomain.com

Click on "Adapter 1"

Make sure "Adapter 1" is enabled and has the Config mode set to "Manual".

Set the "Primary name+domain equal to your machine's FQDN...

Set the Aliases field to it's "Hostname" I.E. "router" (never type in the
quotes!) if you were using "router.mydomain.com".

IP Address should read 10.0.0.1
Netmask should read 255.0.0.0
Net device should read eth0
Kernel Module should correspond to your adapter card.
If you are using a (preferable) PCI lan card, I/O port and IRQ should be
blank.

Click "Accept".

At the "Network Configurator" Screen again click on "Routing and Gateways".

A new box appears. Click on "Defaults".

Another box appears. Next to "Default gateway" make sure the box is BLANK,
however check "enable routing" on, and click Accept.

At the previous screen click on "Other routes to networks".

If there is no entry on the new box, click "add".

In the Gateway field enter 10.0.0.1
In the destination enter 10.0.0.0
In the Netmask enter 10.255.255.255

Click Accept.

You should be back at the First NETWORK Configuration screen. Click on
PPP/SLIP/PLIP.

A new box appears... again blank.

Click on "Add".

Answer "PPP" for "Type of Interface" and click Accept.

For Configuration name, enter "ppp0".

In the phone number field, enter Ex-pressnet's telephone number.

Modem Port should read "/dev/modem"

TURN ON "Use PAP Authentication" and enter your Ex-pressnet USERNAME and
PASSWORD in UPPERCASE in the "Login name" and "Password" fields.

DO NOT click "Accept" yet, rather click "Customize".

A new box appears.

In the Hardware Tab, turn ON "Use Hardware Flow Control...", "Abort
connection on Well-Known errors...", and "Allow any user (de)activate..."

If you are going to use ex-pressnet's DNS (I don't) turn on "use the DNS of
the provider".

Next to "PPP options" type in "defaultroute" in lower case.

Now click on the "Communication" tab box.

Enter your modem's INIT string. "ATZ" or "ATZ&F1" might suffice for most
modems.
Modem dial command should read "ATDT".

Phone number should now read Expressnet's phone dialup, if not, enter it
here.

TURN ON "debug connection".

The first CHAT line (Expect), should read "TIMEOUT"
The second CHAT line (SEND), should read "5"
The third CHAT line (Expect), should read "~--"

Again never type the quotes unless I tell you to.

Now click on the "Networking" TAB.

Turn on "Set default route" and "restart link when connection fails".

You might or might not want to enter a dummy IP address for the bottom two
entries, I have nothing...

Now click on the PAP tab.

Username should read your ex-pressnet login name in UPPER case, if not enter
it.
Secret should read your ex-pressnet password in UPPER case, if not enter it.

Click Accept when this is correct and "quit" at the PPP/Slip/Plip box.

Click "Quit" at the Network Configurator box.

Click "Quit" again at the main Linuxconf box. Linuxconf will ask if you wish
to activate the changes. Let it. Finally exit Linuxconf and Xwindows.

Shutdown your Linux box.

With your Linux machine OFF, make sure that you have your LAN card connected
to the Cable modem box. Now TURN OFF the cable modem. Wait a few seconds and
then turn it back on. THIS IS IMPORTANT. If you do not turn it off at least
once, before bringing up Linux, the cable modem will NOT ARP your lan card.

Once the Cable modem is green again, turn on your Linux machine.

As it comes up, sometime during or after sendmail, it should begin to dial.

Any LAN activity bound for a "foreign" IP will cause the link to come up.
Sendmail counts, so it ends up bringing up the link almost every time.

You can later filter this so that the link comes up only when you want it
to, but first get things working then play with it later.

Now hopefully you have a connection with Ex-pressnet...

You might or might not have DNS working but first check your routes...

Type "ifconfig" in an Xterm.

eth0      Link encap:Ethernet  HWaddr 00:10:5A:04:36:65
          inet addr:10.0.0.1  Bcast:10.255.255.255  Mask:255.0.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3298675 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1639694 errors:0 dropped:0 overruns:0 carrier:2
          collisions:45911 txqueuelen:100
          Interrupt:9 Base address:0xe400

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:48654 errors:0 dropped:0 overruns:0 frame:0
          TX packets:48654 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

ppp0      Link encap:Point-to-Point Protocol
          inet addr:24.239.12.35  P-t-P:24.239.16.12  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:38139 errors:1 dropped:0 overruns:0 frame:1
          TX packets:180954 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10


You should see something much like the above, though without those high
numbered RX/TX packets... heh... I guess I never drop my phone line...

Now try pinging a remote address...

"ping 206.132.41.203"

PING 206.132.41.203 (206.132.41.203) from 24.239.12.35 : 56(84) bytes of
data.
64 bytes from 206.132.41.203: icmp_seq=0 ttl=243 time=168.2 ms
64 bytes from 206.132.41.203: icmp_seq=1 ttl=243 time=165.8 ms
64 bytes from 206.132.41.203: icmp_seq=2 ttl=243 time=179.8 ms
64 bytes from 206.132.41.203: icmp_seq=3 ttl=243 time=169.5 ms

--- 206.132.41.203 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 165.8/170.8/179.8 ms

If you get this far, you are "on the air" although you might still have DNS
problems...

Check this out by typing

"ping www.redhat.com"

If it works, have fun.. if not, you might have to configure your
resolver/bind/nameserver depending upon what you want to do.

Since my Linuxbox acts as a firewall/gateway for other machines, I run my
own nameserver. Linux handles this with aplomb.

Have fun!

-JMS
[EMAIL PROTECTED]

Reply via email to