On Fri, 2005-02-11 at 12:16 -0700, jb wrote: > BTW, the box's IP on eth1 is 10.0.0.1. I have not set up DNS on it, > though it appears I should.
You will want it to be able to resolve host names using another DNS server but you don't need to run a DNS server on this box. > >You need to make sure the forwarding is allowed on the firewall. > >`cat /proc/sys/net/ipv4/ip_forward` > >Should show "1" > > > > > Returns "-bash: 1: command not found > (I suppose that means it is turned on.) No. This means that you ran the command with the `s left in like this: `cat /proc/sys/net/ipv4/ip_forward` Note how it should be run: cat /proc/sys/net/ipv4/ip_forward > >If not you can > >`echo "1" > /proc/sys/net/ipv4/ip_forward` > > > >And your box will then forward packets. This still holds true. > So, I guess that my iptables are not the problem, but that the problem > may lie elsewhere? However, I don't think the DNS is an issue (yet) > because O cannot ping by IP. Do I need to configure the firewall to be a > gateway? The host would not be able to ping anything outside of it's subnet if the routing host will not forward packets from the subnet. Iptables is not a problem from what you have said but we still have not confirmed that the kernel is allowing packets to be forwarded. The two can be set independent of each other *but both must be set*. To recap... Show us the output of: cat /proc/sys/net/ipv4/ip_forward AND iptables -L FORWARD > Thanks for the help. > > --jeremy Let us know, Gabe -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
