Custom Query (115 matches)
Results (49 - 51 of 115)
|#82||fixed||no trafic from local.lan to world.inet|
"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.
|#81||invalid||Wondering can Vuurmuur log connections what what ppl do|
Hello, I own Trower hosting Service Provider, LLC. we offer managed VPS, Managed Dedicated Servers. I am wanting to know is there a way that I can log what thoughs connections do and also see the ip address of thoughs connects? I have used vuurmuur in testing to see what it can do. Just started a few hours ago. I am also wondering because these vps are used for anything is there a way to open up the firewall so anyone can connect, etc. to any port per say? Thank you in advance love the software.
|#77||wontfix||Loopback port redirect not working|
The following does not work as expected:
RULE="Redirect service https from local.lo to local.lo options redirectport=\"80\""
The aim is to redirect requests coming on loopback from port 443->80. It does not work because vuurmuur assigns the rule to
Chain PRE-VRMR-OUTPUT (1 references) target prot opt source destination REDIRECT tcp -- anywhere anywhere tcp dpt:https redir ports 80 R
I believe there are several ways to archieve loopback redirects, but I believe it should be handled implicitly in vuurmuurlib or vuurmuur_conf.