Anyone know if the ability to have a Gateway address to a PK controller 3rd party NIC has been added for V15, or if this is even in the works?
Curious as to the thought process of not having the ability to add a gateway, it is rare for us anyway to have a single LAN segment with switching in the same building, to limit physical switches, we utilize VLAN's, and use firewalls to route all traffic. Having a PK in one area of the plant to utilize the 3rd party communications to a node located in a completely different area, we create a VLAN with a /29 subnet but since all the traffic is routed using Dot1Q just putting the PK on the network does not work without having to add a bunch of static routes and creating a VPLS tunnel to get there.
At least that is all I have been able to come up with. Anyone else have any ideas??
Emerson, was the scenario of a customer using routing and VLANs for all layer 2.5/3 networks not considered, or is there a solution I am missing?
Yes. In v15, the PK Controller network port configuration dialogs have been updated to allow for better management of the network details including setting of the Gateway address to something other than the default first address in the subnet.
Andre Dicaire
In reply to Andre Dicaire:
In reply to Brian Hrankowsky:
Hi Andre, so it’s supposed to be implicit at the .1 address of the subnet? Not working for me. I can not get to the PK. If I plug a laptop into the port the PK mod slave would be at and assign on the laptop with a gateway at .1 no problems. But no way with the PK. My design is from one plant to the other, across from a PK acting as a master at KN, on 192.168.36.0 and the PK at KS on 192.168.136.0 no issues if I sub in a laptop running MDBus for the PK as long as I assign 192.168.136.1 at the KS end. It does not seem to be implicit at .1 hmm.
If it is supposed to be .1 I’ll give another go on our standard routing.
In reply to Benji_Kidmose: