跳到主内容

LAN & WAN port in the same subnet (same network)

评论

1 条评论

  • Kyle Reynolds

    Hi Martin,

    There is a way to accomplish this, but we don't recommend it, and we will not support it. If you want to use it, you will do so at your own risk. We feel that it is a security risk to allow remote access to the whole plant subnet instead of putting the machines on their own segregated LAN. Using NAT to create a separate machine network is best practice. 

    Here are the instructions: 

    Overview:
    It may occur that a customer wants to use an Ewon in an industrial network where only a single subnet is available. Usually, this results in an IP conflict, but there is a work-around for this.

    Step 1
    Run the Ewon wizard as you would normally but ignore the LAN IP address. This can remain the default 10.0.0.53 for now.

    Step 2
    Go to the Comcfg parameter list (Setup → System → Storage → Edit COM cfg) and change the following settings:
    • KillLAN → 1
    • WANItfProt → 2
    • FwrdToWAN → 1
    • NATItf → 2
    Save the settings and reboot the Ewon.

    Step 3
    Change the LAN IP-address of the Ewon into the same range as the WAN IP of the Ewon (= single subnet range). This won't result in an IP-conflict, because the LAN is killed at step 2. Nevertheless, the LAN IP is still needed to create a route in our routing table.

    Step 4
    The Ewon will work as normal for remote access purposes. Even LAN devices & firewall settings in eCatcher work as normal, as well as M2Web visability. But please note, devices should be connected into the WAN port(s) of the Ewon.

    Please Note

    If you lose access to the device web interface, you will have to factory reset the device. 

    Best Regards,

    Kyle Reynolds

    0

请先登录再写评论。