Albert Kwok wrote:
> Yes, it should work without rebooting but svcadm disable
> svc:/network/physical:nwam release the IP address and svcadm enable
> svc:/network/physical:default didn't get an new IP address. I supposed I
> could have done "ifconfig xnf0 dhcp start" to get the new IP address.
>
> Anyway, I must test the reboot of the VM because I am building template for
> my cloud.
>
> Too bad the new nwam service didn't work with DHCP. I like the nwam which
> doesn't required me to create the dhcp.xnf0 and hostname.xnf0. This allows me
> to move the VM from cloud to cloud as different cloud has different driver
> for the NIC.
You're still running snv_111, right? It'd be interesting to know if the
newest-available snv_134 (which is 23 builds or 46 *weeks* newer) does a
better job with this.
But, yeah, it's hard to please everyone. One of the issues that I know
about in this area is that ISPs are well-known for giving out horrible
automatically-generated host names that nobody in his right mind will
want ("h00345c8e700015" is the sort of thing commonly seen), so at least
defaulting to ignoring that mess is a Good Thing for most people.
I realize things are different on the SWAN, though. (Or is that now the
OWAN? ;-})
--
James Carlson 42.703N 71.076W <[email protected]>
_______________________________________________
networking-discuss mailing list
[email protected]
