On Wed, 2003-12-31 at 08:01, Ow Mun Heng wrote: [Snip] > > > The reason to add static routes is if you want to reach > > networks that are not on either of these two networks nor reachable > through your > > > default gateway... > > Ah..solution to my problem. Say I want to go to www.hotmail.com, so, the > packets > will need to go through the 192.168.0 NIC(->wifi->DNS->NAT->Inet etc) to get > there right? I think what you want to do is set up the default gateway to point to the default router on the 192.168.0.0/24 (WIFI) network. Then you will need to get a list of all of your companies internal networks and use static routes on the other interface to route to these networks. Using the addresses you gave in an earlier email, and assuming that all of your internal networks are in the 10.x.y.z address space, then you should create the file /etc/sysconfig/static-routes with the line: eth1 net 10.0.0.0 netmask 255.0.0.0 gw 10.0.0.10 and the file /etc/sysconfig/network should look something like: NETWORKING=yes HOSTNAME=mymachinename GATEWAY=192.168.0.10 Once you have this in place you should (as root) run the command: /sbin/service network restart and hopefully it should all work :-) If it doesn't, then post the output of: /bin/netstat -rn and /sbin/ifconfig and provide more information about what networks you have internally. To debug this kind of setup you should use the commands ping and traceroute. Use both of them with the -n flag to stop name lookups. Start by trying to ping your ethernet interfaces, then the default gateways, and then devices on networks further away. Keith. -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
