Linux-Networking Digest #850, Volume #10 Wed, 14 Apr 99 03:14:11 EDT
Contents:
Re: Just a plain old IP address and dedicated line... (Don Baccus)
Mail server for Linux ([EMAIL PROTECTED])
diald: connect doesn't (Steve Farris)
Kernel Compile: Problem with 2.0.34 + RH 5.1 (Don Werve)
Re: Problem with outbound e-mail on 2.2.5 ("Gary S. Mackay")
DHCPD install glinch ("Hugo Th�riault")
netcart not detected - no dhcp (Bo Hedemark Pedersen)
Re: PPP and chat script problem (Lee Howes)
Red Hat 5.2 RAMDISK ("Jeremiah Daniels")
Virgin net/freeserve (Lee Howes)
Re: Is this Port Scanning? (READ THIS ONE) (Luca Filipozzi)
Re: Network Printer (Linux + MacOS + HP JetDirect) (Leslie Mikesell)
can't ping isp server ("RensFunHog")
Re: Plz help me!! pppd doesn't work. (Randy Sandberg)
----------------------------------------------------------------------------
Subject: Re: Just a plain old IP address and dedicated line...
From: [EMAIL PROTECTED] (Don Baccus)
Date: 13 Apr 1999 16:17:11 PST
In article <[EMAIL PROTECTED]>,
David R. Christianson <[EMAIL PROTECTED]> wrote:
>Which brings up another question; considering the price of cable modem
>services, why - when leasing a dedicated connection (even a dang 56k)
>and a single IP address - is the cost so <expletive deleted> high in
>comparison?
A full-time modem connection eats one of their dialtones
24/7 for one reason.
Out here in the PNW, ISPs are offering DSL with static IPs
for good prices, i.e. $25/month for two IPs and 1 gig tranfer
a month with extra gigs pro-rated at $10/mo. (the phone
company's charge for DSL is extra, $40/mo for 256/256, but
since you get a dialtone simultaneously you can get rid of
your second line if you have one)
--
- Don Baccus, Portland OR <[EMAIL PROTECTED]>
Nature photos, on-line guides, at http://donb.photo.net
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.misc
Subject: Mail server for Linux
Date: Tue, 13 Apr 1999 23:06:13 GMT
Ok everyone,
I was asked to install a mail server for my business using Linux. Now, I know
a few things about Linux, but I have never set up a mail server for Linux. I
know that the Red Hat distribution comes with sendmail already set up, but
can I access this through the internet? I mean, can I write to
[EMAIL PROTECTED] and have it appear in teh mailbox of root? Can I access
this mailbox from my POP3 client anywhere else on the internet?
What program do I use and can someone point me to a FAQ or something so I can
learn how to do this?
- Steve
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: [EMAIL PROTECTED] (Steve Farris)
Subject: diald: connect doesn't
Reply-To: [EMAIL PROTECTED]
Date: Wed, 14 Apr 1999 05:59:54 GMT
I am trying to set up a 486 as IP-masquarade / firewall for a small home
network. Being as this is my first linux box, I expect to make mistakes
and have to sort my way through faqs and manuals to get things working.
I have done alright up to now. I have run out of ideas for getting diald
to work, so I turn to the newsgroups. I hope this post isn't too long, but
I want to provide what I hope is the important piece of information that I
am doing wrong.
I have set up pppd to dial my isp (which gives my a dynamic ip address). I
have ip-masquarade working, and have been able to establish a simple
firewall. So the only piece of the puzzle is to get diald working. I
downloaded the distribution along with the latest patch, ran the patch, did
my make file, make, make install. When I start diald, I can see it start
slip (through the /var/log/message file). I see a sl0 device in my
ifconfig.
However, if I try to do anything which requires a connection, nothing
happens. Ping will just sit there, or sometimes give me a host unknown. I
tried running pppd after diald was running, and managed to connect but
nothing worked since the default route is now through slip which goes
nowhere.
I am running Caldera 1.2 (kernel 2.0.33, pppd 2.2.0, slip 0.8.4). Slip is
loaded using kernld (does this matter?)
My diald.log file gives me outputs similar to these: Calling site
192.168.0.12. Disconnected, call duration 1 seconds. IP transmitted 84
bytes, received 0 bytes. From my messages file, I see the following
activity: Running connect. Connect script failed. Waiting 30 sec before
clear to dial.
Following are relevant scripts.
My diald.conf file:
mode ppp
fifo /etc/diald/diald.ctl
accounting-log /var/log/diald.log
connect /usr/diald/connect
device /dev/modem
speed 115200
modem
lock
crtscts
local 192.168.0.11
remote 192.168.0.12
dynamic
defaultroute
include /usr/lib/diald/standard.filter
ip-up /etc/ppp/ip-up
ip-down /etc/ppp/ip-down
I tried using the example connect script that came with the diald
distribution (putting in my relevant info where appropriate). When that
didn't work, I tried using the chat-script I use for pppd (see below). The
diald manual said to eliminate most of the stuff I had in my options file
for ppp, so my options file is blank when trying to use diald.
This is my options file for ppp:
connect "usr/sbin/chat -v -f /etc/ppp/chat-script"
/dev/modem 38400
modem
crtscts
defaultroute
noipdefault
kdebug 1
This is my ppp chat-script:
ABORT BUSY
"" ATDT9722800
CONNECT ""
ogin: USERNAME
ssword: PASSWORD
Using this setup, pppd works fine. It connects when called (although the
only way I can figure to close a connection is using kill and the pid # I
get from ps. There's got to be a better way...)
If anyone has any tips or pointers, I am at a loss. Thanks!
==========
Steve Farris, [EMAIL PROTECTED]
"Computers are really reliable things that do everything you want
them to do and nothing else." --Linus Torvalds
------------------------------
Date: Wed, 14 Apr 1999 04:48:33 +0000
From: Don Werve <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.help,comp.os.linux.questions,comp.os.linux.setup
Subject: Kernel Compile: Problem with 2.0.34 + RH 5.1
Sorry about the crosspost, but this seems to apply to the above
newsgroups.
I'm running RedHat 5.1, with the [included] 2.0.34 kernel -- I'd like to
re-compile the kernel to include NE2000 support as well as to optimize
it for a Pentium, as I've got an AMD K6-2/333MHz system and I've noticed
that optimized kernels tend to run more quickly than the 'default' i386
Kernel. I know I should upgrade to the 2.2 series kernel, but I'd like
to re-compile the kernel included with my distro before I try doing any
'massive' upgrades -- one step at a time, if you will.
I've tried to compile the kernel before with the following pattern:
make mrproper; make {xconfig | menuconfig}; make dep; make clean;
make zimage; make modules; make modules_install
I can get the kernel to compile fine, but when I load it, I get an error
about /lib/modules/preferred when I boot. The system will run, but none
of the modules will function correctly, such as my vfat support or ppp
support.
It's irritating as hell, and I had to re-install Linux to re-gain
functionality for my system. I'd still like to re-compile the kernel,
and install the NE2000 module, but I want to get this issue resolved
first.
Thanks in advance for the help! :)
Please address replies to my mailbox.
=====================================================
Don Werve -- http://www.iveleague.org/hari/index.html
E-Mail: <[EMAIL PROTECTED]>
"Never take life seriously -- after all, you don't
get through it alive."
- Anonymous
------------------------------
Date: Mon, 12 Apr 1999 18:44:25 -0400
From: "Gary S. Mackay" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: Problem with outbound e-mail on 2.2.5
Glad to hear someone else is having the same problem. I was beginning to
think I was crazy! I "think" I've narrowed it down some. I switched from
an internal Diamond 33.6 modem to an external Diamond 56k and everything
seems to be working now. My guess is that there is something fishy with
one of the drivers in the 2.2.x kernel.
- Gary
Edward Vale wrote:
>
> Michael J Surette wrote:
> >
> > "Gary S. Mackay" wrote:
> >
> > > Since I upgraded my RedHat 5.2 box to the newest
> > > ppp/kernel/diald/dialmon/etc., my users have been able to do everything
> > > except send mail. No matter what OS, email client, etc they use, NO
> > > email will go. They can browse (masq is working), receive e-mail, ftp,
> > > newsgroups, etc., they just can not send mail. As a test I setup an old
> > > 486 with the stock RedHat 5.2 (2.0.36) w/ ppp-2-3-5, and everything
> > > works just fine. I guess one solution is to leave well enough alone, but
> > > being a computer geek, I'd like to know why the new stuff won't work.
> > > (Same modem, phone line, ISP, etc.) Any ideas?
> > >
> > > --
> > > Edison Information Technologies
> > > P.O. Box 554
> > > Milan, OH 44846-0554
> > > 419.499.7040
> > > [EMAIL PROTECTED]
> > > --
> >
> > You need an mta running. On Stampede/Slackware which I am familiar with
> > that would be sendmail.
>
> You don't need sendmail running to SEND mail, only to receive it.
> BTW I have the exact problem as the original poster (with 2.2.1).
>
> > Another possibility is that your ipfw isn't allowing port 25 traffic
> > through.
> >
> > HTH
--
Edison Information Technologies
P.O. Box 554
Milan, OH 44846-0554
419.499.7040
[EMAIL PROTECTED]
--
------------------------------
From: "Hugo Th�riault" <[EMAIL PROTECTED]>
Subject: DHCPD install glinch
Date: Wed, 14 Apr 1999 01:56:30 GMT
hi all
using red hat 5.2 with kernel 2.0.36
and having a problem installing dhcpd, heres the error message i get when
typing the make command
cc -g -DLINUX_2_0 -c dhcpd.c -o dhcpd.o
make: cc: Command not found
make: *** dhcpd.o error 127
and didn t find any cc package????
any ideas
thanx hugo
------------------------------
From: Bo Hedemark Pedersen <[EMAIL PROTECTED]>
Subject: netcart not detected - no dhcp
Date: Wed, 14 Apr 1999 08:12:32 +0200
The first time I installed Redhat 5.1 it automatically
detected my
netcard and sat up a dhcp client for me.
The second time (on the very same machine) it did not
detect my netcard.
I have now installed the dhcpd package, but the
dhcpd.conf file is
missing and the README doesn't seem to mention it.
Is there anyway that I can run the detection program
used in the Redhat
installation proces?
Thanks,
Bo
------------------------------
From: Lee Howes <[EMAIL PROTECTED]>
Subject: Re: PPP and chat script problem
Date: Wed, 14 Apr 1999 07:12:53 +0100
Reply-To: [EMAIL PROTECTED]
My Send/receive pairs appear correct based on minicom which connects, tells me
about the IP addresses that it is connecting then disconnects with no error
message. Do you know why this disconnection would have happened?
Brandon wrote:
> Abhilash wrote:
>
> > Ryan,
> >
> > I did check out the url provided by ts and found it to be useful. I had
> > exactly the same problem as you for my new RHL installation. Configure ppp
> > using linuxconf and make sure you enable PAP; you should be connected to
> > your ISP in no time.
> >
> > Goodluck
> > Abhilash
> >
>
> I had the erorr below (not 8 bit clean) one time during my configuration but
> it wasn't b/c of PAP/CHAP. I had it b/c I had not put in the right
> expect/send strings. After using minicom to be sure of what I need to tel
> the chat script to expect I , of course, then knew what exaclty to send and
> I put that info into my chat script and it worked fine.
>
> brandon
>
> > ts wrote:
> > > Ryan,
> > > Your problem appears to be PAP/CHAP related. Check out the url below and
> > read
> > > this ppp set-up. If you follow it straight through (don't skip
> > anything!!) you
> > > should be connected in no time.
> > > http://axion.physics.ubc.ca/ppp-linux.html
> > >
> > > Regards,
> > > ts
> > >
> > > Lee Howes wrote:
> > >
> > > > Please E-mail replies to [EMAIL PROTECTED], not reply to this message.
> > > >
> > > > This is my log of the communication with virgin net for my ppp
> > connection.
> > > > This clearly does not work, do you have any idea what addition could
> > make
> > > > this work. (NOTE: password and username converted to dashes)
> > > > Apr 10 09:41:53 localhost pppd[668]: pppd 2.3.5 started by root, uid 0
> > > > Apr 10 09:41:54 localhost chat[669]: send (ATDT0645505400^M)
> > > > Apr 10 09:41:54 localhost chat[669]: expect (505400)
> > > > Apr 10 09:42:13 localhost chat[669]: ATDT0645505400
> > > > Apr 10 09:42:13 localhost chat[669]: -- got it
> > > > Apr 10 09:42:13 localhost chat[669]: send (^M)
> > > > Apr 10 09:42:13 localhost chat[669]: expect (ogin:)
> > > > Apr 10 09:42:33 localhost chat[669]: ^M^M
> > > > Apr 10 09:42:33 localhost chat[669]: login:
> > > > Apr 10 09:42:33 localhost chat[669]: -- got it
> > > > Apr 10 09:42:33 localhost chat[669]: send (--user--^M)
> > > > Apr 10 09:42:33 localhost chat[669]: expect (assword:)
> > > > Apr 10 09:42:33 localhost chat[669]: ^M
> > > > Apr 10 09:42:53 localhost chat[669]: login: --user--^M
> > > > Apr 10 09:43:03 localhost chat[669]: Password:
> > > > Apr 10 09:43:03 localhost chat[669]: -- got it
> > > > Apr 10 09:43:03 localhost chat[669]: send (--password--^M)
> > > > Apr 10 09:43:03 localhost pppd[668]: Serial connection established.
> > > > Apr 10 09:43:13 localhost pppd[668]: Using interface ppp0
> > > > Apr 10 09:43:13 localhost pppd[668]: Connect: ppp0 <--> /dev/ttyS2
> > > > Apr 10 09:43:13 localhost pppd[668]: sent [LCP ConfReq id=0x1 <magic
> > > > 0x9a42a177> <pcomp> <accomp>]
> > > > Apr 10 09:43:40 localhost last message repeated 9 times
> > > > Apr 10 09:43:43 localhost pppd[668]: LCP: timeout sending
> > Config-Requests
> > > > Apr 10 09:43:43 localhost pppd[668]: Connection terminated.
> > > > Apr 10 09:43:43 localhost pppd[668]: Receive serial link is not 8-bit
> > > > clean:
> > > > Apr 10 09:43:43 localhost pppd[668]: Problem: all had bit 7 set to 0
> > > > Apr 10 09:44:03 localhost pppd[668]: Hangup (SIGHUP)
> > > > Apr 10 09:44:03 localhost pppd[668]: ioctl(TIOCSETD, N_TTY):
> > Interrupted
> > > > system call
> > > > Apr 10 09:44:04 localhost pppd[668]: Exit.
> > > >
> > > > Thank you, Lee Howes
> > >
> >
> > ------------------ Posted via SearchLinux ------------------
> > http://www.searchlinux.com
------------------------------
From: "Jeremiah Daniels" <[EMAIL PROTECTED]>
Crossposted-To: comp.protocols.smb,comp.os.linux.setup
Subject: Red Hat 5.2 RAMDISK
Date: Tue, 13 Apr 1999 00:01:07 -0700
Does anyone know how to make a bootdisk that does NOT load RAMDISK or a way
to bypass it or something. Because Linux wont install on this 486sx with
only 4 megs of ram.
Jeremiah
Cybertribe
------------------------------
From: Lee Howes <[EMAIL PROTECTED]>
Subject: Virgin net/freeserve
Date: Wed, 14 Apr 1999 07:24:22 +0100
Reply-To: [EMAIL PROTECTED]
IF anyone connects to virgin net or freeserve in the UK could they
please send me their ppp scripts (excluding username and password
obviously, except for any addithional bits that needed to be added to
username to get it to work). This would (probably) be very helpful.
Thank you,
Lee Howes
------------------------------
From: [EMAIL PROTECTED] (Luca Filipozzi)
Subject: Re: Is this Port Scanning? (READ THIS ONE)
Date: Tue, 13 Apr 1999 17:18:32 -0700
In article <7f0ksm$ui3$[EMAIL PROTECTED]>, nicolas_bourbaki@my-
dejanews.com says...
>
>
> Sorry about the formatting in the above post - it looked much better in the
> Preview than it did after posting. Thus I am reposting the message here with
> different formatting which, I hope, will make it readable.
>
> ===========================
>
> Hi guys,
>
> I just wanted to ask those experienced in network security if the following
> "edited" region, copied from my /var/log/messages file, is what it looks like
> to be port scanned? I "edited" the copy to protect the innocent, so I've made
> the following changes:
>
> <my-machine> = substitution for the actual name of my firewalling Linux
> machine
>
> <offending-IP> = substitution for the actual IP address (www.xxx.yyy.zzz) of
> the external machine
>
> <my-IP> = substitution for the actual IP address (www.xxx.yyy.zzz) of my
> machine
>
> Below is the "edited" region of my /var/log/messages file:
>
> ----------------------------------------------------------------------
>
> Apr 11 03:50:48 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:4762 <my-IP>:110 L=44 S=0x00 I=6175 F=0x0000 T=45
>
> Apr 11 03:50:51 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:4762 <my-IP>:110 L=44 S=0x00 I=6309 F=0x0000 T=46
>
> Apr 11 03:50:53 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:6139 <my-IP>:79 L=44 S=0x00 I=6385 F=0x0000 T=46
>
> Apr 11 03:50:56 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:6139 <my-IP>:79 L=44 S=0x00 I=6512 F=0x0000 T=46
>
> Apr 11 03:50:57 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:7326 <my-IP>:23 L=44 S=0x00 I=6575 F=0x0000 T=46
>
> Apr 11 03:51:01 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:7326 <my-IP>:23 L=44 S=0x00 I=6680 F=0x0000 T=46
>
> Apr 11 03:51:02 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:9081 <my-IP>:143 L=44 S=0x00 I=6746 F=0x0000 T=46
>
> Apr 11 03:51:06 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:9081 <my-IP>:143 L=44 S=0x00 I=6846 F=0x0000 T=46
>
> Apr 11 03:51:07 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:10679 <my-IP>:53 L=44 S=0x00 I=6914 F=0x0000 T=46
>
> Apr 11 03:51:11 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:10679 <my-IP>:53 L=44 S=0x00 I=7009 F=0x0000 T=46
>
> Apr 11 03:51:13 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:12321 <my-IP>:635 L=44 S=0x00 I=7079 F=0x0000 T=46
>
> Apr 11 03:51:16 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:12321 <my-IP>:635 L=44 S=0x00 I=7167 F=0x0000 T=46
>
> Apr 11 03:51:18 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:12647 <my-IP>:143 L=44 S=0x00 I=7226 F=0x0000 T=46
>
> Apr 11 03:51:21 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:12647 <my-IP>:143 L=44 S=0x00 I=7328 F=0x0000 T=46
>
> Apr 11 03:51:28 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:14925 <my-IP>:110 L=44 S=0x00 I=7555 F=0x0000 T=46
>
> Apr 11 03:51:31 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:14925 <my-IP>:110 L=44 S=0x00 I=7656 F=0x0000 T=46
>
> Apr 11 03:51:32 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:16413 <my-IP>:110 L=44 S=0x00 I=7719 F=0x0000 T=46
>
> Apr 11 03:51:36 <my-machine> kernel: IP fw-in deny eth0 TCP
> <offending-IP>:16413 <my-IP>:110 L=44 S=0x00 I=7823 F=0x0000 T=46
>
> ----------------------------------------------------------------------
>
> It sort of looks like to me that someone at <offending-IP> was testing access
> every few seconds from a number of different ports from <offending-IP> to
> <my-IP> on a number of priviledged ports including 110 (POP), 79 (finger), 23
> (telnet), 143 (IMAP), 53 (DNS), and 635 (RLZ DBase).
>
> Is this a proper interpretation? If so, what should I do to better protect my
> machine? What should I do to check if they actually succeeded in breaching my
> firewall? (I mean, all I logged was their failures, not their successes.) Is
> there anything else I should do, such as trying to contact the administrator
> of the <offending-IP> machine?
>
> Thanks,
> Nick B.
>
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>
Yes, it looks like you were port scanned.
As for securing your machine.... run as few services as possible and make
sure you keep up on patches for those services that you do run (including
those machines to which you port-forward packets).
Yes, you could contact the offending-IP's ISP. Port scanning isn't
illegal, however, when applied against a machine not under one's
administration, it serves only one purpose: to discover which services
are running so that appropriate exploits can be applied (IMO).
--
Luca Filipozzi <[EMAIL PROTECTED]>
------------------------------
From: [EMAIL PROTECTED] (Leslie Mikesell)
Subject: Re: Network Printer (Linux + MacOS + HP JetDirect)
Date: 14 Apr 1999 01:38:31 -0500
In article <7enr44$na6$[EMAIL PROTECTED]>,
Nick B. <[EMAIL PROTECTED]> wrote:
>
>I also couldn't get the MacOS to tell me the IP address that was assigned to
>the HP JetDirect card in the printer. I did find out from the printer what it
>thinks is its Appletalk name, but this name did not work in various attempts
>at placing it in /etc/printcap or /etc/hosts. Again, the reason why none of
>this worked (nor should it have worked) is, I believe, because there is
>nothing on the Linux side that "ties" the known printer hardware address to
>the known printer Appletalk name. In other words, I need the IP address in
>order to make this connection in the Linux world.
>
>I think what I want is a form of RARP, that is, I want the printer to reply
>to a RARP query using the hardware address by returning its assigned IP
>address. I don't know how to do this however. Is there such a thing as a
>"harware ping", i.e,, a ping-like command where you specify the hardware
>address and it returns the NIC's IP address? Sorry for my naivete.
It isn't going to have an ip address unless you have assigned one
to it. You can do this with BOOTP using the dhcpd server on
Linux. However, if the card is so old, it may not handle lpd
protocol or using multiple protocols very well. If you can't
update the firmware you might try either using a parallel port
connection from the linux box or perhaps installing netatalk
on the linux box so you can chat with the mac and printer via
appletalk.
Les Mikesell
[EMAIL PROTECTED]
------------------------------
From: "RensFunHog" <[EMAIL PROTECTED]>
Subject: can't ping isp server
Date: Wed, 14 Apr 1999 01:40:36 -0500
I just got my pppd working. I view ifconfig and route -n and see my isp
server network address. However when I try to ping it or any other network
addresses nothing replys. I am able to ping my own PC network address and
another PC network address that is connected to my #2 node network. I am
using 10.0.0.0 network address 1 & 2 station. Any ideas. Thanks..
------------------------------
From: Randy Sandberg <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Plz help me!! pppd doesn't work.
Date: Tue, 13 Apr 1999 23:18:24 -0700
Minjung Kim wrote:
>
> Hi!
> I'm newbie in linux.
> I tried to connect to my ISP with ppp.
> --- #>/usr/sbin/pppd /dev/modem 57600 debug connect "/usr/sbin/chat -v
> `` AT OK ATD01432 CONNECT '\d\c'"
> But the modem didn't dial and log message is below.
> ---
> Apr 13 12:22:35 localhost pppd[341]: pppd 2.3.5 started by root, uid 0
> Apr 13 12:22:36 localhost chat[342]: expect (AT)
> Apr 13 12:23:21 localhost chat[342]: alarm
> Apr 13 12:23:21 localhost chat[342]: Failed
> Apr 13 12:23:21 localhost pppd[341]: Connect script failed
> Apr 13 12:23:22 localhost pppd[341]: Exit.
> Apr 13 12:24:35 localhost kernel: PPP: ppp line discipline successfully
> unregistered
> ---
> How can I do ??? Plz help me!!
> My sytem is RedHat 5.2.
I'm a newbie too but I think I know what's going on. Make sure that the
sim link /dev/modem points to either /dev/cuax (where x=0,1,2, or 3
which depends on the com port your modem is connected to) for a box
stock RedHat 5.2 OR /dev/ttySx (where x=0,1,2, or 3 which depends on the
com port your modem is connected to) is you've updated to a 2.2.x
kernel.
1) Therefore, if you just installed RedHat 5.2 and you haven't updated
the kernel and you have an external modem connected to Com1 then you'd
want to see the following line when you do a "ls -l modem" in the /dev
directory:
lrwxrwxrwx 1 root root 5 Apr 13 22:08 /dev/modem ->
cua0
2) If on the other hand, you're using the same out of the box RedHat
5.2, but you've got an internal modem using the Com2 port then you'd
want to see this instead:
lrwxrwxrwx 1 root root 5 Apr 13 22:08 /dev/modem ->
cua1
3) Okay, now lets say you've got the same setup as scenario one but
you've updated your kernel to version 2.2.5...like I just did a few
moments ago and learned the following. You'll want to see this instead:
lrwxrwxrwx 1 root root 5 Apr 13 22:08 /dev/modem ->
ttyS0
a) Now, cd to your /dev directory.
b) type "ls -l modem"
c) What do you see?
If it's wrong you'll need to do the following steps:
a) First make sure you're root by typing "whoami"
b) Okay, now delete /dev/modem (i.e., "rm modem") you'll probably be
asked if it's okay to delete modem...just answer yes.
c) Now create a new sim link by doing ONE the following depending on
which version of the kernel you're using as well as which Com port your
modem is connected to:
1) ln -s cua0 modem
OR
2) ln -s cua1 modem
OR
3) ln -s ttyS0 modem
OR
4) ln -s ttyS1 modem
P.S. In X (i.e., logon as root and type "startx") there is a modem
control panel which will do this automatically for you IF YOU'RE USING
kernel 2.0.x. Other wise it's best to do it as I've shown above. Also,
there is a network control panel that allows you to type this info in.
This does seem to work for both the 2.0.x as well as the 2.2.x kernels.
Well, I hope this helps. Moreover, like I said...I'm a newbie too so if
any of you guru types see a flaw in my logic please let us both know.
Bye for now,
--
Randy Sandberg <[EMAIL PROTECTED]>
Understanding is always the understanding of a smaller problem
in relation to a bigger problem. -- P.D. Ouspensky
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.networking) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Networking Digest
******************************
