Linux-Networking Digest #752, Volume #9 Sat, 2 Jan 99 06:14:47 EST
Contents:
Puzzling MS CHAP problem (Stuart MacDonald)
Re: Cant use two ethernet interfaces (James Huang)
After IP Masquerade done ?? ("Joekie")
Re: US WEST Megabit service? (Lamar Cole)
Re: Setting up a proxy server to distribute a cable modem signal ("Rob")
Re: How can you get Linux to log into NT Server 4.0 (Bill Amsinux)
Re: NOSPAM in addresses.. (Rick Moen)
----------------------------------------------------------------------------
From: Stuart MacDonald <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.slackware
Subject: Puzzling MS CHAP problem
Date: Sat, 02 Jan 1999 06:49:09 GMT
I'm trying to get a linux box to dial into an NT server.
I've read as much documentation as I can find (howtos, mini-howtos,
faqs, source, etc) and haven't found anything that appears to
correspond to my problem.
The problem: MS-CHAP authorization fails every time. The negotiations
appear to go well, and then the NT box just fails the auth
sequence for reasons (mostly) unknown.
Some config info:
Slackware 3.5 (linux 2.0.34, pppd 2.3 patch level 5), an
out-of-the-box install, nothing fancy
NT 4.0 Service Pack 3 (build 1381)
I've triple-checked the NT side of things; the user name is set
correctly, I've re-typed the password for the account twice and
the network is set to "allow any authorization including plaintext".
It's a stand-alone machine at the moment, so the DOMAIN\\username
format shouldn't need to be used; I tested that anyway, with the
same failure resulting.
My ppp-on script: (comments removed for conciseness)
--- Cut Here ---
#!/bin/sh
cd /etc/ppp
TELEPHONE=*70W555-5555
INITSTRING="Z"
ACCOUNT=testuser
PASSWORD=testword
LOCAL_IP=0.0.0.0
REMOTE_IP=0.0.0.0
NETMASK=255.255.255.0
export TELEPHONE ACCOUNT PASSWORD INITSTRING
DIALER_SCRIPT=/etc/ppp/ppp-on-dialer
setserial /dev/cua1 spd_vhi
exec /usr/sbin/pppd file options /dev/cua1 38400 \
$LOCAL_IP:$REMOTE_IP \
netmask $NETMASK defaultroute connect $DIALER_SCRIPT
--- Cut Here ---
My ppp-on-dialer script:
--- Cut Here ---
#!/bin/sh
exec chat -v \
TIMEOUT 3 \
ABORT '\nBUSY\r' \
ABORT '\nNO ANSWER\r' \
ABORT '\nRINGING\r\n\r\nRINGING\r' \
'' \rAT \
'OK-+++\c-OK' ATH0 \
TIMEOUT 30 \
OK AT$INITSTRING \
OK ATDT$TELEPHONE \
CONNECT
--- Cut Here ---
My options file:
--- Cut Here ---
asyncmap 0
crtscts
lock
modem
debug
-pap
user iabuser
remotename ALF
kdebug 127
--- Cut Here ---
My [ch|p]ap-secrets file:
--- Cut Here ---
testuser * testword *
* testuser testword *
--- Cut Here ---
Some notes at this point:
- the kdebug stuff didn't mean much to me, so I've stripped it
out of the log; I can post it later if needed
- the configuration works if I switch -pap with -chap; PAP auth
suceeds and all is fine. The point is I want to get the
MS-CHAP auth working.
What seems to be happening: The protocol negotiation goes okay,
then NT just ignores the CHAP response. I get the same
response on an older system where I had to manually download
and install the MS-CHAP support. I ran the test program
that came with the ppp code I downloaded and it produced
the expected response, so the CHAP encryption is working.
The passwords etc are correct, because I can auth with PAP
successfully. The only hint I can find about what might be
going wrong is NT logs the following in the event log:
Source: Router Type: Warning Category: None
The user connected to port COM2 has been disconnected due to
an authorization timeout.
I don't understand why, since the CHAP response goes out
right away. My only guess is that I haven't configured ppp
correctly somehow. I haven't been able to test against a
second NT box due to hardware constraints.
Thanks in advance for any help.
The syslog: (debug log was re-routed into syslog)
--- Cut Here ---
Dec 15 14:29:43 penguin pppd[5356]: pppd 2.3.5 started by root, uid 0
Dec 15 14:29:44 penguin chat[5357]: timeout set to 3 seconds
Dec 15 14:29:44 penguin chat[5357]: abort on (\nBUSY\r)
Dec 15 14:29:44 penguin chat[5357]: abort on (\nNO ANSWER\r)
Dec 15 14:29:44 penguin chat[5357]: abort on
(\nRINGING\r\n\r\nRINGING\r)
Dec 15 14:29:44 penguin chat[5357]: send (rAT^M)
Dec 15 14:29:44 penguin chat[5357]: expect (OK)
Dec 15 14:29:44 penguin chat[5357]: rAT^M^M
Dec 15 14:29:44 penguin chat[5357]: OK -- got it
Dec 15 14:29:44 penguin chat[5357]: send (ATH0^M)
Dec 15 14:29:44 penguin chat[5357]: timeout set to 30 seconds
Dec 15 14:29:44 penguin chat[5357]: expect (OK)
Dec 15 14:29:44 penguin chat[5357]: ^M
Dec 15 14:29:44 penguin chat[5357]: ATH0^M^M
Dec 15 14:29:44 penguin chat[5357]: OK -- got it
Dec 15 14:29:44 penguin chat[5357]: send (ATZ^M)
Dec 15 14:29:44 penguin chat[5357]: expect (OK)
Dec 15 14:29:44 penguin chat[5357]: ^M
Dec 15 14:29:44 penguin chat[5357]: ATZ^M^M
Dec 15 14:29:44 penguin chat[5357]: OK -- got it
Dec 15 14:29:44 penguin chat[5357]: send (ATDT*70W725-9906^M)
Dec 15 14:29:45 penguin chat[5357]: expect (CONNECT)
Dec 15 14:29:45 penguin chat[5357]: ^M
Dec 15 14:30:03 penguin chat[5357]: ATDT*70W725-9906^M^M
Dec 15 14:30:03 penguin chat[5357]: CONNECT -- got it
Dec 15 14:30:03 penguin pppd[5356]: Serial connection established.
Dec 15 14:30:04 penguin pppd[5356]: Using interface ppp0
Dec 15 14:30:04 penguin pppd[5356]: Connect: ppp0 <--> /dev/cua1
Dec 15 14:30:04 penguin pppd[5356]: sent [LCP ConfReq id=0x1 <asyncmap
0x0> <magic 0x19cc75e0> <pcomp> <accomp>]
We'd like these options please.
Dec 15 14:30:05 penguin pppd[5356]: rcvd [LCP ConfReq id=0x0 <asyncmap
0x0> <auth chap 80> <magic 0x606c> <pcomp> <accomp>]
We want ms-chap if possible.
Dec 15 14:30:05 penguin pppd[5356]: sent [LCP ConfAck id=0x0 <asyncmap
0x0> <auth chap 80> <magic 0x606c> <pcomp> <accomp>]
Can do.
Dec 15 14:30:05 penguin pppd[5356]: rcvd [LCP ConfAck id=0x1 <asyncmap
0x0> <magic 0x19cc75e0> <pcomp> <accomp>]
We like your options.
Dec 15 14:30:05 penguin pppd[5356]: sent [LCP EchoReq id=0x0
magic=0x19cc75e0]
Not sure what this is for.
Dec 15 14:30:05 penguin pppd[5356]: rcvd [CHAP Challenge id=0x2c
<f0349589e548271b>, name = "ALF"]
Hey! Who goes there!
Dec 15 14:30:05 penguin pppd[5356]: sent [CHAP Response id=0x2c
<000000000000000000000000000000000000000000000000edd2f58c6693fc909aa65522645462c2e2bee7e2a58ee14f01>,
name = "iabuser"]
I do!
Dec 15 14:30:05 penguin pppd[5356]: rcvd [LCP EchoRep id=0x0
magic=0x606c]
A response to the above EchoReq I assume.
Dec 15 14:30:08 penguin pppd[5356]: sent [CHAP Response id=0x2c
<000000000000000000000000000000000000000000000000edd2f58c6693fc909aa65522645462c2e2bee7e2a58ee14f01>,
name = "iabuser"]
Huh. 3 seconds and no reply from the NT box. Better send that
"I do!" message again. It occured to me that perhaps the resend of
the response is confusing the NT box, so I tried upping the
chap-restart to 10 seconds. The same failure results, but without
the resend of the reponse.
Dec 15 14:30:08 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
You're not allowed here, maybe tomorrow. I know 691 is the
auth failure code. The other clue (besides the event log entry)
is that NT seems to think the error is transient and we can retry
the auth sequence. Why my linux box doesn't retry it, I don't
know.
The stuff below just repeats until pppd gets tired and times out,
hanging up the modem.
Dec 15 14:30:08 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:08 penguin pppd[5356]: CHAP authentication failed
Dec 15 14:30:08 penguin pppd[5356]: CHAP authentication failed
Dec 15 14:30:10 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:10 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:12 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:12 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:14 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:14 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:16 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:16 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:18 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:18 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:20 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:20 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:22 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:22 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:24 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:24 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:26 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:26 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:28 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:28 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:30 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:30 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:32 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:32 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:34 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:34 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:35 penguin pppd[5356]: sent [LCP EchoReq id=0x1
magic=0x19cc75e0]
Dec 15 14:30:35 penguin pppd[5356]: rcvd [LCP EchoRep id=0x1
magic=0x606c]
Dec 15 14:30:36 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:36 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:38 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:38 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:40 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:40 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:42 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:42 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:44 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:44 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:46 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:46 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:48 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:48 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:50 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:50 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:52 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:52 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:54 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:54 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:56 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:56 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:30:58 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:30:58 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:00 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:00 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:02 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:02 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:04 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:04 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:05 penguin pppd[5356]: sent [LCP EchoReq id=0x2
magic=0x19cc75e0]
Dec 15 14:31:05 penguin pppd[5356]: rcvd [LCP EchoRep id=0x2
magic=0x606c]
Dec 15 14:31:06 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:06 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:08 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:08 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:10 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:10 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:12 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:12 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:14 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:14 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:16 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:16 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:18 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:18 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:20 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:20 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:22 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:22 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:24 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:24 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:26 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:26 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:28 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:28 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:30 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:30 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:32 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:32 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:34 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:34 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:35 penguin pppd[5356]: sent [LCP EchoReq id=0x3
magic=0x19cc75e0]
Dec 15 14:31:35 penguin pppd[5356]: rcvd [LCP EchoRep id=0x3
magic=0x606c]
Dec 15 14:31:36 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:36 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:38 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:38 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:40 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:40 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:42 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:42 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:44 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:44 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:46 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:46 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:48 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:48 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:50 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:50 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:52 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:52 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:54 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:54 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:56 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:56 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:31:58 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:31:58 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:32:00 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:32:00 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:32:02 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:32:02 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:32:04 penguin pppd[5356]: rcvd [CHAP Failure id=0x2c "E=691
R=1"]
Dec 15 14:32:04 penguin pppd[5356]: Remote message: E=691 R=1
Dec 15 14:32:05 penguin pppd[5356]: sent [LCP EchoReq id=0x4
magic=0x19cc75e0]
Dec 15 14:32:05 penguin pppd[5356]: rcvd [LCP EchoRep id=0x4
magic=0x606c]
Dec 15 14:32:06 penguin pppd[5356]: Hangup (SIGHUP)
Dec 15 14:32:06 penguin pppd[5356]: Modem hangup
Dec 15 14:32:06 penguin pppd[5356]: Connection terminated.
Dec 15 14:32:07 penguin pppd[5356]: Exit.
--- Cut Here ---
...Stu
------------------------------
From: James Huang <[EMAIL PROTECTED]>
Subject: Re: Cant use two ethernet interfaces
Date: Sat, 02 Jan 1999 06:50:15 GMT
In article <[EMAIL PROTECTED]>,
Alexander Brinkman <[EMAIL PROTECTED]> wrote:
> My /etc/conf.modules look like this:
>
> alias eth0 ne
> options ne io=0xff00,0x240 irq=10,5
> alias eth1 ne
> options ne io=0xff00,0x340 irq=10,5
>
> Note: You will need to add the io and irq of BOTH cards in the setup
of the
> 2 cards (seperated by commas).
> Also see the documentation that comes with the kernel.
>...
>
> Grtz,
> Eon.
>
Just want to confirm that THIS DOES WORK!
I have 2 SMC EtherEZ cards, each with the following settings:
Card 1: Mem Base: D0000, I/O Base: 240, IRQ: 10, PnP: disabled
Card 2: Mem Base: CE000, I/O Base: 280, IRQ: 11, PnP: disabled
And I typed in these lines in conf.modules:
alias eth0 smc-ultra
options smc-ultra io=0x240,0x280 irq=10,11
alias eth1 smc-ultra
options smc-ultra io=0x240,0x280 irq=10,11
This worked. Finally!
Thanks Eon!
James
(I have to cut the original message, otherwise my news client doesn't
allow me to post!)
------------------------------
From: "Joekie" <[EMAIL PROTECTED]>
Subject: After IP Masquerade done ??
Date: Sat, 02 Jan 1999 06:50:21 GMT
I have configured IP Masquerade on my Linux box and it work fine with my
other Win95 Machine on LAN.
By the way, It is posible to do this :-
Can anyone tell me how to configure so that the modem dial when the client
from Win95 get access to the Internet and the line drop if nobody get access
to the Internet ???
Thanks in advance ....
Joekie Thong
------------------------------
Date: Fri, 01 Jan 1999 20:32:45 -0700
From: Lamar Cole <[EMAIL PROTECTED]>
Subject: Re: US WEST Megabit service?
I have been using the USWest Megabits service for about a month. The
'modem' that came with the service was a Cisco 675. My Linux box
had been serving as the internet gateway for the other machines on
my home lan. When I got the 675, however, I just plugged it into
my hub (using a different cable than the crossover sent with the
MegaBits package), and now the other machines can get out to the
internet without having to go thru my machine. Just configure them
to use DHCP on your Network configuration screens, or (if they're
Linux boxes too) install dhcpcd. The 675 will get them the IP
addresses to use.
Regards,
VLC
Brent Rader wrote:
> I am thinking of trying this Megabit service from US WEST. I want to
> connect my Linux machine with it and then provide internet access to the
> other PCs on my lan. They say that you get an external modem with the
> deal that you can connect via a network card. I called US WEST to find
> out what exactly this modem is but they didn't seem to know. All they
> could tell me is that it is made by Cisco. So, I am wondering if anyone
> has tried this service or happens to know exactly what this modem is and
> if I can use it with Linux on my network??
>
> Thanks,
> BR
------------------------------
From: "Rob" <[EMAIL PROTECTED]>
Subject: Re: Setting up a proxy server to distribute a cable modem signal
Date: Sat, 02 Jan 1999 06:43:27 GMT
Well, you can either have the fun of settingup IP Masquerading on your new
RH 5.2 box, or go to www.sharethenet.com and get the turnkey solution they
provide for $70 and not have to do a thing :)
[EMAIL PROTECTED] wrote in message
<[EMAIL PROTECTED]>...
> I have a cable modem signal coming into my house, and have
>decided to set up a network to split the signal into 2 seperate IP
>addresses so my roommate and I can both use the connection
>simultaneously. I was told linux would handle this best, so I picked
>up Red Hat v5.2 to throw on an old 486 I have sitting around to use as
>the proxy server. I'm in the middle of the installation, and it
>struck me that I have very little idea as to how to exactly go about
>doing this.
>
> Will the linux box be set up as a server? If so, how do I
>configure it? It seems to me, from what people have told me, I may
>have to set it up as a workstation, and get a program to run on it for
>use as a proxy server. I checked sunsite.unc.edu/pub/linux, and
>couldn't really find anything to do this. If this situation is how it
>must be handled, does anyone know where I'd get the proper software
>(GNU GPL if at all possible)?
>
> Thanks very much in advance for help. If at all possible, please
>email your responses to me at [EMAIL PROTECTED], and I will
>post a summary after I have it figured out.
------------------------------
From: Bill Amsinux <[EMAIL PROTECTED]>
Subject: Re: How can you get Linux to log into NT Server 4.0
Date: Sat, 02 Jan 1999 06:43:29 GMT
Hi !
I am afraid that you can't do this. NTs idea is based on the dictatorship
of being
centralised admin and so is MS. The domain controller has the power and
all user
accounts to verify login(logon) to the network for sharing resources.
Unix is not based on the same idea.
But the main thing is to share resources, so you can use SAMBA to connect
with NT.
Personally, my experience with NT and LINUX told me that Linux is very
tolerant
with NT(MS STUFF), but NT is not very co-operative.
What i said is what i know to that extent, comments are welcome.
Bill Amsinux
"Richard F. Jr." wrote:
> I have a Linux system happy :) and running S.u.S.E. Linux 5.3 with -
> kernel 2.0.36.SuSE
> with network support..... So how do I do it ? the interface is 10/100
>
> drop a line please,
> Rich
------------------------------
From: Rick Moen <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.setup
Subject: Re: NOSPAM in addresses..
Date: 2 Jan 1999 09:47:28 GMT
In comp.os.linux.setup Randal <[EMAIL PROTECTED]> wrote:
: I have my news program set to both email and post to group. I figure
: that the person may not check back to the group quickly and I assume
: that when a question is asked, the person asking wants an answer.
: Sometimes desparately.
If you do this, I _sincerely_ hope you mention in the e-mail that
your reply was both posted and mailed.
If you don't do that, then the recipient may spend considerable
time sending you an e-mail reply, only to be faced with the need
to draft a duplicate _newsgroup_ followup the next day. This can
be extremely annoying.
Speaking of annoying, this netiquette discussion is now sprawled across
three technical newsgroups. Please note that I have set follow-ups.
(Why didn't _you_?)
--
Cheers, The cynics among us might say: "We laugh,
Rick Moen monkeyboys -- Linux IS the mainstream UNIX now!
rick (at) linuxmafia.com MuaHaHaHa!" but that would be rude. -- Jim Dennis
------------------------------
** 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
******************************
