Linux-Networking Digest #900, Volume #10 Sun, 18 Apr 99 02:13:42 EDT
Contents:
Re: problem with Tulip card and 2.2.x (NOT 2.0.36!) ("MattW")
Re: Linux - My honest opinion (Juergen Heinzl)
FTPing for peter field ([EMAIL PROTECTED])
Re: cannot connect Internet with Linux (Glenn Graham)
Re: timed looping ("Fredrik Lindstr�m")
Configure NE2000 ethernet card ([EMAIL PROTECTED])
Re: Need help with PPP... ("M.C. van den Bovenkamp")
FTP connections through an ISPs Firewall ([EMAIL PROTECTED])
----------------------------------------------------------------------------
Reply-To: "MattW" <[EMAIL PROTECTED]>
From: "MattW" <[EMAIL PROTECTED]>
Subject: Re: problem with Tulip card and 2.2.x (NOT 2.0.36!)
Date: Sat, 17 Apr 1999 14:13:22 -0700
Sorry mistype....
MattW <[EMAIL PROTECTED]> wrote in message
news:WG7S2.1010$[EMAIL PROTECTED]...
>>>>>> edit the tulip.c and comment out the autodetection or the media. I
forgot<<<<<<<
edit the tulip.c and comment out the autodetection OF the Default Media
something like TULIP_DEFAULT_MEDIA or TULIP_MEDIA_SWITCH I don't
remember
> where it is but it's pretty obvious. Recompile the source. Unfortunately
> my hubs were all autosensing and I didn't have to force a speed so I didnt
> bother trying to figure out how to force a specific speed. Default 100
Full
> Dup worked for me.
>
> The version of Tulip.c (v0.89h) that comes with Redhat 5.2 (2.036 kernel)
> does not have a problem though. I had the same problem with Slacware 3.6.
>
> Hope this helps.
>
> MattW
>
> rj <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> >
> > while we're on the subject, I just got fed up with Solaris non-support
for
> my
> > hardware and switched to Slackware 3.6 (the 2.0.36 kernel or something).
> I have a
> > kingston
> > KNE110T Ethernet card which uses the Tulip driver. I compiled it
(v0.91)
> according
> > to the compile-command at the end of the file and installed the module
in
> the
> > kernel. The
> > if I do an
> >
> > ifconfig eth0
> >
> > I can see the interface, but when I try to configure the interface
> > using
> >
> > ifconfig eth0 <ip-address> netmask <netmask> broadcast <gateway-address>
> >
> > I get an error like
> >
> > SIO(some junk): try again.
> >
> > Not very verbose. Is this an IRQ problem? Am I configuring the
interface
> wrong?
> >
> > any help is greatly appreciated!
> >
> > rj
> >
> > Rod Smith wrote:
> >
> > > [Posted and mailed]
> > >
> > > In article <[EMAIL PROTECTED]>,
> > > BL <[EMAIL PROTECTED]> writes:
> > > > I did further debugging
> > >
> > > I assume this is in reference to a previous posting, but I never saw
it,
> > > and it doesn't seem to be in the same thread as this one. In the
> future,
> > > you might want to reply to your previous messages in situations like
> this,
> > > to be sure people get any necessary context.
> > >
> > > > and determined that with the same hardware and same
> > > > basic kernel config, I can kill the DEC tulip ethernet card with
heavy
> traffic
> > > > on the 2.2 kernel series (up to 2.2.5). While the 2.0.36 kernel
will
> NOT show
> > > > the same problem...
> > > >
> > > > I connect two linux boxes, both running tulip cards, via a rolled
> (xover)
> > > > cable. both are 100/full modes.
> > > >
> > > > I create a heavy traffic load (ping -s 1000 -f) and after a minute
or
> so, the
> > > > activity lights (on the ethernet cards) stops. at this point, the
> only way to
> > > > get this setup back to working is to reboot the 2.2 kernel system.
> note that
> > > > the 2.0.36 system does NOT need to be rebooted - when the 2.2 system
> comes up
> > > > again, all is well and the two systems can talk again.
> > > >
> > > > I then brought the 2.2 system down to 2.0.36 and repeated the
> experiment. NO
> > > > HANGS THIS TIME!
> > >
> > > First, have you tried the latest Tulip drivers from
> > > http://cesdis.gsfc.nasa.gov/linux/drivers/tulip-devel.html? I was
> > > experiencing problems with both a 21143 board and a PNIC Tulip clone
> until
> > > I upgraded to tulip.c version 0.90q. The tulip.c that came with
kernels
> > > through 2.2.3 just wouldn't work with the 21143 board, and the
"stable"
> > > 0.90 worked mostly, but would occasionally flake out. 0.90q seems
much
> > > better so far.
> > >
> > > Second, what precise Tulip chipset(s) are you using? There are at
least
> > > three 10/100 Tulip chipsets from DEC, and several clones. They all
> behave
> > > slightly differently from one another. For instance, a 21140 board
> worked
> > > fine for me with the standard Tulip driver from kernel 2.2.3, but as I
> > > just wrote, a 21143 board didn't.
> > >
> > > Third, I don't have two machines with Tulip cards. What I do have is
an
> > > iMac with whatever networking hardware it's got (BMAC+, according to
> > > dmesg when I boot it into LinuxPPC) and a PC with a Tulip 21143-based
> > > board installed. They're connected via a Linksys 10/100 hub. I've
tried
> > > your ping flood test both ways, with both boxes running Linux, and
I've
> > > experienced no hangs. The one oddity I have noticed is that, when I
use
> > > the iMac to ping the x86 box, the hub's collision light comes on a
lot.
> > > When I ping the other way, that doesn't happen. (Does anybody have
any
> > > ideas about that?)
> > >
> > > --
> > > Rod Smith
> > > [EMAIL PROTECTED]
> > > http://www.channel1.com/users/rodsmith
> > > NOTE: Remove the "uce" word from my address to mail me
> >
>
>
------------------------------
From: [EMAIL PROTECTED] (Juergen Heinzl)
Subject: Re: Linux - My honest opinion
Date: Sat, 17 Apr 1999 21:20:15 GMT
In article <O22S2.2175$_a6.68700@paloalto-snr1>, A. Feiner wrote:
>This post does not intend to flame in anyway. It's just an honest opinion,
>so do not reply unless it's to the matter. No Gates sucks or Novell is dead
>please.
>
>We have been testing Linux Redhat 5.2 for the last three months. We chose
>Redhat since it seemed to be the most widely acknowledge by large corps like
>IBM, Dell, etc. This is the 1st point:
>1. Linux has no place in the business world unless steadily supported by
>these giants. I heard that Compaq is coming out with Alpha for Linux. This
>is a very good start.
It might sound strange but over in Germany you could buy pre-installed
Linux systems quite some time before Compaq even knew it exists. Say
since some companies were able to make money with it, it seemed to
have its place in the business world then already.
>2. Companies like I work for cannot rely on one sharp admin, today here,
>tomorrow there. So if I have the budget, I prefer a recognized,
>well-documented OS, with a solid backbone (Microsoft, Novell, HP-UX etc.).
So M$ software is known to be well documented ? No undocumented
features and such ? Wow, that *is* news to me.
[...]
>Remember, in today's world the purpose is expanding, not maintaining.
>Learning curves should be short, information accessible at all times.
>So until then, I will stick to my current OS.
If your focus is mainly on a short learning curve be assured you'll
find yourself one day either having sold your soul to some company
or simply second class (out of experience with some other companies
department I am not affiliated with anymore).
What I am opposed to is your statement ... today's world is somewhat
more complicated and has more facets. For the rest of what you wrote,
sure. There is always room left for improvement and since, finally,
even the big ones have accepted and adopted Linux as another serious
*nix system expect support and such to become better. You cannot
expect a big bang and there it is, all done, fine and good.
Stay tuned,
Juergen
--
\ Real name : J�rgen Heinzl \ no flames /
\ EMail Private : [EMAIL PROTECTED] \ send money instead /
------------------------------
From: [EMAIL PROTECTED]
Subject: FTPing for peter field
Date: Sun, 18 Apr 1999 05:00:56 GMT
This is a reply to a previous message by peter field about his problems with
FTPing
I do not know if you have solved this problem or not but i will give you
my input.
I recently configured exactly what you are talking about and to make it
work i had to configure my linux computer for the FTP and then use SAMBA
to attatch my windows computers drive to it so that i could have access
to it.read the SAMBA how-to. The invalid PORT command error may be a
result of the IP address on the connecting computer differing from the
IP address which the linux machine is seeing you connected on. This can
occur because the computer you are running on is, itself, behind a
firewall. I recommend going to freshmeat.net and checking out the pages
on ProFTP there i a command that will allow you to connect using foriegn
addresses, which is, unfortunately, a security risk as your logs may not
report the true IP Address of the connecting computers. I believ the
command is AllowForeignAddress but do not quote me on that.
Sincerely,
Jeff Rickard
PS sorry that i had to email you but for some reason I could not post a
reply on dejanews
Peter Field wrote:
I have a PC connected to the Internet via a second PC running Linux
Slackware 2.0 with IP Masquerading.
I can FTP out to the Internet in both passive (Netscape) and active
modes. However, I would like to allow FTP access from the Internet to my
PC. Has anyone written some code to allow this to work ?
Looking at the Linux source code (ip_masq_ftp.c), active FTP only works
because the s/w looks for data containing the FTP command "PORT" and
then makes a masquerade entry for it - otherwise this mode wouldn't work
!
To allow FTP from the Internet would probably require a program like
"redir" to allow connection to port 21 (FTP control port) and then
additional code to check for the FTP commands "PORT" and "Entering
Passive Mode" to support the data connections.
"redir" to port 21 with the current Linux code does not work, I think
this is because the PORT command contains an IP address (internet
address) which does not match the source address that the was used in
the control session (IP address of Masquerade box). I can see the logon
process taking place OK but as soon as the PORT command is sent the
response is always "Invalid PORT command".
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: Glenn Graham <[EMAIL PROTECTED]>
Subject: Re: cannot connect Internet with Linux
Date: Sat, 17 Apr 1999 22:21:55 -0700
If you would like a really simple solution to your
problem, one which was designed for newbies, check out
http://www.nerdsnetwork.com/unix.htm
I think you'll find the easy-way there.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
inTEXT Communications
Vancouver BC
On Sat, 17 Apr 1999, ts wrote:
> Date: Sat, 17 Apr 1999 17:30:09 -0400
> From: ts <[EMAIL PROTECTED]>
> Newsgroups: comp.os.linux.networking
> Subject: Re: cannot connect Internet with Linux
>=20
> I am also new to Linux and just got my ppp working. It appears your machi=
ne
> is asking the ISP to authenticate themselves. You may want to read this f=
or
> more info. This paper worked for me the first time I tried.
> http://axion.physics.ubc.ca/ppp-linux.html
> Good Luck!
>=20
> Ruangvith Tantibhaedhyangkul wrote:
>=20
> > Hi anyone out there,
> >
> > I'm having (rather serious) problems with Linux. I'm using Caldera's
> > OpenLinux 1.3 with KDE 1.0 on Pentium 200, RAM 64 MB and SupraExpress
> > 336i on COM3 (which works fine on 'Microsoft' Windows 98), the 2.0.35
> > kernel was compiled to support pentium and ppp internally. It can't be
> > configured to connect to Internet at all.
> >
> > First I used kppp (script based), it dialed, logged in, and told me tha=
t
> > it was 'logging on to network'. But that was that, it stayed put, until
> > timed-out.
> >
> > Here's what happened on script debug window:
> >
> > ----------start of debugging message----------
> > +++ATH
> > OK
> > ATZ
> > OK
> > ATDT2718000
> > CONNECT 115200Welcome to Asia-Access Internet
> > Host: US1
> > Port: S6/2
> >
> > Username: ruangvit
> > Password:
> > PPP session from (203.145.0.204) to 203.145.3.105 beginning.
> > ----------end of debugging message----------
> >
> > And the corresponding /var/log/messages:
> >
> > ----------start of /var/log/messages----------
> > Apr 10 17:41:39 janbond syslog: ROOT LOGIN ON tty1
> > Apr 10 17:42:00 janbond CRON[810]: (root) CMD ([ -x /usr/sbin/cronloop =
]
> > && /usr/sbin/cronloop Hourly)
> > Apr 10 17:45:42 janbond xntpd[643]: synchronized to LOCAL(0), stratum=
=3D7
> > Apr 10 17:45:42 janbond xntpd[643]: kernel pll status change 89
> > Apr 10 17:47:01 janbond kernel: registered device ppp0
> > Apr 10 17:47:01 janbond pppd[842]: pppd 2.2.0 started by root, uid 0
> > Apr 10 17:47:01 janbond pppd[842]: Using interface ppp0
> > Apr 10 17:47:01 janbond pppd[842]: Connect: ppp0 <--> /dev/modem
> > Apr 10 17:47:32 janbond pppd[842]: LCP: timeout sending Config-Requests
> > Apr 10 17:47:32 janbond pppd[842]: Connection terminated.
> > ----------end of /var/log/messages----------
> >
> > Someone told me to try minicom. I could log in, quited without resettin=
g
> > and typed at commnd prompt 'pppd /dev/modem 38400 crtscts modem
> > defaultroute'. I also commented out /etc/ppp/options. Here's what
> > happened:
> >
> > ----------start of /var/log/messages----------
> > Apr 13 18:25:03 janbond pppd[947]: pppd 2.2.0 started by root, uid 0
> > Apr 13 18:25:03 janbond pppd[947]: Using interface ppp0
> > Apr 13 18:25:03 janbond pppd[947]: Connect: ppp0 <--> /dev/modem
> > Apr 13 18:28:03 janbond pppd[947]: LCP: timeout sending Config-Requests
> > Apr 13 18:28:03 janbond pppd[947]: Connection terminated.
> > ----------end of /var/log/messages----------
> >
> > Of course, on interface, it was nothing but quiet.
> >
> > I tried minicom again, this time using /etc/ppp/options which looked
> > like:
> >
> > ----------start of /etc/ppp/options----------
> > -detach
> > modem
> > lock
> > crtscts
> > defaultroute
> > asyncmap 0
> > mtu 552
> > mru 552
> > lcp-max-configure 60
> > ----------end of /etc/ppp/options----------
> >
> > Here's what happened on the terminal:
> >
> > ----------start of login terminal----------
> > CONNECT 115200
> > Welcome to Asia-Access Internet
> > Host: US1
> > Port: S6/2
> >
> > Username: ruangvit
> > Password:
> > PPP session from (203.145.0.204) to 203.145.3.105 beginning.
> > ----------end of login terminal----------
> >
> > I then pppd, which resulted:
> >
> > ----------start of pppd result----------
> > [root@janbond /root]# pppd
> > ~=FF}#=C0!}!}!} }8}!}$}"(}"}&} } } } }%}& =AC=93=F6}'}"}(}"]}.~~=FF}#=
=C0!}!}!} }} } }
> > }%}& =AC=93=F6}'}"}(}"]}.~~=FF}
> > ----------end of pppd result----------
> >
> > And this is the corresponding /var/log/messages:
> >
> > ----------start of /var/log/options----------
> > Apr 14 11:16:41 janbond pppd[831]: pppd 2.2.0 started by root, uid 0
> > Apr 14 11:16:41 janbond pppd[831]: Using interface ppp0
> > Apr 14 11:16:41 janbond pppd[831]: Connect: ppp0 <--> /dev/ttyp0
> > Apr 14 11:19:41 janbond pppd[831]: LCP: timeout sending Config-Requests
> > Apr 14 11:19:41 janbond pppd[831]: Connection terminated.
> > Apr 14 11:19:41 janbond pppd[831]: Receive serial link is not 8-bit
> > clean:
> > Apr 14 11:19:41 janbond pppd[831]: Problem: nothing was received
> > Apr 14 11:19:41 janbond pppd[831]: Exit.
> > ----------end of /var/log/messages----------
> >
> > I tried looking up the howto's. Nothing seems to help.
> >
> > Waiting for your kindly reply.
> >
> > Ruangvith Tantibhaedhyangkul
> > <[EMAIL PROTECTED]>
> > writing from a Microsoft system.
>=20
>=20
>=20
------------------------------
From: "Fredrik Lindstr�m" <[EMAIL PROTECTED]>
Crossposted-To: linux.dev.admin
Subject: Re: timed looping
Date: Sun, 18 Apr 1999 01:07:21 +0200
Could it be something in crontab that makes it do thoose calls?
[EMAIL PROTECTED] skrev i meddelandet <7fah1c$c94$[EMAIL PROTECTED]>...
>I noticed a few messages dating from a little while back about these
>messages, but nobody seems to have the same cause (or lack of one) that I
>have discovered.
>
>On two linux boxes that I admin (one Sparc and one i386), about 30 of these
>messages appear at a time, in cycles of about 30 minutes:
>
>Apr 17 10:20:11 kermit in.timed[4103]: connect from 205.173.43.230
>
>Following each cycle is the line:
>
>Apr 17 10:20:12 kermit inetd[263]: time/udp server failing (looping),
service
>terminated
>
>Now, I could accept the fact that something was going wrong with timed,
>EXCEPT, IT ISN'T RUNNING! I don't mean that there is no entry in
inetd.conf,
>there is. However, NO NETWORK PACKETS are received during this time that
>relate to timed. The thing that is going on EVERY time this happens is the
>linux boxes are chatting with the NIS master server (updating some cache or
>something). The IP of that computer isn't even 205.173.43.230 though. That
>IP is our dialup server. And it never even talks to the two linux boxes.
>
>Something is VERY strange here. These messages date back to the
installation
>of the linux boxes, so it's nothing that just happened. Anyone have any
>ideas?
>
>--
>Brian Morris
>mailto:[EMAIL PROTECTED]
>Freshman, Computer Engineering, CalPoly, San Luis Obispo, CA
>
>-----------== Posted via Deja News, The Discussion Network ==----------
>http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: [EMAIL PROTECTED]
Subject: Configure NE2000 ethernet card
Date: Sat, 17 Apr 1999 23:40:06 GMT
What steps must I take to have RedHat Linux recognize my NE2000 compatible
ethernet adapter? The adapter settings are irq=7, io=0x320, base=0xC800.
Here is my /etc/conf.modules:
alias sound cs4232
alias midi opl3
options opl3 io=0x388
options cs4232 dma=3,0 io=0x530 mpu_irq=9 irq=5 mpu_base=0x330
alias eth0 ne
options ne io=0x320 irq=7
To activate eth0, I invoke:
ifconfig eth0 10.0.0.1 netmask 255.0.0.0 up
but ifconfig reports:
SIOCSIFADDR: Operation not supported by device
eth0: unknown interface.
SIOCSIFNETMASK: Operation not supported by device
eth0: unknown interface.
What must I do to correct this error?
Derek
Please cc: your response to [EMAIL PROTECTED]
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: "M.C. van den Bovenkamp" <[EMAIL PROTECTED]>
Subject: Re: Need help with PPP...
Date: Mon, 12 Apr 1999 13:21:12 +0200
Andras Gefferth wrote:
> But when it comes to modifying the routing table it breaks.
> If I type 'route' it shows the header of the routing table and then is stops
> doing
> anything, I have to kill it with Ctrl-C or something.
Try using 'route -n'. If that works, you have a DNS problem. Just
'route' by itself will try to resolve the IP addresses to names (using
/etc/hosts, DNS or NIS, whichever is applicable), 'route -n' will not.
Regards,
--
Marco van den Bovenkamp.
CIO EMEA Network Design Engineer,
Lucent Technologies Nederland.
Room: HVS BZK 32
Tel.: (+31-35-687)2724
Mail: [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Subject: FTP connections through an ISPs Firewall
Date: Sun, 18 Apr 1999 05:18:06 GMT
I have been trying to set up an FTP server on my ADSL line. My ISP, Telus,
has a firewall and I needed to bypass it as it would not take standard port
connections (ie. 21 for FTP and 20 for FTP data channel). I found the
appropriate services on my linux box and successfully changed the port
addresses. Now my FTP is operating on ports 2121 FTP and 2120 FTP-data.
Everything appeared to be going fine until I asked some of my friends to test
it. My friends with dial-up connections were able to connect on these higher
port connections under active FTP mode (but not passive), but my friends with
cable modems and ADSL lines could login, but could not get a directory
listing to appear under either active or passive FTP modes. This may be due
to an illegal port connection error message which shows up.
I speculate that the problem has to do with the fact that the computers are
trying to connect with IP addresses that are their home computers and not the
Internet's IP address (going through a router). Another Problem that i
noticed was that when a computer tries to connect over the internet via
passive mode it uses the IP address of my linux box's external interface (the
network card that connects me to my cable modem) and not the Internet IP
address that is assigned to me by Telus (the one people connect to).
Another interesting point is that anyone who uses a DHCP server for their IP
address can connect but static IPs can not.
Another problem is the PASV command scripting. When the FTP client attempts
to connect to my FTP server in passive mode the server sends the client the
command PASV 10.127.73.42 which is not the external IP address but the
internal network interface that connects to the router modem. If anyone
knows of a way to change this (other than recoding the FTP daemon, which i
have already tried) it could solve all my problems.
How can I get my friends with Cable/ADSL lines to connect? (With linux and
Windows 95/98)
Any comments are appreciated.
Sincerely,
Jeff
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
** 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
******************************
