Shorewall users - Feb 2005 - loc2net no longer working (and I read the FAQ)

Colin Viebrock wrote:
> /proc
> 
>    /proc/sys/net/ipv4/ip_forward = 0
-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net
PGP Public Key   \ https://lists.shorewall.net/teastep.pgp.key

Hi all,

This is your standard "I can''t *see* the internet" problem,
except I think
I''ve exhausted all the standard solutions.  The only thing different is
that my house experienced a power outage and now (after the FW rebooted) 
local machines can''t "see" out.

I''ve got a 2-interface setup, using Shorewall 2.0.15 (installed via 
Debian).  eth0 is connected to my DSL modem (uses PPPoE) and eth1 is the 
local 192.168.1.0/24 subnet.

I run a dnsmasq on the firewall.  All loc machines can do DNS lookups 
without problems.

loc2fw connections work fine, as do fw2net.  Just loc2net seems to be 
failing.

I''m attaching the output from:
 	- shorewall version
 	- shorewall status
 	- ip addr show
 	- ip route show

I''ll gladly send more info if more info is needed.

- Colin

p.s. please cc your responses to colin@viebrock.ca and colin@easydns.com 
... since I''m not sure if incoming traffic is working.  Thanks muchly.

Tom Eastep wrote:
> Colin Viebrock wrote:
> 
> 
>>/proc
>>
>>   /proc/sys/net/ipv4/ip_forward = 0
> 
> 
Hint: The Debian maintainer sets IP_FORWARDING=Keep in shorewall.conf.

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net
PGP Public Key   \ https://lists.shorewall.net/teastep.pgp.key

> /proc
>
>    /proc/sys/net/ipv4/ip_forward = 0
How odd.  I''ve now done:

 	echo 1 > /proc/sys/net/ipv4/ip_forward

... and, of course, it now works.  Thanks, Tom.  Any idea why that would 
have changed after a reboot?

- Colin