Thank you for all the help so far. I will try to consolidate further
information in this one message.
My small network is working. The set-up includes five machines
a) one Samba file server (Slackware 3.5 kernel 2.0.34)
b) three win95 clients
c) one Linux box (also Slackware 3.5 kernel 2.0.34) which is a 486 with 8MB
RAM
which I am
trying to make into a IP Masq and fax server, from now refered as the Gateway.
I want the three win95 clients to be able surf the net and possibly
send/receive email through
the Gateway. (I will also get them to fax but that's is for later). The
Gateway
can so far connect to
my ISP using minicom and surf the net (including downloading files) with
lynx.�
All five
machines can ping one another, by hostname and by IP address.
At this point, I can get win95 to ping the ISP's dynamic IP address (obtained
from ifconfig command
on the Gateway when on-line), but nothing else on the outside world.
I now suspect the problem lies in win95 DNS configuration. This is the
"Configuring MS Windows 95" section
of the IP-Masquerading HOW-TO
6. Under the 'DNS Configuration' tab, make sure to put in a name for
���� this machine and enter in your official domain name.� If you don't
���� have your own domain, put in the domain of your ISP.� Now, add all
���� of the DNS server that your Linux host uses (usually found in
���� /etc/resolv.conf).� Usually these DNS servers are located at your
���� ISP though you can be running either your own CACHING or
���� Authoritative DNS server on your Linux MASQ server as well.
���� Optionally, you can add any appropriate domain search suffixes as
���� we
I could put the IP addresses of the ISP (from /etc/resolv.conf) for "DNS
server
search order" but I get into trouble with
every name I put as host and domain name. The problem is every time I set DNS
with ny host and domain
name and the system reboots, I could no longer ping the other local computers
by hostname, although
I could still ping by IP address.
What should I do now??
Shaggy
***********************************
Below are my responses to Jarmo's message.
>echo "** Making sure you have forwarding on..."
>echo "1" > /proc/sys/net/ipv4/ip_forward
>echo "1" > /proc/sys/net/ipv4/ip_dynaddr
Above has been done.
cat /proc/sys/net/ipv4/ip_forward�
and
cat /proc/sys/net/ipv4/ip_dynaddr
both yield the output "1" (without quotes).
>ipchains --flush
>ipchains -P forward DENY
>ipchains -A forward -s 192.168.1.0/24 -j MASQ
>
>exit 0
As Steven <[EMAIL PROTECTED]> kindly informed me, I used
the equivalent command for the 2.0.34 kernet, viz. ipfwadm
in /etc/rc.d/rc.local
ipfwadm _f -p deny
ipfwadm -F -a m -S <ip no of win95 machine #1>/32 -D 0.0.0.0/0
ipfwadm -F -a m -S <ip no of win95 machine #2>/32 -D 0.0.0.0/0
ipfwadm -F -a m -S <ip no of win95 machine #3>/32 -D 0.0.0.0/0
Question: do I also need this line below?
ipfwadm -F -l
