zhangye wrote:Does different NioNode's TCP/IP port not in the same VLAN?We also have many VLANs,but our Nion's TCP/IP port in the same VLAN. We open the third level on switchs,we can access other VLAN's TCP/IP Devices .Do you want to do that?
From what I understand, this is not what he wants to do.
If I am understanding Jason correctly, his computer has a Network Interface Card (NIC) that is capable of interfacing with multiple VLANs in a network structure. You know how you can link more than one VLAN between two network switches with a single cable? He can do that between his computer and the network switch. This is really handy because it means that he does not need two separate NICs and network cables to connect to the control network and the CobraNet network. They both show up on one physical port, with one physical cable connected to the computer. However, in the software on his computer, each of the VLANs show up as a separate entry with different IP addresses (set according to the rules of that VLAN) and he has given "friendly names" to the VLANS so he can keep them straight.
When he starts NWare the "Communications Preferences" dialog box opens and asks him to "Please select the IP you wish to use for NION communications". In a typical computer configuration there is only one or two, maybe three options available in this box. In Jason's situation, each of the VLANs that are available from his network interface show up as a separate entry in this list. What does not show up is the "Friendly Names" he has given to all the interfaces, so he has to reference his notes to remember which IP address is on the VLAN that he actually wants to communicate with. He would like us to pass the friendly names from Windows Networking into NWare so he doesn't have to refer to his notes.
I think it is a good idea!
Jason- Let me know if any of this is incorrect because this is what I am going to pass along to the software engineering crew.
Thanks!
-Josh
Josh Millward
Burnt Orange Studios
