Opened 11 years ago

Closed 11 years ago

#82 closed defect (fixed)

no trafic from local.lan to world.inet

Reported by: firdaus.aziz@… Owned by: Victor Julien
Priority: major Milestone: 0.8
Component: suite Version: 0.7
Keywords: Cc:

Description

"local.lan" to "firewall", "firewall to world.inet" and "world.inet to firewall" are working OK.

But "local.lan to world.inet" is not working. There is no traffic what so ever. Even in logview there is nothing, not even DROP.

The output of "sudo cat /proc/sys/net/ipv4/ip_forward" is "0".

After entering 'sudo echo "1" >/proc/sys/net/ipv4/ip_forward' then only everything works.

Change History (4)

comment:1 Changed 11 years ago by Victor Julien

Milestone: undecided0.8
Version: 0.7

comment:2 Changed 11 years ago by Victor Julien

Status: newassigned

comment:3 Changed 11 years ago by Victor Julien

This issue is related somehow to #84. If the limit match isn't detected the ip_forward flag isn't set. A workaround is starting 'vuurmuur' with the '-t' option. That disables the iptables capabilities detection, so Vuurmuur then assumes that the limit match is available.

comment:4 Changed 11 years ago by Victor Julien

Resolution: fixed
Status: assignedclosed

Fixed by changeset:236.

Note: See TracTickets for help on using tickets.