Linux-Networking Digest #555, Volume #10         Fri, 19 Mar 99 13:13:51 EST

Contents:
  Re: NFS problems with Linux 2.2.x server, freebsd client (David Malone)
  pop3d socket error ("parag")
  Whats SIOCADDRT when its at home? (Martin Powell)
  Network locking (Korny)
  Re: ne.o & 3c509.o compiled ??? ("��d�W")
  Re: For all you Nicrosoft lovers (doole)
  HP OpenView and Linux (Beowulf) ("Alain Coetmeur")
  2 Token Ring-Cards (Efrem Locarno)
  Re: Hylafax receiving (Michael Schlegel)
  Re: Can't find a DE200 nic driver... (Chris MacKenzie)
  Re: DNS related PPP problems. ("Dr. Yuan Liu")
  snmptrap args ([EMAIL PROTECTED])
  Re: The truth about the Pentium III chip and ID --- **boycott info** ("Rufus V. 
Smith")
  by the way... ("Brent Cornwell, Pediatrics Computer Administrator")
  Re: The truth about the Pentium III chip and ID --- **boycott info** (Curt Steger)
  Re: The truth about the Pentium III chip and ID --- **boycott info** 
([EMAIL PROTECTED])

----------------------------------------------------------------------------

From: [EMAIL PROTECTED] (David Malone)
Crossposted-To: comp.unix.bsd.freebsd.misc
Subject: Re: NFS problems with Linux 2.2.x server, freebsd client
Date: 19 Mar 1999 11:40:46 -0000

>> Does anyone have NFS working right with a Linux 2.2.x kernel on
>> the server, and freebsd clients?   It appears to mount and
>> read operations work.  Some writes work but others fail.  Things
>> like a 'cp -R' of a directory tree leaves mostly 0-length files.
>> Did I miss something or is this just broken?

It may be broken - someone sent me this URL yesterday, which
may shed some light on how to fix it:

http://lwn.net/1999/0318/a/knfsd.html

        David.

------------------------------

From: "parag" <[EMAIL PROTECTED]>
Subject: pop3d socket error
Date: Fri, 19 Mar 1999 17:47:13 +0530

i am at loss to get my mail server box to listen for pop3 loging at port 110
from window clients. everything seems ok in inetd.conf. am useing redhat 5.2
and other network services seems fine
any help will be very much appriciated



------------------------------

Date: Fri, 19 Mar 1999 14:51:00 +0000
From: Martin Powell <[EMAIL PROTECTED]>
Subject: Whats SIOCADDRT when its at home?

Hello,

I'm running RH5.2 with a 3com 905b Ethernet card in it, and my
networking isn't working.  It use to until..... I added a SCSI card and
had to re-install the OS for various reasons.

Anyway,
We have a class C IP network, and I would like to access other machines
on this network.  When I ping 192.100.200.117 (one of our machines) it
tells me that the network is un-reachable.  Ha-ha says I.  I need to add
a route into the routing table, which is what I try to do, by using
"route add -net 192.100.200.0 netmask 255.255.255.0 dev eth0".  It then
fails and informs me that SIOCADDRT : operation nos supported by this
device.

What does this mean and how can I resolve this.

Many thanks in advance, Martin P


------------------------------

From: Korny <[EMAIL PROTECTED]>
Subject: Network locking
Date: Fri, 19 Mar 1999 13:10:38 GMT

I run 2 Linux machines at work... both run kernel 2.2.3.  One's an old 486
SCSI system, the other is a PII 350 IDE system.  Both have 3com ethernet
cards.

When I mount a share from the 486 machine on a SUN machine, I get the warning

"WARNING: No network locking on usmbrd02:/remote_data: contact admin to
install server change"

I do not get this warning when I mount a share from the PII box.

Strangely, however, it's the PII box that I'm having trouble with.  An
application I'm testing is unable to use the PII machine to store remote
data. It complains that it can't write one of the files it needs to write. 
(I can cd to that share, though, and create whatever I want - it has 777
perms)  This same application has no trouble writing to the 486 (the one that
produces the warning).

So, I'm guessing I compiled something in the PII's kernel, but not in the
486's.  I cannot figure out what.

Additionally, the PII box automounts home directories on a SUN machine.  I
always get this in the Linux syslog: Mar 16 09:06:37 usmblx01 kernel: lockd:
failed to monitor 137.199.57.6 (the IP addres of the SUN machine where the
home dirs live).

So, I'm hoping someone can explain what network locking is, and if it is
related to lockd (I found no module or daemon on my machine named lockd).

Thanks for your time!

mailto:[EMAIL PROTECTED]

============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own    

------------------------------

From: "��d�W" <[EMAIL PROTECTED]>
Crossposted-To: hk.comp.os.linux,hk.comp.pc
Subject: Re: ne.o & 3c509.o compiled ???
Date: Sat, 20 Mar 1999 00:28:06 +0800

I have done this la !

Enbugger ���g��峹 <7ctncl$l52$[EMAIL PROTECTED]>...
>I am not sure if you are using RedHat.
>If you are, please refer to this document for
>version 2.2 kernel upgrade:
>
>http://www.redhat.com/support/docs/rhl/kernel-2.2/kernel2.2-upgrade.html
>
>Hints:
>Have you done:
>  make modules
>and
>  make modules_install
>?
>
>"��d�W" wrote:
>>
>> Before, I haven't build the kernel.
>> I need to prepare the file /etc/conf.modules:
>>
>> alias eth0 ne
>> options ne io=0x300
>> alias eth1 3c59x
>>
>> And today, I try to build the kernel.
>> I have chosen the [Y] in both 3com NIC support and NE2000 support.
>> So, I won't got this two modules(ne.o and 3c59x.o) any more during
building.
>> Then, the problem happened !!!
>> On starting:
>> ...
>> Enable IPv4 packet forwarding.
>> modprobe: can't locate module net-pf-5
>> ...
>> eth1: unknown interface.     (NE2000 NIC change from eth0 to eth1)
>> modprobe: can't locate module net-pf-5
>>
>> What's more, I try to copy back the files:
>>     ne.o       to /lib/modules/2.2.3/net/ne.o
>>     3c59x.o to /lib/modules/2.2.3/net/3c59x.o
>>
>> Then the system report:
>> ...
>> modprobe: can't locate module net-pf-5
>> insmod: /lib/modules/2.2.3/net/3c59x.o: kernel module version mismatch
>>              /lib/modules/2.2.3/net/3c59x.o was compiled for kernel
version
>> 2.0.36 while this kernel is version 2.2.3.
>> eht1: unknown interface.
>> modprobe: can't locate module net-pf-5
>> ...
>>
>> What should I do now, is that supports been compiled to kernel yet ???
>> I have chosen [Y] for these 2 NIC support already !!!
>> Would you please offer your Kindly Help ?
>
>--
>Enbugger
>
>p.s. Remove /NO-SPAM/ for e-mail.



------------------------------

From: [EMAIL PROTECTED] (doole)
Crossposted-To: alt.os.linux,comp.os.linux.hardware,comp.os.linux.setup
Subject: Re: For all you Nicrosoft lovers
Reply-To: [EMAIL PROTECTED]
Date: Fri, 19 Mar 1999 15:54:47 GMT

[EMAIL PROTECTED] (Don Baccus) apparently said this:
>
>Those who wrote our Constitution understood the world
>better than you do, I'm afraid...
>-- 

Well, as an indicator of just how well YOU understand the world - it's
not "our" constitution, it's yours. I don't live in the glorious,
presumptuous U.S. of A...

------------------------------

From: "Alain Coetmeur" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.admin
Subject: HP OpenView and Linux (Beowulf)
Date: Fri, 19 Mar 1999 16:01:59 +0100


does anybody have information how far you can integrate 
a Linux Beowulf cluster, and a few Linux serveurs
into an environment managed 
with HP OpenView,( and EcoTools and ClusterView ...).



------------------------------

From: Efrem Locarno <[EMAIL PROTECTED]>
Subject: 2 Token Ring-Cards
Date: Fri, 19 Mar 1999 17:34:04 +0100
Reply-To: [EMAIL PROTECTED]

Hi,

I have a linux RH5.2 with 2 token ring (Token ring auto 16/4) (Linux
version 2.0.36 ).

Both are IBM Auto 16/4, configured:
TR0: IRQ: 9, I/O: A20
TR1: IRQ: 3, I/O: A24


The two card seems to run properly alone but I am not able to create a
gateway (with two token ring adapter running at the same time).

Does linux supports two token ring 16/4 token ring adapter (gateway
configuration) ? if yes, how can I configure linux to do it ? 

Thanks in advance,
Efrem.

------------------------------

From: Michael Schlegel <[EMAIL PROTECTED]>
Subject: Re: Hylafax receiving
Date: 19 Mar 1999 13:06:49 +0100

"andy" <[EMAIL PROTECTED]> writes:

> Hi.
> 
> Have just installed Hylafax on SuSE Linux 5.3 and am able to send but not
> receive faxes. Get message saying 'Can not open device' in the log. Assume
> it must be permissions problem for a device but I have not changed anything
> from the defaults.
> 
> Anyone any ideas?

Hi,

there could be AFAIK two reason�s for the message 'Can not open device'.
Either your device is locked by an other application, or faxgetty has
no permission on /dev/xxx.

The first problem so be easy to fix.
In the second case you have to check out as who faxgetty runs. (Test out
"ps axu".) Set the correct permissions of the used device for that user.

E.g.:                        User : fax
        permission for /dev/modem : crw-rw---- 


This should help you

cu miki

-- 
 __  __ _ _    _
|  \/  (_) | _(_)
| |\/| | | |/ /    Privat: [EMAIL PROTECTED]
| |  | | |   <| |     Uni: [EMAIL PROTECTED]
|_|  |_|_|_|\_\_|

------------------------------

From: Chris MacKenzie <[EMAIL PROTECTED]>
Subject: Re: Can't find a DE200 nic driver...
Date: Sat, 20 Mar 1999 04:07:57 +1100

[EMAIL PROTECTED] wrote:

> I am trying to use this old card from Digital on a 486 PC, but I simply can't
> find a correct driver for it. I even tried Digital's web site but nothing
> seems to fit :( I have RedHat 5.2 (Linux 2.0.36) installed.

The driver you want is called depca and it is indeed supported by Linux.
I remember seeing the driver in RedHat v3.03 ! (try modprobe depca)
 
Be aware that DE200's were designed primarily with a 386 in mind and
while they will work with low end 486's they will be kinda slow compared
to it's newer brothers the DE203/4 or 5 (Etherworks 3 Turbo). They are
also a pain in the butt as they can only be configured via the switches
on the NIC itself.
 
Other than that they are a good card that shouldn't give you any
troubles *8-)

-- 
Rgds,
Chris MacKenzie
[EMAIL PROTECTED]

Windows 95/NT - 32 bit extensions and a graphical shell
                for a 16 bit patch to an 8 bit operating
                system originally coded for a 4 bit
                microprocessor, written by a 2 bit company
                that can't stand 1 bit of competition.

------------------------------

From: "Dr. Yuan Liu" <[EMAIL PROTECTED]>
Subject: Re: DNS related PPP problems.
Date: Fri, 19 Mar 1999 12:13:33 -0500

[EMAIL PROTECTED] wrote:
> 
> To solve the problem, I have to manually execute:
> 
> route add default dev ppp0

See if the option
 defaultroute
is in your /etc/ppp/options.

> Chris.
> 
> [EMAIL PROTECTED]
> or
> [EMAIL PROTECTED] (without _'s)

-- 
+--- mailto:[EMAIL PROTECTED] ----------- http://www.ChiTech.ca/ ---+
|         Dr. Yuan LIU           -     Chitech Technologies Inc.  |
+------- (514)281-0494 ------------------ FAX (514)281-0493 ------+

------------------------------

From: [EMAIL PROTECTED]
Subject: snmptrap args
Date: Fri, 19 Mar 1999 17:06:24 GMT

I'm having a hell of a time sending a simple trap to our NMS from our Linux
box.  We just need simple traps such as generic trap # and specific trap #. 
On our SCO and previous UNIX platforms all we had to specify was the IP
address to the NMS and our trap types.  The man for the new snmptrap lists:

snmptrap  -v  1  [common  arguments]  enterprise-oid agent
       generic-trap specific-trap uptime [objectID type value]...

I have no idea what values to use for enterprise-oid and agent.  We have a
packet trace of our previous platform's traps which contain an oid of
1.3.6.1.4.1...(some more numbers) but I can't get that to work and have no
idea why it has to be specified anyway.  I basically just need to open a
socket to the NMS on the appropriate port and send an appropriate packet
right?

As should be obvious, I know virtually nothing about SNMP including oids.

Could someone send me an snmptrap example?  How about one that sends a generic
trap (6), specific trap (1) to IP host 10.10.10.10?  The example in the
snmptrap man page makes no sense to me and seems even to violate their own
syntax chart.

~j

============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own    

------------------------------

From: "Rufus V. Smith" <[EMAIL PROTECTED]>
Crossposted-To: 
comp.lang.perl.misc,comp.lang.python,comp.lang.tcl,comp.mail.sendmail,comp.os.linux.setup,comp.os.ms-windows.advocacy
Subject: Re: The truth about the Pentium III chip and ID --- **boycott info**
Date: 19 Mar 1999 13:40:33 GMT

All that is needed to get to the dial up user is an address of the service
provider's modem that the user called in on!

This is obviously not unique to an individual.

The IP address he gets when he logs in is also out of a pool of addresses
and is also non-unique.


Michael Barnes wrote in message <[EMAIL PROTECTED]>...
>Every MODEM has a MAC address also...so your friends pc is nicless, but not
>macless
>As far as I know you cannot network anywhere without a mac address since
>IP's map directly to machine addresses at lower levels to identify your
>particular machine on any network.  So, if your connected to any network
via
>any hardware device (router, switch, modem, nic) those devices must have
mac
>addresses.
>
>and modems are easy to replace compared to CPU's also...
>
>
>



------------------------------

From: "Brent Cornwell, Pediatrics Computer Administrator" 
<[EMAIL PROTECTED]>
Crossposted-To: 
comp.lang.perl.misc,comp.lang.python,comp.lang.tcl,comp.mail.sendmail,comp.os.linux.setup,comp.os.ms-windows.advocacy
Subject: by the way...
Date: 19 Mar 1999 13:41:12 GMT

take this thread to:   comp.sys.intel
it's more relevant there..



------------------------------

From: Curt Steger <[EMAIL PROTECTED]>
Crossposted-To: 
comp.lang.perl.misc,comp.lang.python,comp.lang.tcl,comp.mail.sendmail,comp.os.linux.setup,comp.os.ms-windows.advocacy
Subject: Re: The truth about the Pentium III chip and ID --- **boycott info**
Date: 19 Mar 1999 13:44:00 GMT
Reply-To: [EMAIL PROTECTED]



Quantum Leaper wrote:

> Michael Barnes wrote in message <[EMAIL PROTECTED]>...
> >Every MODEM has a MAC address also...so your friends pc is nicless, but not
> >macless
>
> Interesting is over 15 years of using modems,  300 baud to 56K modems
> (hopefully a Cable or DSL modem in about a year or so),  I have NEVER heard
> that they have a MAC address?   So what command or how do you get the MAC
> address of a modem?   Does this only apply to Mac modems or all modems? One
> other question,  why would a modem need a MAC address?

Only if it is running on an Apple/Mac!

Any here I thought that a MAC address was a special address book that Billy-bum
kept for retaliation if he ever took over the world. ?:^)


------------------------------

From: [EMAIL PROTECTED]
Crossposted-To: 
comp.lang.perl.misc,comp.lang.python,comp.lang.tcl,comp.mail.sendmail,comp.os.linux.setup,comp.os.ms-windows.advocacy
Subject: Re: The truth about the Pentium III chip and ID --- **boycott info**
Date: 19 Mar 1999 13:44:48 GMT

On Wed, 17 Mar 1999 10:20:04 -0700, "Michael Barnes"
<[EMAIL PROTECTED]> wrote:

true. but.  MAC addresses on your modem go no further than your isp.
in fact, your isp doesn't even use your modems mac address because you
are assigned an ip addres that already has the mac address of the
modem you connected to so yours never goes out into the net.

your network also has a mac address.  this address is used only by
your local network.  I machine on a different network send you info,
they only know the ip address, this is send to the router the router
only know the mac address and ip address in your local network.  If it
cannot find the destination, it forwards it the the next router which
again only know the mac address and ip address if its local network.
it does on the otherhand know which router to send it to based on ip
routing tables. this process is repeated until it finds the router
that knows the destination ip address and sends it to the isp's router
which then looks up the mac address and places the ip packet on th
ethernet with the destination ip and mac address only knowing the
source ip not mac.  mac addresses are NOT forwareded accross even
subnets.

and just to show off, ISP equipment like an ascend or 3com total
control that has 48 modems, all 48 modems have the SAME mac address.
the modem server knows which modem to send it out on based on ip
address.


>Every MODEM has a MAC address also...so your friends pc is nicless, but not
>macless
>As far as I know you cannot network anywhere without a mac address since
>IP's map directly to machine addresses at lower levels to identify your
>particular machine on any network.  So, if your connected to any network via
>any hardware device (router, switch, modem, nic) those devices must have mac
>addresses.
>
>and modems are easy to replace compared to CPU's also...
>
>
>
>Bill Anderson wrote in message <[EMAIL PROTECTED]>...
>>Tim Roberts wrote:
>>>
>>> John Lehmann <[EMAIL PROTECTED]> wrote:
>>>
>>> >Kano wrote:
>>> >>
>>> >> Oh come on. Many other standard devices (ethernet cards, for example)
>>> >> have their
>>> >> own unique serial numbers that software can use at will. Get over it.
>>> >>
>>> >
>>> >Yes - but ethernet mac cards are only broadcast over the lan, not over
>>> >the net (except by Office98, of course).
>>>
>>> The POINT here is that it is exactly as easy to embed my unique MAC
>address
>>> in an Internet transaction as it is to embed my unique Pentium-III CPU ID
>>> in an Internet transaction.  Any software which will go to the trouble to
>>> fetch the unique CPU identifier and send it over the network to identify
>me
>>> could just as easily be written TODAY to use a MAC address for exactly
>the
>>> same purpose.  The CPU identifier is not significantly different in
>concept
>>> from the MAC address, and yet there has not been a hue and cry to boycott
>>> NIC manufacturers.
>>
>>Ho wmany home users ar LAN connected to the internet?
>>oh, yeah, that's right, they dial up with a modem; no getting a MAC
>>address from a machine that does not have one.
>>
>>>
>>> >And what do you mean get over it???  This kind of personal information
>>> >is valuable.  Business are willing to pay for it.  This kind of
>>> >behavior IS DOWNRIGHT THEFT!!!
>>>
>>> But whatever they could do with a CPU ID, they are probably already doing
>>> with a MAC address.  It is just as good as a unique identifier.  "Get
>over
>>> it" is exactly the right attitude.
>>
>>Can you explain how they would be getting a MAC address from my friends'
>>NIC-less pc?
>>
>>A MAC address is not as good, in any event. NICs get changed mor often
>>than cpus (in most cases). IIRC MAC addresses can be changed, and there
>>have been cases of MAC addresses beinf reused?
>
>


------------------------------


** 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
******************************

Reply via email to