On Thu, 23 Sep 1999, Tim wrote:
+>
+>I'd like to create a new network using IP Aliasing to allow us some
+>growth. Our existing network is 192.168.100.0 and we use 192.168.100.10
+>as our gw on the clients. I'd like to create a new network 192.168.200.0
+>and allow access to both networks regardless of their ip (192.168.100.xxx
+>or 192.168.200.xxx) and also allow them internet access through
+>192.168.100.10 (inetgw)
+>
+>I have a box that's used for internet access that we can't modify (I'll
+>call this box 'inetgw') with an ip address of say 192.168.100.10
+>
+>I went to my Linux box (we'll call this timbox) that has an internal ip of
+>192.168.100.225 and an alias (eth0:0) of 192.168.200.10.
+>
+>What I'd like to do is create this new network (192.168.200.0) using IP
+>Alias and be able to see both networks (100.0 and 200.0) from any machine.
+>
+>Here's what I've done so far:
+>timbox:
+>/sbin/ifconfig eth0:0 192.168.200.0 netmask 255.255.255.0 up
+>/sbin/route add -net 192.168.200.0 netmask 255.255.255.0 dev eth0
+>(not sure if the above is necessary)
+>
+>At this point from timbox I can successfully ping both nets without any
+>problems.
You can ping because "timbox" have 192.168.100.225 not the eth0:0
+>
+>Now I'd like to be able to go to my laptop (timlaptop) with an IP Address
+>of 192.168.100.50 and see both the 100.0 and 200.0 networks. I've set the
+>gw of timlaptop to 192.168.100.225, but everytime I try to ping
+>192.168.200.10 it ends up going out to the internet via 192.168.100.10
+>which is the inetgw box that I can't do anything with, but has
+>masquerading installed for our Internet Acces.
+>
+>Can anyone offer any assistance? Are my ifconfig and route statements
+>correct? Am I doing something wrong with the ipchains rules? Can I set
+>up timbox to give everyone internally access to both 192.168.100.0 and
+>192.168.200.0 networks when I can't touch the 192.168.100.10 (inetgw) box
+>that is now the gw on all machines in house?
+>
+>If anyone can offer suggestions (examples on what syntax I should be
+>using) on what it is that I need to do or am doing wrong I would greatly
+>appreciate any and all guidance.
+>
A quick solution here might help.
In Timbox should have:
eth0 192.168.100.225 default-gw is 192.168.100.10
eth0:0 192.168.200.10 default-gw is 192.168.200.1
^^^^^^^^^^^^^
(must match at inetgw's eth0:0)
In inetgw should have:
eth0 192.168.100.10 default-gw is xxx.(your Internet gw-ip)
eth0:0 192.168.200.1 default-gw is xxx.(your Internet gw-ip)
^^^^^^^^^^^^^^
(This ip is the default gw for all your 192.168.200.x net)
Then add routing to inetgw:
route add -net 192.168.100.0 gw 192.168.200.1 dev eth0:0
route add -net 192.168.200.0 gw 192.168.100.10 dev eth0
Of course, you have to adjust your subnet mask and etc.
These routing should be able to let both network to see each other.
The idea here is to make your inetgw as the default gateway for both
network instead of making your Timbox as the gateway.
This might help.
Regards,
== Yen Jet ==
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Chan: "The bad news is, the Y2K bug will make all of our computers
thinks it's the year 1900. The good news is, that gives us
an extra 100 years to fix the problem!"
Chan: Let's do => lynx http://3401483843/
============================8<=======================================
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
