John Andersen wrote:
On 2/23/2012 6:15 AM, Per Jessen wrote:
James Knott wrote:
Per Jessen wrote:
I'm setting up a new box and started out with ip forwarding enabled. This seemed to prevent internet access, so I tried disabling forwarding with yast, but this only caused a hang. I ended up having to walk to the datacentre to access the physical console.
Just wondering before I start digging into this - are there any (more or less) known issues wrt ip forwarding and/or the enabling/disabling thereof in 12.1 ?
IP forwarding is used only if you're using the computer as a router.
Yes, this box is set up as a router.
And you configured the SuseFirewall? (or shut it down to test?)
Yes, it's disabled, I never use it. There is no other firewall active either. The YaST issue I mentioned has disappeared, but I'm still left with access to external networks (e.g. websites) not working when I activate ip forwarding. The box is set up as follows:
Subnet1 = 192.168.0.0/21 Subnet2 = 192.168.8.0/21 Default route = 192.168.2.7
When forwarding is disabled, everything works as normal (as on any other box on subnet1. When I enable forwarding, access to external networks via the default route eventually time out. I have not yet investigated it in depth, I was just wondering if there were any known issues.