|
From: Schley A. K. <sa...@gm...> - 2009-12-10 14:32:05
|
It still fails. I tried enabling this yesterday as I recalled I needed to do so when I was using bridged mode for OpenVPN. I re-enabled it just now to be sure, and things still fail. -- -a "Only two things are infinite, the universe and human stupidity, and I'm not sure about the former." --Einstein On Dec 10, 2009, at 8:27 AM, Jan Just Keijser wrote: > Schley Andrew Kutz wrote: >>> the default is that everything is allowed ; iptables -L -n -v will show you that (maybe list 'iptables -t nat -L -n -v' to be safe) >>> >> >> [0]root@vault:~$ iptables -L -n -v Chain INPUT (policy ACCEPT 9232 packets, 1856K bytes) >> pkts bytes target prot opt in out source destination >> Chain FORWARD (policy ACCEPT 9183 packets, 1533K bytes) >> pkts bytes target prot opt in out source destination >> Chain OUTPUT (policy ACCEPT 4264 packets, 686K bytes) >> pkts bytes target prot opt in out source destination >> Looks good to me. >> >> >>> routing is enabled on the machine, I assume (because otherwise some other things would have failed already) ? >>> >> >> /proc/sys/net/ipv4/ip_forward is set to 0, but everything else is working. I thought this was strange as well. I just assumed because I'm using a tunnel for OpenVPN and not bridging, that OpenVPN handled the routing. >> >> > whoa! > in order to forward stuff between (non-bridged) interfaces you need to have ip_forwarding enabled. What happens if you do > echo 1 > /proc/sys/net/ipv4/ip_forward > and try again? > > cheers, > > JJK > |