Hi Mike.. and adding this route to the box2, will allow me to ping box2/eth0 from box1? or are you saying that i'd have to add the route to box1. if i have to add a route to box1, then i'd have to add a route to every box in the system... which isn't what i'd want to do. again.. thanks for the basic understanding.. thanks -----Original Message----- From: fedora-list-bounces@xxxxxxxxxx [mailto:fedora-list-bounces@xxxxxxxxxx]On Behalf Of Mike Wright Sent: Monday, November 26, 2007 12:20 PM To: For users of Fedora Subject: Re: ip masquerading/subnets bruce wrote: > hi john... > > i might be missing/lost some emails... so let me start at the very > beginning!! bear with me if you find yourself repeating something you've > already stated... > > my initial system (two boxes, nothing between them) > > windows linux > box1 ----- >>> ------ box2 >>>>>> (future separate lan box) > eth0 (wireless) ath0 eth0 > > box1 > eth0 - 192.168.1.3 > > box2 > ath0 - 192.168.1.5 > eth0 - 192.168.2.5 > > from box1, i can ping 192.168.1.5 > from box1, i can't ping 192.168.2.5 > > from box2, i can ping box1 (192.168.1.3) > > so, what do i/should i do to connect/ping box2/eth0 from box1? The linux box is now a router and from the point of view of box1 ath0 is just another gateway. box1 needs to know about any routes available to it and it apparently already has a default route which points to your first router. default routes are the ones taken when the desired desitination ip is not already specified in the routing table(0). Since you know where 192.168.2.5 is you can add a specific route for that and, in fact, since you want to add a future box to that lan, and assuming it's a /24 bit netmask, you would use something like this: (as root) /sbin/ip route add 192.168.2.0/24 via 192.168.1.5 dev eth0 hth, Mike Wright -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
