Well it will work, the big problem is two adjacent addresses on two
different interfaces.
personally I would have split the subnet in two so that a netmask of
x.x.x.0/27 could be used.
I had to do similar thing when running a radio ip hub here, where users
were linked on different interfaces with each interface using a
different frequency..
If there is only 1 machine on each interface it dos'nt matter about
broadcast addresses, as there's only 1 machine to broadcast to.
So the only way to route is with host routing.
Also if adding to rc.local dont forget to delete the default routing

/sbin/route del -net 192.168.0.0 netmask 255.255.255.0 eth2

Richard
On Sat, 2003-06-28 at 22:00, SainTiss wrote:
> Well, that would work of course, but it's rather ugly don't you think?
> 
> I'm looking for the way MDK does these things by default.. Must be
> somewhere in /etc/sysconfig
> 
> Hans
> 
> On Sat, 2003-06-28 at 23:12, richard bown wrote:
> > HI
> > try adding to rc.local at the end of the file
> > /sbin/route add -host 192.168.0.2 eth1
> > /sbin/route add -host 192.168.0.3 eth2
> > HTH 
> > Richard
> > 
> > On Sat, 2003-06-28 at 20:59, Steven Broos wrote:
> > > Quick lesson in subnetworking, because I think the problem isn't your
> > > IPtables-settings but your network layout.
> > > 
> > > 192.168.0.x is a class C network address. 192.168.0 is the network
> > > address, and the last number is the host-portion of the address.
> > > If all PCs have an address beginning with 192.168.0 and a netmask of
> > > 255.255.255.0 they are on the same subnet, and don't need routing.
> > > If you need to separate your LAN into difefrent subnets, use 192.168.0.x
> > > and 192.168.1.x etc...
> > > 
> > > Creating a subnet with mask 255.255.255.255 isn't possible, because that
> > > way you don't have any broadcast/network-addresses.
> > > 
> > > If you think this goes into the right direction, please give more
> > > details about your LAN and ask for more information :-)
> > > 
> > > regards,
> > > Steven
> > > (CCNA)
> > > 
> > > 
> > > 
> > > 
> > > On Sat, 2003-06-28 at 20:47, SainTiss wrote:
> > > > Well, what I *need* e.g. on the gateway is something like this:
> > > > 
> > > > Kernel IP routing table
> > > > Destination     Gateway         Genmask         Flags Metric Ref    Use
> > > > Iface
> > > > 192.168.0.3     0.0.0.0         255.255.255.255 UH    0      0        0
> > > > eth2
> > > > 192.168.0.2     0.0.0.0         255.255.255.255 UH    0      0        0
> > > > eth1
> > > > 213.118.248.0   0.0.0.0         255.255.252.0   U     0      0        0
> > > > eth0
> > > > 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0
> > > > lo
> > > > 0.0.0.0         213.118.248.1   0.0.0.0         UG    0      0        0
> > > > eth0
> > > > 
> > > > However, by default those upper 2 rules aren't there, and instead
> > > > there's a rule like this:
> > > > 
> > > > 192.168.0.0     0.0.0.0         255.255.255.0 U    0      0       
> > > > 0       eth2
> > > > 
> > > > So in other words, by default ALL LAN traffic is routed through eth2,
> > > > while obviously traffic with 192.168.0.2 should be routed via eth1.
> > > > 
> > > > Did that make it any clearer?
> > > > 
> > > > Thanks,
> > > > 
> > > > Hans
> > > > 
> > > > On Sat, 2003-06-28 at 20:18, Bill Mullen wrote:
> > > > > On Sat, 28 Jun 2003, SainTiss wrote:
> > > > > 
> > > > > > I just changed my network configs here, and it seems the routing table
> > > > > > got messed up...
> > > > > > 
> > > > > > I know the solution (ie adding some rules and deleting some), but I was
> > > > > > wondering if there was some file or something where I could specify the
> > > > > > right rules, so that the table is setup correctly at boot?
> > > > > > 
> > > > > > what's the default way to do this? I'm guessing some file which is then
> > > > > > processed by ifup or something, but I'm not sure...
> > > > > 
> > > > > Depends on what's messed up. :)
> > > > > 
> > > > > Most settings draw on the information in the "/etc/sysconfig" directory, 
> > > > > specifically the "network" file and the various "ifcfg-<interface>" ones 
> > > > > in the "network-scripts" subdirectory. For simpler setups, these are all 
> > > > > you'll need to adjust, but we have no idea how complicated your normal 
> > > > > routing table actually is ... care to offer a hint? ;)
> > > 
> > > 
> > > 
> > > ______________________________________________________________________
> > > 
> > > Want to buy your Pack or Services from MandrakeSoft? 
> > > Go to http://www.mandrakestore.com
-- 
richard bown <[EMAIL PROTECTED]>


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to