Ed Jaeger wrote:
> On my system diald uses 192.168.xxx.2 when it comes up - try giving your
> win95 box a different IP, like 192.168.0.10...
>
> Nikolopoulos Vasilis wrote:
> >
> > Hello linux-diald users
> >
> > I have a small network in my home of two PC. One runs Linux and the
> > other runs win95
> >
> > I use the private class C ip 192.168.0.1 for the Linux and 0.2 for the
> > windows. I also use 192.168.0.1 as my gateway in win95. I run diald on
I have the same type of setup, Win95 box and Linux Box (Suse 5.1). My Linux
box is the gateway to the internet via apache as a proxy server from the win95
box. But to get this to work. First, there must be a "/etc/networks" file.
This must list all the hosts on your network and their IP addresses. The
first address (loopback 127.0.0.0) and then the next entries (complete with
domain name) works great. I also use the private class C ip but 1.1 for linux
and 1.3 for win95 (I plan to add 1.2 for os/2 in the near future:-). Also,
you should have a "/etc/hosts" which again lists the addresses and complete
names of the hosts along with an alias for each one. On the win95 machine,
there are also some files that need to be configured to allow tcpip to work.
I've had diald working here for about a year now and both machines can access
the internet with no problem. On the win95 box, you'll (once you get your
network working) have to set up your browsers to look to your linux box as a
proxy server (very easy whether it be netscape or ie).
Also, I did also set up a cached name server on my linux box to help prevent
"nuisance dialouts". This was accomplished by setting the linux box up first
in the search list. There are also some filters and delays that were needed
to be changed, but it's been so long, I don't remember exactly which ones:-(
One more thing, instead of setting diald to come up when you first boot up,
I've found it better to set it up in my root crontab to launch at a particular
time. (also shutdown at a particular time as well since I do run a dual
system on my linux box (os2 and linux)). This fell right in line with setting
up a schedule to fetch and send any mail as well:-).
I also did a couple of changes to the default connect script that is shipped
with diald. This was done because my better half wanted to hear the modem
during the day but not at night:-)
BTW, when you set up win95 for a intranet, tcpip alone will not suffice, you
will probably need to add the capability of the netbios protocol (especially
if you use samba and want to access drives/devices on the linux box).
I hope some of this helps:-)
cya l8r
Leon McClatchey
mailto:[EMAIL PROTECTED]
Linux User 78912 (Linux Box)
$3,000,000
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
