[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: routing




Steve Lee <maillist blitzen net> writes:

> I'm sorry.  I will try to be more specific.
> 
> On Thu, 10 Feb 2000, Philippe Moutarlier wrote:
> 
> > 
> > Your description is a little bit difficult to follow :
> > 
> > How A and B are hooked together ? 
> Both a and b is hooked to a switch/hub
> but a also has an extra nic for the dsl line.
> Box a should be a router for Box b, too.
> It only works if I setup Box b using the internal
> ip address.
> > 
> > I don't understand your A:nic.2 setting : do you alias the whole 
> > range 128-135 ? If yes, for what for ?
> I alias and use 129-132 and 134.
> I'm trying to use 133 on another machine
> These are real ip address asign for use on the net.
> Also i use two as dns, two for web, one for email.
> etc.  
> > 

You do 2 aliases ?  :

eth1:0 129-132
eth1:1 134 


I don't known dsl that much (use cable modem) but is your dsl line plugged into the hub ?

Otherwise, all is going to go through your A:nic2 interface in any case.

Also, you have to tell A about the special route to B. Otherwise A will try to answer to B by going out to the dsl line by default. Something like :

route add -host Baddress eth0

Philippe

> > In that case you have a conflict for the 133 ...
> > 
> I would like to use it for a database server like
> MySql only to take the load off the machine.
> Is it that I can't alias in between a set of ip range
> and strip one off to use on another machine?
> > could you be more precise ?
> > 
> > Philippe
> > 
> > 
> > Steve Lee <maillist blitzen net> writes:
> > 
> > > here is the whole scoop on my routing problem.
> > > Box A.  main system where the dsl line is
> > > hooked up to.  has two network cards.
> > > nic 1. internal address 192.168.230.1
> > > nic 2. external address 207.113.56.128 -135
> > > ip aliased for all the ip. and where the dsl 
> > > modem is hooked up to and routed out.
> > > 
> > > Box B  will handle some load by using one of
> > > the external ip from Box A.
> > > 207.113.45.133
> > > 
> > > 
> > > Now Box A and Box B works fine if i use internal
> > > address for box B. by giving it a address 192.168.230.2
> > > i can ping the world, etc. and it works.
> > > but when i give box b an address 207.113.56.133
> > > i can't even ping anyone but itself.
> > > Now, i'm a little aww at what i did wrong.
> > > Is the setup for ifcfg-eth1, networks, etc.
> > > different when i want to let someone into the internal
> > > network. did i setup some kind of firewall, that i don't
> > > even know?  help.  
> > > 
> > > 
> > > 
> > > 
> > > 
> > > -- 
> > > To unsubscribe: mail redhat-list-request redhat com with "unsubscribe"
> > > as the Subject.
> > 
> > 
> > -- 
> > To unsubscribe: mail redhat-list-request redhat com with "unsubscribe"
> > as the Subject.
> > 
> 
> 
> -- 
> To unsubscribe: mail redhat-list-request redhat com with "unsubscribe"
> as the Subject.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]