Linux-Networking Digest #978, Volume #10 Wed, 28 Apr 99 06:13:35 EDT
Contents:
Re: NetGear 10/100 Ethernet Card and drivers ("EFH")
Re: free computer13 (James Lee)
rcp bug? Some silly experimentation (David Steuber)
Progress, but no success (Dhiren Patel)
Re: Changing Telnet Ports? ("Rocky Seelbach")
Re: ppp under linux - Please, help! (Gerrit Hiddink)
Linux sockets bug? (Luca Deri)
Translate (i)pppd hex output to ascii (Gerrit Hiddink)
Re: Installing Linux and NT ("Clair Mooza")
Linux Networking Configuration (0x0100)
Re: NT faster than Linux? (Stan Hewitt)
Re: Intel 82558 LAN Adapter ("Staffan Emr�n")
Linux in nt domain ("Steve Yen")
dial up PPP sever (Jerome Fayot)
----------------------------------------------------------------------------
From: "EFH" <[EMAIL PROTECTED]>
Subject: Re: NetGear 10/100 Ethernet Card and drivers
Date: Thu, 22 Apr 1999 07:15:07 -0400
Frank Miles <[EMAIL PROTECTED]> wrote in message
news:7fkp45$m1m$[EMAIL PROTECTED]...
> In article <7fj2qc$f36$[EMAIL PROTECTED]>,
> Brian Zamora <[EMAIL PROTECTED]> wrote:
> >I have a Pentium running Linux 5.1(I think I seem to be the only one
> >running 5.1) Anyways The Netgear310tx net card is timing out when I turn
I recently purchased the Netgear310tx and was pleased to find that it came
with Netgears own version of the Tulip driver on the install disk. The
driver is in the directory Linux and install help can be found in
Help\Linux. The help file says that you should use their version of the
driver and not the regular Tulip driver. It's working like a charm for me,
great to see companys supporting Linux for their products.
------------------------------
From: James Lee <[EMAIL PROTECTED]>
Crossposted-To:
comp.lang.basic.visual.misc,comp.lang.c,comp.lang.c++,comp.lang.java.programmer,comp.lang.javascript,comp.lang.perl.misc,comp.os.linux.advocacy,comp.os.linux.hardware,comp.os.linux.misc,comp.os.linux.setup,comp.os.os2.advocacy,com
Subject: Re: free computer13
Date: 28 Apr 1999 00:56:08 -0500
In comp.os.linux.setup opus007 <[EMAIL PROTECTED]> wrote:
: I hate spam.
More like framing than spamming.
Hmmm.. I love spams (the meat in the metal can kind).
------------------------------
From: David Steuber <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: rcp bug? Some silly experimentation
Date: 27 Apr 1999 22:42:53 -0400
A while back, I posted a message stating that I couldn't rcp a 2GB
file from solo (a laptop computer) to interloper (a PPro 200). Both
are running SuSE 6.0 with the 2.0.36 kernel.
Today, I got nfs setup and working. Interloper is the nfs server and
is mounted to /interloper on solo. I performed the following
commands:
david@solo:/interloper/home/david/tmp > cat /dev/zero > zero
cat: write error: Invalid argument
david@solo:/interloper/home/david/tmp > ls -l
total 2105376
-rw-r--r-- 1 david users 2147482624 Apr 27 20:39 zero
david@solo:/interloper/home/david/tmp > rm zero
david@solo:/interloper/home/david/tmp > time cat /dev/zero > zero
cat: write error: Invalid argument
real 11m3.494s
user 0m1.160s
sys 1m52.190s
david@solo:/interloper/home/david/tmp > time cp zero ~/tmp/
real 63m50.375s
user 0m1.190s
sys 2m21.920s
The write error that cat spits out is the file hitting the 2GB limit.
I think the time difference from the creation of the file from
/dev/zero and the copy can be explained away be disk io limitations on
each of the machines, particularly solo. Clearly the cpu usage is
minimal. Both machines are connected via 100bt ethernet and a 100bt
hub. All NICs are 3COM and so is the hub.
The history of this exploration of moving large files between machines
goes like this. I discover that ftp times out when moving large
files. I enable rcp (and rsh) from solo to interloper, but not the
other way around. This works for a while. Then I find that moving
really large files locks up the network, forcing me to remove and
reinsert the NIC on solo to get networking back. Also, I find that I
can't conviniently rcp a huge number of little files. So I now have
nfs set up.
I admit that I am doing unusual things, but rcp and ftp should have
worked. I am glad that nfs does. I hope the day comes when nfs works
from linux to any other nfs client/server. Or maybe a better file
sharing protocol will come along.
In case anyone missed the question, Is there a known bug in rcp for
copying very large files? Can anyone reproduce it (rcp a 2GB file)?
Where is the proper place to report this bug? The man page does not
say. Of course there is always the posiblity that there is a problem
with my setup.
--
David Steuber
http://www.david-steuber.com
If you wish to reply by mail, _please_ replace 'trashcan' with 'david'
in the e-mail address. The trashcan account really is a trashcan.
Those who do not understand Unix are condemned to reinvent it, poorly.
-- Henry Spencer
------------------------------
Date: Tue, 27 Apr 1999 23:04:12 -0700
From: Dhiren Patel <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.protocols.ppp,linux.redhat.ppp
Subject: Progress, but no success
So I'm not having any luck getting pppd to connect. Initially, chat
would not talk to the serial port, even though minicom could (I verified
I was using the same device in both cases). Now, after a complete
reinstall, chat seems to be able to talk to the modem (I can manually
dial via 'cat - >/dev/ttyS1'), but it doesn't seem to want to listen.
The log in /var/log/messages shows that chat is sending 'AT' to the
modem and expecting 'OK', but it doesn't seem to receive it. Doing this
manually in minicom works fine. Any clues would be greatly
appreciated...
Dhiren
------------------------------
From: "Rocky Seelbach" <[EMAIL PROTECTED]>
Subject: Re: Changing Telnet Ports?
Date: Tue, 27 Apr 1999 19:33:13 -0700
[EMAIL PROTECTED] wrote;
>I currently run redhat 5.1 and have telnet disabled in /etc/inetd.conf.
When
>connecting remotely I use ssh. I now run an icecast server, and for
>admistration of the server it uses telnet to port 8002. I'd like to enable
>telnet to use 8002 and disable 23.
I'm not familiar with icecast, so I'm not sure whether you are talking about
enabling a server on port 8002 or telneting from somewhere else into port
8002 on the icecast server. For getting from another system to port 8002 on
the server you only need to telnet <server> <port> with most telnet clients.
telnet servername 8002
If the icecast server already has a telnet server listening on port 8002
then this approach makes sense. You can see if it has put a listen on that
port with netstat. Using netstat, you can see every tcp/udp service that is
available on your machine.
netstat -a will show you all the services using the /etc/services entries
for the ports, and netstat -an will show it all to you numerically.
netstat -an | grep 8002 will show you if port 8002 is up and listening.
>Telnet is really only a security risk on this machine if it's on 23.
Not sure I'd agree with that. Port 23 is the well known port for telnet,
but port scanners don't care what port they get an answer on.
>How do I go about changing that? Is it simply a
>matter of modifying /etc/services to reflect the new port number,
>rereading /etc/inetd.conf and starting the server?
Putting up a telnet server on port 8002 would be as simple as changing the
port number in /etc/services for the telnet entry and thumping inetd.
However, I'd recommend copying the entry in /etc/services to telnet2 for the
new port number, and then copy the telnet entry in /etc/inetd.conf, using
telnet2 for the service. That way, even though you have port 23 disabled,
you can enable it if you want.
------------------------------
From: Gerrit Hiddink <[EMAIL PROTECTED]>
Crossposted-To: comp.protocols.ppp
Subject: Re: ppp under linux - Please, help!
Date: 28 Apr 1999 07:18:47 GMT
In comp.protocols.ppp Laurent Masse-Navette <[EMAIL PROTECTED]> wrote:
> #----/etc/ppp/options----
> #
> ipxcp-accept-remote
> ipxcp-accept-local
> ipxcp-accept-network
if you want IP connectivity and no IPX (IPX can be used by
Microsoft Windows Network) then I'd suggest using ipcp-accept-remote
and ipcp-accept-local.
> #silent
> kdebug 7
> pap-max-authreq 20
> pap-restart 10
> asyncmap 0xa0000
> noauth
> user userName
I think you need to fill in your account name here, unless it has been
changed to protect the innocent.
> domain mindspring.com
> noipdefault
> debug
> defaultroute /dev/modem 57600
> netmask 255.255.255.0
> mtu 1500
> connect "/usr/sbin/chat -v ABORT BUSY ABORT 'NO CARRIER' '' 'AT&F0' OK
> ATDP8890177 ogin userName word myPassword '' '\d\c'"
same goes here: are you sure you've typed the correct username and
password?
> Apr 26 22:16:41 localhost pppd[888]: sent [PAP AuthReq id=0x1
> user="userName" password="myPassword"]
> Apr 26 22:16:51 localhost pppd[888]: sent [PAP AuthReq id=0x2
> user="userName" password="myPassword"]
> Apr 26 22:16:51 localhost pppd[888]: rcvd [PAP AuthNak id=0x0 49 6e 76 61 6c
> 69 64 20 4c 6f 67 69 6e 3a 20 55 6e 6b 6e 6f 77 6e 20 75 73 65 72 6e 61 6d
> 65 2e 0d 0a]
These string of numbers represent text. I do not know why the developers
of pppd decided to print it in hex numbers, but if you translate it to
ascii it reads:
"Invalid Login: Unknown username."
so I'd suggest to check the username, password combination both in
the connect script as well as in /etc/ppp/pap-secrets.
I'll post the tiny little program I used to translate hex into ascii
in the relevant newsgroups.
Grit
------------------------------
From: Luca Deri <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.system
Subject: Linux sockets bug?
Date: Wed, 28 Apr 1999 09:18:10 +0200
Reply-To: [EMAIL PROTECTED]
This is a multi-part message in MIME format.
==============F55A5C1073DB7CC431CAB4D4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi all,
I'm currently developing a network monitoring application named ntop
(http://www-serra.unipi.it/~ntop/). One of the ntop users (Olaf
Schnapauff) found a very strange problem. This problem occurs only on
Linux i386 (Alpha works for instance).
Please find enclosed a very simple application (packetLogger - based on
Linux sockets) you can use to reproduce the problem. Suppose to have
host A (MAC Address 08:00:69:0B:6F:A1) and host B (MAC Address
00:20:AF:73:C6:2E). Host B is an i386 running Linux 2.X. No matter what
OS runs on A. Now start "packetLogger 08:00:69:0B:6F:A1
00:20:AF:73:C6:2E" in order to filter packets flowing though A and B. I
suppose there's no other traffic (e.g. telnet) between A and B. Now from
A do 'ftp B' and transfer a file C (large, e.g. > 1 MB). Stop
packetLogger, look at the # of packets and restart it. Now from B do
'ftp A' and transfer the very same file C [if A and B are Linux boxes
you can start packetLogger on both hosts]. You will notice that in the
second case you've lost many packets whereas in the first case
everything works fine.
Do you have a clue of what could cause this problem?
Thanks in advance, Luca.
--
Luca Deri Finsiel S.p.A.
Via Matteucci 34/B 56124 Pisa, Italy.
Ph. +39/050/968.639 Fax. +39/050/968.626
Email: [EMAIL PROTECTED] WWW: http://www.tlcpi.finsiel.it/~deri/
Software is about stuff, about getting hands dirty - Jim Coplien
==============F55A5C1073DB7CC431CAB4D4
Content-Type: text/plain; charset=us-ascii;
name="packetLogger.c"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="packetLogger.c"
#include <sys/param.h>
#include <sys/ioctl.h>
#include <sys/socket.h>
#include <sys/time.h>
#include <net/if.h>
#include <linux/if_ether.h>
#include <netinet/in.h>
#include <errno.h>
#include <malloc.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
struct ethernet_header {
u_char ether_dhost[6];
u_char ether_shost[6];
u_short ether_type;
};
char* etheraddr_string(const u_char *ep)
{
u_int i, j;
char *cp;
struct enamemem *tp;
static char buf[sizeof("00:00:00:00:00:00")];
char hex[] = "0123456789ABCDEF";
cp = buf;
if ((j = *ep >> 4) != 0)
*cp++ = hex[j];
else
*cp++ = '0';
*cp++ = hex[*ep++ & 0xf];
for(i = 5; (int)--i >= 0;) {
*cp++ = ':';
if ((j = *ep >> 4) != 0)
*cp++ = hex[j];
else
*cp++ = '0';
*cp++ = hex[*ep++ & 0xf];
}
*cp = '\0';
return (buf);
}
int main(int argc, char* argv[]) {
struct ifreq ifr;
struct sockaddr sa;
char *device = "eth0";
unsigned long packetNum=0, totLen=0;
int fd;
if(argc != 3) {
printf("Usage: %s <MAC Addr. host A> <MAC Addr. host B>\n", argv[0]);
printf("Example: %s 08:00:69:0B:6F:A1 00:20:AF:73:C6:2E\n", argv[0]);
return(-1);
}
fd = socket(PF_INET, SOCK_PACKET, htons(ETH_P_ALL));
if (fd < 0) {
printf("Error creating socket.\n");
return(-1);
}
/* Bind to the interface name */
memset(&sa, 0, sizeof(sa));
sa.sa_family = AF_INET;
(void)strncpy(sa.sa_data, device, sizeof(sa.sa_data));
if (bind(fd, &sa, sizeof(sa))) {
printf("bind: error\n");
return(-1);
}
memset(&ifr, 0, sizeof(ifr));
strncpy(ifr.ifr_name, device, sizeof(ifr.ifr_name));
if (ioctl(fd, SIOCGIFHWADDR, &ifr) < 0 ) {
printf("SIOCGIFHWADDR: error\n");
return(-1);
}
/* Base the buffer size on the interface MTU */
memset(&ifr, 0, sizeof(ifr));
strncpy(ifr.ifr_name, device, sizeof(ifr.ifr_name));
if (ioctl(fd, SIOCGIFMTU, &ifr) < 0 ) {
printf("SIOCGIFMTU: error\n");
return(-1);
}
while(1) {
struct sockaddr from;
int fromlen, cc, len=0;
u_char bp[2048], srcHost[64], dstHost[64];
struct ethernet_header *ep;
do {
fromlen = sizeof(from);
cc = recvfrom(fd, bp, 2048, 0, &from, &fromlen);
len += cc;
} while (strcmp(device, from.sa_data));
ep = (struct ethernet_header*)bp;
strcpy(srcHost, etheraddr_string(ep->ether_shost));
strcpy(dstHost, etheraddr_string(ep->ether_dhost));
if(strcmp(srcHost, argv[1]) && strcmp(srcHost, argv[2]))
continue;
else if(strcmp(dstHost, argv[1]) && strcmp(dstHost, argv[2]))
continue;
else {
totLen += len;
printf("%5d\t%8u\t%s -> %s (len=%d)\n",
++packetNum, totLen, srcHost, dstHost, len);
}
}
close(fd);
return(0);
}
==============F55A5C1073DB7CC431CAB4D4==
------------------------------
From: Gerrit Hiddink <[EMAIL PROTECTED]>
Crossposted-To: comp.protocols.ppp,xs4all.isdn,nl.comp.isdn,de.alt.comm.isdn4linux
Subject: Translate (i)pppd hex output to ascii
Date: 28 Apr 1999 07:29:16 GMT
Hi,
some (all?) versions of (i)pppd print important messages only in hex
characters. These messages sometimes contain clues as to why setting up
a connection fails, so it is very important to be able to read these
messages. They look like this:
Apr 26 22:16:51 localhost pppd[888]: rcvd [PAP AuthNak id=0x0 49 6e 76 61 6c
69 64 20 4c 6f 67 69 6e 3a 20 55 6e 6b 6e 6f 77 6e 20 75 73 65 72 6e 61 6d
65 2e 0d 0a]
I've written a tiny program to translate it into ascii. It could have been
done with programs like 'hexdump', but figuring out how they work costs more
time than writing it.
My program is written as a filter, i.e. it accepts characters from stdin and
writes them to stdout. You can start it with: "cat | hex", and then copy
and paste the hexadecimal numbers into standard in. Compiling instructions
are in the source.
Here's the source (completely free of copyrights, rights and warranty):
#include <stdio.h>
#include <stdlib.h>
/* compile with cc hex.c -o hex
** Converts hex to ascii
** Written by G. Hiddink ([EMAIL PROTECTED])
*/
int conv(int a)
{
if (a>'9')
{
a=a|32;
return a-'a'+10;
}
else
return a-'0';
}
void main ()
{
int a,b;
while (!feof(stdin))
{
a=fgetc(stdin);
while ((a==' ') || (a==13) || (a==10))
a=fgetc(stdin);
b=fgetc(stdin);
printf("%c",conv(a)*16+conv(b));
}
}
------------------------------
From: "Clair Mooza" <[EMAIL PROTECTED]>
Subject: Re: Installing Linux and NT
Date: Wed, 28 Apr 1999 00:42:11 -0500
Thanks! I will definitely check that out.
-What'sHerFace?
news.eunet.be wrote in message <7g4hko$r71$[EMAIL PROTECTED]>...
>Hello,
>
>You should read the LINUX-NT-mini-Howto that can be found in the Linux
>Documentation Project. It will guide you through the installation.
>You will also find everyhting concerning boot loader configuration.
>URL : http://metalab.unc.edu/LDP and you can find several mirrors on the
>net.
>
>Yves Van de Weyer.
>
------------------------------
From: [EMAIL PROTECTED] (0x0100)
Subject: Linux Networking Configuration
Date: Wed, 28 Apr 1999 09:16:02 GMT
Problem:
1) After boot is complete, 'ifconfig -a' reports 'lo'
recognized as 127.0.0.1 with appropriate Mask, etc. Also, 'eth0' is
shown, but w/o an IP, Mask, etc. Neither device appears already set to
active (UP).
2)Unable to ping any of the devices from Linux box. (Even
after activating them using: ifconfig lo up; ifconfig eth0 up). This
is displayed:
ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1): 56 data bytes
ping:sendto:Network is unreachable
ping:wrote 127.0.0.1 64 chars, ret = -1
@ ^c, I get:
"xx" packets transmitted, 0 packets received, 100% packet loss
3)Oddly, after making manual entries in the Routing Table,
then running 'routed', I can ping my Win98 box from the Linux box,
(AND, vice versa) but still cannot ping 'lo', eth0', or 'eth1' (when
included) FROM the Linux box!
4)System displays:"eth0 media is TP" , then hangs after:
'ifconfig eth0 up' if I set an IP for eth0 and try to ping
it.
My Research To Date:
Ethernet-HOWTO
NET-3-HOWTO
RH Install Guide @ www.redhat.com
System Info:
Intel 233MMX (PI)
Asus TXP4 Main Board
eth0: DEC 21040 using de425 driver
eth1: Linksys LNE PCI II using ne2000 driver
Both NIC's at separate IRQ's
Each NIC shares IRQ with PCI Steering
Kernel: 2.0.36 with BOTH drivers compiled
Both NIC's work fine under Win98 using dual-boot feature.
I feel like I've overlooked something incredibly basic and simple.
I'm open to suggestions...
[BTW, I'd prefer prefer to work from the console.]
------------------------------
From: Stan Hewitt <[EMAIL PROTECTED]>
Crossposted-To: linux.samba,uk.comp.os.linux
Subject: Re: NT faster than Linux?
Date: Tue, 27 Apr 1999 04:55:48 -0600
Well the bozos that run the test spent a hell of a lot of energy tuning thier
NT system
and ZIP tuning to linux box.
Please note they had linux doing reverse DNS lookups for EACH hit.........
and IIS doesnt do that, it just logs the ip# like they could have had thier
linux box do too. If they had bothered to read the doc that CAME WITH
apache, theyd know that. Morons.
It seems to me it was a race between NT and thier DNS.... not linux.
Plus on the PS list I dont see and httpd running which means they had
it running from thier inetd.
With that in mind I was extremely impressed linux preformed as it did.
I hope someone does a test like this and cares for thier linux box as they
did thier NT box. Its just ridiculous. Leave it to Microsoft to pull a stunt
like that
------------------------------
From: "Staffan Emr�n" <[EMAIL PROTECTED]>
Subject: Re: Intel 82558 LAN Adapter
Date: Wed, 28 Apr 1999 10:52:59 +0200
I've been using the 82558, both on separate NIC's and integrated on
motherboards, on several mashines and they all worked right out of the
box. Be shure to use the eepro driver. No options should be needed, this
driver autoprobes the chip for any information it needs.
Be shure however that the chip is really 82558, and not 82559. This is a
new chip released by Intel by february this year, and it is as far as I
know not yet supported. Intel themselves say that Linux support for
82559 will be available by the autumn, but maybe someone else could
write a driver before that.
Best regards
Staffan Emren, Tricom data AB
Matt Klein wrote:
>
> I have the Intel 82558 LAN Adapter on my motherboard... Has anyone had
> any success in using this with Linux? I think this is the same chipset
> that is present on many of the supported Intel networking cards, so I
> think it should work... I am running redhat 5.1 (kernel 2.0.36). Any
> help would be appreciated...
> --
> Matt Klein
> [EMAIL PROTECTED]
------------------------------
From: "Steve Yen" <[EMAIL PROTECTED]>
Subject: Linux in nt domain
Date: Wed, 28 Apr 1999 17:33:28 +0800
Reply-To: "Steve Yen" <[EMAIL PROTECTED]>
Hi there,
I am currently having some integration problem with Linux Red Hat 5.2
and Nt 4.0 Server.
Environment: The NT server is setup as a primary and the linux is
installed as a member of the network. Setup the linux as a gateway,
running DHCP and PPP as well.
Problem: Unable to lock in from clients (WIN 95/98) to the primary
domain server (NT 4.0 Server) from the windows networking login box.
The error message displayed "the password you supplied is incorrect
or the access to the server is denied" .
However I do not have any problem logging in from other member server
(running NT) as well as other NT Workstations within the network.
Please note that all the users accounts are maintained on the
Primary. There are no duplicate user accounts in the linux box.
Temporary solution: Down the linux to allow everyone running 95/98 to
login before bringing up the linux.
Please help me out on this asap.
Thanks alot!
Steve Yen ([EMAIL PROTECTED])
------------------------------
From: Jerome Fayot <[EMAIL PROTECTED]>
Subject: dial up PPP sever
Date: Wed, 28 Apr 1999 11:25:36 +0200
Hi,
has anyone already managed to establish a modem to modem PPP connection
between a Linux machine and a Windows98 machine, the windows acting as a
dialup PPP server ?
In such a case, I would be interested in the required script files for
linux and the configuration for windows.
Thanks a lot
Jef
------------------------------
** 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
******************************
