Requests Custom Firewall / Port Forwarding features....

[pitboss]

The firewall rules including those on the port forwarding and related filtering does not seem to work for a VPN connections. This is due to the traffic being routed to the tunxx interfaces rather than the eth0 default interface. At the moment the only solution is to add the custom iptables rules by ssh to the router and run the necessary iptables command for port forward. This method however will not a survive a reboot unless written to jffs.

Is it possible to add this feature, to add a custom rules page for iptables entry in the firewall settings that will save the settings OR add interface selection in the Virtual Server/Port Fowarding of the WAN settings?

Thank you

 

[RMerlin]

The firewall rules including those on the port forwarding and related filtering does not seem to work for a VPN connections. This is due to the traffic being routed to the tunxx interfaces rather than the eth0 default interface. At the moment the only solution is to add the custom iptables rules by ssh to the router and run the necessary iptables command for port forward. This method however will not a survive a reboot unless written to jffs.

Is it possible to add this feature, to add a custom rules page for iptables entry in the firewall settings that will save the settings OR add interface selection in the Virtual Server/Port Fowarding of the WAN settings?

Thank you

This would basically require rewriting a lot of the low-level routing code, and it still wouldn't work properly if your tunnel providers isn't forwarding ports on their end anyway, so this isn't likely to happen.

 

[pitboss]

Would be great to have a window in the GUI to enter custom scripts and save them to the jffs partition.
Looks like vpn users has no choice but to learn bash and iptables using ssh or telnet command to do this.

 

[RMerlin]

Would be great to have a window in the GUI to enter custom scripts and save them to the jffs partition.
Looks like vpn users has no choice but to learn bash and iptables using ssh or telnet command to do this.

With over 30 different potential scripts and config files supported, this is impossible to manage in any sane way through the webui.

A webui wouldn't prevent you from having to understand bash and iptables. All it would do is save you from learning to use a program like WinSCP, which is hardly difficult.