Linux-Networking Digest #56, Volume #10 Sat, 30 Jan 99 14:13:39 EST
Contents:
Re: Problem with ethernet startup: SIOCSADDR etc.(SOLVED) (Matthew Callaway)
Compaq Convenience Base NIC (Phil)
RH5.2 multiple network cards, telnetd + ftpd slow to respond (Bill Rausch)
PPP package source (Josh Gentry)
Re: lessons learned while setting up masquerading (Matt Kressel)
Re: Slow minicom and seyon? (Clifford Kite)
Re: Problem w/ DEC205 (ewrk3) net card - eth0 (probe ok but not ping) ("Glenn
Eldridge")
PPP Dial-In Server Documentation ? ("David Travers")
Free Recipes <Gourmet & Chili> ([EMAIL PROTECTED])
dialin server and chap (Josh Gentry)
Re: DHCP Server setup - Complete rookie need help please (Stephen Carville)
Re: Redhat 5.2's Samba + Windows 2000 Pro (build 1965) DOES NOT NETWORK (Steve Russo)
----------------------------------------------------------------------------
From: Matthew Callaway <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Problem with ethernet startup: SIOCSADDR etc.(SOLVED)
Date: Fri, 29 Jan 1999 13:53:24 -0600
Well, it turns out I wasn't doing anything wrong after all. It turns out that
I'm just a little bit stupid, and had a little bit of bad luck. First, why I'm
dumb. Earlier in this thread, I claimed that my card was ISA, then I changed my
mind after looking in my case. I saw that it was PCI. "Huh, I thought. How
could I have messed that up?" Well, it IS and ISA card. I looked at my sound
card at a wierd angle and thought it was the net card. Okay, so I'm dumb. But
my card in fact is ISA. So, that still doesn't solve the problem.
Turns out that this Kingston NE2000 ISA card is used. I got it from a buddy of
mine for a great price (free). He neglected to mention at the time that he had
used some software to change the port address on the card from something normal
like 0x300 or 0x320 to 0x2c0. He'd done this to resolve a conflict that he was
having with an old S3 video card bug. Anyway, I had to go into the ne.c source
code and add 0x2c0 to the list of available ports to scan. Then it all worked
just fine.
Whew. Mystery solved.
------------------------------
Date: Sat, 30 Jan 1999 10:57:06 -0700
From: Phil <[EMAIL PROTECTED]>
Subject: Compaq Convenience Base NIC
I am trying to config a Compaq Armada 4120 laptop with a Compaq
convenience base containing a NIC.
I have been unsuccessful so far. When the machine boots, I see the
following two lines:
modprobe: no dependency information for modules:
"/lib/module/2.0.36/net/tlab.o"
Delaying eth0 initialization
When the system halts, the same modprobe line above shows up followed
by:
eth0: unknown interface
I am guessing at the driver since RedHat doesn't support the Compaq
NIC's. I found the link between the Compaq and the "tlan" driver on
another distribution site. I don't know the base address or interupt
for the NIC in the base - yet, otherwise I would try the "ne" driver.
Windows which is also installed on the machine does not report either
the address or its irq, but it does work.
Any help is appreciated,
-Phil
------------------------------
From: [EMAIL PROTECTED] (Bill Rausch)
Subject: RH5.2 multiple network cards, telnetd + ftpd slow to respond
Date: Fri, 29 Jan 1999 11:27:28 -0800
I've installed RH 5.2 on a Dell PII/300 box. It has two ethernet cards (1
10BaseT and 1 100baseT) and a token ring card. (On the 100baseT net is
another Dell PII/300 box with identical hardware running SW 3.4. It was
previously set up by someone else who is no longer available. It will have
a newer Linux installed on it too eventually.) The 10baseT network
contains miscellaneous other Unix boxes. The token ring has PCs and AIX
workstations and other.
Everything works, but...
Telnet or ftp from the RH box to anywhere works fine.
Telnet or ftp to the RH box sort of works. From the SW box, everything is
fine. From the token ring machines, the connect message comes back
immediately but the actual login prompt takes forever to appear (over a
minute). Once it finally appears however, everything works just fine.
What the heck is going on? I assume it is something about opening a
socket back to the client but what? The SW 3.4 machine does not have this
problem. netstat on the two machines shows identical output. ifconfig
shows identical output
Traceroute from the RH box to a token ring AIX box tried to go down the
10baseT ethernet path instead of the token ring like it should have. I
fixed this by hardcoding the network startup script to do the tr device
before the eth devices. It still didn't help the telnet or ftp daemons
though.
I assume I need to do something with routing but I'm not enough of an
expert to figure it out. All of my previous experience with UNIX systems
has only involved a single network card per host.
TIA, Bill
--
Bill Rausch
bill at numerical dot com
UNIX, Mac, Windows software development
------------------------------
From: [EMAIL PROTECTED] (Josh Gentry)
Subject: PPP package source
Date: Sat, 30 Jan 1999 09:53:50 -0800
Is there a PPP homepage or similar resource?
Josh
*** Posted from RemarQ - http://www.remarq.com - Discussions Start Here (tm) ***
------------------------------
Crossposted-To: comp.os.linux
From: Matt Kressel <[EMAIL PROTECTED]>
Subject: Re: lessons learned while setting up masquerading
Date: Fri, 29 Jan 1999 17:58:56 GMT
mike schmelzer wrote:
>
> I am pleased to report that I finally got masquerading
> to work last night at 23:55 EST. I want to thank everybody
> who helped with all my questions.
>
> In a feeble attempt to repay my karmic debt,
> here is a brief list of some of the stuff I learned
> along the way. I hope it helps the next poor bastard.
>
> Some of this advice may be RedHat specific,
> and some may be RedHat 5.1 specific. YMMV.
>
> 1. Disable PnP on your cards. Hand set the IRQs and addresses.
> 2. Cycle the power on your machine after changing card settings.
> 3. The kernel . . . .
> Linux version 2.0.34 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #1 Fri May 8
>16:05:57 EDT 1998
> . . . does contain masquerade support.
> 4. Don't try to tell the system which card to be eth0
> and which to be eth1 on bootup. I tried all kinds
> of boot-time options, and they were all ignored.
> The card with the lower MAC got eth0, end of story.
> 5. The config files for the cards can be found at
> /etc/sysconfig/network-scripts/ifcfg-eth?
> The format of the files should be easy enough to suss out.
> 6. Make sure that forwarding is turned on.
> Set FORWARD_IPV4=yes in
> /etc/sysconfig/network
> Doing this puts a value of 1 in the file
> /proc/sys/net/ipv4/ip_forward
> Alternatively, you can echo a "1" into the file by hand.
> (That's a "one" not an "ell" but I think any non-zero works.)
> 7. ifconfig, route, and ipfwadm work pretty much as advertised
> in the masquerading mini-HOWTO
> 8. Be persistent. Nothing is ever easy the first time you
> do it, no matter how simple it all seems in retrospect.
>
> Alright, you poor bastard, get to it! Good luck!
> --
I would like to applaud this person for doing this. You see, many
questions on this group are answered over and over. Sometimes the
HOWTOs are either too generic or out of date to be of help. We as users
of Linux should post our efforts in the manner above so that a simple
search of dejanews could show us all the specific info we need to know.
I realize that this is not always feasible, but its worth a try.
Anyone listening have some fla^H^H^H opinions ??
-Matt
--
Matthew O. Kressel | INTERNET: [EMAIL PROTECTED]
+--------- Northrop Grumman Corporation, Bethpage, NY ---------+
+--------- TEL: (516) 346-9101 FAX: (516) 346-9740 ------------+
------------------------------
From: [EMAIL PROTECTED] (Clifford Kite)
Subject: Re: Slow minicom and seyon?
Date: 30 Jan 1999 12:06:21 -0600
Mungert ([EMAIL PROTECTED]) wrote:
: I have a Tashika 56K IDE Voice/Fax/Data Modem. Kernel 2.0.36.
: When I use minicom or seyon to make a connection to my
: ISP. The login prompt is very slow; it takes about 5-10 seconds for
: the text I type to appear on the terminal prompt. The result is a timeout
: and thus no login.
: Could this be a modem problem; it works fine doing the same thing in
: WinDOZE, would you credit it? Or have I not set the modem, minicom or seyon
: up correctly. My modem uses /dev/cua2. I used the slackware 3.4 setup
: program to configure the modem for me. I have not changed the default
: setting on minicom or seyon. My internet provider claims to support ppp Unix
It's very likely that the IRQ configured for Linux is not the IRQ that
the modem actually uses. The IRQ is set with setserial at bootup time,
likely in /etc/rc.d/rc.serial . Find out what IRQ the modem actually
uses and configure /dev/cua2 to use it with setserial at bootup. Oh,
and you need to start using /dev/ttyS2 rather than /dev/cua2 which the
powers-that-be will banish someday.
--
Clifford Kite <[EMAIL PROTECTED]> Not a guru. (tm)
/* Editing with vi is a lot better than using a huge swiss army knife. */
------------------------------
From: "Glenn Eldridge" <[EMAIL PROTECTED]>
Subject: Re: Problem w/ DEC205 (ewrk3) net card - eth0 (probe ok but not ping)
Date: Sat, 30 Jan 1999 10:04:34 -0800
Problem solved!
This is a bit embarrassing... The Linux box was configured correctly. But,
I found that PC I was using to test connectivity had an incorrect IP
address.
For those reading this that are looking for hints read the below:
If you are not using routing and want all PCs to have connectivity, make
sure that the netmask is the same for all PCs.
Then make sure that you match the IP address with the netmask. Example: if
you have 255.255.255.0 as a netmask, your IP net address on all PCs in this
non-routed network will need to have the same starting number (I believe
called octets). This is very important!
Further example...
The problem was this:
Linux netmask - 255.255.255.0
Linux IP address - 192.168.1.1
2nd PC netmask - 255.255.255.0
2nd PC IP address - 192.168.2.1 (this address should have been 192.168.1.2)
I hope this helps someone!
Thanks to Malware and Jon Niehof for your assistance! Your questions helped
my research...
Glenn
Malware wrote in message <[EMAIL PROTECTED]>...
>Hi Glenn,
>
>you wrote:
>> Thanks for the reply. A lot of my frustraction is the HOWTO docs are
not
>> helping. I've tried "route add ..." many times and I also checked
>> /etc/sysconfig/network to verify it's insertion. I'm thinking that one
of
>
>This way we are stuck. Plz post the output of "ifconfig -n eth0" and
>"route -n".
>
>
>Malware
------------------------------
From: "David Travers" <[EMAIL PROTECTED]>
Subject: PPP Dial-In Server Documentation ?
Date: Fri, 29 Jan 1999 23:14:24 -0000
I am trying my best to setup a PPP server that will allow Windows 95/NT
clients to dial into our network via a Linux box.
I have read all the information on the PPP Howto's and other documentation
have been able to
create a PPP client when which can connect to an ISP.
However I cannot get the PPP server to work. The modems will auto anwser on
the two serial ports, handshaking does occur but the PP connection just
fails and the Linux modems hangs up.
Could anyone suggest web sites relating to PPP servers on Linux or any tips
on the steps that are required to get a PPP server to work.
Documentation should preferably include detailed specs on complier
directives if recompilis is reuired of the kernel or other packages. Sample
of configuration files would be nice
I have Suse 5.2 (kernel 2.0.34) compiled to support PPP, IP Firewall, IP
Masquerading and IP Forwarding, 2 US Robotics 33.6 Fax Modems and the server
is currently an AMD K6 233Mhz with 96MB Ram (using server for other tasks as
well).
Thanks in advance.
David Travers
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To:
comp.lang.javascript,comp.lang.perl.misc,comp.os.linux.advocacy,comp.os.linux.hardware,comp.os.linux.misc,comp.os.linux.setup,comp.publish.cdrom.hardware,comp.sys.amiga.misc,comp.sys.ibm.pc.games.action
Subject: Free Recipes <Gourmet & Chili>
Date: Saturday, 30 Jan 1999 12:59:06 -0600
http://www.knownet.net/users/dietden/
------------------------------
From: [EMAIL PROTECTED] (Josh Gentry)
Subject: dialin server and chap
Date: Sat, 30 Jan 1999 09:52:25 -0800
For every server I have seen set up to use PAP by including the "require-
pap" option, the options fill also
includes the option "refuse-chap." I have not seen an explanation of why
the "refuse-chap" option is
neccessary. Will anyone explain?
Josh
*** Posted from RemarQ - http://www.remarq.com - Discussions Start Here (tm) ***
------------------------------
From: Stephen Carville <[EMAIL PROTECTED]>
Subject: Re: DHCP Server setup - Complete rookie need help please
Date: 30 Jan 1999 18:26:18 GMT
First, be sure the DHCP packages is installed: "rpm -q dhcp" It is not
installed by default. If dhcp is not installed load the CD-ROM and install
it. The packages is called "dhcp-2.0b1pl6-2.i386.rpm" or something close
to that.
Once installed there will be a script /etc/rc.d/init.d/dhcpd. This is the
best way to start dhcp on a redhat system.
Just "su" to root and type:
"/etc/rc.d/init.d/dhcpd restart"
and let the Redhat script do the dirty work for you. You can also tell the
script to "stop" or "start" the server but unless you are sure of the state
of dhcp, it is better to use the restart option.
The installation also creates a couple of symlinks
/etc/rc.d/rc3.d/S65dhcpd
/etc/rc.d/rc5.d/S65dhcpd
These tell Linux to start he service on boot up in runlevels 3 (network and
console) and 5 (network and X).
The above assumes you have the /etc/dhcpd.conf file setup. If not, dhcpd
will halt with an error.
BTW, you don't; need to recompile the kernel to setup dhcp. In fact, I
have been setting up Linux servers for about two yaers now using the Redhat
distro and have never _had_ to recompile a kernel.
GV Morgon wrote:
>
> First off, let me state that my Linux experience is basically zip, and I've
> been "assigned" the task of deploying a DHCP server. I've gotten Redhat
> 5.2, kernel 2.0.36 installed onto a 486/66 8 meg RAM, 500Meg HDD. What I
> need to know is what exactly do I have to do to get this machine to act as a
> DHCP server for Windows 95/98/NT clients operating on a network shared with
> Netware 4.11 servers? I checked out "man dhcpd" and it gave some
> interresting info, but when I type "dhcpd" at the command prompt nothing
> happens. "Command not found" error. When I look in the /sbin directory
> there is no dhcpd program, but when I installed under the RedHat program, I
> told it to install the dhcp daemon. So where did it go? Did it not
> install? According to the printed install manual from RedHat the dhcp
> daemon is version 2.0b1pl6. I noticed that in the /sbin directory the
> dhcpcd program is in there, but when I type "dhcpcd" at the prompt, I get a
> "Command not found" error. For that matter I cant even get the games to
> load . I understand that Linux is case sensitive, but I can't get any of
> the programs to execute.
>
> The game plan here is to put to use these old 486 machines we have as DHCP
> servers instead of tossing into the dumpster. Currently we are using
> Windows NT 4 server on Toshiba 440 and 490 laptops to simply act as a DHCP
> server at various office locations. Waste of perfectly good laptops for
> such a mediocre task. For some corporate reason, using the DHCP server
> capabilites of the routers is not an option (a different department manages
> them and refuses to allow it).
>
> While I am well seasoned at dealing with NT machines, I have no
> configuration experience with Linux machines. Recompiling the kernel was
> something that never came to my mind in the past in dealing with NT
> machines. But I like the idea of having that capability to expedite the
> time it takes to deploy security and bug fixes. But if I can't get a game
> to even run under Linux when I'm looking at the file in front of me, I
> wonder how badly I can screw up a recompile :)
>
> As an aside, the GUI for Novell 5 and Xwindows sure do look a lot
> alike...although Xwindows is infinitely faster :)
>
> I would like to extend some thank you's in advance to all who help me on
> this.
>
> Glenn V. Morgon
--
Stephen Carville
[EMAIL PROTECTED]
====================================================
Management: The art of hiring intelligent, skilled individuals and then
ignoring their advice.
------------------------------
From: [EMAIL PROTECTED] (Steve Russo)
Crossposted-To:
microsoft.public.winnt50.beta.networking,microsoft.public.winnt50.beta.networking.protocols,microsoft.public.winnt50.beta.general,linux.samba,linux.redhat.misc,comp.protocols.smb
Subject: Re: Redhat 5.2's Samba + Windows 2000 Pro (build 1965) DOES NOT NETWORK
Date: Fri, 29 Jan 1999 20:51:22 GMT
Yep, just make sure you have
encrypt passwords = yes
in your /etc/smb.conf file and you should be set. Here is a quick copy
of mine if you would like.
Also!!!!!!! Remember to export your /etc/passwd file to
/etc/smbpasswd by running this command.
cat /etc/passwd | mksmbpasswd.sh > /etc/smbpasswd
##### /etc/smb.conf CUT HERE ##################################
workgroup = MYGROUP
wins server = WINSRV
domain controller =WINSRV
domain master = no
os level = 0
#This is for servers with two network cards or IP's. Take this out if
#you have a machine with only a single IP.
interfaces = 206.8.30.10/2 192.168.0.30/24
[global]
encrypt passwords = yes
mangle case = yes
mangled names = yes
default case = lower
case sensitive = no
preserve case = yes
short preserve case = yes
[Ftp]
comment = Share For FTP Files
path = /home/ftp
public = yes
only guest = no
writable = yes
printable = no
[WWW]
comment = Share For WWW Files
path = /home/httpd/html
public = yes
only guest = no
writable = yes
printable = no
valid users = www
######## Done /etc/smb.conf #################
On 29 Jan 1999 15:28:20 -0500, Greg Menke <[EMAIL PROTECTED]> wrote:
>"Slam" <[EMAIL PROTECTED]> writes:
>
>> So you're saying that I must upgrade to Samba v2.0 for Win2k Pro to see the
>> shares?
>>
>>
>> James Nord <[EMAIL PROTECTED]> wrote in article
>> <[EMAIL PROTECTED]>...
>> > Slam wrote:
>> > >
>> > > Should I upgrade to Samba 2.0? Is it Windows 2000 compatible?
>> >
>> > I have, works fine although NT5 *refuses* to send plain text passwords
>> > even after configuring it to do so.
>> >
>> > /James
>> >
>
>I think 1.9 will do encrypted passwords, so it should work. I think its
>the same issue as 95/98/NT password encryption. The man pages and help
>files discuss password encryption issues- and there are references to
>it on the Samba website.
>
>Gregm
------------------------------
** 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
******************************
