Zum Hauptinhalt gehen

Suche

ETS Professional Feature Requests

Toggle multiple interfaces - simultaneously downloading (VPN)

Kommentare

12 Kommentare

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

  • Offizieller Kommentar
    Michael Critchfield

    Dear all, 

    can you please try the way it is intended, with the Interface Selection set to "Automatic"? Because only then you give ETS the freedom to choose the correct Interface. And following your description, only on "Automatic" can ETS do multiple parallel downloads to IP Interfaces/Routers

  • Patrick Patschok

    Habe das selbe Problem! - Wir haben teilweise 10-20 IP Gateways - damit ist kein konstruktives Arbeiten möglich.

    Dies sollte in der ETS 6 raschest nachgeholt werden. Ansonsten sie für prof. User nicht verwendbar ist!

    Werde vorläufig keine Anlagen in die Vers 6 nachziehen! - In ETS 5 funktioniert es ja.

    4
  • Mateus Sybilla

    .

    2
  • Sebastian Arnestad

    We are still wating to get back this function!

    3
  • Sebastian Arnestad

    "The way it is intended" does not find KNX/IP routers automatically on most of our VPN connections to our customers. With ETS5, you could manually set an interface to each KNX line, and this worked good if the routers could not be found automatically. I have VPN connection to projects with over 40 KNX/IP routers, and the routers are not detected automatically when connected via VPN.

    Please reconsider reimplementing, it is a HUGE timesaver when using VPN, where automatic disovery of KNX/IP routers does not work.

    3
  • Klaus Gütter

    In ETS 6.3, you can enter the IP address of an IP Interface/IP Router in the Sidebar (Properties). ETS will then - if Multicast is not possible - try to connect directly point-to-point to the interface. This works with the "Automartic" selection in the connection menu.

    -2
  • Davy De Maegt

    Klaus, this is not always working. For example if a have a knx router/interface that is not in ETS (like schneider wiser, basalte core, logic machine, ...) We also have projects where every knx router/interface is after a network router with port forwarding. Every knx router/interface is having the same ip from the network router. The unique identification is through the ip inside ets, not the ip that is in the device.... We would like to have the option back where we can fill in the ip of the network router and the netwerk router is port forwarding to the knx router/interface. Also in a lot of projects we are not allowed to put a fixed IP in the knx router/interfaces. This is done through dhcp reservation.

    2
  • Mateus Sybilla

    Dear KNX association

    This automatic function may work just fine in your testing environment, but it is NOT working as intended in the real world cases.

    There has been a lot of pressure about securing KNX installations and using VPN, but the tools we got today just does not work with it.

    There has also been an issue that I reported to you with automatic protocol detection in bus manager and VPN.

    Please consider this feedback from professionals, who works with multiple KNX installations daily.

    Mateus

    1
  • Klaus Gütter

    Hello Davy and Mateus,

    thank you very much for your feedback! We really want to deeply understand your problem and use case.

    @Davy The IP address you enter in the field need not be the IP address in the interface. If there is some address translation going on, you can enter the IP address to be used by ETS.

    I do not understand your remark about DHCP: for ETS it does not matter if the IP address is fixed or assigned via DHCP reservation.

    @Mateus You refer to the problem when TCP is blocked by a firewall and only UDP connections are possible? Indeed, if the interface reports TCP support, ETS will always use TCP. For secure interfaces, this is also the only possible protocol. I'm not yet completely convinced that a fallback to UDP would be a good option.

    Klaus

    0
  • Stien Van Gestel

    Hi Mateus

    If the network supports KNXnet/IP Multicast, no configuration is needed.

    If KNXnet/IP Multicast is not supported — for example, when the PC is in a different VLAN — you can enter the IP address of the KNX/IP interface in the "Assigned IP Address" field. Ensure all checkboxes for the automatic interface settings are enabled.

    I regularly use parallel connections in both multicast and non-multicast networks.

    Stien

    0
  • Mateus Sybilla

    @Klaus Gütter
    It is misleading when selected protocol is Automatic, and user gets an connection error just because ETS could not connect via TCP, while UDP still works.

    I think as long as it is Automatic, ETS should try UDP when TCP fails, before it throws an error to the user.

     

    @Stien Van Gestel
    I can assure you, It is not working with any of our customer's VPNs.
    But it used to work with ETS5.

    There is no multicast via VPN due to security reasons.

    0
  • Stien Van Gestel

    Hi Mateus
    I'm not using VPN, so I can't give you any advice.
    I know if multicast is not supported, you can enter the assigned IP manually and ETS will make an automatic connection without multicast.

    0