On Wed, Feb 23, 2011 at 03:38:08PM +0300, Otandeka Simon Peter wrote: > Richard, > > First of all have one default gateway. Usually the public IPs default gw is > used. So your public IPs should use that. > For your private IP, you may need to specifically set a route in your table > to channel traffic through the gateway specified something like > "route add -net 172.16.0.0 gw 172.16.0.1 eth3". > I am not on my suse box to test it out but I think it is written like that.
You need a range of IPs to specify a network. route add -net 172.16.0.0/16 gw 172.16.0.1 eth3 The problem is that eth3 is already configured with a 255.255.0.0 netmask, so that doesn't make any sense. Here is a little networking theory. There are two kinds of IP addresses ones which are reachable directly and ones which need a gateway. Known and unknown in other words. IP address cannot be both known and unknown. In this case 172.16.0.1 is known. That's a gateway and we don't need a gateway to reach the gateway. In fact with a netmask of 255.255.0.0 all the addresses which start with 172.16. are known and do not need a gateway. If your internal network is really set up to need a gateway (ie all the addresses are unknown except the gateway), and I totally don't believe it is then you'd have to configure it like this: ifconfig eth3 172.16.0.10 netmask 255.255.255.255 route add -host 172.16.0.1 eth3 route add -net 172.16.0.0/16 gw 172.16.0.1 eth3 But that's nonsense. :P You don't need a gateway for the internal network. regards, dan carpenter _______________________________________________ The Uganda Linux User Group: http://linux.or.ug Send messages to this mailing list by addressing e-mails to: [email protected] Mailing list archives: http://www.mail-archive.com/[email protected]/ Mailing list settings: http://kym.net/mailman/listinfo/lug To unsubscribe: http://kym.net/mailman/options/lug The Uganda LUG mailing list is generously hosted by INFOCOM: http://www.infocom.co.ug/ The above comments and data are owned by whoever posted them (including attachments if any). The mailing list host is not responsible for them in any way.
