Intranet plus cable connection.

I have a main Linux computer with two ethernet cards. One card is
conected to the Internet via a cable modem. This is all functional.
The second card is physically connected to a Windows 98SE computer via
an ethernet patch cord. The Windows box also has an ethernet card of
course. It is the Windows box that is the new player in my
configuration. So the physical circuit is Windows computer, patch
cord, Linux computer,short patch cord, cable modem and Internet. At
this point Linux autoconfigures the cable connection via DHCPCD. The
other connection is not yet configured in software.

I want to set things up so that the Windows computer can access the
Internet via the same cable connection through the Linux box.

It would be nice, but not essential, if the Windows computer could
also access my Linux computer directly via Apache.

The OS is Slackware 9.1.

Two questions:

Is the above described lash up sufficient or do I need an external
router box in the circuit somewhere?

What is an up-to-date book or HOWTO to guide me thorugh the
configuration process?

I have two O'Reilly books, one by Olaf Kirch on Linux networking and
another on TCPIP in general. However they both have pub dates around
1996. I am looking for something a bit more up to date. Also, for this
kind of lashup which of the many howtos should I be looking at?

All replies appreciated.

John Culleton

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Is the above described lash up sufficient or do I need an external
> router box in the circuit somewhere?

you need a crossover cable between your linux box and your w98 box
otherwise your tx will go to your tx as opposed to your rx. in other
words, both machines will be talking but neither listening. if you
use a crossover cable, you don't need a hub or switch to make this
work.

on linux, enable forwarding (routing) between interfaces, and
configure your inside interface like this (outside will use DHCP from
ISP):

ifconfig 192.168.0.1 netmask 255.255.255.0

and configure your w98 interface with an ip address of 192.168.0.2
subnet mask 255.255.255.0 and with a gateway of 192.168.0.1. it can
use the DNS servers from your ISP.

ping each computer from the other to ensure IP connectivity. then,
from w98, ping a server (using IP address) on the internet that you
know isn't quenching ICMP echo's. if this works, ping same server
using DNS name (host.domain.com). if these work, you are good to go.

good luck
oliver




-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQB9DcrcoUT0UavXJEQL5BwCgo8VH6OHMT1unHVXG6FoFbT 2wTCUAn2C2
bxnD17WqCPeg7NYdu9hCOMmQ
=2rhj
-----END PGP SIGNATURE-----

"Oliver O'Boyle" <(E-Mail Removed)> wrote in message news:<VrHTb.6045$(E-Mail Removed)> ...
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > Is the above described lash up sufficient or do I need an external
> > router box in the circuit somewhere?
>
> you need a crossover cable between your linux box and your w98 box
> otherwise your tx will go to your tx as opposed to your rx. in other
> words, both machines will be talking but neither listening. if you
> use a crossover cable, you don't need a hub or switch to make this
> work.
>
The cable is marked crossover.
> on linux, enable forwarding (routing) between interfaces,

----using what command to enable forwarding?

and
> configure your inside interface like this (outside will use DHCP from
> ISP):
>
> ifconfig 192.168.0.1 netmask 255.255.255.0
>
---did this, specifying eth0 for the card.

> and configure your w98 interface with an ip address of 192.168.0.2
> subnet mask 255.255.255.0 and with a gateway of 192.168.0.1. it can
> use the DNS servers from your ISP.
>
---Is this something I configure on the Win box itself? Or do I add it
to /etc/hosts?


Thanks for your help so far!

John Culleton

"Oliver O'Boyle" <(E-Mail Removed)> wrote in message news:<VrHTb.6045$(E-Mail Removed)> ...
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> you need a crossover cable between your linux box and your w98 box
> otherwise your tx will go to your tx as opposed to your rx. in other
> words, both machines will be talking but neither listening. if you
> use a crossover cable, you don't need a hub or switch to make this
> work.
>
Aha! I think I have a straight through cable. So it's back to Radio
Shack to get the correct cable.

> on linux, enable forwarding (routing) between interfaces,

Via the route command? Another command?

and
> configure your inside interface like this (outside will use DHCP from
> ISP):
>
> ifconfig 192.168.0.1 netmask 255.255.255.0
>

I suspect I would need to specify the inner card by addiing (in my
case) eth0 to the command. (eth1 is already taken for the internet
connection.) Am I right?

> and configure your w98 interface with an ip address of 192.168.0.2
> subnet mask 255.255.255.0 and with a gateway of 192.168.0.1. it can
> use the DNS servers from your ISP.

Again, which command should I use?
>
> ping each computer from the other to ensure IP connectivity. then,
> from w98, ping a server (using IP address) on the internet that you
> know isn't quenching ICMP echo's. if this works, ping same server
> using DNS name (host.domain.com). if these work, you are good to go.

Will do after the above is straightened out.

Thanks!

John C.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> > on linux, enable forwarding (routing) between interfaces,

there are probably 3 ways, one of which is the GUI (linuxconf
depending on what distro you are using, or otherwise whatever network
control panel GUI tool is available to you) tool that changes the
file(s) used in the other two ways.

the second way (though i've just been told that this way is
deprecated in favour of the third way) is to change the
/etc/sysconfig/network file so that the line Forward_IPV4=yes is
in it.

And if you look up what this does, all it does is stick a 1 in
/proc/sys/net/ipv4/ip_forward, which is the third way. (there may be
another way as well depending on the distro and release you have but
one of these should do it for you).

> > ifconfig 192.168.0.1 netmask 255.255.255.0
>
> I suspect I would need to specify the inner card by addiing (in my
> case) eth0 to the command. (eth1 is already taken for the internet
> connection.) Am I right?
>

yes, sorry I wasn't clear on that.

> > and configure your w98 interface with an ip address of
> > 192.168.0.2 subnet mask 255.255.255.0 and with a gateway of
> > 192.168.0.1. it can use the DNS servers from your ISP.
>
> Again, which command should I use?
> >

go to your control panel and double click on the Networks icon. it
will present you with all the adapters and modems in your w98
machine. locate your ethernet card's TCP/IP entry and configure it.
you only need to enter the ip address/mask, and maybe DNS servers if
you want. don't bother with the other stuff. you can check the status
of your card with the winipcfg command (make sure the card is in the
drop down box to get the correct info).

> > ping each computer from the other to ensure IP connectivity.
> > then, from w98, ping a server (using IP address) on the internet
> > that you know isn't quenching ICMP echo's. if this works, ping
> > same server using DNS name (host.domain.com). if these work, you
> > are good to go.
>
> Will do after the above is straightened out.
>
> Thanks!
>

np, good luck.

oliver

> John C.

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQB/lX7coUT0UavXJEQI8QwCfaw1AgWBZOlTPLKNhXAI2M6VEKfgAo IR8
OVNlNsvAecpo2oLHYnzBbULi
=i5pV
-----END PGP SIGNATURE-----

(E-Mail Removed) (John Culleton) wrote in message news:<(E-Mail Removed) om>...
> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message news:<VrHTb.6045$(E-Mail Removed)> ...
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> >
> >
> > you need a crossover cable between your linux box and your w98 box
> > otherwise your tx will go to your tx as opposed to your rx. in other
> > words, both machines will be talking but neither listening. if you
> > use a crossover cable, you don't need a hub or switch to make this
> > work.
> >
> Aha! I think I have a straight through cable. So it's back to Radio
> Shack to get the correct cable.
>

This post is superceded by the post next previous to it in time. Sorry.

John Culleton wrote:
> This post is superceded by the post next previous to it in time. Sorry.

FWIW, does Your newsreader know the "cancel" option...?


Just a thought, Jack.

--
----------------------------------------------------------------------
My personal reading of the string "MicroSoft" expands to "NanoWeak"...

"Oliver O'Boyle" <(E-Mail Removed)> wrote in message news:<XDRTb.6976$(E-Mail Removed)> ...
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > > on linux, enable forwarding (routing) between interfaces,
>
> there are probably 3 ways, one of which is the GUI (linuxconf
> depending on what distro you are using, or otherwise whatever network
> control panel GUI tool is available to you) tool that changes the
> file(s) used in the other two ways.
>
> the second way (though i've just been told that this way is
> deprecated in favour of the third way) is to change the
> /etc/sysconfig/network file so that the line Forward_IPV4=yes is
> in it.
>
> And if you look up what this does, all it does is stick a 1 in
> /proc/sys/net/ipv4/ip_forward, which is the third way. (there may be
> another way as well depending on the distro and release you have but
> one of these should do it for you).

I have everything working but the pass through to the internet. The
value in /proc/sys/net/ipv4/ip_forward was 1 already.

On the windows machine I assigned the same DNS servers as I had in
/etc/resolv.conf. I also assigned 192.168.0.1 as the third DNS choice.
The windows machine can contact the Apache server running on the
Linux machine but it cannot connect elsewhere.

I wnt to /etc/rc.d and rooted around until a found the statement
/etc/rc.d/rc.ipv_forward start
I executed that statement. Still no help.

I note that I have a named process running. Could this be messing
something up?

Thanks for your help to date. I feel I am very close to final success.

John Culleton

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

john,

sorry to take so long to get back.

can you ping anything outside your network using just an IP address?
try pinging your firewall's outside IP. then its gateway (your ISP).
then something beyond that.


"John Culleton" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message
> news:<XDRTb.6976$(E-Mail Removed)> ...
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > > > on linux, enable forwarding (routing) between interfaces,
> >
> > there are probably 3 ways, one of which is the GUI (linuxconf
> > depending on what distro you are using, or otherwise whatever
> > network control panel GUI tool is available to you) tool that
> > changes the file(s) used in the other two ways.
> >
> > the second way (though i've just been told that this way is
> > deprecated in favour of the third way) is to change the
> > /etc/sysconfig/network file so that the line Forward_IPV4=yes
> > is in it.
> >
> > And if you look up what this does, all it does is stick a 1 in
> > /proc/sys/net/ipv4/ip_forward, which is the third way. (there may
> > be another way as well depending on the distro and release you
> > have but one of these should do it for you).
>
> I have everything working but the pass through to the internet. The
> value in /proc/sys/net/ipv4/ip_forward was 1 already.
>
> On the windows machine I assigned the same DNS servers as I had in
> /etc/resolv.conf. I also assigned 192.168.0.1 as the third DNS
> choice.
> The windows machine can contact the Apache server running on the
> Linux machine but it cannot connect elsewhere.
>
> I wnt to /etc/rc.d and rooted around until a found the statement
> /etc/rc.d/rc.ipv_forward start
> I executed that statement. Still no help.
>
> I note that I have a named process running. Could this be messing
> something up?
>
> Thanks for your help to date. I feel I am very close to final
> success.
>
> John Culleton

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQCNKB7coUT0UavXJEQLfaACfUutZlLXweacnhqX9jmgrxI ViJAgAoOlY
gUsX/Rm3yisyA2Pcaaq9cT2B
=MgRV
-----END PGP SIGNATURE-----

"Oliver O'Boyle" <(E-Mail Removed)> wrote in message news:<hSHUb.25435$(E-Mail Removed) m>...
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> john,
>
> sorry to take so long to get back.

Not a problem! I appreciate your help.
>
> can you ping anything outside your network using just an IP address?
> try pinging your firewall's outside IP. then its gateway (your ISP).
> then something beyond that.

Using a Linux CDR in my satellite machine I can only ping the local
address of my main computer, i.e. 192.168.0.1 When I try to ping the
dynamically assigned external address of my main computer 67.20.162.xx
the error message is "network is unreachable." Obviously I can't get
to my ISP either.

If I run my satellite computer under Win98 I get similar results. It
can access the Apache server on my main machine but can't reach the
internet.

Next I will deactivate my named process and reboot. Perhaps that is
getting in the way somehow.

Thanks again for your help. Anyone else who wants to chime in please
do so.

Joh Culleton