I can get the win98 client to access the shared files on the linux box with samba (only with the firewall disabled), but I can't get the win98 client to browse the internet.

I have the DHCP server running and by using WINIPCFG on the win98 machine, the DHCP server issues the correct IP address (otherwise I couldn't access the shared files on the linux box), but when I open the browser on the win98 machine, the page(s) can not be displayed.

Is there a SIMPLE, step by step instruction on how to get the win98 machine to browse the net?

I'm using RH9 with the Kde desktop. I can connect to the internet from the linux box using KPPP.

Is there any software that could this up for me?

Did you give the win-box a proper name-server
and gateway address to look at?



Cheers,
Tink

All settings in the TCP/IP section of win98 are set to auto configure from the linux DHCP server.

The settings of the dhcpd.conf file is :-

ddns-update-style ad-hoc;
subnet 192.168.0.0 netmask 255.255.255.0
{
option broadcast-address 192.168.0.255;
deny bootp;
default-lease-time 86400;
max-lease-time 604800;

option subnet-mask 255.255.255.0;
range 192.168.0.65 192.168.0.250;
option routers 192.168.0.1;
}

The settings for the RH9 network config are :-

unchecked obatin IP address from (pull down box) DHCP
checked static IP addresses
Manual IP address settings:-
IP address 192.168.0.1
Subnet Mask 255.255.255.0
no default gateway

Settings on win98 via WINIPCFG:-

hostname BEDROOM
Broadcast mixed
DHCP Server 192.168.0.1
Subnet mask 255.255.255.0
Default Gateway 192.168.0.1

When I click on 'release' to release the DHCP server, and clicked on 'renew' the linux box DHCP server issues the correct IP addresses.

you've not exaplined your network topology at all... are meant to assume that your linux box is teh gateway?? in which case you will need to check the ip masqaurading you've got setup. this is typically possible to auto configure as part of a firewall, which you should neevr just disable.

I tried the masquerading, with (logged in as root):

route -A POSTROUTING -t nat -s 192.168.0.0/24 -o eth0 -j MASQUERADE

all that happens is than an error '/host/eth0 not found' is displayed

It really sounds like you need to look into iptables scripts for a masquerading firewall.

There seem to be at least three problems...

First you seem to have a firewall on your internal network interface, which is normally not needed for most home users wanting to use linux as a router.

Second you will need to have the MASQERADE working and ip forwarding enabled to access the internet..

Third problem is DNS. Nameservers are required, and can be assigned via DHCP or manually.