Doug Coats wrote: > Christopher - you have been a great help! > > My internal network ip is 192.168.4.1 and I need it to access the > aa.bb.166.2 interface or eth3. What would the rule look like that I > need to add? > > ip route add 192.168.4.0/24 (??? i don't know your subnet - guessing your netmask here) dev ethx (replace x with the 192.168.4.1 interface) proto kernel scope link src 192.168.4.1 table Cable ip route add 192.168.4.0/24 (??? i don't know your subnet - guessing your netmask here) dev ethx (replace x with the 192.168.4.1 interface) proto kernel scope link src 192.168.4.1 table T1 That should fix things for both interfaces. Or use the command only for the table that corresponds to eth3. cheers, Christopher > > > On Thu, Jul 2, 2009 at 6:51 PM, Christopher Chan > <christopher.chan at bradbury.edu.hk > <mailto:christopher.chan at bradbury.edu.hk>> wrote: > > > > As a follow up issue. The only thing that is not working > properly is > > that I can not pull up my website that is hosted on this server from > > our private network. > > > > Do I need iproutes for my other two nics? I have never needed them > > before. > > > > > > That is because you never redirected routing lookups to the custom > tables. You can either add routing entries for your internal network > into those two custom tables or you can add two SNAT rules > assuming you > also use the box as a nat box for the Internet. > _______________________________________________ > CentOS mailing list > CentOS at centos.org <mailto:CentOS at centos.org> > http://lists.centos.org/mailman/listinfo/centos > > > ------------------------------------------------------------------------ > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >