Ticket #82 (closed defect: fixed)

Opened 16 months ago

Last modified 16 months ago

no trafic from local.lan to world.inet

Reported by: firdaus.aziz@… Owned by: victor
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

Changed 16 months ago by victor

  • version set to 0.7
  • milestone changed from undecided to 0.8

Changed 16 months ago by victor

  • status changed from new to assigned

Changed 16 months ago by victor

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.

Changed 16 months ago by victor

  • status changed from assigned to closed
  • resolution set to fixed

Fixed by changeset:236.

Note: See TracTickets for help on using tickets.