Linux-Networking Digest #539, Volume #11 Tue, 15 Jun 99 08:13:48 EDT
Contents:
Re: WIn 95 printing over SAMBA ("Ferdinand V. Mendoza")
Re: Setting up a two computer CSLIP network. (Dr Paul Kinsler)
Genius 56K modem + Redhat 6.0 doesn't work ! ([EMAIL PROTECTED])
RE: Linux with ISDN router ? Advice ?! ("Carlos RCU")
Re: 3com-ing a netwerk (Skaya)
Re: 3c905b problem with 2.0.36 (Skaya)
Re: 3C509B Etherlink III (Ben Hodson)
Re: in.ftpd : login failed (Richard van Es capgemini.nl>)
Re: printing setup problems ([EMAIL PROTECTED])
Re: Modem initial string (Juan Carlos Larroya Huguet)
Re: The sendmail command takes 60 seconds to finish ?????????? ([EMAIL PROTECTED])
Sharing printers between Linux and Win95 ("S.R.F. Materie Plastiche S.p.A")
Re: PPP Scripting... Help?
Re: Sendmail POP (Malware)
Re: Trouble with Caldera NetWare Client (Malware)
Re: Linux Win98 Networking Problems!! (Rafo)
PPP Problems (Mick Farmer)
----------------------------------------------------------------------------
From: "Ferdinand V. Mendoza" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: WIn 95 printing over SAMBA
Date: Tue, 15 Jun 1999 13:30:05 +0400
Oh! Oh, I found the answer this morning when I
tried again. On the Printer properties I have to
capture the port (this is a clickable button) and
put in the LPT1 port and the correct path to
my server which is the \\$HOSTNAME\lp,
enable the "reconnect at logon" checkbox and
it was a smooth ride afterwards.
Ferdinand
>
------------------------------
Crossposted-To: comp.os.linux
From: [EMAIL PROTECTED] (Dr Paul Kinsler)
Subject: Re: Setting up a two computer CSLIP network.
Date: Tue, 15 Jun 1999 10:00:02 +0100 (BST)
In comp.os.linux.misc Jon Striley <[EMAIL PROTECTED]> wrote:
> I have a null modem cable hooked to the parallel port on the redhat
> box, and a serial port on the SuSE machine. I want to have both
> computers just talk/ aka. ping as a first priority. Eventually I would
> like both to be able to print via a printer on the SuSE box, and
> connect to the internet via the modem on the Redhat box. I would also
> like both systems to be able to share files. Right now I have nothing,
> not even a ping gettings through. I am totally lost. I think I can
> figure out everything if I just get them to talk. Could someone tell me
> how to get them taking? Thanks.
To connect serial-to-serial using SLIP, I use my script
http://bloch.leeds.ac.uk/kinsler/linux/script/Slip,
which I run on each machine to do get them to talk by slip.
Even if you dont like the script, you can see the sequence
of commands.
--
==============================+==============================
Dr. Paul Kinsler
Institute of Microwaves and Photonics
University of Leeds (ph) +44-113-2332089
Leeds LS2 9JT (fax)+44-113-2332032
United Kingdom [EMAIL PROTECTED]
WEB: http://www.ee.leeds.ac.uk/staff/pk/P.Kinsler.html
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.hardware,comp.os.linux.setup
Subject: Genius 56K modem + Redhat 6.0 doesn't work !
Date: Tue, 15 Jun 1999 09:25:10 GMT
Hi,
I have just got a Genius 56K PnP modem to replace my old ISA one. I
have set the BIOS to disable Com2 and told it I have a non PnP OS.
I have win98 on the same machine and according to it and the diags
that came with the modem it is working fine, however I cannot dial
out using "Dial up Networking".
I got the irq and the io ranges for the modem and booted into linux,
which is RedHat 6.0. I tried to use setserial to set the irq and i/o
ranges for /dev/ttyS1 that win98 had given me. The irq was fine, but
how do I set a pair of i/o ranges ? Win98 gave me two ranges for the
modem, but it seems that setserial will only allow me to set one
value for the ioport.
I set the ioport to be the low values of the first range win98
specified, but when I then ran setserial it did not identify the
UART correctly, it just said it was "unknown". When I ran it on
/dev/ttyS0 it was fine. Unsurprisingly when I ran minicom and
just typed "at" I got no reponse from the modem. Chat just said
that it couldn't get the terminal i/o.
Any ideas or suggestions as to what I may be missing. To the best
of my knowledge this is not a winmodem.
Thanks a lot.
Simon.
P.S If possible please copy me on your reply.
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: "Carlos RCU" <[EMAIL PROTECTED]>
Subject: RE: Linux with ISDN router ? Advice ?!
Date: Tue, 15 Jun 1999 11:39:36 +0200
> Greetings
>
> We have a small LAN here of Win 95 machines, with an ISDN router on the
> network. The router is set as the default gateway on the windows
> machines, and this works easily and effectively.
>
> I have now installed linux on one of the machines, and would like it to
> access the internet in a similar way.
>
> Is there a howto for configuring a network in this way ? Has anyone done
> it, and know the pitfalls ? How do I set up the rooting, and is there
> any danger of the linux machine demanding a dial-up every couple of
> minutes during the night ?! And is there any smart software that might
> be able to tell me whether the router is online or not ???
>
> Any help or advice with this would be greatly appreciated !
>
> Thank you.
>
> Cheers
>
> Jamie.
If you installed RedHat try with 'netconf'.
For making Linux to reach Internet use the command 'route' to see your
routing tables.
At least you should have a root for loopbacking (lo) to 127.0.0.0 and
another one for reaching your network.
You should add the default route for Internet like this:
route add default gateway x.x.x.x eth0
Where x.x.x.x is the IP address of your router and eth0 is the device name
of your network card.
Hope this is helpful to you.
Salu2
Carlos
Try man route to see how it works.
------------------------------
From: Skaya <[EMAIL PROTECTED]>
Subject: Re: 3com-ing a netwerk
Date: Tue, 15 Jun 1999 12:33:02 +0200
Reply-To: [EMAIL PROTECTED]
> > I don't think 486's are going to be able to keep up with 100Mbps
> > traffic. For one thing, most 486's that I have seen are not pci
> > equipped, and I don't think you will find any 100Mbps isa NIC's. I
> > don't think they exist. So you might be back to 10Mbps after all!
> That is surely true, but the core machines of my network will be in the
> 300-350 mhz with a 100mhz bus, so hopefully the 100Mb (roughly speaking)
> NIC will be the bottleneck in those systems (I'm still building them).
well, I have 4 * 486 at home. 3 of them are PCI systems.
of course, they can't handle the load of a 100 mbps network.
but one of them is the gateway between the 10 mbps and the 100 mbps
network (10 is for macs, internet access, and x-terminals ; 100 is for
the big boxes and my workstations.)
by the way, a slow pentium (p100...) will handle 100 mbps without
problems.
the point is : how will you feed the network? my ide disks (yuck!) can't
spit more than 3 mbytes per sec, so THEY are the bottleneck in the
system.
> don't know if you can mix machines communicating at 10 & 100 to the same
> hub/switch. (that's one of the many things I hope to learn through all
> of this).
it depends :)
-generally, 100 mbps switches also perform 10 mbps. and that's one of
the
best ways to mix 10 and 100 mbps networks.
-generally, hubs don't mix very well. my 100 mbps hub is a 100 mbps
ONLY,
and the led won't even lit if I plug a 10 mbps NIC. there are 10/100
hubs,
but all those I saw were crap (except when fitted with a so-called
"switch
module", which doesn't turn it into a switch, but adds a 2-port switch
between the 10 and the 100 mbps segment). you must know that a 10/100
hub
is two hubs all-in-one, with two separate collision domains, and that
doesn't
mix pretty well.
-generally also, switches can do full duplex. I organize lan-parties
(quake
and so on) and we have for this purpose a few costy switches, all full
duplex.
of course, your mileage may vary, and I expect comments about what I
said
above.
> But at the worst the 486s will have to be a seprate network,
> after I get it working then I get to figure out how to connect the 2
> (100 and 10) networks together.
I choosed a 486 fitted with a intel etherexpress pro 100 card and a hp
10
mbps adapter. runs perfectly. I have 2 separate IP subnets. I think it
can
be a hell of a bitch to configure if you are a totally neophyte to IP
networks, but with the help of the Network Administration Guide (by Olaf
Kirsch, available on-line frome the LDP and hardcopy from O'Reilly, with
very good french translation) it should be very easy.
switches are more easily configured but cost $$$ . We only need them
for the big, bad networks (with more than 50 clients all playing quake
and leeching quake mods from ftp ;)
> Once I'm done with my networking experiments, I will have a really
> powerfull distributed workstation, with certain aps being run via X to a
> "main" workstation that I will run my desktop and small apps, with lots
> of NFS mounted directories from the non-486 machines, so I will be a
> bandwith hog inside my own little network. Can I help it if I like to
> burn CDs, listen to mp3s, encode mp3s, compile kernels, scan pictures,
> download the latest and greatest from debian.org, and play quake all at
> once...
a few comments... it's perfectly possible. I did all that with my 10
mbps
network. I went for 100 mbps because I had an offer for cards and hubs.
I can even listen to mp3 on a 486 x-terminal (decompression occurs on a
p200 mmx on the above floor, is piped from mpg123 thru rsh, and then
arrives on the x terminal in pcm format, ready to play with bplay or
amp).
My two cents tip about burning CDRs : instead of mounting the "source"
thru samba or NFS, try making an iso image on the machine which holds
the source, and then pipe it thru rsh to a cdrecord process on another
machine. If you can't figure what I mean, feel free to ask details.
> > As far as compatibility goes, all hubs seem to speak tcp/ip. Not all
> > hubs will forward DHCP requests, however.
> Aaaah, that's an interesting little factoid!
in fact, NO hub speak tcp/ip, except the managed ones. hubs don't
understand
tcp/ip, they forward it without any question or mood. so they will
forward
DHCP requests. the same is true for switches.
my word about managed hubs/switches : if you get one for the same price
of an unmanaged one, go for it ; else it's not very useful. I have
a dlink 1612tx ; that allows me to telnet it, so I can watch statistics,
but the main purpose will be to consult traffic logs thru SNMP agents
(so you can make beautiful stats, like those made by IPAC)
------------------------------
From: Skaya <[EMAIL PROTECTED]>
Subject: Re: 3c905b problem with 2.0.36
Date: Tue, 15 Jun 1999 12:46:23 +0200
Reply-To: [EMAIL PROTECTED]
> first get dos setup prog for the card and set it to IRQ 10 or 11, but
> get it OFF of 15. Also disable PnP. then let Linux look for it.
am thinkink it won't work - pci cards can't be setup that way.
> >... I then replaced it with a 3com 3c905b 100 base Tx PCI
> >card. The system would not find the new card.
when your system boots, you should see (before lilo...) a panel
telling what pnp hardware has been detected. check if you see your
"ethernet adapter" (that is what should be displayed)
you can also use "lspci" - get it if it's not installed. it's a
very cool piece of software ;) listing everything on your pci bus.
> >... Coincidentally, I was installing
> >Sybase on this machine (which went fine BTW) and it did a scan of my
> >hardware and told me I had a 3c905b configured at IRQ 15 and 0x6500.
irq 15 is strange. normally irq 14 = first ide controller, and irq 15 =
second ide controller, and is generally not shareable.
> >a DOS environment, then use the configuration utility to set the card at
> >IRQ10 and 0x300. Then I hope the boot code will find the damn thing and
> >give me a working network link. I now find I don't have any actual DOS
> >system left, just Win 95. Well I don't see what else to do so tonight I
> >will boot w95 from floppy then try to run the configuration utilities.
try hitting shift+f5 when the fatidic "windows 95" text line appears.
it should take you to a command line.
my 2 cents tip : check you're not out of irqs (cat /proc/interrupts),
you
should have irq 9, 10, 11, or 12 free for use. good pci cards can share
interrupts (I have 2 * 3c905b and 1*intel etherexpress pro 100, and one
3com and the intel share perfectly)
my 3 cents tip : try to load the driver via modules. the driver you
should
use is "3c59x". Usually it doesn't make sense to compile net drivers
into
the kernel, except when :
- you want to make a diskless workstation (obviously...)
- you don't want modules (for security reasons or whatever...).
------------------------------
From: Ben Hodson <[EMAIL PROTECTED]>
Subject: Re: 3C509B Etherlink III
Date: Tue, 15 Jun 1999 11:37:56 GMT
There is a utility called 3c5x9cfg.exe (runs under dos - I have it on a
boot disk) that allows configuration of the card itself. I always turn
of pplug and play and set the IRQ and BASE address to something I know
to be free (/proc helps here).
Autoprobing can also be a bit funny so I usually have something lke ...
alias eth0 3c509
options 3c509 irq=10
In my /etc/conf/modules file to clear this up....
I've never had any problems with these cards once I've done that...
tara...
--
=========================================================
Ben Hodson, [EMAIL PROTECTED]
Philips Research Labs, Tel : +44 1293 815750
Redhill, Fax : +44 1293 815500
Surrey,
RH1 5HA
=========================================================
One world, One web, One program - Micro$~1 Promotional Ad
Ein Volk, Ein Reich, Ein Fuhrer - Adolf Hitler
=========================================================
------------------------------
From: Richard van Es <"richard.van.es<a"@t>capgemini.nl>
Subject: Re: in.ftpd : login failed
Date: Tue, 15 Jun 1999 13:01:58 -0500
peter wrote:
> <SNIP>
>
> and the use I tried to logon with (root) is also listed in /etc/ftpusers
>
> <SNIP>
This is what's wrong..................the file /etc/ftpusers lists the users
that are NOT allowed to ftp to this machine. If you want to ftp
with root, you should take root out of this file.
> what the hell is wrong here.
> (tcp/wrapper ist also not the problem, cause I come to the login ...)
>
> peter
>
> -----------------
> pilsl@
> ANTISPAM
> goldfisch.atat.at
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: printing setup problems
Date: Tue, 15 Jun 1999 06:51:18 -0400
L J Bayuk wrote:
> [EMAIL PROTECTED] wrote:
> >Matt Templeton wrote:
> >
> ><snip>
> >
> >> I can print from the local box, but on remote boxes I
> >> > receive an error:
> >> >
> >> > lpr: connect: Connection refused
> >> > jobs queued, but cannot start daemon
> >
> >Then I check the lpq and see this:
> >
> >emachine.markzee.net: waiting for queue to be enabled on pigpen
> >
> ><status of jobs queued>
> >
> >pigpen.markzee.net: lpd: /var/spool/lpd/lp: unknown printer
>
> This message means: The machine you are printing from is trying
> to send to an non-existant printer on the server. But I can
> guess more: I'll bet your printing machine's printcap has:
> :rp=/var/spool/lpd/lp:
> It should be just this:
> :rp=lp:
Thanks, that did it. Missed that in the docs somewhere....
--
Mark
------------------------------
From: Juan Carlos Larroya Huguet <[EMAIL PROTECTED]>
Subject: Re: Modem initial string
Date: Mon, 14 Jun 1999 21:44:23 +0200
RnJhbmsgWWFuIHdyb3RlOg0KDQo+IEkndmUgZ290IGFuIGV4dGVybmFsIHVzIHJvYm90aWNz
IG1vZGVtLCA1NkssIG1vZGVsIDU2ODYuIEkgd2FudCB0bw0KPiB1c2UgaXQgdW5kZXIgUkgg
NS4yLCBidXQgSSBjYW5ub3QgZmluZCBhIGdvb2QgaW5pdGlhbCBzdHJpbmcgZm9yIHRoaXMg
Z3V5LA0KPiBzbyB0aGF0IEkgZ290IGEgdmVyeSBzbG93IG1vZGVtIHNwZWVkLiAgRG9lcyBh
bnlvbmUga25vd3MgYWJvdXQNCj4gd2hhdCdzIHRoZSBpbml0aWFsIHN0cmluZyBmb3IgdGhp
cyBtb2RlbCBvZiBtb2RlbT8NCj4NCj4gVGhhbmtzIGEgbG90LA0KPg0KPiBGcmFuaw0KDQpJ
IGhhdmUgYSBVU1IgNTZLIE1lc3NhZ2UgbW9kZW0uIEluIG15IG1vZGVsIHRoZXJlIGFyZSBz
b21lIHByZXByb2dyYW1lZA0KcHJvZmlsZXMuDQpUcnkgQVRaMiAuIEl0IGdpdmVzIHRvIG1l
IDU2ayBWOTAgKFJlYWxseSA0NTY1NSBvciBzb21ldGhpbmcgbGlrZSB0aGF0KQ0KR29vZCBM
dWNrDQoNCkpDDQo=
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.mail.sendmail,comp.unix.aix,comp.unix.programmer
Subject: Re: The sendmail command takes 60 seconds to finish ??????????
Date: Tue, 15 Jun 1999 10:04:29 GMT
In article <7k518v$78d$[EMAIL PROTECTED]>,
"Louis Banens" <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> The last couple of weeks the sendmail command takes exactly 60
seconds to
> finish. Can anybody tell me what te reason could be ?
>
> RS6000 AIX 4.3
> Command: sendmail [EMAIL PROTECTED] <file
>
> Regards,
>
> Louis Banens
>
Hi louis
Do you use DNS ?
I know that the timeout for a DNS lookup when the DNS server is
unavailable is exact 60 seconds.
So check your /etc/resolv.conf file and see if your DNS server is valid.
You can also create a /etc/netsvc.conf file to change the hostname
lookup order like: hosts = local,bind
Brenzef
>
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: "S.R.F. Materie Plastiche S.p.A" <[EMAIL PROTECTED]>
Subject: Sharing printers between Linux and Win95
Date: Tue, 15 Jun 1999 12:56:00 +0000
Reply-To: [EMAIL PROTECTED]
I have a Linux server and a Win95 Client with a printer connected to it.
Both PC are connected via TCP/IP.
The client is connected via telnet (TeraTerm, a serious one!, not that
empty box given with win95 which someone calls telnet) to the Linux
machine and sometimes I have to print Linux files on the printer
connected to the win95 machine.
Is it possible to redirect the output from the Linux machine to the
printer physically connected to the Win 95 PC?
If it were possible, how could get it?
Thanks to everybody for paying attention.
Paul
------------------------------
From: [EMAIL PROTECTED] ()
Crossposted-To:
alt.os.linux.dial-up,alt.uu.comp.os.linux.questions,comp.os.linux.help,comp.os.linux.setup
Subject: Re: PPP Scripting... Help?
Date: Mon, 14 Jun 1999 12:42:17 -0700
On Mon, 14 Jun 1999 13:16:45 -0400, Troy C. Newman <[EMAIL PROTECTED]> wrote:
>I finally got my modem working and am currently trying to configure my
>dial-up connection... I've played a little with the commands and have
>dialed the isp but then nothing... is there a way to find out what the
>script should say/do to establish and maintain the connection or is it a
>matter of trial and error for different isp's.
>
>any help would be greatly appreciated...tcn.
minicom is good for just 'taking a look around'.
It's a comms package (telix,procomm,vanterm).
My page at http://penguin.lvcm.com has a couple of
good links for scripting. Including Worldnet's docs.
Also, try "locate ISP" at the command prompt and
look into what it gives you.
--
bash: the power to toast your registry in style... |||
/ | \
------------------------------
From: Malware <[EMAIL PROTECTED]>
Subject: Re: Sendmail POP
Date: Mon, 14 Jun 1999 23:58:32 +0200
Hi Francisco,
you wrote:
> I have linux 5.2 server installed and I have sendmail on it but when I try
> to connect to the pop it refuses the conection, what could that be?
Sendmail does not include a POP3 server. It's a seperated program. There
should be one on the CD but I would not recomend you using this one. It
does have a serious security problem. Get a later version from RedHat's
web-site in the hope it will still run on this oldish version.
Malware
------------------------------
From: Malware <[EMAIL PROTECTED]>
Subject: Re: Trouble with Caldera NetWare Client
Date: Mon, 14 Jun 1999 23:49:17 +0200
Hi Jonas,
you wrote:
> I have a NetWare 4.11 server that I would like to connect to from my RedHat
> Linux 6.0 mashine. I wan't to use calderas client to log in on the NDS tree.
> Can anybody please post a simple HowTo on installing, configuring IPX and
> the NetWare client on a RedHat 6 mashine to work with NW411.
When I did check it months ago, they had a RPM and installation
instructions for RedHat available at there web-site.
Malware
------------------------------
From: Rafo <[EMAIL PROTECTED]>
Subject: Re: Linux Win98 Networking Problems!!
Date: Mon, 14 Jun 1999 16:33:03 -0400
George:
Thanks for the hint. These are the pins I am using with the RJ45 (8 pin)
connector:
(Assume both connector clips point up.)
Connector A Connector B
1 <--------> 3
2 <--------> 6
3 <--------> 1
6 <--------> 2
I performed a continuity check with an ohm meter and tested ok. Are these the
correct pins?
Regards,
RA
uswest news wrote:
> This may sound dumb, but check well your null cable. I had the same problem
> until I got the connections right. Failing that, post your routing table and
> ifconfig output.
>
> Regards,
>
> George
>
> Rafo wrote in message <[EMAIL PROTECTED]>...
> >Hello:
> >I am attempting to network a win98 box with a linux system. All I am
> >trying to do, is to run Apache HTTPD on the Linux box and access it from
> >the win98 system so I can test CGI scripts.
> >
> >I am attempting to connect them using ethernet cards. I have assigned
> >the following IP addresses:
> >WIN98 IP:192.168.1.110 Mask:255.255.255.0
> >Linux: IP:192.168.1.100 Mask:255.255.255.0
> >
> >The linux system boots up with out a problem, it detected the ethernet
> >hardware ok. I have the hosts file properly structured, netestat looks
> >ok. At the linux box, when I ping for localhost and for 192.168.1.100
> >there are no problems, all packet sent are received. However, when I
> >ping for the win98 system (192.168.1.110) I get no reply. At the win 98
> >system I can ping both localhost and 192.168.1.110 but I can't ping the
> >linux box. In other words, the systems are not able to talk at all. I
> >have connected them using a crossover (NULL) cable as suggested in the
> >Ethernet-HOWTO.
> >
> >This has to be a simple problem to fix. Please, someone come to the
> >rescue!!
> >
> >Thanks in advance.
> >
> >RA
> >
> >
> >
------------------------------
Crossposted-To: comp.os.linux.setup
From: mick@penguin (Mick Farmer)
Subject: PPP Problems
Date: Tue, 15 Jun 1999 11:03:26 GMT
Hi,
I used to have a Solaris box that communicated with a BSD/OS
box without problems. I've now changed to RH 5.2 and can't
get the two systems to connect using pppd. The problem
appears to be in the negotiation stage. Any ideas?
This is /etc/ppp/options.
# Options for all ppp connections (mick, 11 Jun 1999)
#
crtscts # Use hardware flow control
lock # Use UUCP-style locking
This is /etc/ppp/peers/plan7.
# Options for penguin -> plan7 dialout (mick, 11 Jun 1999)
#
/dev/ttyS0
193.61.29.127:193.61.29.79
connect '/usr/sbin/chat -v -f /etc/ppp/chat-plan7'
debug
kdebug 7
modem
noaccomp
nobsdcomp
noccp
nodeflate
nopcomp
novj
This is /etc/ppp/chat-plan7.
# Chat script for penguin -> plan7 dialout (mick, 11 Jun 1999)
#
ABORT 'BUSY'
ABORT 'ERROR'
ABORT 'NO ANSWER'
ABORT 'NO CARRIER'
ABORT 'NO DIALTONE'
'' atz
OK atdt902082445480
CONNECT ''
ogin: XXXXXXXX
ssword: XXXXXXXX
This is the extract from /var/log/ppp.
Jun 15 11:32:43 penguin pppd[7881]: pppd 2.3.5 started by root, uid 0
Jun 15 11:32:44 penguin chat[7882]: abort on (BUSY)
Jun 15 11:32:44 penguin chat[7882]: abort on (ERROR)
Jun 15 11:32:44 penguin chat[7882]: abort on (NO ANSWER)
Jun 15 11:32:44 penguin chat[7882]: abort on (NO CARRIER)
Jun 15 11:32:44 penguin chat[7882]: abort on (NO DIALTONE)
Jun 15 11:32:44 penguin chat[7882]: send (atz^M)
Jun 15 11:32:44 penguin chat[7882]: expect (OK)
Jun 15 11:32:44 penguin chat[7882]: atz^M^M
Jun 15 11:32:44 penguin chat[7882]: OK
Jun 15 11:32:44 penguin chat[7882]: -- got it
Jun 15 11:32:44 penguin chat[7882]: send (atdt902082445480^M)
Jun 15 11:32:45 penguin chat[7882]: expect (CONNECT)
Jun 15 11:32:45 penguin chat[7882]: ^M
Jun 15 11:32:59 penguin chat[7882]: atdt902082445480^M^M
Jun 15 11:32:59 penguin chat[7882]: CONNECT
Jun 15 11:32:59 penguin chat[7882]: -- got it
Jun 15 11:32:59 penguin chat[7882]: send (^M)
Jun 15 11:32:59 penguin chat[7882]: expect (ogin:)
Jun 15 11:32:59 penguin chat[7882]: 14400/ARQ^M
Jun 15 11:32:59 penguin chat[7882]: ^M^M
Jun 15 11:32:59 penguin chat[7882]: ^M^M
Jun 15 11:32:59 penguin chat[7882]: BSDI BSD/OS 2.1 (plan7.dcs.bbk.ac.uk) (tty00)^M^M
Jun 15 11:32:59 penguin chat[7882]: ^M^M
Jun 15 11:32:59 penguin chat[7882]: login:
Jun 15 11:32:59 penguin chat[7882]: -- got it
Jun 15 11:32:59 penguin chat[7882]: send (XXXXXXXX^M)
Jun 15 11:33:00 penguin chat[7882]: expect (ssword:)
Jun 15 11:33:00 penguin chat[7882]: Ppenguin^M^M
Jun 15 11:33:00 penguin chat[7882]: Password:
Jun 15 11:33:00 penguin chat[7882]: -- got it
Jun 15 11:33:00 penguin chat[7882]: send (XXXXXXXX^M)
Jun 15 11:33:00 penguin pppd[7881]: Serial connection established.
Jun 15 11:33:01 penguin pppd[7881]: Using interface ppp0
Jun 15 11:33:01 penguin pppd[7881]: Connect: ppp0 <--> /dev/ttyS0
Jun 15 11:33:01 penguin pppd[7881]: sent [LCP ConfReq id=0x1 <magic 0x6378383d>]
Jun 15 11:33:03 penguin pppd[7881]: rcvd [LCP ConfReq id=0xe <mru 1500> <asyncmap 0x0>
<magic 0x2e57e4ae> <pcomp> <accomp>]
Jun 15 11:33:03 penguin pppd[7881]: sent [LCP ConfRej id=0xe <pcomp> <accomp>]
Jun 15 11:33:03 penguin pppd[7881]: rcvd [LCP ConfReq id=0xf <mru 1500> <asyncmap 0x0>
<magic 0x2e57e4ae>]
Jun 15 11:33:03 penguin pppd[7881]: sent [LCP ConfAck id=0xf <mru 1500> <asyncmap 0x0>
<magic 0x2e57e4ae>]
Jun 15 11:33:04 penguin pppd[7881]: sent [LCP ConfReq id=0x1 <magic 0x6378383d>]
Jun 15 11:33:04 penguin pppd[7881]: rcvd [LCP ConfReq id=0x10 <mru 1500> <asyncmap
0x0> <magic 0x2e57e4ae>]
Jun 15 11:33:04 penguin pppd[7881]: sent [LCP ConfAck id=0x10 <mru 1500> <asyncmap
0x0> <magic 0x2e57e4ae>]
Jun 15 11:33:04 penguin pppd[7881]: rcvd [LCP ConfAck id=0x1 <magic 0x6378383d>]
Jun 15 11:33:04 penguin pppd[7881]: sent [IPCP ConfReq id=0x1 <addr 193.61.29.127>]
Jun 15 11:33:31 penguin last message repeated 9 times
Jun 15 11:33:34 penguin pppd[7881]: IPCP: timeout sending Config-Requests
Jun 15 11:33:34 penguin pppd[7881]: sent [LCP TermReq id=0x2 "No network protocols
running"]
Jun 15 11:33:34 penguin pppd[7881]: rcvd [LCP TermAck id=0x2 "No network protocols
running"]
Jun 15 11:33:34 penguin pppd[7881]: Connection terminated.
Jun 15 11:33:35 penguin pppd[7881]: Exit.
This is the extract from /var/log/messages.
Jun 15 11:32:43 penguin pppd[7881]: pppd 2.3.5 started by root, uid 0
Jun 15 11:32:44 penguin chat[7882]: abort on (BUSY)
Jun 15 11:32:44 penguin chat[7882]: abort on (ERROR)
Jun 15 11:32:44 penguin chat[7882]: abort on (NO ANSWER)
Jun 15 11:32:44 penguin chat[7882]: abort on (NO CARRIER)
Jun 15 11:32:44 penguin chat[7882]: abort on (NO DIALTONE)
Jun 15 11:32:44 penguin chat[7882]: send (atz^M)
Jun 15 11:32:44 penguin chat[7882]: expect (OK)
Jun 15 11:32:44 penguin chat[7882]: atz^M^M
Jun 15 11:32:44 penguin chat[7882]: OK
Jun 15 11:32:44 penguin chat[7882]: -- got it
Jun 15 11:32:44 penguin chat[7882]: send (atdt902082445480^M)
Jun 15 11:32:45 penguin chat[7882]: expect (CONNECT)
Jun 15 11:32:45 penguin chat[7882]: ^M
Jun 15 11:32:59 penguin chat[7882]: atdt902082445480^M^M
Jun 15 11:32:59 penguin chat[7882]: CONNECT
Jun 15 11:32:59 penguin chat[7882]: -- got it
Jun 15 11:32:59 penguin chat[7882]: send (^M)
Jun 15 11:32:59 penguin chat[7882]: expect (ogin:)
Jun 15 11:32:59 penguin chat[7882]: 14400/ARQ^M
Jun 15 11:32:59 penguin chat[7882]: ^M^M
Jun 15 11:32:59 penguin chat[7882]: ^M^M
Jun 15 11:32:59 penguin chat[7882]: BSDI BSD/OS 2.1 (plan7.dcs.bbk.ac.uk) (tty00)^M^M
Jun 15 11:32:59 penguin chat[7882]: ^M^M
Jun 15 11:32:59 penguin chat[7882]: login:
Jun 15 11:32:59 penguin chat[7882]: -- got it
Jun 15 11:32:59 penguin chat[7882]: send (XXXXXXXX^M)
Jun 15 11:33:00 penguin chat[7882]: expect (ssword:)
Jun 15 11:33:00 penguin chat[7882]: Ppenguin^M^M
Jun 15 11:33:00 penguin chat[7882]: Password:
Jun 15 11:33:00 penguin chat[7882]: -- got it
Jun 15 11:33:00 penguin chat[7882]: send (XXXXXXXX^M)
Jun 15 11:33:00 penguin pppd[7881]: Serial connection established.
Jun 15 11:33:01 penguin kernel: ppp_ioctl: set dbg flags to 70000
Jun 15 11:33:01 penguin kernel: ppp_ioctl: set flags to 70000
Jun 15 11:33:01 penguin kernel: ppp_tty_ioctl: set xasyncmap
Jun 15 11:33:01 penguin pppd[7881]: Using interface ppp0
Jun 15 11:33:01 penguin pppd[7881]: Connect: ppp0 <--> /dev/ttyS0
Jun 15 11:33:01 penguin kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Jun 15 11:33:01 penguin kernel: ppp_ioctl: set flags to 70000
Jun 15 11:33:01 penguin kernel: ppp_ioctl: set mru to 5dc
Jun 15 11:33:01 penguin kernel: ppp_tty_ioctl: set rcv asyncmap ffffffff
Jun 15 11:33:01 penguin kernel: ppp_ioctl: set flags to 70010
Jun 15 11:33:04 penguin kernel: ppp_tty_ioctl: set xmit asyncmap 0
Jun 15 11:33:04 penguin kernel: ppp_ioctl: set flags to f070010
Jun 15 11:33:04 penguin kernel: ppp_ioctl: set mru to 5dc
Jun 15 11:33:04 penguin kernel: ppp_tty_ioctl: set rcv asyncmap ffffffff
Jun 15 11:33:04 penguin kernel: ppp_ioctl: set flags to f070010
Jun 15 11:33:34 penguin pppd[7881]: IPCP: timeout sending Config-Requests
Jun 15 11:33:34 penguin kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Jun 15 11:33:34 penguin kernel: ppp_ioctl: set flags to f070010
Jun 15 11:33:34 penguin kernel: ppp_ioctl: set mru to 5dc
Jun 15 11:33:34 penguin kernel: ppp_tty_ioctl: set rcv asyncmap ffffffff
Jun 15 11:33:34 penguin kernel: ppp_ioctl: set flags to f070010
Jun 15 11:33:34 penguin kernel: ppp: channel ppp0 closing.
Jun 15 11:33:34 penguin pppd[7881]: Connection terminated.
Jun 15 11:33:35 penguin pppd[7881]: Exit.
------------------------------
** 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
******************************
