Linux-Networking Digest #931, Volume #9 Tue, 19 Jan 99 06:13:44 EST
Contents:
Re: Connect without hub ([EMAIL PROTECTED])
Re: lpd configuration problem ([EMAIL PROTECTED])
Re: cant get Samba to work right ("Glenn Davy")
Re: Online with Linux (cgreek)
Re: Need help compiling C in Linux, NIC not working. ([EMAIL PROTECTED])
Re: DOES LINUX SUCK (David Steuber)
Re: Which network driver for SMC 8216T and Red Hat 5.2? (Rick Moen)
Re: /usr over nfs? (Richard Hector)
Re: Need help with diagnosing a network problem ("Jay D Ribak")
Network card problems (megasurg)
Re: Access to Windows Neighbourhood workgroup from Linux (Benjohn007)
Re: Very nasty networking problem! (Brian McCauley)
FTP slowing down PPP (Jerome De Greef)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED]
Crossposted-To:
comp.dcom.lans.ethernet,comp.sys.sun.admin,comp.os.ms-windows.networking.win95
Subject: Re: Connect without hub
Date: Mon, 18 Jan 1999 08:15:10 GMT
In article <[EMAIL PROTECTED]>,
Rob Wiltbank <[EMAIL PROTECTED]> wrote:
> No, a hub is designed to to take packets and distribute them as best as
> is can to their destination. You're more likely to have packets collide
> on a peer to peer than through a hub.
Perhaps I am wrong, but I thought a hub simply made the appropriate
electrical connections. That is, to my knowledge, a hub does not
deal with packets, only with electronics. (If it deals with packets
and distributes them to their destinations appropriately, then it
is probably a switch. Granted, one could say "hub" and mean
"switching hub", but in those context (microhubs) that's probably
not the idea.)
So, in my understanding, you're *just* as likely to have packets
collide on a two host network whether or not you have a hub.
- Logan
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: lpd configuration problem
Date: Mon, 18 Jan 1999 09:42:52 GMT
In article <[EMAIL PROTECTED]>,
Sai Manohar Gopisetty <[EMAIL PROTECTED]> wrote:
How about sending us your /etc/printcap file so we can try
to give you an educated answer ?
--Ariel
> Hello,
>
> I am running RH 5.2 on my computer and I'm having problems sending print
> jobs to a remote printer. Apparently my lpd is not appending the
> hostname to the configuration and data files, so the lpd on the
> printserver is not processing the requests. Here is the log from the
> printserve's syslog:
>
> %Jan 5 16:24:41 printserve syslog: /usr/local/lib/lpd: ap_gradcol-
> Printjob:
> control file origin 'Aa02487' and H entry 'dharma.princeton.edu' do not
> match
> at Tue Jan 5 16:24:41 1999
>
> The sysadmin sent his opinion on this:
>
> "The 'H' entry is one of the entry's inside the control file, indicating
>
> the host name that sent the file. The "control file origin" is based
> on the filename for the controlfile and datafile; chances are your lpd
> is not building those filenames to properly include the hostname. So
> if the control file 'H' entry says "myhostname" the files might be
> named 'dfAa03142myhostname' and 'cfAa03142mythostname'.
>
> If you want to print, you'll need to reconfigure/fix your lpd."
>
> So, HOW do I reconfigure my lpd? There is nothing in the man pages that
> talks about any configuration file.
>
> Thanks for your help.
>
> Sai.
>
>
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: "Glenn Davy" <[EMAIL PROTECTED]>
Subject: Re: cant get Samba to work right
Date: Mon, 18 Jan 1999 20:24:15 +1100
>>. My win95 doesnt see linux as a
>> server
Quick question for you. When you say this, does this mean that it doesn't
appear in network neighbourhood? If so I've _often_ found on MSnetworks that
I have to right click on network neighbourhood and use find computer to find
the server. If this doesn't help email me a copy of smb.conf
Glenn
[EMAIL PROTECTED]
------------------------------
From: cgreek <[EMAIL PROTECTED]>
Subject: Re: Online with Linux
Date: Tue, 19 Jan 1999 10:49:54 +0800
Don't know if I still can remember configuring minicom
to change the default /dev/modem device to the /dev/ttyS1 or 2.
This was the thing that happened to me.
cgreek
[EMAIL PROTECTED]
Stef wrote:
> : I really can't figure out why I can't get the modem to work. When I run
> : minicom it says there is no such file or dir /dev/modem, but the file is
> : there.
>
> Yes, it will say so, if there is nothing connected to it.
> Does the kernel recognize your serial ports during startup?
>
> Stef
> --
> WebMaster D-WERK
> UNIX and Windows NT administration, SOS-ETH
> ETH Zurich
> [EMAIL PROTECTED] http://hoes.li
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Need help compiling C in Linux, NIC not working.
Date: Mon, 18 Jan 1999 09:38:39 GMT
In article <77p83q$n9u$[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
Yup.
cd /usr/src/linux
mv drivers/net/tulip.c drivers/net/tulip.c.old
cp /path_to_new_driver/tulip.c drivers/net/tulip.c
make config
(In the network section, define tulip as a module)
make modules modules_install
depmod -a
insmod /lib/modules/`uname -r`/net/tulip.o
(or add a:
alias eth0 3c59x
in /etc/conf.modules before running depmod -a, and afterwards
just run: modprobe eth0.)
--Ariel
> Help!
>
> During the installation of Red Hat Linux 5.2, the NIC (among other things)
> failed to be recognized. I downloaded the the source for the Linksys
> Etherfast 10\100 LAN drivers from Linksys for Linux, but I don't know how to
> compile it. I used the command:
>
> gcc -o tulip tulip.c
>
> It gave me 2750 lines of parse errors, deferencing pointer to incomplete
> type, undeclared this and that. At Linksys's help section
> http://www.linksys.com/support/solution/nos/linux.htm, they gave me a link to
> this file:
>
> http://cesdis.gsfc.nasa.gov/linux/drivers/tulip.c
>
> This is the same file I am trying to compile. Any advice as to how to
> compile it? Am I missing anything? My goal is to get my network operational
> so I can fix all the other misconfigurations, but the files I need for the
> other problems are too big to fit on a floppy; thus I need a network
> connection. Any help will be much appreciated.
>
> Thanks.
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: David Steuber <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.advocacy,linux.redhat.install
Subject: Re: DOES LINUX SUCK
Date: 18 Jan 1999 02:56:52 -0500
<[EMAIL PROTECTED]> writes:
-> I know this questions is highly debated.
Actually, this question is argued. Debate implies some sort of effort
is put into constructing logical claims based on technical merits and
useability.
-> But consider this,
-> I've got a generic un-modified RedHat 5.2 install,
-> with a supported PCMCIA card from 3com, a 3CXEM556B.
->
-> Now after 2 full days of work, and countless emails to and from helpful
-> folks, including the gentlemen who maintains the PCMCIA page, the darn
-> thing still doesn't work.
The PCMCIA card doesn't work? Or the whole of Linux?
If you are talking about the NIC, then I know something of what you
mean. I purchased my NIC seperatly from my notebook computer to make
sure I was getting a supported NIC. I had to fetch the latest PCMCIA
drivers to recognize the card. But David Hinds and Donald Becker have
done a good job. I followed the make mantra and I was in bussiness.
So. Did you get xforms and build cardinfo? This is a very useful
program to let you know if the card is even recognized.
It is an unfortunate fact of life that things don't always go
smoothly. But this doesn't mean that Linux sucks. Not by a long
shot. It took me about three days of solid effort to get my notebook
computer set up. Believe me, it was worth it.
I have the SuSE 5.3 distro. I spent the first day simply deciding
which packages to install. With only a 6.4GB drive, I didn't want to
throw in the works. The actual install took about 30 minutes and I
had a working Linux installation.
The next day was spent setting up my X server. That required fetching
the latest NeoMagic driver. I also decided to rebuild my kernel.
Linux makes it so easy to rebuild the kernel that I no longer think of
it as something strange to do. The build only takes about 8 minutes.
I was following a recipe for doing all this. I didn't, and still
don't, have a clue.
The network card was the hardest thing to set up. My first difficulty
was getting the damn thing. 3Com had come out with a new card. It
was a gratuitous change as far as I can tell. The card I wanted was
discontinued. So I got the new card only to find that the pcmcia
drivers I had didn't know what the hell it was. Going back to the
pcmcia site fixed that. New drivers were already available for it.
I went through make configure, make, and make install. Suddenly
cardinfo was showing me the card. Then all I had to do was figure out
how to set up /etc/route.conf. There are actually only two lines in
that file.
Basicly, what I went through was the inevitable trials of a total
newbie without a clue. The satisfaction of getting it all working was
quite indescribable.
The reason Windows installs so easily is quite simple. Microsoft
threw a lot of programmers at getting an install utility that knows
all about every piece of hardware out there. It knows windows.
However, if you run into hardware that windows doesn't recognize, and
you don't have drivers for it, you are sol.
I am sure you will get your NIC working if you keep at it. There was
probably some simple step you left out or something.
After things have been working for a while, you will wonder why you
ever bothered with windows.
Good luck!
--
David Steuber
http://www.david-steuber.com
s/trashcan/david/ to reply by mail
SYSTEM ALERT: /dev/null is full. Please delete any unnecessary files.
------------------------------
From: Rick Moen <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Which network driver for SMC 8216T and Red Hat 5.2?
Date: 18 Jan 1999 11:22:45 GMT
[Followups snipped.]
In comp.os.linux.setup Ed Finch <[EMAIL PROTECTED]> wrote:
: Greetings!
: I'm installing Red Hat 5.2 on some old Swan 486 systems with
: SMC 8216T network cards. Red Hat 5.2 offers these choices for
: network drivers:
: SMC 9000 Series
: SMC Ultra
: SMC Ultra 32
: Which of these should I select?
See:
http://metalab.unc.edu/LDP/HOWTO/Ethernet-HOWTO-5.html#smc
--
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
------------------------------
From: Richard Hector <[EMAIL PROTECTED]>
Subject: Re: /usr over nfs?
Date: Tue, 19 Jan 1999 00:59:00 +1300
Geoff Short wrote:
>
> Markus Hauke ([EMAIL PROTECTED]) wrote:
> :
> : On the clients should only run a minimal Linux system, so that they can
> : boot on their own and then do mount the /usr tree from the server.
>
> Yes, most unix systems seem to be designed to do this, and allow /usr
> to be read-only if you like. Certainly Slackware assumes that /usr
> may be nfs mounted.
>
> As long as the system startup scripts mount /usr as soon as possible, you
> shouldn't have any problems.
>
I was thinking about doing this at home (I have a machine with a 40meg
hard disk). But what is likely to happen with Debian or Redhat's package
management? Will they lose track of what's where, or are they designed
to handle this?
Richard Hector
------------------------------
From: "Jay D Ribak" <[EMAIL PROTECTED]>
Subject: Re: Need help with diagnosing a network problem
Date: Mon, 18 Jan 1999 10:48:44 -0500
I know this is a little late, but I had been on vacation the past week. I
solved the problem--it is a bit long-winded, though. I replaced the hub
with a switch, but was still seeing collisions. The new switch, however,
had individual collision lights, so I could see where they were coming
from...they were coming from the uplink port! The short version of the
story is that the uplink port on the original switch was set to Full-duplex
and it was trying to communicate with a half-duplex hub, then a half-duplex
switch. I set my new switch to full duplex on that port and the problem
disappeared. I can't believe I didn't see that to begin with...
Thanks for the tips though
Jay R
Joerg Ammon wrote in message <[EMAIL PROTECTED]>...
>Hi Jay,
>
>in case you're planning to replace your hub by a switch - do that quick!
>Since a switch writes packet statistics on every port it's really no big
deal to
>
>identify a bad NIC (in case you have one!).
>
>From what I can see in your loggings it might as well be just a busy
>shared media ethernet!!!
>What applications have you got running?
>How many user accessing this segment?
>etc...
>
>Do a quick calculation AND change to a switch soon!
>
>The only proper way of identifying a bad hub port is shuffling the links to
free
>ports ;-(
>
>In case you've got some sort of packet sniffer (there is e.g. tcpdump) you
might
>as
>well get a hint of your problem on actual looking at the packets
themselves. If
>you see
>a large number of error frames you can then identify the host.
>
>Jay D Ribak wrote:
>
>> Hi,
>> I am having a bit of a network problem on my small network. I am not
>> sure where to go from here to troubleshoot the problem further.
Background:
>> 5 Linux PCs on a mini-hub, all running 10mbs ethernet. The hub is
uplinked
>> to a 10mbs switch, which is in turn connected to a Cisco router and a T1.
I
>> have noticed huge numbers of collisions lately on each system. When
>> looking at the hub, the collision LED is blinking at least once every two
>> seconds. Here are some stats from ifconfig on one of the boxes:
>>
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:62419179 errors:1984 dropped:1984 overruns:627
>> frame:1984
>> TX packets:63294738 errors:2 dropped:0 overruns:0
carrier:256644
>> coll:436889
>> Interrupt:10 Base address:0x300
>>
>> As you can see the number of collisions is quite large. This is now
slowing
>> down performance between the systems, and from the T1 into the servers
from
>> the outside world. I am not sure if I have a bad NIC somewhere, a bad
port
>> on the hub, or what. I also don't know how to figure that out from
here.
>> I have another 10mbs switch on order, and I plan on replacing the hub
with
>> the switch. From what I understand of switching technology this should
>> significantly lower or eliminate the collisions. I don't really like
the
>> idea of glossing over a potential problem with a NIC though. The
systems
>> are also high availability servers and so I can't just bring them down to
>> swap out NICs unless I have proof that one is indeed bad.
>>
>> What tools are there in Linux to allow me to analyze network traffic to
>> figure out which system is causing all of the collisions?
>>
>> Thanks
>> Jay R.
>
>
>
------------------------------
From: megasurg <[EMAIL PROTECTED]>
Subject: Network card problems
Date: Mon, 18 Jan 1999 03:36:38 -0800
I'm having some difficulty with one of my machine connecting to the
network with linux. I have 3 machines and two of them connect fine.
One of the machines however doesn't seem to recognize the network card.
What I see is that when I boot into linux there is no light on the hub
indicating activity. However that same machine is dual booted with
windows95 and when I boot into windows95 the light is lighted and it is
connected to the network. This is odd behavior I would say. I have
done all the network setup as far as configurations the same on all
machines and yet this one doesn't come up. They all are using the same
network card (an Intel Etherexpress 16) so there should be no support
problems there. I think it is mainly that light is not lit on the hub,
but why is it lit when I boot into win95 and not linux? Can anyone help
me out? Please tell me any suggestions or info you may have. Thank
You.
--
"If there is a *quintessential zone of human privacy* it is the mind."
If you wish to send me a message using PGP my key is located here:
http://www.teleport.com/~megasurg/pgpmegasurg
------------------------------
From: [EMAIL PROTECTED] (Benjohn007)
Subject: Re: Access to Windows Neighbourhood workgroup from Linux
Date: 18 Jan 1999 15:34:42 GMT
Use Samba.
try man samba or
http://samba.org
------------------------------
From: Brian McCauley <[EMAIL PROTECTED]>
Subject: Re: Very nasty networking problem!
Date: Mon, 18 Jan 1999 08:47:34 +0000
[EMAIL PROTECTED] (Scott W. Petesen) writes:
> When I first boot the system (slackware 3.5, 2.0.34 kernel) everything
> is fine until I connect to my ISP. After a couple minutes to a couple
> days my linux server can not connect to ANYTHING anymore (telnet,
> fetchmail, sendmail, ftp). I cannot even telnet to the localhost!
Please define "cannot". What happens when you try? What mesages does
it give and how long does it pause between them?
Rule of thumb: Never post to Usenet saying "I can't do foo", you will
immediately be asked "what happens when you try?". It would simplify
matters if you were to answer this question without it needing to be
asked.
Shot-in-the-dark: Are you running a caching nameserver? Have you
tried killing and restarting that? If the "named" process had somehow
stalled/broken this could probably explain the symptoms.
> I inow this maybe a tough one since I have heard of only ONE other
> person with this problem.
Yes, if BIND turns out to be the culprit then this is true. BIND is
very rarely the culprit.
--
\\ ( ) No male bovine | Email: [EMAIL PROTECTED]
. _\\__[oo faeces from | Phones: +44 121 471 3789 (home)
.__/ \\ /\@ /~) /~[ /\/[ | +44 121 627 2173 (voice) 2175 (fax)
. l___\\ /~~) /~~[ / [ | PGP-fp: D7 03 2A 4B D8 3A 05 37...
# ll l\\ ~~~~ ~ ~ ~ ~ | http://www.wcl.bham.ac.uk/~bam/
###LL LL\\ (Brian McCauley) |
------------------------------
From: Jerome De Greef <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.setup
Subject: FTP slowing down PPP
Date: Mon, 18 Jan 1999 16:36:01 +0100
Hi,
I've a strange problem using PPP 2.3.3 with RedHat 5.1 Kernel 2.0.36,
BocaModem 28.8, P90 48 Mb RAM.
Everything is working fine until I make download (via FTP, MC or
Netscape). Then, as soon as the file transfer begins (at 2.7 Kb/Sec,
seems OK for a 28.8 modem) , it seems it's using the whole bandwidth and
if I continue to browse, Netscape drops at less than 100 bytes/sec (I've
seen 7 bytes/sec one time :-( ).
I've played with MRU and MTU and using ping I have my response time
ranging from >5000 ms (MRU = 1500) to 800-1000 ms (MRU=296). I use
Asyncmap=0, crtscts, etc
Is it normal or am I missing something (should I say that I never had
this problem with Win95)?
Thanks for helping,
Jerome
------------------------------
** 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
******************************
