Port forwarding(virtual server) bug

Home Page Forums Network Management Signal a BUG Port forwarding(virtual server) bug

This topic contains 1 reply, has 0 voices, and was last updated by  Expert 8 years ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #42863

    Expert
    Member

    Hi all.
    I’ve found a bug. Beta 14. When I forward a port during web-interface (Router=>Virtual server), the page script generates iptables rule incorrectly. The problem is in /root/kerbynet.cgi/scripts/router_patconfig script.
    The string

    if [ “$VIRTUALIP” != ANY ] ; then
    VIP=”-d $VIRTUALIP”

    MUST be

    if [ “$VIRTUALIP” != ANY ] ; then
    VIP=”-s $VIRTUALIP”

    I’ve fixed it, all works fine. I hope it will be fixed in next releases. Good luck!

    #51601

    imported_fulvio
    Participant

    It is not a bug. On my opinion make more sense to match the destination IP (Virtual IP).

    Regards
    Fulvio

    #51602

    Expert
    Member

    Fulvio,thanks for your answer. But my situation is:
    Our company have internal network 192.168.0.0/24 and 1 Externat internet IP. Let it be $E. Three managers of the company wants to work at home with their remote workstations via Microsoft RDP (port 3389). Their home IP’s are $A,$B,$C. So, I need the next schematic:

    $A=>$E=>192.168.0.100:3389
    $B=>$E=>192.168.0.101:3389
    $C=>$E=>192.168.0.102:3389
    Other incoming conections to company’s gateway ($E) must be dropped.

    This schema is impossible to release with your algorithm because every packet, coming to external interface will have $E destination adress.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.