[lug] subnets

[Hugh Brown]

On Tue, 2002-07-16 at 04:35, Warren Sanders wrote:
> I'd go an easier route; assuming the masq box has one nic.  Do an alias 
> for that nic so that it is both 192.168.1.1 and 192.190.1.1.  
> 
> But now that I did some research on this, I found this page that may 
> blow my suggestion out. 
>  http://www.tldp.org/HOWTO/IP-Masquerade-HOWTO/aliasing.html


The masq'ing box has two nic's.  One on the outside and one on the
inside. For now, I just want the internal network to talk to the other
one.  I'll worry about external access later.

I aliased the internal nic to the 192.190.1.0 subnet and can ping the
other hosts on the network.  I would like machines on the 192.168.1.0
network to be able to talk to the 192.190.1.0 network.  Unfortunately,
they can't.  I can ping 192.190.1.1 (the masq box) but I can't ping
other 192.190.1.x boxes.

route on the masq box:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.1.1   0.0.0.0         255.255.255.255 UH    0      0        0
eth1
xxx.xxx.xxx.xxx 0.0.0.0         255.255.255.255 UH    0      0        0
eth0
192.190.1.1     0.0.0.0         255.255.255.255 UH    0      0        0
eth1
127.0.0.1       0.0.0.0         255.255.255.255 UH    0      0        0
lo
xxx.xxx.xxx.xxx 0.0.0.0         255.255.255.192 U     0      0        0
eth0
192.190.1.0     0.0.0.0         255.255.255.0   U     0      0        0
eth1
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0
eth1
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0
lo
0.0.0.0         xxx.xxx.xxx.xxx 0.0.0.0         UG    0      0        0
eth0

Sorry about the word wrap.  evolution doesn't seem to let me configure
that.

it seems like there is a route to use eth1 for all traffic on
192.190.1.0/255.255.255.0 but I've been wrong many a time before.

What am I missing?

Hugh



> 
> Hugh Brown wrote:
> 
> >network newbie question.
> >
> >I am in a bit of situation.
> >
> >We won the second phase of a contract and have the job of porting a
> >windows based system to an os independent system.  The company delivered
> >the machines but put them on the 192.190.1.x/24 subnet and told us that
> >changing the ip address of the two systems would be burdensome to do. 
> >Their obligation is to deliver a system that works.  It seems to work
> >okay, but I don't know how to get the two systems to see the Internet at
> >large.
> >
> >I have the two systems on an ipchains masqueraded network.
> >
> >How do you normally put two distinct subnets on a network and get them
> >to go out to the right destination
> >
> >
> >Here's the setup
> >
> >Internet--- external interface (ipchains box) 192.168.1.1----|
> >                                                             |
> >                                                     Internal Network
> >                                                             |
> >                                                             |
> >                                                      192.190.1.x/24
> >
> >I know I haven't explained this very well so please help me clarify.
> >
> >Hugh
> >
> >
> >
> >_______________________________________________
> >Web Page:  http://lug.boulder.co.us
> >Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> >Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
> >
> >  
> >
> 
> -- 
> Warren Sanders
> http://MontanaLinux.Org
> 
> 
> 
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug