Linux-Networking Digest #112, Volume #12          Wed, 4 Aug 99 18:13:43 EDT

Contents:
  Re: Cobalt Qube 2 Windows file sharing partial failure (updated, but still no 
solution) (LONG) (Andrew Williams)
  Re: newbie dns and telnet ("Gert Jensen")
  users can't mount cdrom (Jeff Greer)
  Re: pop-mail in redhat 6.0 and remote popping? (Anthony Valentine)
  Re: It is Linux stupid! ("John N")
  Re: POP3 (Anthony Valentine)
  redir and ipportfw ([EMAIL PROTECTED])
  in.ftpd zombie problem with wu-ftpd on RH6 (Brian Daniels)
  Re: Linux and MS Proxy Server HELP! ([EMAIL PROTECTED])
  Re: Network cards for both WindowsNT and Linux (Rod Smith)
  Re: PPP (Dial-out) connection requirements ([EMAIL PROTECTED])
  Re: Ifconfig help (dead_grandmother)

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

From: Andrew Williams <[EMAIL PROTECTED]>
Crossposted-To: comp.os.ms-windows.nt.admin.networking,comp.protocols.smb
Subject: Re: Cobalt Qube 2 Windows file sharing partial failure (updated, but still no 
solution) (LONG)
Date: Wed, 04 Aug 1999 21:37:37 +0200

how long are the User names?  try looking at
http://www.germany.net/teilnehmer/101/69082/samba.html#4.4.1.
hope that helps.


Lucius Chiaraviglio wrote:

>         I am definitely a linux newbie and only sort of expert with
> Windows NT, but I have run into a stumper that still has the Cobalt
> Networks technical support people stumped (and they've been working on
> this for several days, with over a week inserted in the middle for
> both them and me to think about it).  Previously determined
> information is first in this message, followed by new information.
>
> Previously determined information (mostly -- new items have a *)
> ----------------------------------------------------------------
>
>         At the places I work -- San Luis Obispo, CA and
> Emeryville, CA -- we have a Cobalt Qube 2 at each site acting as a
> web/ftp/e-mail/file/DNS/DHCP/WINS server and network address
> translator, with several Windows NT 4.0 clients (and in the case
> of San Luis Obispo, also Windows 95 and Windows 98 clients).  The
> problem we are having is that when I try to do the following at our
> San Luis Obispo site, it always gives the error message "incorrect
> password or unknown username for:" / {Qube 2 network name}, even
> though I just put in my correct user name and password.  I can confirm
> that my user name nd password are correct because I am able to use FTP
> to get to my files.  In contrast, if I log in as "admin" with the
> appropriate password, I can get to "admin"-accessible files without a
> hitch.  Not only that, but at our Emeryville site, I have no such
> problem with user files either.  It makes no difference what my
> Windows NT user name and password are.  The same thing happens with
> Windows NT 4.0 SP3, SP4, and SP5, and with Windows 95 SP1 (with the
> difference that the Windows 95 user name has to be the same as the
> Qube user name, because when attempting to access a shared volume, it
> only asks for a password, and not a user name).  I checked all of the
> Qube 2 services in the web-based configuration interface to confirm
> that nothing was left out of or set incorrectly set in the
> configuration for Windows file sharing, FTP, DNS, and DHCP -- if
> something is incorrectly set for one of these services, it must be set
> in a part of a configuration file that does not show up in the
> web-based interface.  I also manually looked inside of /etc/smb.conf,
> and although I am not familiar with what does what in this file, I
> didn't notice anything obviously strange when comparing these files
> from the two systems; however, I don't think it is anything in here,
> because the only difference between the files (according to diff) is
> the line which specifies the workgroup/domain for the Cobalt Qube 2).
> I didn't experiment with manually editing any configuration files,
> because this might void the Cobalt warranty, and I am not sufficiently
> familiar with linux to know what is safe to edit and what isn't.
>
>         To summarize:
>
> Case 1:
>
> 1.      Log in on Windows NT 4.0 (SP3 -- I may have also tried this
>         on a machine with SP4, but I'm not sure) in our Emeryville
>         office.
> 2.      Double-click Network Neighborhood.
> 3.      Navigate until the Cobalt Qube 2 is shown; double-click on it.
> 4.      Enter any valid Cobalt Qube 2 user name (except "root", which
>         is specifically forbidden) and password combination.
> Result: It works -- the files for the user you selected are now
>         accessible just as if they were on a Windows NT file server.
>
> Case 2:
> 1.      Log in on Windows NT 4.0 (SP3, SP4, or SP5) or Windows 95 SP1
>         in our San Luis Obispo office.  If logging in on Windows 95,
>         log in as "admin".
> 2.      Double-click Network Neighborhood.
> 3.      Navigate until the Cobalt Qube 2 is shown; double-click on it.
> 4.      Enter "admin" and the Cobalt Qube 2 password for this account
>         (Windows 95 does not give the opportunity to enter the user
>         name).
> Result: It works -- the files accessible to the "admin" account are
>         now accessible just as if they were on a Windows NT file
>         server.
>
> Case 3:
> 1.      Log in on Windows NT 4.0 (SP3, SP4, or SP5) or Windows 95 SP1
>         in our San Luis Obispo office.  If logging in on Windows 95,
>         log in as a valid Cobalt Qube 2 user other than "admin".
> 2.      Double-click Network Neighborhood.
> 3.      Navigate until the Cobalt Qube 2 is shown; double-click on it.
> 4.      Enter any valid Cobalt Qube 2 user name except "root" or
>         "admin", and the appropriate password (if using Windows 95,
>         enter only the password for the Cobalt Qube 2 user name you
>         used to log into Windows 95).
> Result: It never works -- it always claims the user name and password
>         are incorrect.
>
>         Variations I have tried (under Windows NT 4.0 SP4 at our San
> Luis Obispo office), with absolutely no effect:
>
> A.      Make a Windows NT account with the same name and password as
>         the Cobalt Qube 2 account.
> B.      Change the Windows NT machine's workgroup to be the same as
>         the workgroup/domain that the Cobalt Qube 2 is in.
> C.      Different Windows NT 4.0 service packs as noted above (not on
>         the same computer).
> D.      Different computers with the same Windows NT 4.0 service pack.
> E.      Change what (if any) accounts are permitted telnet access into
>         the Cobalt Qube 2.
> *F.     Change a San Luis Obispo office Windows NT machine's name to
>         be the same as the unix user name (except for the case -- it
>         won't let me make it lower case).
> *G.     Enable plain text password negotiation on a San Luis Obispo
>         office Windows NT machine -- not acceptable for long-term
>         use, but it didn't even help in the short run.
>
>         I also confirmed that every Windows 95/NT computer I used is
> capable of correctly accessing files on a Windows NT 4.0 SP3 server.
> On the subset of these computers that I also tried pinging the Cobalt
> Qube 2 or accessing it via FTP, ping and FTP also work correctly.
>
>         Our networks are configured very similarly, with the following
> differences:
>
> 1.      The domain/workgroup names are different.
> 2.      The outside IP addresses (on the secondary ethernet interfaces
>         of the Cobalt Qube 2's) are different.
> 3.      The Emeryville office only has 1 Windows NT workgroup, whereas
>         the San Luis Obispo office has multiple Windows NT workgroups.
> 4.      The Emeryville office has its connection to the outside world
>         (from the secondary ethernet port of the Cobalt Qube 2)
>         through an Alcatel DSL 1000 "modem" over DSL service provided
>         by Pacific Bell; the San Luis Obispo office has its connection
>         to the outside world (also from the secondary ethernet port of
>         the Cobalt Qube 2) via an ethernet cable to a hub and/or
>         router in the office of our local ISP next door.
> 5.      Something unknown in the configuration of the Emeryville
>         office connection to the outside world causes a reverse DNS
>         lookup by a remote site to return a CNAME record instead of a
>         PTR record (according to the sysadmin of the remote site) --
>         see my accompanying post (about resulting problem) only in
>         comp.os.linux.networking.
> *6.     In the Emeryville office, the Windows NT machines have the
>         same name (except for case) as the unix user name of the
>         person who normally uses it.  On the other hand, this doesn't
>         seem to make a difference (see F above).
> 7.      The Cobalt Qube 2's differ very slightly as detailed below.
>
>         The Cobalt Qube 2 in our Emeryville office (on which things
> seem to work properly) is configured with the following software:
>
> Cobalt OS Release 4.0               (original install)
> Cobalt Qube2 Update Release 1.0     (original install)
> Shell History Patch Release 1.1     (original install)
> "RUNNING MFG TESTS" minor bug       (original install -- a patch is
>                                     available, but not installed here)
>
>         The Cobalt Qube 2 in our San Luis Obispo office (on which
> Windows file sharing doesn't work right) is configured with the
> following software:
>
> Cobalt OS Release 4.0               (original install)
> Cobalt Qube2 Update Release 1.0     (added as patch from manufacturer)
> Shell History Patch Release 1.1     (added as patch from manufacturer)
> Doesn't have "RUNNING MFG TESTS" bug
>
> Note:  Cobalt OS 4.0 on the Cobalt Qube 2 identifies itself (before it
> gives the login prompt) as "Cobalt Linux release 4.0 (Fargo)" /
> "Kernel 2.0.34 on a mips".
>
> New information
> ---------------
>
>         Our /etc/smb.conf as it came from the manufacturer (including
> the incorrect server string) follows.  Note that the Emeryville and
> San Luis Obispo versions are identical except for the workgroup name.
>
> [BEGIN /etc/smb.conf]
>
> ;  Samba Configuration
> ;  Revision 1.0 for the 2700RJ, [EMAIL PROTECTED] 17.oct.98
> ;
> ;  DO NOT USE THE \ CONTINUATION!  THE QUBE PARSING CODE WILL CHOKE ON
> IT!
> ;
> [global]
>    alternate permissions = no
>    case sensitive = no
>    dead time = 5
>    debug level = 0
>    default case = upper
>    delete readonly = yes
>    delete veto files = yes
>    dns proxy = no
>    domain logons = yes
>    domain master = no
>    encrypt passwords = yes
>    follow symlinks = yes
>    guest account = ftp
>    local master = yes
>    lock directory = /var/lock/samba
>    locking = yes
>    log file = /var/log/samba
>    mangle case = no
>    map hidden = yes
>    map system = yes
>    max log size = 5000
>    oplocks = yes
>    os level = 1
>    preferred master = yes
>    preserve case = yes
>    security = user
>    server string = Cobalt Qube 2800WG
>    share modes = yes
>    short preserve case = yes
>    socket options = TCP_NODELAY
>    strict locking = yes
>    veto files = /Network Trash Folder/
>    wide links = yes
>    wins support = yes
>    workgroup = acmppi
> ;
> [homes]
>    comment = Home Directories
>    browseable = no
>    read only = no
>    create mask = 0755
> ;
> ;home BEGIN (do not delete this line)
> [home]
>   path = /home/groups/home
>   public = no
>   browseable = yes
>   writable = yes
>   printable = no
>   create mask = 0775
>   valid users = admin @home
>   force create mode = 0664
>   force directory mode = 0775
>   hide dot files = yes
> ;home END (do not delete this line)
> ;allusers BEGIN (do not delete this line)
> [allusers]
>   path = /home/groups/allusers
>   public = no
>   browseable = yes
>   writable = yes
>   printable = no
>   create mask = 0775
>   valid users = admin @allusers
>   force create mode = 0664
>   force directory mode = 0775
>   hide dot files = yes
> ;allusers END (do not delete this line)
>
> [END /etc/smb.conf]
>
> Note:  The Samba version included in Cobalt OS 4.0 is a release of
> 1.9.18p10 (according to the included man pages and according to the
> help information printed by smbd when called with incorrect command-
> line parameters) that apparently does not come with smbfs (even
> though the man pages mention it).
>
>         I have tried changing the security setting to SHARE and making
> homes browseable (both with and without also making homes have user
> only and user = %S).  If I try it this way, the user "admin" is no
> longer able to access any shares formerly accessible to "admin"; a
> "homes" share shows up in the Windows NT Network Neighborhood, but
> attempting to access it either fails with "incorrect password or
> unknown username" (if user only and user = %S are set) or gives an
> error message "The network name could not be found" without even
> giving an opportunity to enter a user name or password.  I have also
> tried setting debug level to 3 or 10 (both with and without setting
> password chat debug) and looking for error messages in /var/log/samba,
> but this doesn't give me any information deeper than "NT password
> incorrect" error messages (even with password chat debug set, it won't
> show the value or encrypted value it thinks it got for the password --
> note that encrypt passwords is set in /etc/smb.conf).
>
>         I did always perform a "kill -HUP" on all smbd processes after
> saving changes to /etc/smb.conf (but for some reason, changing the
> server string to "Cobalt Qube 2 %h" seems to have no effect).
>
>         I should note that even though "server appliances" such as the
> Cobalt Qube 2 are supposed to just work when you plug them in with
> minimal setup, this has not been the case (this problem isn't the only
> problem that has driven me to call tech support, just the first one to
> get them stumped too).  It is driving me up the wall, because I am
> completely out of ideas as to what could be wrong.
>
>         On a somewhat related note:  something in Cobalt OS 4.0 leaves
> around plain text password files (found by searching the entire hard
> disk for a couple of passwords).  All such files that I found seem to
> be related to AppleTalk (even though this is not turned on on this
> machine), and they are all set to have permissions 0600, but this is
> still not good.
>
> Lucius Chiaraviglio | [EMAIL PROTECTED]
> --------
> To reply to this message, remove the "not at" characters from in front of the
> abbreviation of the company name (Advanced CMP Products, Inc.).  If you are
> seeing this in an e-mail message, it is because I am posting it and e-mailing
> it at the same time -- normal e-mail messages from me do not have this feature.
> Note:  I am trying a new news server -- it seems to work well, but it has a
> very short expiration time (1 week for most groups), so I will likely miss your
> reply unless you send it by e-mail in addition to posting it.

--
Mielipiteet omiani - Opinions personal, facts suspect, especially on my
   http://www.germany.net/teilnehmer/101/69082/samba.html
Simple Samba Solutions web page                             ICQ 1722461



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

From: "Gert Jensen" <[EMAIL PROTECTED]>
Subject: Re: newbie dns and telnet
Date: Wed, 4 Aug 1999 22:29:38 +0200

Thanks for the help!!

Gert Jensen



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

From: [EMAIL PROTECTED] (Jeff Greer)
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: users can't mount cdrom
Reply-To: [EMAIL PROTECTED]
Date: Wed, 04 Aug 1999 21:13:44 GMT

Hello,

Why can I only mount the cdrom drive as root?

here is /etc/fstab

/dev/scd0               /mnt/cdrom              iso9660
noauto,ro,user  0 0

-rwxr-xr-x   1 root     users       37672 Oct  6  1998 /bin/mount
brwxrwxrwx   1 root     users     11,   0 May  5  1998 /dev/scd0
lrwxrwxrwx   1 guest    users           4 Mar 26 04:23 /dev/cdrom
-> scd0


Shouldn't this be automatically setup by mainstream linux
distros?  Linux will be useless as an OS for the desktop as long
as braindead problems like this exist.  Linux sure needs a set of
desktop standards.  

I like Linux, but setting up some things is a complete waste of
time.  I am not interested in knowing how to make my cdrom
mountable by guests.  There should be a standard script to handle
this.
--
Jeff Greer
B.S. computer science, University of MO - Rolla
==================================================
Windows NT has crashed,
I am the Blue Screen of Death,
No one hears your screams...

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

From: Anthony Valentine <[EMAIL PROTECTED]>
Subject: Re: pop-mail in redhat 6.0 and remote popping?
Date: Wed, 04 Aug 1999 13:17:58 -0800

RedHat 6.0 doesn't come with the pop server software installed.

To check to see if you have it, type:
which ipop3d

If you get something like:
/usr/sbin/ipop3d
you have the software installed.  If you get something like:
which: no inpop3d in /sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/. . .
then you don't have it installed in which case, you need to download (or get
from your RH6 CD) the imap rpm and install it.  For me this would be with the
command:
rpm -i /cdrom/RedHat/RPMS/imap-4.5-3.i386.rpm
your command may differ depending on where you mount your cd-rom (/mnt/cdrom
for example).

Once you get imap installed, everything should work.


Anthony




Mendel wrote:

> Can anybody tell me what I am doing wrong in my mail configuration?
> Everytime I log into the pop-port, it gives a comment like Connection
> closed by foreign host. When I email to the domain in question I get an
> error saying it might be an MX-misconfiguration, but it looks like
> everything is ok...
> telnet localhost 110
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> Connection closed by foreign host.
>
> When loggin in with Eudora from win 98, it says:
> Logging into POP Server
> Error reading from network Cause: Connection closed by foreign host (0)
>
> In the error-mail to postmaster it reads:
> 553 mail.amorf.com config error: mail loops back to me (MX problem?)
> 554 <[EMAIL PROTECTED]>... Local configuration error
>
> The pop-3 service is turned on in inetd.conf, and is listening on port 110.
> What can I do, please help,
> Mendel


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

From: "John N" <[EMAIL PROTECTED]>
Subject: Re: It is Linux stupid!
Date: Wed, 4 Aug 1999 17:16:55 -0400

Thank you Dan.
I definitely tried to copile the source, to not avail. It will give me a ton
errors (imposible to describe here) and will not compile and I'm sure I'm
following the instructions. Will try again and revert.
Meantime, BIG THANKS :)>
Thaddeus Speed wrote in message <[EMAIL PROTECTED]>...
>John N wrote:
>
>> Hello everybody,
>>
>> I've installed RH5.2 with all the trimmings, but there only one problem.
>> I still cannot make my network component work.
>>
>> Even though I've mouth-to-mouth resucitation, aspirin, and some other
stuff,
>> I can not revive the dead ...
>>
>> This looks to me like the Blair Witch Project ... and I'm shaking ...
>>
>> The problem is this.
>> I've downloaded Donald Becker's rtl8391 source code for my SMC1211tx nic,
>> but since I'm a DOS/Windows-in-transition-to-a-better-world kind of guy,
I'm
>> stuck with with the source, cannot compile, finaly I do not know how to
>> attach the final .o file to the kernel.
>>
>> Help please, before I commit harakiri with a razor blade.
>>
>> John Nunez  <:)
>>
>> P.S. Still loving Linux ... :)
>
>the instructions for compiling the driver are commented at the bottom of
the
>source.  so just cat the source, and type in what it says. It has one entry
for
>multiple processors and one not, and then another one.  Be sure to use the
>right one.
>after you have the .o file, move it to /lib/modules/[kernel
version]/net.(this
>is where it is in RH6, you better make sure.)
>
>Then write back if you don't know how to do the conf.modules and
>/etc/sysconfig/network-scripts/ifcfg-et0 thing
>TIP: if you don't want to mess with the config files directly, use Control
>Panel: kernel button for ailiasing the module, and networking for the rest.
>This also has an easy "activate" button to save you from modprobe, etc.
>Dan.
>
>



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

From: Anthony Valentine <[EMAIL PROTECTED]>
Subject: Re: POP3
Date: Wed, 04 Aug 1999 13:24:19 -0800

If you haven't already, uncomment the pop3 (and pop2 if you use pop2) line(s)
in the /etc/netd.conf.  Then refresh inetd with:

killall -HUP inetd

then try to telnet to port 110, and you should get something like:
+OK POP3 mis3.sbs.com v7.59 server ready

Anthony



Chip Transisto wrote:

> Yes, I know.  As my message said, I installed imap (rpm -i imap*.rpm)
> but I still don't have POP.  In 5.2, all you had to do was install
> imap.  In 6.0 there is another step since a simple install won't work.
> My question was, does anyone know what the extra step is after you
> install imap?
> Thanks.


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

From: [EMAIL PROTECTED]
Subject: redir and ipportfw
Date: Wed, 04 Aug 1999 21:17:39 GMT

I upgraded to RedHat 6.0 and I was wondering where the hell REDIR and
IPPORTFW went off to.  I don't mind IPPORTFW because it now a part of
IPCHAINS, but about the REDIR I definitely care.
What I'm trying to do is set up a firewall system with my web server
and mail server behind it.  When e-mail or a web request come to the
site, I want it REDIRected to their appropiate servers.  Is their
something new that I am overlooking or do I have to use REDIR.  And if
so, where can I find REDIR and/or an appropriate tool to do such a task.
If you have any other reliavant info pertaining to gateways, firewalls,
or the subject, please e-mail me at [EMAIL PROTECTED]
Thank you
Benjamin Hayes


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

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

From: [EMAIL PROTECTED] (Brian Daniels)
Subject: in.ftpd zombie problem with wu-ftpd on RH6
Date: Wed, 04 Aug 1999 20:31:22 GMT

We're using wu-ftpd-2.5.0-2 on RedHat 6.0.  The server is working
fine, but we have noticed the following problem:

After several days of operation, there will be many 'leftover'
in.ftpds.  We allow 100 users at a time and this is resulting in users
being denied access to the site even though there are only 3-4 active
connections.

If you do a ftpshut followed by a killall in.ftpd, then all is fine
for several more days.

Once the problem develops, a ps shows:

# ps ax | grep in.ftpd
27280 ?        SW     0:00 [in.ftpd]
29153 ?        SW     0:00 [in.ftpd]
29530 ?        SW     0:00 [in.ftpd]
30009 ?        SW     0:00 [in.ftpd]
31063 ?        SW     0:00 [in.ftpd]
31067 ?        SW     0:00 [in.ftpd]
31384 ?        SW     0:00 [in.ftpd]
31899 ?        SW     0:00 [in.ftpd]
31948 ?        SW     0:00 [in.ftpd]
32115 ?        SW     0:00 [in.ftpd]
  324 ?        SW     0:00 [in.ftpd]
  572 ?        SW     0:00 [in.ftpd]
  581 ?        SW     0:00 [in.ftpd]
 1094 ?        SW     0:00 [in.ftpd]
 1449 ?        SW     0:00 [in.ftpd]
 1709 ?        SW     0:00 [in.ftpd]
 2302 ?        SW     0:00 [in.ftpd]
 2519 ?        SW     0:00 [in.ftpd]
<many more follow>

wu-ftpd is being launched from inetd.conf as follows:
ftp     stream  tcp     nowait.255      root    /usr/sbin/tcpd in.ftpd
-l -a -t240 -T240

Any ideas on solving this would be appreciated.

Thanks,
Brian
([EMAIL PROTECTED])


Anything you can imagine (and many things you can't), someone, 
somewhere on the net is doing.

Brian Daniels                  [EMAIL PROTECTED]
      http://www.mindspring.com/~briandaniels

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

From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.hardware,comp.os.linux.setup
Subject: Re: Linux and MS Proxy Server HELP!
Date: Wed, 04 Aug 1999 20:55:59 GMT

Could you provide a bit more of an explanation...
how can squid or apache provide connectivity to
the microsoft proxy server..?

In article <[EMAIL PROTECTED]>,
  scott <[EMAIL PROTECTED]> wrote:
> Hi,
>
> You will find both Squid and Apache on the
Redhat 6 CD.
>
> > Howdy,
> >
> > I have just set up RedHat 6.0, and want to run
it as my main operating
> > system.  On my local intranet I am running MS
Proxy Server 2.0 on NT Server,
> > and in my current Win98 system I have the WSP
(winsock proxy) Client
> > installed for all winsock requests (so it
makes the internet seemless in
> > windows).  How do I access the proxy server in
Linux?  Is there no WSP
> > Client
> > equivalent for linux?  Is there another way of
setting up linux so it can
> > use the proxy server?
> >
> > I know the obvious answer would be to replace
NT Server with linux, but I am
> > trying to take linux one step at a time (i am
relatively new to it)...
> >
> > Any help would be greatly appreciated...  And
may i just say, LINUX RULES
> > :-)
> >
> > EvanD
> > [EMAIL PROTECTED]
>
>



Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

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

From: [EMAIL PROTECTED] (Rod Smith)
Subject: Re: Network cards for both WindowsNT and Linux
Date: Wed, 04 Aug 1999 21:05:28 GMT
Reply-To: [EMAIL PROTECTED]

[Posted and mailed]

In article <7o9gva$d61$[EMAIL PROTECTED]>,
        [EMAIL PROTECTED] writes:
> I want to buy a low-end network card for both WindowsNT and Linux
> (RH6.0). One local store Axion Tech seems to have good reputation. But
> their tech support says none of their cards have drivers for Linux. I
> just can't believe it. Can anyone help? Their NICs page is at

PRECISELY what did they say?  Did they say that their cards don't COME
WITH Linux drivers?  Or did they say that drivers flat-out aren't
available?  If the latter, buy elsewhere, or know that you're dealing with
clueless bozos pontificating on something about which they know nothing. 
If the former, fine; most NICs (and other hardware, for that matter)
doesn't come with Linux drivers, since the Linux drivers come with Linux. 
A few NICs do have Linux drivers on floppies or on the manufacturer's web
sites, but I don't know offhand if either of the ones you mentioned falls
into that category.

> I'm particularly interested in their best sellers, i.e. "3COM:3C905BTX,
> ETHERLINK XL, 10/100MBPS, PCI, TWISTEDOEM, PCI for $50" or
> "D-LINK:DFE-530TX, 10/100 MBPS ETHERNET PCI ADAPTERPNP, NWAY AUTO
> NEGOTIATION, FULL DUPLEX, LED STATUS for $19"

Both these are supported.  The 3COM uses the 3c59x driver, and the D-Link
uses the via-rhine driver.  The 3COM is the more sophisticated board, but
I'm not sure there'd be much of a difference in a low-end network.  I've
got a D-Link DFE-530TX in one of my system, and it works fine with Linux.

> Is there one central place on the Web that lists all NICs supported by
> Linux?

The list of UNSUPPORTED boards would be much more manageable.  ;-)

Seriously, though, you could check at
http://cesdis.gsfc.nasa.gov/linux/drivers.  I don't think there's a
complete list, but there's a LOT about Linux NIC drivers on those pages. 
If I'm not mistaken, the site is maintained by Donald Becker, who wrote a
large number of them.

-- 
Rod Smith
[EMAIL PROTECTED]
http://www.channel1.com/users/rodsmith
NOTE: Remove the "uce" word from my address to mail me
Author of _Special Edition Using Corel WordPerfect 8 for Linux_, from Que

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

From: [EMAIL PROTECTED]
Subject: Re: PPP (Dial-out) connection requirements
Date: Wed, 04 Aug 1999 20:58:28 GMT

In article <7oa59h$t6r$[EMAIL PROTECTED]>,
  [EMAIL PROTECTED] wrote:
> Hi All,
> I have to set up my PPP such that :
>
> (i) It doesn't disconnect if the connection is Idle
> (ii) It automatically reconnects if my ISP drops the connection. Even
if
> it means multiple reconnection attempts [maybe - with predefined
breaks]
>
> Or in other words I want my m/c to be connected to the internet all
the
> time 24x7.
>
> What all PPP options do I use ?
>
> will the 'persist' option lead to automatic execution of the
chatscript
> when the connection drops ?
>
> Any Sample script ?
>
> TIA
> Rajeev
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
>

Yes the persist option is what you need.  But if your address is
dynamically allocated, every time your connection drops you will have a
different IP.  So you may want to look at auto-config scripts.


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

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

From: [EMAIL PROTECTED] (dead_grandmother)
Subject: Re: Ifconfig help
Date: Wed, 04 Aug 1999 22:02:43 GMT

this will restart your network connection without rebooting...

type "/etc/rc.d/init.d/network stop;/etc/rc.d/init.d/network start"

your granny



On Wed, 04 Aug 1999 21:02:20 GMT, [EMAIL PROTECTED] (Sam Levy)
wrote:

>I'm having a problem trying to use ifconfig to change the ip number of
>of my ethernet interface. If I issue an ifconfig eth0 down command the
>card will no longer ping other boxes on the network.
>I then issue an ifconfig eth0 172.16.x.x up command changing the
>interface's IP number from 172.16.y.y. to 172.16.x.x
>If I then do ifconfig the display tells me the address has changed to
>172.16.x.x and the card should be up but I still cannot ping other
>boxes on the network.
>if I reboot and allow the old IP number to be set on the interface it
>works fine.
>is there something else I must do to re activate the card with the new
>address. 
>I know I can change the ifcfg-eth0 file in the
>etc/sysconfig/network-scripts directory and then reboot but I'm trying
>to save the extra reboot.
>
>Thanks for any suggestions
>Sam


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


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