Hi,
You can define any extra attribute, like NETMASK, in the Virtual Network
template when you create it.
Those attributes can be accessed within the VM using contextualization. In
[1], there's a brief example with a DNS field.
Don't forget to make your vmcontext script do something useful with t
I think the "255.255.255.0" is not suitable for the "B" type network.
wen.y...@cs2c.com.cn wrote:
In script vmcontexttty ,the subnet mask of virtual machine is setted
as "255.255.255.0". If the subnet mask of physical PC isn't equal to
"255.255.255.0", then the physical PC can communicate wit
In script vmcontexttty ,the subnet mask of virtual machine is setted as
"255.255.255.0". If the subnet mask of physical PC isn't equal to
"255.255.255.0", then the physical PC can communicate with virtual machine
or not?
For example:
The physical PC's IP is "10.1.29.105", subnet mask
is "255.
