Linux-Networking Digest #696, Volume #9 Mon, 28 Dec 98 11:13:29 EST
Contents:
Re: Where's RedHat rc.inet1, rc.inet2 files?? ("Lewis Foti")
Re: Calling On ipfwadm Gurus! :) (Lars Hofhansl)
Re: Where's RedHat rc.inet1, rc.inet2 files?? ("Graham Miller")
DHCPD reports Network not reachable (Floris Jan)
Program to display Linux Xwindows on NT 4 Desktop? ("Jez Tucker")
Linux IP address _and_ port redirection with ipfwadm? (Kevin Kretz)
TELES ISDN card driver needed! ("Gerard A. Wassink")
Re: Some problems related to IP masquerading (Norman Jordan)
Re: dialing up problem[redhat] (Mads Westermann)
Re: dialing up problem[redhat] (Mads Westermann)
Re: Masquerading... should be working, why isn't it? (Giovanni Gigante)
Re: dialing up problem[redhat] (Mads Westermann)
Re: Unidentified network card (Rad Morka)
----------------------------------------------------------------------------
From: "Lewis Foti" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.help,comp.os.linux.questions,comp.os.linux
Subject: Re: Where's RedHat rc.inet1, rc.inet2 files??
Date: Mon, 28 Dec 1998 10:08:35 -0000
On RedHat the directory structure is as follows:
/etc/rc.d
/etc/rc.d/init.d
/etc/rc.d/rc0.d
/etc/rc.d/rc1.d
/etc/rc.d/rc2.d
/etc/rc.d/rc3.d
...
The /etc/rc.d/init.d directory holds all the scripts to start and stop
applications, while the rcX.d directories have symlinks into the init.d
directory which effectively rename the scripts, prefixing them with either
KXX or SXX indicating whether this is a start or stop script. The XX is a
pair of numerals indicating in which order the scripts should be run. For
example in /etc/rc3.d there are the following scripts;
K15postgresql S10network S45pcmcia S85httpd
K20rusersd S11portmap S50inet S85sound
K20rwhod S15nfsfs S55named S91smb.rpmsave
K30sendmail S20random S60lpd S99linuxconf
K55routed S30syslog S60nfs S99local
K70ipfwadm S40atd S70ipfwadm
K87ypbind S40crond S75keytable
S01kerneld S40portmap.rpmsave S85gpm
A long listing of one of the scripts shows the following linking;
[lewisf@sol lewisf]$ ls -l /etc/rc.d/rc3.d/*httpd
lrwxrwxrwx 1 root root 15 Jul 5 11:03
/etc/rc.d/rc3.d/S85httpd -> ../init.d/httpd
Take a look inside the rc.d/rc script for more details.
Hope this helps
regards
Lewis
Vincent wrote in message <[EMAIL PROTECTED]>...
>The Slackware distrubution has the following files for building an
>Intranet:
>
>/etc/HOSTNAME
>/etc/hosts
>/etc/host.conf
>/etc/resolv.conf
>/etc/rc.d/rc.inet1
>/etc/rc.d/rc.inet2.
>
>The RedHat 5.1 distrubution has all of the above, except for:
>
>/etc/resolv.conf
>/etc/rc.d/rc.inet1
>/etc/rc.d/rc.inet2
>
>I cannot find these 3 files anywhere in the RedHat distribution. Where
>would these files be in RedHat 5.1?
>
> Thanks,
> Vincent
>
------------------------------
From: Lars Hofhansl <[EMAIL PROTECTED]>
Subject: Re: Calling On ipfwadm Gurus! :)
Date: Mon, 28 Dec 1998 12:01:53 +0100
Ki-Won Lee wrote:
>
> Hello,
>
> I was not able to get net access all of a sudden after having rebooted my box.
> But I had resolved the problem. I had put in my rc.local these entries:
[...]
> ipfwadm -I -o -a reject -S 0.0.0.0/0 -D <my.ip.address>/32
This is the culprit. What it does is rejecting ALL traffic to your
site. I don't know what you wanted to achieve, but you should either
specify the source address or a port number (on source or destination)
[...]
Cheers,
Lars
--
Legal Warning: Anyone sending me unsolicited/commercial email
WILL be charged a $100 proof-reading fee. See US Code Title 47,
Sec.227(a)(2)(B), Sec.227(b)(1)(C) and Sec.227(b)(3)(C).
Linux grows, see http://counter.li.org/ and register.
------------------------------
From: "Graham Miller" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.help,comp.os.linux.questions,comp.os.linux
Subject: Re: Where's RedHat rc.inet1, rc.inet2 files??
Date: Mon, 28 Dec 1998 17:19:33 +1000
Vincent wrote in message <[EMAIL PROTECTED]>...
>The Slackware distrubution has the following files for building an
>Intranet:
[snip]
>
>The RedHat 5.1 distrubution has all of the above, except for:
>
>/etc/resolv.conf
>/etc/rc.d/rc.inet1
>/etc/rc.d/rc.inet2
>
>I cannot find these 3 files anywhere in the RedHat distribution. Where
>would these files be in RedHat 5.1?
>
/etc/resolv.conf should be there with search and nameserver items
the rc.inet? files are not part of redhat linux. You'd have to say for what
they are used for me to advise the equivalent ones for RH
Greyman
[EMAIL PROTECTED]
------------------------------
From: Floris Jan <[EMAIL PROTECTED]>
Subject: DHCPD reports Network not reachable
Date: Mon, 28 Dec 1998 12:21:41 +0100
==============766E6CBC15672199F6407162
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hello,
I have a problem. I try to set up DHCP on my network by installing dhcpd on my
linux box (RH 5.2). I configured dhcpd for 1 subnet (192.168.1.0 netmask
255.255.255.0) and specified one range (see dhcpd.conf below:)
subnet 192.168.1.0 netmask 255.255.255.0 {
option domain-name "cartoon.nl";
option domain-name-servers 192.168.1.1;
option routers 192.168.1.1;
range 192.168.1.10 192.168.1.200;
default-lease-time 259200;
}
[dhcpd.conf]
When I start dhcpd with the -d option, I get the following output:
[root@silvester /etc]# dhcpd -d
Internet Software Consortium DHCPD $Name: V2-BETA-1-PATCHLEVEL-6 $
Copyright 1995, 1996, 1997, 1998 The Internet Software Consortium.
All rights reserved.
Listening on Socket/eth0/192.168.1.0
Sending on Socket/eth0/192.168.1.0
DHCPDISCOVER from 00:10:4b:e1:76:ec via eth0
DHCPOFFER on 192.168.1.10 to 00:10:4b:e1:76:ec via eth0
sendpkt: Network is unreachable
DHCPDISCOVER from 00:10:4b:e1:76:ec via eth0
DHCPOFFER on 192.168.1.10 to 00:10:4b:e1:76:ec via eth0
sendpkt: Network is unreachable
I can ping and do all other TCP/IP stuff on my network if I use static IP's,
so I guess my network card is working properly. I'll include my kernel route
information table below:
[root@silvester /etc]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
sun4000.casema. * 255.255.255.255 UH 0 0 2 ppp0
192.168.1.0 * 255.255.255.0 U 0 0 6 eth0
127.0.0.0 * 255.0.0.0 U 0 0 4 lo
default sun4000.casema. 0.0.0.0 UG 0 0 59 ppp0
Does anybody know what the solution to my problem could be? Any help is
appreciated.
Greetz
Floris Jan
==============766E6CBC15672199F6407162
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
Hello,
<P>I have a problem. I try to set up DHCP on my network by installing dhcpd
on my linux box (RH 5.2). I configured dhcpd for 1 subnet (192.168.1.0
netmask 255.255.255.0) and specified one range (see dhcpd.conf below:)
<P><TT>subnet 192.168.1.0 netmask 255.255.255.0 {</TT>
<BR><TT> option domain-name
"cartoon.nl";</TT>
<BR><TT> option domain-name-servers
192.168.1.1;</TT>
<BR><TT> option routers 192.168.1.1;</TT>
<BR><TT> range 192.168.1.10
192.168.1.200;</TT>
<BR><TT> default-lease-time 259200;</TT>
<BR><TT>}</TT>
<P> [dhcpd.conf]
<P>When I start dhcpd with the -d option, I get the following output:
<P><TT>[root@silvester /etc]# dhcpd -d</TT>
<BR><TT>Internet Software Consortium DHCPD $Name: V2-BETA-1-PATCHLEVEL-6
$</TT>
<BR><TT>Copyright 1995, 1996, 1997, 1998 The Internet Software Consortium.</TT>
<BR><TT>All rights reserved.</TT>
<BR><TT>Listening on Socket/eth0/192.168.1.0</TT>
<BR><TT>Sending on Socket/eth0/192.168.1.0</TT>
<BR><TT>DHCPDISCOVER from 00:10:4b:e1:76:ec via eth0</TT>
<BR><TT>DHCPOFFER on 192.168.1.10 to 00:10:4b:e1:76:ec via eth0</TT>
<BR><TT>sendpkt: Network is unreachable</TT>
<BR><TT>DHCPDISCOVER from 00:10:4b:e1:76:ec via eth0</TT>
<BR><TT>DHCPOFFER on 192.168.1.10 to 00:10:4b:e1:76:ec via eth0</TT>
<BR><TT>sendpkt: Network is unreachable</TT>
<BR>
<P>I can ping and do all other TCP/IP stuff on my network if I use static
IP's, so I guess my network card is working properly. I'll include my kernel
route information table below:
<P><TT>[root@silvester /etc]# route</TT>
<BR><TT>Kernel IP routing table</TT>
<BR><TT>Destination
Gateway
Genmask Flags Metric
Ref
Use Iface</TT>
<BR><TT>sun4000.casema.
*
255.255.255.255 UH 0
0
2 ppp0</TT>
<BR><TT>192.168.1.0
*
255.255.255.0 U 0
0 6 eth0</TT>
<BR><TT>127.0.0.0
*
255.0.0.0 U
0 0
4 lo</TT>
<BR><TT>default sun4000.casema.
0.0.0.0 UG
0 0 59
ppp0</TT><TT></TT>
<P><TT>Does anybody know what the solution to my problem could be? Any
help is appreciated.</TT><TT></TT>
<P><TT>Greetz</TT>
<BR><TT> Floris Jan</TT></HTML>
==============766E6CBC15672199F6407162==
------------------------------
From: "Jez Tucker" <[EMAIL PROTECTED]>
Crossposted-To:
microsoft.public.windowsnt.apps,microsoft.public.windowsnt.terminalserver.applications
Subject: Program to display Linux Xwindows on NT 4 Desktop?
Date: Mon, 28 Dec 1998 09:36:35 -0000
Hi,
I'm looking for a program that will display the Xwindow output from my
Redhat 4.2 linux box onto my NT 4.0 W/S desktop.
I don't want to do it the other way around (NT on UNIX) as I only have a
mono VGA monitor for the unix box and I need the color one for NT. Doing it
this way, i can keep the mono monitor for a terminal shell and bring up the
xwindows stuff on my PC (preferably using the power of the Matrox Mil' II
card in the PC to disply the screen, rather than the Matrox Mil' I card in
the unix box to display the screen).
If it were free/shareware that'd be even better. I don't really want an
expensive corporate solution.
Any ideas much appreciated,
Jez Tucker
emailto:[EMAIL PROTECTED]
------------------------------
From: Kevin Kretz <[EMAIL PROTECTED]>
Subject: Linux IP address _and_ port redirection with ipfwadm?
Date: Mon, 28 Dec 1998 06:41:53 -0500
I've successfully used ipfwadm to proxy my home network across a
cablemodem.
I now have an additional need: to make a connection to a server
listening on a port not allowed through our company's firewall. I have
a Linux box (RedHat 5.1) on the inside, and I'm connected over an ISDN
dialup through the firewall. I know of a bunch of allowed ports and
would like to connect to the Linux machine on one of those ports, and
have ipfwadm (or another fw/proxy app) redirect it to the actual port on
the actual server I need to make a connection with.
>From what I understand, ipfwadm can redirect a request to a different
_local_ port on the machine running ipfwadm, but not to a different IP
address. Am I wrong?
Thanks in advance - if a response needs to be e-mailed (posting's better
... I've seen other similar questions here) my e-mail is my first name
at my last name dot net.
Kevin Kretz
------------------------------
From: "Gerard A. Wassink" <[EMAIL PROTECTED]>
Subject: TELES ISDN card driver needed!
Date: Mon, 28 Dec 1998 12:11:17 +0100
Hello world :>)
I am looking for a way to get my TELES ISDN card up and running to be
able to connect to the internet from my Linux box. I'm running Red Hat
Linux 5.2.
Can anyone give me some information please?
Tnx in advance,
Gerard A. Wassink
------------------------------
From: Norman Jordan <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: Some problems related to IP masquerading
Date: Mon, 28 Dec 1998 12:13:49 GMT
==============383363D0D46FAF02690DC8AC
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mohd-Hanafiah Abdullah wrote:
> We have set up several Linux client machines behind an IP masquerade server.
> That is, the server is the GATEWAY to the outside world. We are using the
> addresses 192.168.1.x for all the machines within the masquerade. The server
> has two NIC cards and it acts as the DNS and DHCP server for the clients as
> well. Things work fine if the server is up. But as soon as the server goes
> down for any reason, the GATEWAY is no longer available of course, and the
> other machines will have problems running like not being able to:
>
> - open xterm sessions
> - run KDE
> - scan emails in MH
> - and many other things related to X windows
>
> Why do all the above operations need to have the GATEWAY to be up before they
> can run properly? Please help. Thanks.
>
> Napi
Make sure that each computer has itself in its own /etc/hosts file. That could
be the problem.
-- Norman Jordan -- Electrical Engineering Student
The Linux Resource Center
==============383363D0D46FAF02690DC8AC
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
Mohd-Hanafiah Abdullah wrote:
<BLOCKQUOTE TYPE=CITE>We have set up several Linux client machines behind
an IP masquerade server.
<BR>That is, the server is the GATEWAY to the outside world. We are
using the
<BR>addresses 192.168.1.x for all the machines within the masquerade.
The server
<BR>has two NIC cards and it acts as the DNS and DHCP server for the clients
as
<BR>well. Things work fine if the server is up. But as soon
as the server goes
<BR>down for any reason, the GATEWAY is no longer available of course,
and the
<BR>other machines will have problems running like not being able to:
<P> - open xterm sessions
<BR> - run KDE
<BR> - scan emails in MH
<BR> - and many other things related to X windows
<P>Why do all the above operations need to have the GATEWAY to be up before
they
<BR>can run properly? Please help. Thanks.
<P>Napi</BLOCKQUOTE>
Make sure that each computer has itself in its own /etc/hosts file.
That could be the problem.
<P>-- Norman Jordan -- Electrical Engineering Student
<P><A HREF="http://members.home.net/2817628153/">The Linux Resource Center</A>
<BR> </HTML>
==============383363D0D46FAF02690DC8AC==
------------------------------
From: [EMAIL PROTECTED] (Mads Westermann)
Crossposted-To: alt.os.linux
Subject: Re: dialing up problem[redhat]
Date: Mon, 28 Dec 1998 13:26:12 +0100
In article <75utfc$[EMAIL PROTECTED]>, [EMAIL PROTECTED]
says...
> �ڦbinstall redhat5.2 ��, in "Network Configuration",
> there are three choices:
> 1. Keep the current IP configureation
> 2. Reconfigure network now
> 3. Don't set up networking
>
> I choose 3, is it the main factor making me failed in using modem
> to dialing up to school, Since I configure my modem
> in Linuxconf, enter all phone no.,modem port,login name and
> password in PPP configuration and push "test",
> no dialing up sound heard. Please help.
>
Try using minicom to verify that you can speak to the modem manually -
I.e. issue an ATZ command and get an OK as reply.
If you for any reason can't speak to the modem try using minicom's
configure menu (press ctrl-A followed by an O) to disable hardware
handshake. If it's already disabled try to enable it.
Then try to issue the ATZ command again - any luck??
If it works with hardware handshake turned off you're in deep s...
Without hardware handshake your link will run significantly slower. -
That's why I have spent my entire xmas trying to get it to work, with no
luck and no clue as to why it doesn't work.
Rgds.
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Mads Westermann)
Subject: Re: dialing up problem[redhat]
Date: Mon, 28 Dec 1998 13:30:13 +0100
In article <75utfc$[EMAIL PROTECTED]>, [EMAIL PROTECTED]
says...
> �ڦbinstall redhat5.2 ��, in "Network Configuration",
> there are three choices:
> 1. Keep the current IP configureation
> 2. Reconfigure network now
> 3. Don't set up networking
>
> I choose 3, is it the main factor making me failed in using modem
> to dialing up to school, Since I configure my modem
> in Linuxconf, enter all phone no.,modem port,login name and
> password in PPP configuration and push "test",
> no dialing up sound heard. Please help.
>
Try using minicom to verify that you can speak to the modem manually -
I.e. issue an ATZ command and get an OK as reply.
If you for any reason can't speak to the modem try using minicom's
configure menu (press ctrl-A followed by an O) to disable hardware
handshake. If it's already disabled try to enable it.
Then try to issue the ATZ command again - any luck??
If it works with hardware handshake turned off you're in deep s...
Without hardware handshake your link will run significantly slower. -
That's why I have spent my entire xmas trying to get it to work, with no
luck and no clue as to why it doesn't work.
Rgds.
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Giovanni Gigante)
Crossposted-To: casema.linux
Subject: Re: Masquerading... should be working, why isn't it?
Date: Mon, 28 Dec 1998 12:35:41 GMT
On Thu, 24 Dec 1998 18:23:44 -0600, Philip Wall / Wild Card
<[EMAIL PROTECTED]> wrote:
>Jasper Janssen wrote:
>>
>> Hi.
>>
>> I've done everything I and the faqs/howto's could think of, and still
>> it won't work.
After a lot of despair, I have discovered that the FAQ does not
mention a detail: you have to enable IPV4 forwarding, which is
usually disabled at boot by default.
On redhat 5.2, go to /etc/sysconfig, in the network (or was it
networking?) file there is a line like "IPV4_FORWARDING=off",
modify that.
Giovanni
------------------------------
From: [EMAIL PROTECTED] (Mads Westermann)
Crossposted-To: alt.os.linux
Subject: Re: dialing up problem[redhat]
Date: Mon, 28 Dec 1998 12:55:18 +0100
In article <75utfc$[EMAIL PROTECTED]>, [EMAIL PROTECTED]
says...
> �ڦbinstall redhat5.2 ��, in "Network Configuration",
> there are three choices:
> 1. Keep the current IP configureation
> 2. Reconfigure network now
> 3. Don't set up networking
>
> I choose 3, is it the main factor making me failed in using modem
> to dialing up to school, Since I configure my modem
> in Linuxconf, enter all phone no.,modem port,login name and
> password in PPP configuration and push "test",
> no dialing up sound heard. Please help.
>
Try using minicom to verify that you can speak to the modem manually -
I.e. issue an ATZ command and get an OK as reply.
If you for any reason can't speak to the modem try using minicom's
configure menu (press ctrl-A followed by an O) to disable hardware
handshake. If it's already disabled try to enable it.
Then try to issue the ATZ command again - any luck??
If it works with hardware handshake turned off you're in deep s...
Without hardware handshake your link will run significantly slower. -
That's why I have spent my entire xmas trying to get it to work, with no
luck and no clue as to why it doesn't work.
Rgds.
[EMAIL PROTECTED]
------------------------------
Crossposted-To: comp.os.linux.questions
From: Rad Morka <[EMAIL PROTECTED]>
Subject: Re: Unidentified network card
Date: Mon, 28 Dec 1998 14:30:02 GMT
>
> P.S. irq=10 io=0x320 is set by the jumpers
> Tried the modules: 8390.o and ne.o but they doesn't seem to work.
>
make sure that you are specifying those settings during bootup as
parameters instead of hoping for autodetect to work
if that doesn't work you can try to build a kernel with all the drivers
compiled in, and hope that one of them works, then remove the unnecassary
ones.
rad
------------------------------
** 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
******************************
