cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Kepware should be able to connect to Thingworx using IPv6

Kepware should be able to connect to Thingworx using IPv6

If you specify a server name for KW to use to connect to TW it often gets resolved with an IPv6 address... and the connection fails (until you give KW an IPv4 address for TW). This means we can't use IPv6 or FQDNs/DNS. It also makes certificate validation slightly dubious.

2 Comments
pjahn
16-Pearl

IPv6 should be supported by PTC in general.

MikeFR
8-Gravel
I agree. The base issue for this particular example is IPv6 handling on Thingworx.

IPv6 support would give:
-Auto MTU discovery e.g. you're on PPPoE internet and the max packet size is wierd and won't let packets go straight through your router
-Better perf over non-wired connections
-No delay from a browser trying IPv6 then falling back to IPv4... this can be a non-trivial amount of time like 1 sec or the fallback could fail
-Better QoS, Security
-More efficient routing