Linux-Networking Digest #627, Volume #12 Sat, 18 Sep 99 05:13:33 EDT
Contents:
REdhat and default gateway problem (Alan)
Re: Sohoware Nic setup MX98715 chip and tulip driver???? (Paul Lew)
Re: Is remote GUI possible ("Mr. Coburn")
Re: Samba and Switched Hub Networks (Rein Klazes)
rsh: adding a command (Thomas R. Shannon)
Re: WaveLAN drivers for linux (Tilmann Singer)
Re: Compiling SAINT 1.4 on Redhat Linux 6.0 (Vilmos Soti)
What is the best souce for Proxy setup ("ms")
Re: WinNT Can't See Linux Box ("kdoswald")
Re: Connecting to isp with linux, letting windows connect through linux (Jonathan
Sprague)
Re: fetchmail, procmail ??? (Cameron L. Spitzer)
Re: 3c90x: new 3com GPL driver ("Mr. Coburn")
PPP compression vs. modem compression (Hal Sadofsky)
recommendation for pcmcia ethernet+modem (Oscar Carrillo)
Re: Arrgghhh...text file transfer NT -> RH6.0 ("Ross Crawford")
Re: Arrgghhh...text file transfer NT -> RH6.0 ([EMAIL PROTECTED])
Re: Remote server monitoring akin to AlertPage (Kevin Reed)
Problem with LinkSys Netcard ("Qiang Xue")
Re: Why can't I telnet to root ?? ("Mr. Coburn")
IP Masqing and proxy arp? (john)
Re: Recommendation for 100Mbps Switched Ethernet hardware (Bryan)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Alan)
Subject: REdhat and default gateway problem
Date: Sat, 18 Sep 1999 05:18:19 GMT
I have a small network using IP Masquerade, connected to a DSL line. A
l "inside" IPs are in the private range. I just recently installed
Redhat on a box for one user and this is my first time using Redhat as
I've always used Slackware.
The problem I'm having is with the default gateway of the Redhat box.
It has one NIC and the IP is 192.168.3.2 but the gateway that I have
to use to get to the net through the masquerade box is 192.168.0.1
which is the IP of eth1 on the masq box. Eth0 on the masq box is a
real IP that connects to the DSL modem. Using linuxconf, I've set up
the ip for eth0 at 192.168.3.2 the route for the 192.168.3.0 subnet,
the route for the 192.168.0.0 subnet using 192.168.3.2 as the gateway
for it. I also set up the default gateway as 192.168.0.1.
When I run "network start" though everything comes up fine except for
the default gateway. I get an error in the logs that says SIOCADDRT:
Network is unreachable. I assume that for whatever reason the route to
the 192.168.0.0.subnet has not been setup correctly in time to add the
gateway BUT, the route command shows the proper route to the
192.168.0.0 subnet. The funny thing is that, if I run network start
one more time, the default gateway comes up fine and I can ping the
other box and internet IPs or I can run
/sbin/route add default gw 192.168.0.1 eth0 after it fails the first
time and the routing table is right so obviously the 192.168.0.0
subnet route is correct. I'm just at a loss as to why it won't work
the first time the "network" script runs.
Also I can put all of the ifconfig and route commands in a shell
script and run it and everything comes up fine.
Any ideas why this is happening? Like I said I've never used REdhat
before. In Slack I just put the proper route and ifconfig lines in
/etc/rc.d/rc.inet1 and everything worked. Thanks for any advice.
------------------------------
From: [EMAIL PROTECTED] (Paul Lew)
Subject: Re: Sohoware Nic setup MX98715 chip and tulip driver????
Reply-To: [EMAIL PROTECTED]
Date: Fri, 17 Sep 1999 18:16:33 GMT
If RH's tulip.c it ver 0.90, then you need the 0.90 from
NDC (SOHOware). Or download any version 0.91e or higher,
0.91g may be the "latest".
Hagen Fuhrmann <[EMAIL PROTECTED]> wrote:
>John Verderber wrote:
>> Hi
>> I purchsed the soho ware 10/100 network starter kit. This has 2 pci
>> nics with the MX98715 chip on it. It came with a tulip.c driver. I am
>> running redhat 6.0 that already has the tulip driver installed. 6.0
>> finds the card and installs it no problem eth0 starts normally and that
>> is it. I can ping the etho port and the loopback but the fard will not
>> broadcast to the network. I am at my wits end. The driver that I got
>> with the card will not compile properly. I asmit my programming
>> experience is limited.
>
>I am encountering the same problem. The card works fine in Windows 98. In
>Linux the Tulip.o driver is included, recognizes the card and has no
>problem. But I am not able to ping any other computer except for localhost.
>
>Configuration:
>10/100 MHz card with autosense. Dual-speed hub with autosense.
>And I do not know how to disable P&P in the BIOS. There is no such menu
>item.
>
>
>
>
------------------------------
From: "Mr. Coburn" <[EMAIL PROTECTED]>
Subject: Re: Is remote GUI possible
Date: Sat, 18 Sep 1999 06:09:19 GMT
Steve Waldo wrote:
> I'm maintaining a server remotely and sometimes wish I could run a graphical
> program, such as linuxconf. Anyone know how this can be accomplished?
>
> Thanks.
> --Steve
I tried to log in to the server as a normal user, su to root, and then do
"control-panel" (red hat). It said something like "NO, NO, Daddy don laow no
external dudes (ttys) to use this control panel". SOOOOOOOO. I set up ssh
and do root user on SSA credentials without paraphrase. Be root on your
machine. Set the DISPLAY variable on your local machine, enter "ssh xxx" where
xxx is the remote machine, any X clients you pop up on the remote machine will
talk to the local Xserver created by ssh and that "fake" server will send the
stuff through the ssh encrypted connection back to your local machine and pop
up a real x client on your desktop under your local window manager.
This is a very nice rig. The remote stuff (control panel or whatever) likes it
just fine as it sees a LOCAL xterm and the stuff flowing back and forth is
encrypted like a rock and the 1024 bit ssa credentials stuff is pretty hard to
crack. I do this because servers are not supposed to have big graphic heads
and fancy video. They are supposed to have little teletypes and lots of disks
and memory and networking stuff. Thetas why they call em servers. The idea of
making the administration of a server a lot easier by using X and Web stuff is
good. The idea of then locking out all but the local display is kinda dumb.
SSH solves the problem for me.
OH. BTW I thought linuxconf was a character interface thing or capable of
both X and character interface. What I really want to use is the KDE stuff.
------------------------------
From: Rein Klazes <[EMAIL PROTECTED]>
Subject: Re: Samba and Switched Hub Networks
Date: Fri, 17 Sep 1999 20:17:54 +0200
[EMAIL PROTECTED] wrote:
> P.S. Please ignore the name/email address in the headers... Wine won't
> allow me to redefine my user settings in Forte Agent.
I can change my settings just fine.
Rein.
--
Rein Klazes
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Thomas R. Shannon)
Subject: rsh: adding a command
Date: 17 Sep 1999 18:28:19 -0500
I can rlogin to my machine at work with no problem. Naturally enough,
I can also use rsh to login with no problem. However, if I use rsh
and add a command at the end, say "emacs", I get "permission denied".
Is there additional security involved here? How do I solve this?
Thanks for any advice,
Tom
--
Quote of the day for Friday, 17 September, 1999:
"A man's greatest strength develops at the point where he overcomes=20
his greatest weakness."
- Elmer G. Leterman
------------------------------
From: Tilmann Singer <[EMAIL PROTECTED]>
Subject: Re: WaveLAN drivers for linux
Date: Fri, 17 Sep 1999 20:19:16 +0200
Hi
> Are drivers available for Lucent Technologies WaveLAN for linux (Redhat 6.0)?
there are two afaik, one of them is running just fine on my laptop.
just do an internet search on wavelan and linux, there is some excellent
documentation out there (can't remember the links, sorry).
There are several versions of Lucent WaveLAN Cards, so make sure you
know exactly for which one you are looking for a driver
------------------------------
From: Vilmos Soti <[EMAIL PROTECTED]>
Subject: Re: Compiling SAINT 1.4 on Redhat Linux 6.0
Date: Sat, 18 Sep 1999 06:17:30 GMT
Stephen Zepp wrote:
>
> Has anyone had any problems compiling SAINT on a 6.0 stock kernel?
> I'm getting the following errors with make linux:
>
> [root@panther saint-1.4]# make linux
Hi,
What do you mean under a 6.0 stock kernel? If it is RedHat, or anything
based on glibc21, then the parameter for make is not linux but
linux-glibc21.
> In addition, the reconfigure script gives me:
>
> [root@panther saint-1.4]# ./reconfig
> /bin/sh: -S: bad option
The reconfig script is actually a perl script. Run it by typing
perl reconfig
Good Luck, Vilmos
------------------------------
From: "ms" <[EMAIL PROTECTED]>
Subject: What is the best souce for Proxy setup
Date: Sat, 18 Sep 1999 06:25:21 GMT
I am setting up a Proxy to stand between a T1 line and my internal network.
Can anyone tell me the best Proxy(I am running RedHat Linux 6.0)?
And can you point me in the direction of some pretty basic setup
instructions(do's/don'ts, things to watch for).
--Thanks
Mike Sargent
[EMAIL PROTECTED]
------------------------------
From: "kdoswald" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.admin
Subject: Re: WinNT Can't See Linux Box
Date: Fri, 17 Sep 1999 23:16:33 -0700
Have you checked the ip address's on the nt boxes vs. the Linux box make
sure they are all running in the same subnet with same subnet mask..
Also might want to try removing any other protocols you have loaded on a NT
box.. I know we have problems at my work if IPX/SPX is loaded..
..Kevin
eTc Computer Consultants <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
>
> I just built a linux server intended for integration into a small lan of
> winNT machines. As I usually do, I built the server in my little shop,
> where I have win98/95/31 boxes all around, and everything was working
> perfectly in about an hour (shares via samba). Of course samba requires
> tcp/ip to be working, but this is always very simple with linux, as well
> as with windows.
>
> BUT !!!!!
>
> tcp/ip is NOT working correctly with the NT boxes. Here are the
> symptoms:
>
> 1) the nmbd component of samba broadcasts ok to NT boxes (doesn't need
> tcp/ip);
> 2) from the server, I can view shares on NT boxes (w/smbclient--requires
> tcp/ip);
> 3) from the server, I can ping all the NT boxes (requires tcp/ip, of
> course);
> 4) NONE of the NT boxes can ping the server, even if they can see the
> server on the network (presumably because of nmbd getting through via
> netbeui, or other).
>
> As far as the nt boxes are concerned, the ip of my linux box does not
> exist, even though my linux box sees them all just fine.
>
> What am I missing? I have not worked much with NT -- is NT blocking my
> server out of its domain? If so, I couldn't find anywhere on the NT
> server to change that.
>
> TIA for any tips.
>
>
> Eric
------------------------------
Date: Fri, 17 Sep 1999 14:28:38 -0500
From: Jonathan Sprague <[EMAIL PROTECTED]>
Subject: Re: Connecting to isp with linux, letting windows connect through linux
take a look here for a bunch of links;
http://www.on-net.net/~jsprag/linuxnet.htm
"Michael A. Painter" wrote:
> Dear friends,
> I have my own computer using SuSE Linux 5.3 connecting to the net
> over a modem. I also have a windows computer that i built for my parents
> downstairs. I have ethernet cards installed in both with a crossover cable
> between them. What do I need to set up on the linux computer to let the
> windows computer use the net?
>
> Thank you,
> Michael Painter
>
> p.s. Please email me a reply also
-----------== Posted via Newsfeeds.Com, Uncensored Usenet News ==----------
http://www.newsfeeds.com The Largest Usenet Servers in the World!
======== Over 73,000 Newsgroups = Including Dedicated Binaries Servers =======
------------------------------
From: [EMAIL PROTECTED] (Cameron L. Spitzer)
Subject: Re: fetchmail, procmail ???
Date: 17 Sep 1999 19:24:07 GMT
In article <[EMAIL PROTECTED]>, Va Thao wrote:
>Here is what I have already setup:
>
>I'm Running Redhat 6.0 with ipmasquerading enabled.
>
>I have an account on my isp. My isp picks up all the mail that goes to
>[EMAIL PROTECTED] then delivers it to my local account.
>
>I have my linux box dial my isp and use fetchmail to grab all the mail
>that my isp has deliver to my mailbox.
>
>Now that I have the mail on my box, How do I sort these mails on my
>linux box and deliver these mail to the correct users mailbox so that it
>can be accessed by windows 95/98 machine on the lan.
Create accounts for each user.
Use your local message transfer agent (Sendmail on Red Hat?)
to sort the mail into those users' mailboxes.
This will happen automatically if the mail is correctly addressed
and your Sendmail believes mydomain.com is the box it's running on.
Once the mail is sitting in the users' mailboxes, they can fetch it
with POP3 or IMAP, if you configure one of those servers.
I'm using the Qmail message transfer agent, and the IMAP-4.6 "beta"
IMAP server. IMAP-4.6 comes with a pop3 server that's really just
a wrapper around its imapd. Red Hat probably came with qpopper.
The only disadvantage to the Sendmail and qpopper from Red Hat
is they are storing all the mail in /var/spool/mail.
For this to work, Sendmail and qpopper have to run as root, and
so do all the local email clients. Not a problem if you only have
a few users and they're all trustworthy or you don't give them
shell and FTP access. I prefer Qmail's idea of delivering
the mail to a known file in each user's home directory.
But I had to patch imapd to inform it of this nonstandard location,
and I may have broken imapd's ability to support multiple
mailboxes per user.
Cameron
------------------------------
From: "Mr. Coburn" <[EMAIL PROTECTED]>
Subject: Re: 3c90x: new 3com GPL driver
Date: Sat, 18 Sep 1999 06:17:02 GMT
Jonathan Wilson wrote:
> Sorry, I forgot to ask the real question: where can I get this new
> driver from?
>
> JW
you don't need a new driver. The driver is in the stuff for 3com that
comes with kernels 2.0.36 and up. It is called a BOOMERANG and the same
driver manages a bunch of 3com cards including the xl combo the 3c900,
3c900c, etc. I assume you are talking about a pci card and not some
weird isa thing you found in the dinosaur graveyard.
------------------------------
From: [EMAIL PROTECTED] (Hal Sadofsky)
Subject: PPP compression vs. modem compression
Date: 17 Sep 1999 23:22:31 -0700
In reading about modem operations, I learn (is this really true?) that
disabling modem compression will decrease latency. Clearly though,
there is then a loss of speed when transferring large compressible
files.
If one enables PPP compression does one make up for this? That is,
is it best to disable modem compression and enable PPP compression
in order to get lower latency but still appropriate compression?
Hal Sadofsky
------------------------------
From: [EMAIL PROTECTED] (Oscar Carrillo)
Subject: recommendation for pcmcia ethernet+modem
Date: 17 Sep 1999 18:35:50 GMT
Hi,
I'm using an Adaptec 1460 pcmcia card for SCSI.
I would also like to use an ethernet/modem combo
pcmcia card. I've discovered that a cardbus option
is definitely not a good idea. Does anyone have a
recommendation for a pcmcia card to do this job.
In other words, a card that will do ethernet/modem and
be able to co-exist with an Adaptec 1460 pcmcia card.
I'm using RedHat 6.0 on an HP notebook 2100.
Any suggestions greatly appreciated.
Oscar
[EMAIL PROTECTED]
A
------------------------------
From: "Ross Crawford" <[EMAIL PROTECTED]>
Subject: Re: Arrgghhh...text file transfer NT -> RH6.0
Date: Sat, 18 Sep 1999 18:07:05 +1000
Ted,
You files probably have DOS EOL (End-of-line) characters. They differ from
Unix (and Macs do them different, too). Using FTP in ASCII mode converts
these nicely, but Samba can't, because it doesn't know when conversion is
needed. To convert these manually, use:
dos2unix file.dos >file.unix
unix2dos file.unix >file.dos
HTH
ROSCO
<[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
>
> Hi,
>
> I copied over my .java and Makefiles to RH6.0 from my NT4.0 to my
> RH6.0 and guess what the Makefile refuses to work. I know there is no
> syntax errors. However, I suspect that there are some unprintable
> characters in the makefile that screwed the make utility up.
>
> If I delete the makefile totally and re-write it, then it works.
> Otherwise no luck. If anyone knows some problems with transferring
> ASCII files between NT4.0 -> RH6.0 with Samba, please help...thanks.
>
>
> Ted
>
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Arrgghhh...text file transfer NT -> RH6.0
Date: Sat, 18 Sep 1999 07:31:20 GMT
On Sat, 18 Sep 1999 07:26:53 GMT, [EMAIL PROTECTED] wrote:
>
>Hi,
>
>I copied over my .java and Makefiles to RH6.0 from my NT4.0 to my
>RH6.0 and guess what the Makefile refuses to work. I know there is no
>syntax errors. However, I suspect that there are some unprintable
>characters in the makefile that screwed the make utility up.
>
>If I delete the makefile totally and re-write it, then it works.
>Otherwise no luck. If anyone knows some problems with transferring
>ASCII files between NT4.0 -> RH6.0 with Samba, please help...thanks.
>
>
>Ted
>
The funny thing is the error output from the Makefile also get
garbled. It does not help to delete the contents of the makefile and
restart. I had to actually delete the Makefile itself.
Here is the error:
', needed by `Line.class'. Stop. `Line.java
Line.class:Line.java
javac Line.java
There is a tab there. The same thing works if I delete the Makefile
first and re-type....strange...
------------------------------
From: Kevin Reed <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.misc
Subject: Re: Remote server monitoring akin to AlertPage
Date: Sat, 18 Sep 1999 06:29:58 GMT
Try big Brother...
http://maclawran.ca/bb-dnld/
In article <50xE3.19832$[EMAIL PROTECTED]>,
"Stephen Perkins" <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm looking for some a software package that will constantly monitor
the
> health of remote servers and services. Something along the lines of
> AlertPage from Geneva Software or SiteScope. However, I'd like the
utility
> to run on Linux and, preferrably, not cost an arm and a leg.
>
> Specifically, I need to automatically ping a set of servers every
minute,
> and if the ping fails x times in a row, send an email message to a
> predetermed address. When/if the server comes back, I'd like a
different
> message sent.
>
> It would be nice to be able to monitor services as well (Sendmail,
DNS, WWW,
> etc) but that is not required.
>
> I'm sure there is something like this available, but searchs on
dejanews etc
> came up empty. I'm probably using the wrong keywords. Any thoughts
> regarding this would be appreciated!
>
> Thanks in advance,
>
> - Steve
>
> P.S. Running RedHat 6.0 and would love an RPM pointer...
>
>
--
Kevin Reed
TNET Services
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: "Qiang Xue" <[EMAIL PROTECTED]>
Subject: Problem with LinkSys Netcard
Date: Sat, 18 Sep 1999 04:24:02 -0400
I am install RedHat 6.0 (kernel 2.2.5) with a LinkSys EtherFast
10/100 LAN PCI netcard.
During installation, I select "tulip", it cannot probe out the
net device. So I stopped installing netcard. I downloaded tulip.c
of version 0.9. I compiled it and put it in /lib/modules/net/tulip.o,
then "depmod -a" and "insmod tulip.o". With "netconf" I chose "DHCP"
and set network device as "tulip". Okay, I restarted the system,
and the system failed to bring up the tulip interface!
The card works well under Windows 98 (DHCP networking). And a diagnosis
program in LINUX also detected out the card. Then what's the problem?
I am rather ignorant of LINUX and don't know the necessary processes
to deal with such kind of problem. Can anyone help me out? Thanks a lot.
------------------------------
From: "Mr. Coburn" <[EMAIL PROTECTED]>
Subject: Re: Why can't I telnet to root ??
Date: Sat, 18 Sep 1999 06:43:21 GMT
Scott Simpson wrote:
> > > Whenever I try to telnet to my Linux box as user "root", it will not
> > > authenticate me, even though I put in the correct password. I can
> telnet to
> > > my Linux machine as any other user. I can also "su" once I've done this
> and
> > > become root, but it sure would be nice to telnet there directly.
>
> > Theresa Halloran <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
> > You need to add the shell you are using when you login as root to the
> > /etc/shells file. Then it will let you telnet to linux machine.
>
> You are incorrect. It has nothing to do with /etc/shells. You need to edit
> /etc/securetty to enable root on a pty. You can only login to root on the
> terminals in /etc/securetty.
You are all wrong. It is in about a kabillion different mechanisms that forbid
root login and the list grows daily. The linux system has, over the last 3
years, become so clogged up with security crap that you can't do anything with
it any more. Each entity (the pams boys, the hosts.allow boys, the nfs geeks,
the shell boys and just about every other club) that has any jurisdiction at
all has brewed up their own set of pet roadblocks to keep anybody from getting
anything done. I gave up and learned enough about SSH to get it working and
went at it that way. What a mess.
------------------------------
From: john <[EMAIL PROTECTED]>
Subject: IP Masqing and proxy arp?
Date: Sat, 18 Sep 1999 08:20:07 GMT
Hello,
Could someone please elaborate on the following quote? It is from the
Linux IP Masquerade mini HOWTO v1.20.
"Quoting Pauline Middelink:
Do not forget to mention the ANYBOX should have the Linux box
as its gateway (whether is be the default route or just a subnet
is no matter). If the ANYBOX can not do this, the Linux machine
should do a proxy arp for all routed address, but the setup of
proxy arp is beyond the scope of the document."
Thanks for any comments.
John
------------------------------
From: Bryan <Bryan@[EMAIL PROTECTED]>
Subject: Re: Recommendation for 100Mbps Switched Ethernet hardware
Crossposted-To: comp.sys.ibm.pc.hardware.networking
Date: Fri, 17 Sep 1999 20:52:19 GMT
In comp.os.linux.networking David C. <[EMAIL PROTECTED]> wrote:
: I should have said "network" instead of "segment". Layer-2 information
: is definitely valid when transmitted across bridges.
: The addresses are not necessarily unique, however. The Ethernet spec
: allows for host-assigned addresses, which may be used instead of the
: factory-assigned addresses. If they are used, it is possible for two
: hosts on two different networks to have the same layer-2 address. (It
: wouldn't be a smart thing to do, but that's another subject.)
you sayin' DECnet isn't 'smart'? ;-) ;-)
that's the most famous protocol that -required- the mac addr be a
writeable register. since the mac addr was a math function of the
DECnet (routing, layer3) addr, when you set a node's DECnet addr, the
mac addr had to correspond/change.
I agree it was more stuff to have to worry about, but having duplicate
DECnet addr's was just as bad as having dupe mac's. and you'd notice
the misconfig quickly enough, so the problem wouldn't last long ;-)
: >
: > usually these days, routers can fallback to bridging mode and bridge
: > what they can't natively route.
: Maybe. It depends on how they're configured. If each port is connected
: to a different network/subnet, this won't happen. If multiple ports are
: connected to the same network/subnet, then the router may bridge packets
: between those ports.
doesn't depend only on the port config or the subnets on those ports;
its usually a global setting that defines whether bridging should
occur on non-routed frames or not. the fact that port-A is on one
subnet and -B is on another means nothing to lan-based protocols (eg,
LAT), when stations on those respective segments want to talk.
--
Bryan, http://www.Grateful.Net - Linux/Web-based Network Management
->->-> to email me, you must hunt the WUMPUS and kill it.
------------------------------
** 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
******************************
