Linux-Networking Digest #19, Volume #10 Wed, 27 Jan 99 12:13:42 EST
Contents:
PAP problem Please Help!! (Partha Sri)
Re: RedHat 5.2 and NE2000 (Joel Burton)
Linux, banet.net, & fast net access in Malden, MA (Rod Smith)
Re: PPP Server ("Charles Stack")
Re: IPX/PPP Client Problem (Malware)
nprint & spanish characters ("Manuel Mar�a Villapecell�n Cid")
Newbee: NIC Install?/DE-528(D-Link)/Debian(current "stable") (Tracy Clarke)
TCP/IP dies with DEC Tulip (David Wilk)
Re: ppp help ([EMAIL PROTECTED])
Changing IP address ("Shane S.")
Re: Dial-Up Server (Maddog)
----------------------------------------------------------------------------
From: Partha Sri <[EMAIL PROTECTED]>
Subject: PAP problem Please Help!!
Date: Wed, 27 Jan 1999 08:37:25 -0600
Reply-To: [EMAIL PROTECTED]
Hi All:
I have been trying to get my PPP connection going for quite sometime
now. But I am having the most bizarre problem. My ISP uses PAP and
I dont have to issue a command to invoke PPP. But for some reason after
establishing the serial connection my pppd does a LCP timeout. And
I get fcs errors. I even spoke to my ISP guy and he says that his
terminal server is just waiting and doing nothing after the connect.
I even tried sending the login and passwd and got the same result. There
is no noise in my phone connection so fcs errors is what I dont
understand!! I checked the modem too.. it is fine.
And btw I have a static IP address. And my ISP guy took the same scripts
and it worked for him on a slackware kernel 2.0.34 and pppd 2.2.5.
I use RH5.2, pppd 2.3.5 and my kernel is 2.0.36. But since I dont have
X going I dont use RH's interface. I use a USR 56K v.90 external modem.
I have my own set of scripts which are very simple. I have attached my
options file and my log file for your reference. I am sorry about the
lengthy log file but I am really desperate.. need help please!!
And another interesting thing is that I am not able to connect to my
ISP using minicom. After dialing and the hissing noise nothing happens!!
Technically I shoud get the login prompt. This is happening when I dial
to my other ISPs too. So, this is not an ISP issue. Something is wrong
with my m/c.
Also can anyone recommend a good 56K internal modem which will work with
linux??
Any help will be greatly appreciated.
Thanks a lot,
Partha
Here is my options file:
==========================================================
# comments allowed
+pap
/dev/modem 38400
name partha
-detach
passive
pap-timeout 120
debug
kdebug 25
crtscts
modem
mtu 512
asyncmap 0
defaultroute
206.158.123.179:0.0.0.0
==============================EOF============================
Here is my log file with prime time debugging:
==============================================================
Jan 24 07:01:00 agni PAM_pwdb[8241]: (su) session opened for user news
by (uid=9
)
Jan 24 07:01:00 agni PAM_pwdb[8241]: (su) session closed for user news
Jan 24 08:01:00 agni PAM_pwdb[8276]: (su) session opened for user news
by (uid=9
)
Jan 24 08:01:00 agni PAM_pwdb[8276]: (su) session closed for user news
Jan 24 09:01:00 agni PAM_pwdb[8311]: (su) session opened for user news
by (uid=9
)
Jan 24 09:01:00 agni PAM_pwdb[8311]: (su) session closed for user news
Jan 24 10:01:00 agni PAM_pwdb[8346]: (su) session opened for user news
by (uid=9
)
Jan 24 10:01:00 agni PAM_pwdb[8346]: (su) session closed for user news
Jan 24 11:01:00 agni PAM_pwdb[8381]: (su) session opened for user news
by (uid=9
)
Jan 24 11:01:00 agni PAM_pwdb[8381]: (su) session closed for user news
Jan 24 11:16:14 agni pppd[8425]: pppd 2.3.5 started by root, uid 0
Jan 24 11:16:14 agni pppd[8425]: pppd 2.3.5 started by root, uid 0
Jan 24 11:16:15 agni chat[8429]: abort on (BUSY)
Jan 24 11:16:15 agni chat[8429]: abort on (NO CARRIER)
Jan 24 11:16:15 agni chat[8429]: abort on (ERROR)
Jan 24 11:16:15 agni chat[8429]: abort on (NO DIALTONE)
Jan 24 11:16:15 agni chat[8429]: abort on (NO ANSWER)
Jan 24 11:16:15 agni chat[8429]: send (ATZ^M)
Jan 24 11:16:34 agni chat[8429]: OK
Jan 24 11:16:34 agni chat[8429]: -- got it
Jan 24 11:16:34 agni chat[8429]: send (ATDT 687-2241^M)
Jan 24 11:16:34 agni chat[8429]: expect (CONNECT)
Jan 24 11:16:34 agni chat[8429]: ^M
Jan 24 11:17:04 agni chat[8429]: ATDT 687-2241^M
Jan 24 11:17:04 agni chat[8429]: CONNECT
Jan 24 11:17:04 agni chat[8429]: -- got it
Jan 24 11:17:04 agni chat[8429]: send (^M)
Jan 24 11:17:04 agni pppd[8425]: Serial connection established.
Jan 24 11:17:04 agni pppd[8425]: Serial connection established.
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set flags to 190000
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set flags to 190000
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: get flags: addr bffffbfc
flags 0
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set flags to 190000
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set xasyncmap
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set flags to 190000
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set xasyncmap
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: get flags: addr bffffb94
flags 0
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set flags to 190000
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set flags to 190000
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: get flags: addr bffffbfc
flags 0
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set flags to 190000
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set xasyncmap
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set flags to 190000
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set xasyncmap
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: get flags: addr bffffb94
flags 0
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set flags to 190000
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set flags to 190000
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set mru to 5dc
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set mru to 5dc
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set rcv asyncmap ffffffff
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set rcv asyncmap ffffffff
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: get flags: addr bffffba8
flags 0
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set flags to 190000
Jan 24 11:17:14 agni kernel: ppp_tty_ioctl: set flags to 190000
Jan 24 11:17:14 agni kernel: ppp_dev_xmit_lower: fcs is 176d
Jan 24 11:17:14 agni kernel: ppp: ppp flush, count = 46
Jan 24 11:17:14 agni kernel: 7E FF 7D 23 C0 21 7D 21 ~.}#.!}!
Jan 24 11:17:14 agni kernel: 7D 21 7D 20 7D 34 7D 22 }!} }4}"
Jan 24 11:17:14 agni kernel: 7D 26 7D 20 7D 20 7D 20 }&} } }
Jan 24 11:17:14 agni kernel: 7D 20 7D 25 7D 26 59 BF } }%}&Y.
Jan 24 11:17:14 agni pppd[8425]: Using interface ppp0
Jan 24 11:17:14 agni pppd[8425]: Using interface ppp0
Jan 24 11:17:14 agni pppd[8425]: Connect: ppp0 <--> /dev/modem
Jan 24 11:17:14 agni pppd[8425]: Connect: ppp0 <--> /dev/modem
Jan 24 11:17:14 agni pppd[8425]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
<magic
0x59bfc0a7> <pcomp> <accomp>]
Jan 24 11:17:14 agni kernel: C0 A7 7D 27 7D 22 7D 28 ..}'}"}(
Jan 24 11:17:14 agni kernel: 7D 22 6D 7D 37 7E }"m}7~
Jan 24 11:17:14 agni kernel: ppp: receive buffer, count = 7
Jan 24 11:17:14 agni kernel: 9E 1C 1E 00 1E FF 9E .......
Jan 24 11:17:17 agni kernel: ppp_dev_xmit_lower: fcs is 176d
Jan 24 11:17:17 agni kernel: ppp: ppp flush, count = 46
Jan 24 11:17:17 agni kernel: 7E FF 7D 23 C0 21 7D 21 ~.}#.!}!
Jan 24 11:17:17 agni kernel: 7D 21 7D 20 7D 34 7D 22 }!} }4}"
Jan 24 11:17:17 agni kernel: 7D 26 7D 20 7D 20 7D 20 }&} } }
Jan 24 11:17:17 agni kernel: 7D 20 7D 25 7D 26 59 BF } }%}&Y.
Jan 24 11:17:17 agni kernel: C0 A7 7D 27 7D 22 7D 28 ..}'}"}(
Jan 24 11:17:17 agni kernel: 7D 22 6D 7D 37 7E }"m}7~
Jan 24 11:17:17 agni kernel: ppp_tty_read: called buf=08064610 nr=1504
Jan 24 11:17:17 agni kernel: ppp_tty_read: no data (EAGAIN)
Jan 24 11:17:20 agni kernel: ppp_dev_xmit_lower: fcs is 176d
Jan 24 11:17:20 agni kernel: ppp: ppp flush, count = 46
Jan 24 11:17:20 agni kernel: 7E FF 7D 23 C0 21 7D 21 ~.}#.!}!
Jan 24 11:17:20 agni kernel: 7D 21 7D 20 7D 34 7D 22 }!} }4}"
Jan 24 11:17:20 agni kernel: 7D 26 7D 20 7D 20 7D 20 }&} } }
Jan 24 11:17:20 agni kernel: 7D 20 7D 25 7D 26 59 BF } }%}&Y.
Jan 24 11:17:20 agni kernel: C0 A7 7D 27 7D 22 7D 28 ..}'}"}(
Jan 24 11:17:20 agni kernel: 7D 22 6D 7D 37 7E }"m}7~
Jan 24 11:17:20 agni kernel: ppp_tty_read: called buf=08064610 nr=1504
Jan 24 11:17:20 agni kernel: ppp_tty_read: no data (EAGAIN)
Jan 24 11:17:23 agni kernel: ppp_dev_xmit_lower: fcs is 176d
Jan 24 11:17:23 agni kernel: ppp: ppp flush, count = 46
Jan 24 11:17:23 agni kernel: 7E FF 7D 23 C0 21 7D 21 ~.}#.!}!
Jan 24 11:17:23 agni kernel: 7D 21 7D 20 7D 34 7D 22 }!} }4}"
Jan 24 11:17:23 agni kernel: 7D 26 7D 20 7D 20 7D 20 }&} } }
Jan 24 11:17:23 agni kernel: 7D 20 7D 25 7D 26 59 BF } }%}&Y.
Jan 24 11:17:23 agni kernel: C0 A7 7D 27 7D 22 7D 28 ..}'}"}(
Jan 24 11:17:23 agni kernel: 7D 22 6D 7D 37 7E }"m}7~
Jan 24 11:17:23 agni kernel: ppp_tty_read: called buf=08064610 nr=1504
Jan 24 11:17:23 agni kernel: ppp_tty_read: no data (EAGAIN)
Jan 24 11:17:26 agni kernel: ppp_dev_xmit_lower: fcs is 176d
Jan 24 11:17:26 agni kernel: ppp: ppp flush, count = 46
Jan 24 11:17:26 agni kernel: 7E FF 7D 23 C0 21 7D 21 ~.}#.!}!
Jan 24 11:17:26 agni kernel: 7D 21 7D 20 7D 34 7D 22 }!} }4}"
Jan 24 11:17:26 agni kernel: 7D 26 7D 20 7D 20 7D 20 }&} } }
Jan 24 11:17:26 agni kernel: 7D 20 7D 25 7D 26 59 BF } }%}&Y.
Jan 24 11:17:26 agni kernel: C0 A7 7D 27 7D 22 7D 28 ..}'}"}(
Jan 24 11:17:26 agni kernel: 7D 22 6D 7D 37 7E }"m}7~
Jan 24 11:17:26 agni kernel: ppp_tty_read: called buf=08064610 nr=1504
Jan 24 11:17:26 agni kernel: ppp_tty_read: no data (EAGAIN)
Jan 24 11:17:29 agni kernel: ppp_dev_xmit_lower: fcs is 176d
Jan 24 11:17:29 agni kernel: ppp: ppp flush, count = 46
Jan 24 11:17:29 agni kernel: 7E FF 7D 23 C0 21 7D 21 ~.}#.!}!
Jan 24 11:17:29 agni kernel: 7D 21 7D 20 7D 34 7D 22 }!} }4}"
Jan 24 11:17:29 agni kernel: 7D 26 7D 20 7D 20 7D 20 }&} } }
Jan 24 11:17:29 agni kernel: 7D 20 7D 25 7D 26 59 BF } }%}&Y.
Jan 24 11:17:29 agni kernel: C0 A7 7D 27 7D 22 7D 28 ..}'}"}(
Jan 24 11:17:29 agni kernel: 7D 22 6D 7D 37 7E }"m}7~
Jan 24 11:17:29 agni kernel: ppp_tty_read: called buf=08064610 nr=1504
Jan 24 11:17:29 agni kernel: ppp_tty_read: no data (EAGAIN)
Jan 24 11:17:32 agni kernel: ppp_dev_xmit_lower: fcs is 176d
Jan 24 11:17:32 agni kernel: ppp: ppp flush, count = 46
Jan 24 11:17:32 agni kernel: 7E FF 7D 23 C0 21 7D 21 ~.}#.!}!
Jan 24 11:17:32 agni kernel: 7D 21 7D 20 7D 34 7D 22 }!} }4}"Jan 24
11:17:32 agni kernel: C0 A7 7D 27 7D 22 7D 28 ..}'}"}(
Jan 24 11:17:32 agni kernel: 7D 22 6D 7D 37 7E }"m}7~
Jan 24 11:17:32 agni kernel: ppp_tty_read: called buf=08064610 nr=1504
Jan 24 11:17:32 agni kernel: ppp_tty_read: no data (EAGAIN)
Jan 24 11:17:34 agni kernel: ppp: receive buffer, count = 4
Jan 24 11:17:34 agni kernel: FC 8E FC FE ....
Jan 24 11:17:35 agni kernel: ppp_dev_xmit_lower: fcs is 176d
Jan 24 11:17:35 agni kernel: ppp: ppp flush, count = 46
Jan 24 11:17:35 agni kernel: 7E FF 7D 23 C0 21 7D 21 ~.}#.!}!
Jan 24 11:17:35 agni kernel: 7D 21 7D 20 7D 34 7D 22 }!} }4}"
Jan 24 11:17:35 agni kernel: 7D 26 7D 20 7D 20 7D 20 }&} } }
Jan 24 11:17:35 agni kernel: 7D 20 7D 25 7D 26 59 BF } }%}&Y.
Jan 24 11:17:35 agni kernel: C0 A7 7D 27 7D 22 7D 28 ..}'}"}(
Jan 24 11:17:35 agni kernel: 7D 22 6D 7D 37 7E }"m}7~
Jan 24 11:17:35 agni kernel: ppp_tty_read: called buf=08064610 nr=1504
Jan 24 11:17:35 agni kernel: ppp_tty_read: no data (EAGAIN)
Jan 24 11:17:38 agni kernel: ppp_dev_xmit_lower: fcs is 176d
Jan 24 11:17:38 agni kernel: ppp: ppp flush, count = 46
Jan 24 11:17:38 agni kernel: 7E FF 7D 23 C0 21 7D 21 ~.}#.!}!
Jan 24 11:17:38 agni kernel: 7D 21 7D 20 7D 34 7D 22 }!} }4}"
Jan 24 11:17:38 agni kernel: 7D 26 7D 20 7D 20 7D 20 }&} } }
Jan 24 11:17:38 agni kernel: 7D 20 7D 25 7D 26 59 BF } }%}&Y.
Jan 24 11:17:38 agni kernel: C0 A7 7D 27 7D 22 7D 28 ..}'}"}(
Jan 24 11:17:38 agni kernel: 7D 22 6D 7D 37 7E }"m}7~
Jan 24 11:17:38 agni kernel: ppp_tty_read: called buf=08064610 nr=1504
Jan 24 11:17:38 agni kernel: ppp_tty_read: no data (EAGAIN)
Jan 24 11:17:41 agni kernel: ppp_dev_xmit_lower: fcs is 176d
Jan 24 11:17:41 agni kernel: ppp: ppp flush, count = 46
Jan 24 11:17:41 agni kernel: 7E FF 7D 23 C0 21 7D 21 ~.}#.!}!
Jan 24 11:17:41 agni kernel: 7D 21 7D 20 7D 34 7D 22 }!} }4}"
Jan 24 11:17:41 agni kernel: 7D 26 7D 20 7D 20 7D 20 }&} } }
Jan 24 11:17:41 agni kernel: 7D 20 7D 25 7D 26 59 BF } }%}&Y.
Jan 24 11:17:41 agni kernel: C0 A7 7D 27 7D 22 7D 28 ..}'}"}(
Jan 24 11:17:41 agni kernel: 7D 22 6D 7D 37 7E }"m}7~
Jan 24 11:17:41 agni kernel: ppp_tty_read: called buf=08064610 nr=1504
Jan 24 11:17:41 agni kernel: ppp_tty_read: no data (EAGAIN)
Jan 24 11:17:44 agni kernel: ppp: receive buffer, count = 1
Jan 24 11:17:44 agni kernel: FC .
Jan 24 11:17:41 agni last message repeated 9 times
Jan 24 11:17:44 agni pppd[8425]: LCP: timeout sending Config-Requests
============================================================================
------------------------------
From: Joel Burton <[EMAIL PROTECTED]>
Subject: Re: RedHat 5.2 and NE2000
Date: Wed, 27 Jan 1999 09:47:19 -0500
> During my installation of the RedHat 5.2 distribution I get asked about my
> NIC. I have a genuine NE2000 in the machine. It claims that it cannot be
> detected, even if I feed it the IO and IRQ manually.
>
> What is the way to proceed?
Some basic things to consider/answer:
1. Does the card work under another operating system?
2. Are you sure you have the right IRQ and IO? If you're also currently
running under Windows 95/98, you can get this information from the System
control panel.
3. Does your card let you switch between plug and play mode and jumperless
mode? If so, I'd set it to jumperless mode.
4. *How* are you specifying the IRQ and IO in the RH5.2 setup? What's the
exact string?
Good luck.
------------------------------
From: [EMAIL PROTECTED] (Rod Smith)
Subject: Linux, banet.net, & fast net access in Malden, MA
Date: 27 Jan 1999 03:55:54 GMT
Hi,
I'm moving to Malden, Massachusetts (a Boston "suburb," though it's not
very suburban) soon and am looking at net access options. Malden doesn't
yet seem to be well-wired for fast net access by cable modem or DSL, but
Bell Atlantic claims they'll have DSL up in two or three months. I was
therefore planning to get a Bell Atlantic dialup PPP account in the hopes
that I won't need to change my e-mail address when I switch from that to
DSL. I got their Windows-based software and set up an account, which has
a banet.net address (unlike most Bell Atlantic discussions I've seen,
which seem to give bellatlantic.net addresses). The problem is that I
can't get it to work from Linux. It works fine from Windows, but when I
try from either Linux (using XISP) or OS/2 I get a message back from the
ISP saying "Error 20 Incorrect account or user ID," followed by an
OS-generated message to the effect that PAP (or CHAP; I've tried both)
authentication failed. The phrasing of this makes me think they may be
scrambling the login names in some unknown way, though I've also messed
with passwords interminably, to no avail. I'm using Red Hat Linux 5.2
with PPP 2.3.5, XISP 2.5p4, and kernel 2.2.0-pre1. I've tried lots of
variations on XISP's entries and the entries in my /etc/ppp/pap-secrets
file. It all works fine with my current ISP (using different usernames,
passwords, etc., of course). Again, I get the same behavior in OS/2 as I
do in Linux, so I don't think it's some obscure Linux config problem.
So, does anybody have any ideas on this?
Alternatively, does anybody know of some other company that's offering DSL
service now (or soon) in Malden that I may have overlooked?
Failing that, if anybody would like to recommend a Linux-friendly dialup
ISP in the Boston area, I'm entertaining suggestions for alternatives,
particularly if I might be able to use them via some DSL setup in the near
future.
--
Rod Smith
[EMAIL PROTECTED]
http://www.users.fast.net/~rodsmith
------------------------------
From: "Charles Stack" <[EMAIL PROTECTED]>
Subject: Re: PPP Server
Date: Mon, 25 Jan 1999 15:52:33 -0500
If you are using mgetty, on the entry in /etc/inittab, add a -R n where n is
the number of seconds mgetty will wait for a second call from you (after 30
seconds). If a call doesnt come in 30 < t <30+n seconds, mgetty forgets
about. If it does come in that interval, mgetty will answer the phone.
------------------------------
From: Malware <[EMAIL PROTECTED]>
Subject: Re: IPX/PPP Client Problem
Date: Wed, 27 Jan 1999 16:34:21 +0100
Hi Andy,
you wrote:
> >Did you try this out? I do not see how it does work. In the first run of
> I try - this works.
Ok, atleast one who did - I did not :-(
> First of all I must say that I talk about ppp-2.3.5. (I hav't 2.3.4
> and don't know about it).
Ok, then we talk about the same version. Wouldn't event try to run a
earlier one while using kernel 2.1.132.
AN> I have go->neg_name == 0. All works fine. May be you set
AN> ipx-router-name in /etc/ppp/options ? If yes tell me why ?
As I write above I have no practical problem with. I'm just interested
to find the point my interpretation does leave the path things are
going.
> ACKCINETWORK: we send netnumber - we received it. OK
> ACKCINODE: same with node. OK
> ACKCINAME: Hm... I don't use it and have go->neg_name == 0.
> Therefore this macro is skiped.
As I wrote, I did not saw where it would be setted to 0 as it is setted
to 1 in a function ipxcp_init (or the like - not have the code handy)
but only reseted when receiving a reject for. But as you have pracitical
experience I believe you that it can be 0 from the very start and later
on will go to find the code making this possible - I just want to know
it. With your later post - which I qouted above - you point me to an
option which might be a good starting point for my search.
> But if I should be writing this function, I wrote this fragment
> of code like (shematicaly):
[...]
> while (len > 2) {
> GETCHAR(citype, p);
> GETCHAR(cilen, p);
> len -= 2;
> switch (citype) {
> case IPX_NETWORK_NUMBER:
> ...
> break;
> case IPX_NODE_NUMBER:
> ...
> break;
[...]
> }
But as I understand the comment within the existing code the protocol
needs the options to be acked in the order they was requested. Your code
idea would break this logic and accept them in any order. RFC-1548 does
state in section 5.2 "Configure-Ack":
RFC1548> received Configure-Request. The acknowledged Configuration
RFC1548> Options MUST NOT be reordered or modified in any way.
RFC1570 - which is an update to RFC1548 - does not touch this statement.
But I found no statement if the receiver is permitted to accept options
ACK-ed out of order.
Summary: Thanks for your description. I'll goon making self-studies as I
think there is no more controverse. But about the last point (your code
idea) I would be happy to hear about your point of view. Let's move that
into private mail or a more approciate forum like comp.protocols.ppp
(I'll "subscribe" to this forum today evening so you might just start
posting there if interested about talking there).
Malware
------------------------------
Date: Wed, 27 Jan 1999 14:53:09 +0100
From: "Manuel Mar�a Villapecell�n Cid" <[EMAIL PROTECTED]>
Subject: nprint & spanish characters
Hi guys!
I'm trying to print spanish characters (accents) using the nprint
utility included in ncpfs-2.0.11-3 for i386. The package is a rpm
included in my redhat 5.0 distribution. The kernel I'm using is 2.0.32.
It's possible to print everything but these characters. Does anybody
know how to fix this?
Thanks!!!!
------------------------------
Date: Tue, 26 Jan 1999 21:41:26 -0500
From: Tracy Clarke <[EMAIL PROTECTED]>
Subject: Newbee: NIC Install?/DE-528(D-Link)/Debian(current "stable")
I downloaded the Debian Linux "setup disks", got it installed without
too much trouble, even set it up auto mount all my WIN/DOS hd's
(/etc/fstab) But I can't seem to get it to use my D-Link DE-528 NIC
(connected to a cable modem) The disk that came with it (D-Link) does
have "Linux" drivers, but doesn't seem to work. It extracts the files to
a different directory then stated in the help app. and tells me to run a
bunch of "make" commands,.. of course the make command doesn't seem to
be available to me at this point.
I did scan through this NG and DEJA-NEWS Before posting this, and I
have used UNIX before (CLIX/Ingr.)
Please Help me!
Tracy.
P.S.
pII 300mhz/512L2/128Mb Ram/Matrox G200 Millennium
------------------------------
From: [EMAIL PROTECTED] (David Wilk)
Subject: TCP/IP dies with DEC Tulip
Date: Tue, 26 Jan 1999 22:51:05 -0500
Howdy folks,
I recently setup a web (and everything else) server on a dual PII box with
a DEC tulip 10/100 ethernet card. I've got it recompiled with 2.0.36
modularized. The problem is that after up and running fine for between 24
and 72 hours, it just plain stops responding to anything IP. I can't
ping, telnet, nothing. I take a look at the console and it looks fine.
no crash, nothing. I looked in syslog and found only one weird log. it
would print the message: ICMPlogd: can't connect to destination from
127.0.0.1 <local host>
this message is repeated over and over a couple hundred times.
Let me know if you have any thoughts.
Thanks!
DAve
--
'Linux, choice of a GNU generation'
'My other machine is a linux box'
'What? You mean you *have* to reboot?'
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: ppp help
Date: Mon, 25 Jan 1999 20:49:45 GMT
I got the same error when I wasn't authenticating
correctly with my ISP (i never got thru the login stage
and pppd was trying to figure out ip addresses, etc.)
In article <[EMAIL PROTECTED]>,
Minh Giang <[EMAIL PROTECTED]> wrote:
> Hi,
> I'm having trouble connect to our ISP using RedHat 5.2 Linux using
> pppd.
> here are my setup:
>
> # /etc/resolv.conf
> search fast.net
> nameserver 198.69.204.2
> nameserver 198.69.204.7
>
> #/etc/ppp/options
> connect /etc/ppp/ppp-on-dialer
> 115200
> crtscts
> asyncmap 0
> defaultroute
> modem
> lock
> noipdefault
>
> #/etc/ppp/ppp-on-dialer
> #!/bin/sh
> exec chat -V
> TIMEOUT 10 \
> ABORT "\nBUSY\R" \
> ABORT "\nNO ANSWER\r" \
> ABORT "\nNO CARRIER\r" \
> ABORT "\nNO DIAL TONE\r" \
> ABORT "\nRING\r\n\r\n\RING\r" \
> '' AT \
> TIMEOUT 35 \
> OK ATDT9540300 \
> CONNECT ''
>
> #/etc/ppp/pap-secrets
> myusername * my_password
>
> my message log:
>
> .....localhost pppd[536]: pppd 2.3.5 started by root, uid 0
> .....localhost ifup-ppp: pppd started for ppp0 on /dev/modem at 115200
> .....localhost pppd[536]: Serial connection established
> .....localhost pppd[536]: Using interface ppp0
> .....localhost pppd[536]: LCP: timeout sending Config-Requests
> .....localhost pppd[536]: Connection terminated
> .....localhost pppd[536]: Exit.
>
> What's wrong???? please help a very frustrated man
>
> --mpg
>
>
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: "Shane S." <[EMAIL PROTECTED]>
Subject: Changing IP address
Date: Tue, 26 Jan 1999 11:17:49 -0700
Hi there,
I was wondering if someone could help me out.
Our Linux admin bailed out. We are changing our network IP address.
I was wondering what are the files I need to edit to change the IP address,
subnet mask, Gateway IP address, and DNS enteries?
Many thanks
Shane
------------------------------
From: Maddog <[EMAIL PROTECTED]>
Subject: Re: Dial-Up Server
Date: Wed, 27 Jan 1999 16:18:18 GMT
Charles Stack wrote:
> This topic comes up several times a week. Search this newsgroup for an
> entry by Josh Gentry and you should find a link to a document he has written
> a detailed document describing how to stetup a dialin server (using a
> modem).
I searched the newsgroup and found no info.. if any one has the link could you
please pass it on?
thanks
Dave
------------------------------
** 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
******************************
