Hi David,
David Edmondson wrote:
I'd like to enhance Solaris network configuration slightly to allow
guest domain IPv4 details to be passed from the domain building
control tools through to the relevant components in Solaris
(svc:/network/physical and uts/common/fs/nfs/nfs_dlinet.c).
Attached is a proposal, roughly in the form of a fasttrack.
I'd like to make a suggestion or two...
...
| Variable | Type | Meaning | Examples
|
|------------+--------+-----------------------------------+-----------------------------|
| ip | string | IPv4 address of the domain | "10.6.39.40"
|
| netmask | string | netmask of the domain | "255.255.255.0"
|
| gateway | string | default router for the domain | "10.6.39.1"
|
| dhcp | string | is DHCP enabled? | "on" "off"
|
| vif | list | network interfaces specifications | see below
|
| nfs_root | string | pathname of NFS root filesystem |
"pushrod:/export/root/xen1" |
| nfs_server | string | IPv4 address of the NFS server | "10.6.39.80"
|
Can we expand this to also cover peer-to-peer connections,
such as tunnels, etc?
I'll continue reading the rest of it later (timeout interrupt)..
Darren
_______________________________________________
networking-discuss mailing list
[email protected]
