Linux-Networking Digest #276, Volume #12 Wed, 18 Aug 99 19:13:47 EDT
Contents:
Re: RAS ppp dialup response? ("Robert_Glover")
tulip.c recognizes Macronix MX98715AEC but brings link down (Benjamin Kunz)
Re: Routing.. ("Phil")
Re: Solved Linksys Etherfast 10/100 Problems ([EMAIL PROTECTED])
Re: WhereToFind? Socket 7 motherboard with onboard ethernet, sound, and (Shawn
Green)
Re: Can't get 2 NIC's to work too (Scott McEachern)
Re: RAS ppp dialup response? (Clifford Kite)
PPP problem ([EMAIL PROTECTED])
yes!! samba! (Lindoze 2000)
Re: Linux NFS: 'Permission denied' error ([EMAIL PROTECTED])
ppp intermitent connection (Salvador =?iso-8859-1?Q?Main=E9=20L=F3pez?=)
----------------------------------------------------------------------------
From: "Robert_Glover" <Please_reply_to@newsgroup>
Subject: Re: RAS ppp dialup response?
Date: Wed, 18 Aug 1999 18:45:24 -0000
Try using the PASSIVE option.
[EMAIL PROTECTED] wrote in message <7pe78o$ou0$[EMAIL PROTECTED]>...
>My company recently switched to Microsoft RAS which supposedly supports
>ppp access. However, when I dial up the number using minicom, I get no
>"garbage" on the screen that I normally expect from a ppp server.
>Starting up pppd by hand, pppd does not get very far:
>
>Connect: ppp0 <--> /dev/cua0
>LCP: timeout sending Config-Requests
>Connection terminated.
>
>It looks like there is no ppp server on the other end, and doesn't even
>get to the server negotiation phase. Connecting via Win95 works,
>though.
>
>Thanks for any pointers.
>
>-Maurice
>
>
>Sent via Deja.com http://www.deja.com/
>Share what you know. Learn what you don't.
------------------------------
From: Benjamin Kunz <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: tulip.c recognizes Macronix MX98715AEC but brings link down
Date: Wed, 18 Aug 1999 20:44:47 +0200
Hi.
Well, the Subject says it - The MX98715AEC chip is apparently recognized
by the tulip driver, but does not function - the link LED goes off - is
there any chance to get these cards to operate with linux?
Thanks in advance -
ben
------------------------------
From: "Phil" <[EMAIL PROTECTED]>
Subject: Re: Routing..
Date: Wed, 18 Aug 1999 13:59:21 -0700
I think you need to confirm or add default gw routes for each machine.
If a machine on a subnet has a packet with an IP it doesn't know how to
deliver (outside it's subnet) it sends the packet to it's default gateway.
The job of the gw is to check it's routing tables and figure out where to
send the packet. The gateway machine should have default routes in it to
allow it to deliver packets between subnets attached to it and a default gw
route for packets not on it's attached subnets.
I don't see routes on some of your machines.
Hope this helps,
Phil
Dustin Puryear <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> I have two gateways on one subnet. The first is the company's internet
> firewall and has the address 192.168.1.1. The second connects this
> subnet with the other subnets and has the address 192.168.1.2. Also,
> 192.168.1.2 uses 192.168.1.1 as the default route.
>
> Now, machines on the other subnets are not able to access the
> internet. Also, windows machines are only able to access the internet
> if they have 192.168.1.1 as the default route. What do I need to
> change in order for all machines to access both the internet and the
> other subnets? Following are examples for the routing tables of
> machines both on the local and remote subnets:
>
> [Linux on another subnet (192.168.11.1)]
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window
> irtt Iface
> 192.168.1.2 0.0.0.0 255.255.255.255 UH 0 0
> 0 ppp0
> 255.255.255.255 0.0.0.0 255.255.255.255 UH 0 0
> 0 eth0
> 192.168.1.0 192.168.1.2 255.255.255.0 UG 0 0
> 0 ppp0
> 192.168.11.0 0.0.0.0 255.255.255.0 U 0 0
> 0 eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
> 0 lo
> 0.0.0.0 192.168.1.2 0.0.0.0 UG 0 0
> 0 ppp0
>
> [SCO OSR5 on local subnet (192.168.1.3)]
> Routing tables
> Destination Gateway Flags Refs Use Interface
> default 192.168.1.2 UGS 2 944 net1
> 127.0.0.1 127.0.0.1 UH 3 6848 lo0
> 192.168.1 192.168.1.3 UC 1 0 net1
> 192.168.1.3 127.0.0.1 UGHS 3 61 lo0
> 224 192.168.1.3 UCS 0 0 net1
>
> [Linux on local subnet (192.168.1.2)]
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window
> irtt Iface
> 192.168.11.1 0.0.0.0 255.255.255.255 UH 0 0
> 0 ppp0
> 255.255.255.255 0.0.0.0 255.255.255.255 UH 0 0
> 0 eth0
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0
> 0 eth0
> 192.168.11.0 192.168.11.1 255.255.255.0 UG 0 0
> 0 ppp0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
> 0 lo
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0
> 0 eth0
>
> [Linux on local subnet, firewall (192.168.1.1) with diald]
> Destination Gateway Genmask Flags MSS Window
> irtt Iface
> 206.151.208.72 0.0.0.0 255.255.255.255 UH 0 0
> 0 ppp0
> 206.151.208.72 0.0.0.0 255.255.255.255 UH 0 0
> 0 ppp0
> 127.0.0.3 0.0.0.0 255.255.255.255 UH 0 0
> 0 sl0
> 127.0.0.3 0.0.0.0 255.255.255.255 UH 0 0
> 0 sl0
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0
> 0 eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
> 0 lo
> 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0
> 0 ppp0
> 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0
> 0 sl0
>
> Any help is appreciated!
> ---
> Dustin Puryear
> [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.hardware
Subject: Re: Solved Linksys Etherfast 10/100 Problems
Date: Wed, 18 Aug 1999 21:14:43 GMT
I got the following hillarious article from the tulip driver archives.
Hope it solves most of your Linksys Etherfast 10/100 LAN card problems
on Linux:
Linksys PNIC II glitches
Robin Whittle ([EMAIL PROTECTED])
Sat, 14 Aug 1999 01:29:42 +1000
Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Kevin Myer: "Re: strange behavior with 21143 cards"
Previous message: Richard Dynes: "Re: 2.2.11 and tulip.c issues"
Short version:
1 - The Linksys LNE100TX NICs I recently purchased with the
*excellent* super-cost-effective EZXS55W 5 port 10/100 Meg switch
are more trouble that they are worth for me, due to difficulties
with drivers under Linux, and a few other intermittent problems
which have been reported, and observed.
2 - Positive appraisal and defanning of the EZXS55W.
- - - -
Dear Donald and Linksys people,
(Also to the Tulip driver development list.)
Thanks, Donald, for your Ethernet drivers for Linux!
I am writing to report that your currently valid driver version (v0.91
4/14/99) at
http://cesdis.gsfc.nasa.gov/linux/drivers/tulip.c
does not work with my particular Linksys NICs, but that the version
which comes on a floppy from Linksys does.
"v0.90f 12/17/98 Originally written by
[EMAIL PROTECTED]
Driver modified for Linksys LNE100TX Fast Ethernet
PCI Adapter on 01/13/99"
Here is a description of the NIC.
PCB says:
Part No.: LNE100TX
Version 2.0
P/N:6804057404 REV:A2
(Date code on foil side of PCB: "9816".)
LSI, 128 pins:
LINKSYS
LNE100TX
LC82C115
C9914
T4023702
37BDX
This card has a "WOL" Wake On LAN connector and a 6 pin jumper to
configure it.
These NICs works fine with Windows 98.
They are not recognised at all by the Red Hat 6.0 installation
procedure. (This is a pest even if the card is subsequently made to
work, since I find it easier to install via LAN and set up all the
networking details during installation, rather than later.)
Once RH6.0 is installed, attempts to use the normal tulip.o driver
fail, with an error message pointing out that the card ID of:
11ad c115
is not recognised.
Therefore, I looked up the Ethernet HowTo, which took me to the
Linksys page:
http://www.linksys.com/support/solution/nos/linux_lne100tx.htm
which directed me to use the latest available driver at:
http://cesdis.gsfc.nasa.gov/linux/drivers/tulip.c
(v0.91 4/14/99) which I compiled and installed. The driver was happy
with the NIC, but it would not in fact send or receive any packets to
the LAN (actually to a magnificent Linksys 100 Mbps 5 port *switch*).
(BTW, the Linksys page says to "depmod -a", which I did, but this is
not mentioned on the development page.)
I tried every other possible configuration thing, and still it would
not work.
When I compiled the driver from the floppy, the worked fine. (Althoug
I have not extensively tested it.)
Clearly the "v0.91 4/14/99" driver is supposed to work with this chip,
since:
1 - The source mentions its PCI ID and has special provisions for it.
2 - The Linksys site indicates that this is the driver code to use.
3 - The driver recognises the chip and installs itself happily, with
the message:
"Lite-On PNIC-II rev 37 at . . . . IRQ 9"
4 - TCP-DUMP reports activity of packets sent to this interface.
However, it simply doesn't work! (I have not tried the "testing"
version of the driver, currently "v0.91g".)
Here are some suggestions for Linksys to improve matters:
1 - Correct the page:
http://www.linksys.com/support/solution/nos/linux_lne100tx.htm
which states that for RH5.2 and 6.0 the standard drivers will
work. (Below that, there is a qualification, for if they don't!)
Also, it states that the current driver from the Tulip team
should work, which it doesn't - for these particular cards.
2 - Make the Floppy 2 /linux/ directory more helpful than simply the
tulip.c file and the GPL copying file. Point the user to the
web support page, and the Tulip development site. Give explicit
compilation and installation instructions in a readme.txt file.
Other concerns
==============
I note in the Errata of:
http://cesdis.gsfc.nasa.gov/linux/drivers/tulip.html
"Due inaccurate documentation, autonegotiation cannot be enabled on
the PNIC chip."
This sounds like a good reason to use another kind of NIC!
This NIC card in my Windows machine occasionally (say every ten or
twenty minutes - or more often with lots of activity?) appears to die
for a second or so. The three LEDs for this card on the 5 port switch
go off together, and then come back on together.
According to the mailing list archives, a number of incorrect
behaviours have been observed with some PNIC based cards. I am not
sure if these are exactly the same cards as I have, but I would prefer
to avoid using cards which occasionally send invalid data to the LAN.
Whether these problems are caused by faulty driver design or not, I
cannot tell.
The point is, life is too way short to be spending time debugging
other people's hardware and software when all you want is a handfull
of bulletproof NICs! I can buy tried-and-tested Intel NICs (S/H
82557s for USD$33) and not have to worry about any of this! I only
got these Linksys NICs as part of the switch package, and I don't plan
to buy any more, or use them except perhaps on Windows machines . . .
but even then, I want real-time audio through the LAN, so I can't have
NICs going to sleep for a moment.
The Tulip Development Page has details of joining the mailing list.
Here are some URLs of recent postings in the archive pointing to
anomalous behaviour of PNIC cards (not necessarily the same type as
mine):
Problem with Linksys etherfast 10/100
http://www.tux.org/hypermail/linux-tulip-bug/1999-Jul/0014.html
Linksys PNIC card hangs up under load (v. 0.91g)
http://www.tux.org/hypermail/linux-tulip-bug/1999-Jul/0012.html
Odd bug when using tulip v0.91g on a LinkSys EtherFast 10/100 card
http://www.tux.org/hypermail/linux-tulip-bug/1999-Aug/0003.html
" . . . Whenever I send data from this card, it randomly (as far as
I can tell) cuts 2 characters within the file and moves them
forward a character before replacing them. . . . "
(Seriously low-level user debugging!)
- - - -
I have put the tulip.c from the floppy, this email, and any other
related files at:
http://gair.firstpr.com.au/temp/tulip/
- - - -
All hail the Linksys EZXS55W 5 port 10/100 Ethernet Switch!
===========================================================
Finally, lest someone think I have something against Linksys, let me
say that I think their new 5 port 10/100 Ethernet EZXS55W *Switch* is
a beauty! The cost here, ex-tax, with two NICs and two cables as a kit
was AUD$330, which is USD$215. If you look around, such as:
http://www.1stcomputersource.com/cgi-win/detail.exe?443980
the switch itself can be purchased for USD$124.
It is small, and has a fan - which is a source of noise and a dust and
long-term maintenance issue. (The fan is a 40mm sleeve bearing
Sunon.)
I modified my EZXS55W for fanless operation by removing the rear
panel, replaceing the top panel with a metal grid, adding a large
heatsink to the heatsink on the main LSI (I found one which
interdigitated nicely, used silicone grease, and cut some sheet
aluminium to slot into the side-slots of the case and work as a spring
to hold it in place) and adding a heatsink to the second largest LSI
(Allayer AL102).
As far as I know, this device is a faultless full-duplex 5 port 10/100
meg switch. Apart from perhaps its use of a fan, I think it is
beautifully made - and its cost is extremely attractive!
- Robin
===============================================================
Robin Whittle [EMAIL PROTECTED] http://www.firstpr.com.au
Heidelberg Heights, Melbourne, Australia
First Principles Research and expression: Consulting and
technical writing. Music. Internet music
marketing. Telecommunications. Consumer
advocacy in telecommunications, especially
privacy. M-F relationships. Kinetic sculpture.
Real World Electronics and software for music including:
Interfaces Devil Fish mods for the TB-303, Akai sampler
memory and Csound synthesis software.
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: Shawn Green <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.portable,comp.os.linux.hardware
Subject: Re: WhereToFind? Socket 7 motherboard with onboard ethernet, sound, and
Date: Wed, 18 Aug 1999 12:08:27 -0700
OK, I need to ask. Why/how are you going to put a computer in your car?
BTW, go to www.atacom.com or www.astak.com. You may be able to find the
board at one of those places.
Shawn
David Scott Copus wrote:
> I'm looking for a Socket 7 (preferable Super 7) that has *onboard*
> sound, ethernet, and video. Does anybody recommend any
> motherboards that have all these features... and can work
> with Linux?
>
> Or... if you know where I can look to find motherboards with all
> these features... I will gladly accept any suggestions!!
>
> Just curious... but would an Intel 166 MMX (socket 7) run _cooler_
> or _warmer_ than any Pentium II chip? I want to put a computer
> in my car... and am concerned about heat. :>
>
> thanks!
> Scott.
> [EMAIL PROTECTED]
------------------------------
From: Scott McEachern <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,comp.os.linux.setup
Subject: Re: Can't get 2 NIC's to work too
Date: Wed, 18 Aug 1999 22:06:35 GMT
eelco of viola wrote:
> Ed Wilts <[EMAIL PROTECTED]> schreef in berichtnieuws
> [EMAIL PROTECTED]
> > [EMAIL PROTECTED] wrote:
> > >
> > > I have 2 identical 3com 905b NIC's. When I use just
> > > one to connect my machine to the outside world
> > > everthing is fine. As soon as I try to put both cards
> > > in nothing works. On bootup I get a delaying
> > > initialization message for both eth0 & eth1. Also adm
> > > takes forever to start when this happens.
> >
> > Try re-compiling your kernel without making the NIC modular. On some
> > (all?) NICs, making them modular won't work. I've got mine permanent
> > (and after all, I'm using them all the time anyway) and it's working
> > fine compiled in. I'm using PCI-based NE2000 clones.
> >
> > .../Ed
> > --
> > Ed Wilts
> > Mounds View, MN, USA
> > mailto:[EMAIL PROTECTED]
>
> Hello I`ve got the same problem using two NE2000 pci clones.
> I have them compiled in the kernel But they still won`t work together.
> At startup no delayes or failing messages.
>
> Can annyone shed another light on this matter maybe?
>
> thanks Eelco
I'm running SuSE 6.1, 2.2.10 with two PCI NE2k clones without any
problems. I only have the NE2k driver compiled in, and not as a module,
and the driver picks up both.
I wonder if it's because you have PnP enabled in your BIOS? Linux
usually get hairy around that stuff. I'm just wondering if they are both
competing for the same IRQ or something...
Try upgrading to the latest kernel (thus latest drivers)?
--
mailto:[EMAIL PROTECTED]
http://www3.sympatico.ca/scott.mceachern
On the side of the software box, in the "System requirements section",
it said "Requires Windows 95 or better." So I installed Linux.
------------------------------
From: kite@NoSpam.%inetport.com (Clifford Kite)
Subject: Re: RAS ppp dialup response?
Date: 18 Aug 1999 16:29:04 -0500
[EMAIL PROTECTED] wrote:
: My company recently switched to Microsoft RAS which supposedly supports
: ppp access. However, when I dial up the number using minicom, I get no
: "garbage" on the screen that I normally expect from a ppp server.
: Starting up pppd by hand, pppd does not get very far:
: Connect: ppp0 <--> /dev/cua0
: LCP: timeout sending Config-Requests
: Connection terminated.
Don't really know NT RAS but isn't there a text exchange required to
start things rolling? Something like the caller sending CLIENT and the
NT returning CLIENTSERVER?
--
Clifford Kite <kite@inet%port.com> Not a guru. (tm)
/* A salute to Inspector Baynes, of the Surry Constabulary, the only
police Inspector to ever best Mr. Sherlock Holmes at his own game.
"The Adventure of Wisteria Lodge", by Sir Arthur Conan Doyle. */
------------------------------
From: [EMAIL PROTECTED]
Subject: PPP problem
Date: Wed, 18 Aug 1999 21:59:04 GMT
Hi,
I am a little new to the Linux world and would like some help on getting
my ppp working. I installed RH6.0 a few days ago and have still not been
successful with ppp.
When I execute the ppp and chat scripts (copied and changed from
/usr/doc), the modem dials out and I get an IP address allocated to my
machine, but I am not able to ping anyplace except the IP address I am
assigned. I have checked /etc/resolv.conf for an erroneous entry, and to
me it looks ok. It doesn't matter if I use an IP address or a domain
name in the ping. There is still no response.
Entries in my log:
Aug 18 15:13:51 zeus kernel: CSLIP: code copyright 1989 Regents of the
University of California
Aug 18 15:13:51 zeus kernel: PPP: version 2.3.3 (demand dialling)
Aug 18 15:13:51 zeus kernel: PPP line discipline registered.
Aug 18 15:13:51 zeus kernel: registered device ppp0
Aug 18 15:13:51 zeus pppd[1631]: pppd 2.3.7 started by root, uid 0
Aug 18 15:13:52 zeus chat[1632]: timeout set to 3 seconds
Aug 18 15:13:52 zeus chat[1632]: abort on (\nBUSY\r)
Aug 18 15:13:52 zeus chat[1632]: abort on (\nNO ANSWER\r)
Aug 18 15:13:52 zeus chat[1632]: abort on (\nRINGING\r\n\r\nRINGING\r)
Aug 18 15:13:52 zeus chat[1632]: send (rAT^M)
Aug 18 15:13:52 zeus chat[1632]: expect (OK)
Aug 18 15:13:52 zeus chat[1632]: rAT^M^M
Aug 18 15:13:52 zeus chat[1632]: OK
Aug 18 15:13:52 zeus chat[1632]: -- got it
Aug 18 15:13:52 zeus chat[1632]: send (ATH0^M)
Aug 18 15:13:52 zeus chat[1632]: timeout set to 30 seconds
Aug 18 15:13:52 zeus chat[1632]: expect (OK)
Aug 18 15:13:52 zeus chat[1632]: ^M
Aug 18 15:13:53 zeus chat[1632]: ATH0^M^M
Aug 18 15:13:53 zeus chat[1632]: OK
Aug 18 15:13:53 zeus chat[1632]: -- got it
Aug 18 15:13:53 zeus chat[1632]: send (ATDT594-9858^M)
Aug 18 15:13:53 zeus chat[1632]: expect (CONNECT)
Aug 18 15:13:53 zeus chat[1632]: ^M
Aug 18 15:14:09 zeus chat[1632]: ATDT594-9858^M^M
Aug 18 15:14:09 zeus chat[1632]: CONNECT
Aug 18 15:14:09 zeus chat[1632]: -- got it
Aug 18 15:14:09 zeus chat[1632]: send (^M)
Aug 18 15:14:09 zeus chat[1632]: expect (sername:)
Aug 18 15:14:09 zeus chat[1632]: 14400/ARQ/V32/LAPM/V42BIS^M
Aug 18 15:14:10 zeus chat[1632]: ^M
Aug 18 15:14:10 zeus chat[1632]: Annex Command Line Interpreter *
Copyright 1991 Xylogics, Inc.^M
Aug 18 15:14:10 zeus chat[1632]: ^M
Aug 18 15:14:10 zeus chat[1632]: Checking authorization, Please
wait...^M
Aug 18 15:14:10 zeus chat[1632]: username:
Aug 18 15:14:10 zeus chat[1632]: -- got it
Aug 18 15:14:10 zeus chat[1632]: send (my_userid^M)
Aug 18 15:14:11 zeus chat[1632]: expect (assword:)
Aug 18 15:14:11 zeus chat[1632]: my_userid^M
Aug 18 15:14:11 zeus chat[1632]: password:
Aug 18 15:14:11 zeus chat[1632]: -- got it
Aug 18 15:14:11 zeus chat[1632]: send (my_password^M)
Aug 18 15:14:11 zeus chat[1632]: expect (nnex:)
Aug 18 15:14:11 zeus chat[1632]: ^M
Aug 18 15:14:11 zeus chat[1632]: ^M
Aug 18 15:14:11 zeus chat[1632]: Permission granted; Type telnet or ppp
for network connection^M
Aug 18 15:14:11 zeus chat[1632]:
===============================================================================^M
Aug 18 15:14:11 zeus chat[1632]:
Aug 18 15:14:11 zeus chat[1632]: To start ppp connection type ppp at the
annex prompt after logging in.^M
Aug 18 15:14:11 zeus chat[1632]: ^Iannex:
Aug 18 15:14:11 zeus chat[1632]: -- got it
Aug 18 15:14:11 zeus chat[1632]: send (ppp^M)
Aug 18 15:14:11 zeus pppd[1631]: Serial connection established.
Aug 18 15:14:11 zeus pppd[1631]: Using interface ppp0
Aug 18 15:14:11 zeus pppd[1631]: Connect: ppp0 <--> /dev/ttyS1
Aug 18 15:14:13 zeus kernel: PPP BSD Compression module registered
Aug 18 15:14:13 zeus kernel: PPP Deflate Compression module registered
Aug 18 15:14:16 zeus pppd[1631]: local IP address 128.198.66.19
Aug 18 15:14:16 zeus pppd[1631]: remote IP address 128.198.66.66
Output of my netstat -rn is as follows:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
192.168.1.1 0.0.0.0 255.255.255.255 UH 0 0 0
eth0
128.198.66.66 0.0.0.0 255.255.255.255 UH 0 0 0
ppp0
192.168.1.0 192.168.1.1 255.255.255.0 UG 0 0 0
eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
lo
0.0.0.0 128.198.66.66 0.0.0.0 UG 0 0 0
ppp0
0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0
eth0
Output of ifconfig is as follows:
eth0 Link encap:Ethernet HWaddr 00:00:21:62:61:8D
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:514 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:12 Base address:0x280
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:275 errors:0 dropped:0 overruns:0 frame:0
TX packets:275 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
ppp0 Link encap:Point-to-Point Protocol
inet addr:128.198.66.19 P-t-P:128.198.66.66
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
I have been looking for ideas in this newsgroup and have looked at the
PPP-HOWTO as well. I don't know what I am missing. I am very thankful
for any help offered.
Thanks,
Krishna.
------------------------------
From: Lindoze 2000 <[EMAIL PROTECTED]>
Subject: yes!! samba!
Date: Wed, 18 Aug 1999 18:53:13 -0400
I got windoze to see samba for the first time yesterday by accident!
Today I got windoze to see files on my linux box via. samba by accident!
now how can I add and remove shares on my linux?
so say I want to add /home/thisguy and /mnt
Later I decide to not show /mnt
how would I do this?
--
Thank you for your valuable input. Your useful answers will benifit
other users as well.
You are Linux!
########################################################
## ##
## My Experiment ##
## http://www.FusionPlant.com ##
## ##
########################################################
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Linux NFS: 'Permission denied' error
Date: Wed, 18 Aug 1999 21:51:24 GMT
It's a bug... Had the same problem in our shop. Found many other
people having same problem with RH 6.0 Solution stated was to upgrade
to a newer kernel and get newer nfs daemon.
-Dave
In article <[EMAIL PROTECTED]>,
Allen Wong <[EMAIL PROTECTED]> wrote:
> Robert,
>
> Please post your "exports" file and the output of this command:
>
> /usr/sbin/showmount -e <NFS server>
>
> Allen
> --
> Linux: If you're not careful, you might actually learn something.
>
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: Salvador =?iso-8859-1?Q?Main=E9=20L=F3pez?= <[EMAIL PROTECTED]>
Subject: ppp intermitent connection
Date: Fri, 13 Aug 1999 09:40:50 +0200
Hello:
I used to connect my LAN to internet though a on-demand dial-up
connection (diald + ipmasquerading).
Then I upgraded to RH6.0 and changed diald by pppd. The connection
worked but it went really slow. The transfer rate vary from 8 KB/s to
0KB/s without apparent reason.
Here go my configuration files. Does someone find something wrong on
them?
NOTE: now, I'm using a proxy in a windows machine until I find a better
solution
Thank you very much in advance
=======================
/etc/rc.d/local.rc
===============================
# material para IP-masquerading
/sbin/modprobe ip_masq_ftp
# ipchains
/sbin/ipchains -P forward DENY
/sbin/ipchains -A forward -s 192.168.1.0/24 -j MASQ
# pppd con opciones de llamada bajo demanda
pppd
/etc/ppp/options
==========================================
connect /etc/ppp/infovia
demand
192.168.0.1:192.168.0.20
ipcp-accept-local
ipcp-accept-remote
idle 600
holdoff 15
mtu 1500
#mru 1500
crtscts
modem
passive
#+pap
user usuario@psi
noipdefault
debug
defaultroute
asyncmap a0000
/dev/modem
115200
/etc/ppp/infovia
====================================
#!/bin/sh
/usr/sbin/chat -v ABORT BUSY ABORT "NO CARRIER" "" "ATZ" "OK"
"ATDT0952079000"
CONNECT ""
/var/log/messages
===================================
Aug 10 08:57:05 servidor pppd[616]: Starting link
Aug 10 08:57:06 servidor chat[873]: abort on (BUSY)
Aug 10 08:57:06 servidor chat[873]: abort on (NO CARRIER)
Aug 10 08:57:06 servidor chat[873]: send (ATZ^M)
Aug 10 08:57:06 servidor chat[873]: expect (OK)
Aug 10 08:57:06 servidor chat[873]: ATZ^M^M
Aug 10 08:57:06 servidor chat[873]: OK
Aug 10 08:57:06 servidor chat[873]: -- got it
Aug 10 08:57:06 servidor chat[873]: send (ATDT0952079000^M)
Aug 10 08:57:07 servidor chat[873]: expect (CONNECT)
Aug 10 08:57:07 servidor chat[873]: ^M
Aug 10 08:57:30 servidor chat[873]: ATDT0952079000^M^M
Aug 10 08:57:30 servidor chat[873]: CONNECT
Aug 10 08:57:30 servidor chat[873]: -- got it
Aug 10 08:57:30 servidor chat[873]: send (^M)
Aug 10 08:57:30 servidor pppd[616]: Serial connection established.
Aug 10 08:57:30 servidor pppd[616]: Connect: ppp0 <--> /dev/modem
Aug 10 08:57:35 servidor pppd[616]: Remote message: Password Accepted
Aug 10 08:57:35 servidor modprobe: can't locate module ppp-compress-21
Aug 10 08:57:35 servidor modprobe: can't locate module ppp-compress-26
Aug 10 08:57:35 servidor modprobe: can't locate module ppp-compress-24
Aug 10 08:57:42 servidor pppd[616]: Unsupported protocol (0x31) received
Aug 10 08:58:06 servidor pppd[616]: Unsupported protocol (0x31) received
=======================
--
Salvador Main� L�pez
CentroRed SL - Desarrollos
http://www.centrored.com
------------------------------
** 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
******************************
