Sorry for the typo. test machine is 192.168.2.20 On Fri, Oct 03, 2003 at 11:44:55AM +0300, Nick Patavalis wrote: > On Fri, Oct 03, 2003 at 03:21:48AM -0500, Indraneel Majumdar wrote: > > Hi, > > I seem to be having a silly problem with routing. Cannot connect to > > 192.168.1.1 from test machine (details below). I will be grateful if > > someone could suggest a fix. > > > > ---------------- 192.168.1.0 > > | | > > ___ ___ ___ > > | | | | | | > > | 1 | | 2 |-- 192.168.2.0 ----| 1 |-- 129.x.y.z > > | | | | | | | > > ^^^ ^^^ | ^^^ > > | | | > > ---------------- 192.168.3.0 |________ > > | | > > | 2 | > > |test | > > | | > ^^^^^ > > > > 192.168.1.1 (192.168.3.1) is a DNS/DHCP/TFTP machine > > 192.168.1.2 (192.168.3.2, 192.168.2.2) is a router > > 192.168.2.1 (129.x.y.z) is a (diskless) firewall > > 192.168.2.2 is a test machine > > > > It seems that you have two interfaces with the *same* IP address > (192.168.2.2 is shared by the router and the test-machine). This > should obviously not work! > > /npat > > -- > A picture is worth 10,000 words -- but only those to describe the > picture. Hardly any sets of 10,000 words can be adequately described > with pictures. > - > : send the line "unsubscribe linux-net" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- http://www.smartpatch.net - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
