just wanted to make sure (netmasking, IP addrs, and masquarading)

I am connected to the internet from my machine, hostname HomeRouter,
through DSL modem, ppp0. I am doing masquarading and nat. HomeRouter has
two NICs: eth0 takes in the connection from ppp0, and eth1 is connected
to a switch. My internal home machine, hostname Home1, has it's eth0
connected to the switch. Pictorially, it is like this:


----------- -------
|HomeRouter| |Home1|
~~>pp0---->eth0,eth1---->Switch--------eth0
|__________| | |_____|
|
|__eth0(Home2)


The HomeRouter has (the following is from my /etc/network/interfaces file):
auto eth0
iface eth0 inet static
address 192.168.1.0
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.25

... and ....
auto eth1
iface eth1 inet static
address 192.168.0.2
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255


My internal machine, Home1, is running Win98, and has been given:
IP: 192.168.0.10
netmask: 255.255.255.0
broadcast: 192.168.0.255
gateway: 192.168.0.2
and nameserves as given by my IP.



The above configuration works fine. So, now I want to add a computer to
my internal network, naming it Home2. So all I have to do is connect
eth0 of Home2 to the switch and give the new computer 192.168.0.11 as
its IP. THis should work, right? I just want to make sure this is
supposed to work. The new computer doesn't, and if I am sure my
networking is okay, I can then focus on the hardware.


Thanks,
->HS

--
(Please remove all underscores from my email address to get the correct
one. Apologies for the inconvenience, but this is to reduce spam.)

On Wed, 21 Apr 2004 16:10:25 -0400, H. S. <(E-Mail Removed)> wrote:
>
> I am connected to the internet from my machine, hostname HomeRouter,
> through DSL modem, ppp0. I am doing masquarading and nat. HomeRouter has
> two NICs: eth0 takes in the connection from ppp0, and eth1 is connected
> to a switch. My internal home machine, hostname Home1, has it's eth0
> connected to the switch. Pictorially, it is like this:
>
>
> ----------- -------
> |HomeRouter| |Home1|
> ~~>pp0---->eth0,eth1---->Switch--------eth0
> |__________| | |_____|
> |
> |__eth0(Home2)
>
>
> The HomeRouter has (the following is from my /etc/network/interfaces file):
> auto eth0
> iface eth0 inet static
> address 192.168.1.0
> netmask 255.255.255.0
> network 192.168.0.0
> broadcast 192.168.0.25

The above settings appear to be incorrect (unless it is for pppoe, in
which case the eth0 IP is not used). I actually set ethernet to adsl
modem to netmask 255.255.255.255, network and broadcast same as IP, so
nothing would route out of it if it wanted to (pppoe handles the tcp/ip
traffic on that line). If it actually connects to a hardware
gateway/router or modem/router, its IP (address) should likely end with
something other than 0 or 255 for netmask 255.255.255.0 and network would
be 192.168.1.0, broadcast 192.168.1.255.

> ... and ....
> auto eth1
> iface eth1 inet static
> address 192.168.0.2
> netmask 255.255.255.0
> network 192.168.0.0
> broadcast 192.168.0.255

Appears correct.

> My internal machine, Home1, is running Win98, and has been given:
> IP: 192.168.0.10
> netmask: 255.255.255.0
> broadcast: 192.168.0.255
> gateway: 192.168.0.2
> and nameserves as given by my IP.
>
>
>
> The above configuration works fine. So, now I want to add a computer to
> my internal network, naming it Home2. So all I have to do is connect
> eth0 of Home2 to the switch and give the new computer 192.168.0.11 as
> its IP. THis should work, right? I just want to make sure this is
> supposed to work. The new computer doesn't, and if I am sure my
> networking is okay, I can then focus on the hardware.

If you used IP 192.168.0.11 for Home2 with same network, broadcast,
gateway and nameservers as Home1, it should work. Make sure it does not
have any other lingering gateways from past use, and if Windows is set to
NEVER dial a connection (or that it is on a LAN).

Note that if Home2 is Win98se, it originally had a problem where MSIE
failed to realize when it was connected to an existing network. In that
case if it asks if you want to work offline, just click "Try again" (until
you have a chance to do all Win updates, including MSIE version).

--
David Efflandt - All spam ignored http://www.de-srv.com/

Apparently, _David Efflandt_, on 04/21/04 22:29,typed:

>>The HomeRouter has (the following is from my /etc/network/interfaces file):
>>auto eth0
>>iface eth0 inet static
>> address 192.168.1.0
>> netmask 255.255.255.0
>> network 192.168.0.0
>> broadcast 192.168.0.25
>
>
> The above settings appear to be incorrect (unless it is for pppoe, in
> which case the eth0 IP is not used). I actually set ethernet to adsl
> modem to netmask 255.255.255.255, network and broadcast same as IP, so
> nothing would route out of it if it wanted to (pppoe handles the tcp/ip
> traffic on that line). If it actually connects to a hardware
> gateway/router or modem/router, its IP (address) should likely end with
> something other than 0 or 255 for netmask 255.255.255.0 and network would
> be 192.168.1.0, broadcast 192.168.1.255.


Yes. Somebody else also pointed out this to me. It seems that the
parameters on eth0 have no effect at all since eth0 is talking to ppp0
over pppoe.


<SNIP> <SNIP>

> If you used IP 192.168.0.11 for Home2 with same network, broadcast,
> gateway and nameservers as Home1, it should work. Make sure it does not
> have any other lingering gateways from past use, and if Windows is set to
> NEVER dial a connection (or that it is on a LAN).
> Note that if Home2 is Win98se, it originally had a problem where MSIE
> failed to realize when it was connected to an existing network. In that
> case if it asks if you want to work offline, just click "Try again" (until
> you have a chance to do all Win updates, including MSIE version).

Home2 had Windows 2000, which was something I hardly cared about, except
that it gave another opportunity to test the network. However, I was
more interested in Linux. So I had tried making Home2 work with the
network with Debian, Knoppix and Fedora. None of them worked. eth0 was
detected okay, but ping never worked. There was usually 98% packet loss.

Anyhow, thanks for your message, I am more or less banking towards the
faulty hardware theory.

regards,
->HS



--
(Please remove all underscores from my email address to get the correct
one. Apologies for the inconvenience, but this is to reduce spam.)

H. S. ((E-Mail Removed)) wrote:
: Home2 had Windows 2000, which was something I hardly cared about, except
: that it gave another opportunity to test the network. However, I was
: more interested in Linux. So I had tried making Home2 work with the
: network with Debian, Knoppix and Fedora. None of them worked. eth0 was
: detected okay, but ping never worked. There was usually 98% packet loss.

: Anyhow, thanks for your message, I am more or less banking towards the
: faulty hardware theory.

: regards,
: ->HS

I don't know how you can conclude this as hardware issue if Win2k
works but Linux doesn't. There is a difference between hardware
detection and proper configuration. It seems to me that your NIC
is detected but the required software module is not properly loaded.
If you can provide information on your NIC, we will be able to tell
you the required module.

Apparently, _Alex Yung_, on 04/22/04 10:22,typed:

> I don't know how you can conclude this as hardware issue if Win2k
> works but Linux doesn't. There is a difference between hardware

Looks like I haven't been clear in my earlier message. The network
worked neither in Linux _nor_ in Windows. The NIC showed similar
behavior in both cases. Also, I haven't concluded with certainty that it
was a hardware problem, I was only banking towards that option pending
some other concrete evidence.

What I wanted to convey in my earlier message was that prior to putting
the Home2 computer onto the network, it had Windows which I was planning
to erase. Before doing that however, I installed Linux in a different
partition and tried to bring up networking. That didn't work. So I tried
to bring it up in Windows since Windows usually does such detection
tasks quite easily. That didn't work either.

> detection and proper configuration. It seems to me that your NIC
> is detected but the required software module is not properly loaded.
> If you can provide information on your NIC, we will be able to tell
> you the required module.

The card in question was Linksys LNE100TX ver 5.1. When I tried to bring
up eth0, it was done successfully with Linux. The modules being used
were: tulip, and crc32 (by tulip).

BTW, maybe this will help:
knoppix@ttyp0[knoppix]$ uname -a
Linux Knoppix 2.4.24-xfs #1 SMP Mi Feb 4 01:03:50 CET 2004 i686 GNU/Linux
knoppix@ttyp0[knoppix]$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0. 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.0.2 0.0.0.0 UG 0 0 0 eth0


thanks,
->HS

--
(Please remove all underscores from my email address to get the correct
one. Apologies for the inconvenience, but this is to reduce spam.)