[OpenIndiana-discuss] Nwam interfaces and aliases

[Jim Klimov]

On 2014-02-27 12:38, Stefan Müller-Wilken wrote:
> Jim,
>
> can you be more specific on the syntax errors? What did nwamcfg complain about?

Yes, now that I'm back to the home network ;)

root at n54l:~# ifconfig bge0 addif 10.94.56.100/24 up
Created new logical interface bge0:1

root at n54l:~# ifconfig bge0:1
ifconfig: status: SIOCGLIFFLAGS: bge0:1: no such interface

root at n54l:~# dmesg

Thu Feb 27 02:06:44 MSK 2014
...
Feb 27 02:06:34 n54l nwamd[74]: [ID 902597 daemon.error] 1:
   nwamd_ncu_handle_if_state_event: address 10.94.56.100 not managed
   by nwam added, removing it
Feb 27 02:06:34 n54l nwamd[74]: [ID 766609 daemon.error] 1:
   nwamd_ncu_handle_if_state_event: address 10.94.56.100 not managed
   by nwam removed, nothing to do

root at n54l:~# ipadm show-addr
ADDROBJ           TYPE     STATE        ADDR
lo0/v4            static   ok           127.0.0.1/8
bge0/_b           dhcp     ok           192.168.1.111/24
vnic127001/v4     static   ok           192.168.127.1/24
tun0/_a           static   ok           192.168.131.50->192.168.131.49
lo0/v6            static   ok           ::1/128
bge0/_a           addrconf ok           fe80::2a92:4aff:fe36:bc8/10



The following was done by examples from a blog, and failed at syntax:

root at n54l:~# ipadm create-addr -T static -a 10.94.56.100/24 
bge0/ipv4alias
ipadm: Could not create address: Persistent operation on temporary object

root at n54l:~# ipadm create-addr -t -T static -a 10.94.56.100/24 
bge0/ipv4alias
ipadm: Could not create address: Interface does not exist


Ultimately, this worked for me (to peek into a 10.94.56 subnet):

root at n54l:~# dladm create-vnic -t -l bge0 vnic1
root at n54l:~# ifconfig vnic1 plumb 10.94.56.100/24 up
root at n54l:~# ifconfig vnic1
vnic1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 
1500 index 6
         inet 10.94.56.100 netmask ffffff00 broadcast 10.94.56.255
         ether 2:8:20:9e:b6:26

Regarding the disablement of NWAM, I was inclined to do that -
and configure things the way I do them for decades, but this is
a box in my brother's home with the LAN managed by an access point.
If he ever changes networking settings there, he won't be too happy
about logging into the NAS box to learn how to change static IP setup.
Of course, I could leave the physical default configuration with DHCP
as well, but this is not something I'd cheerfully experiment with being
several thousand miles away ;)

So whatever works out of the box... I'm rather happy with here, just
to be safe.

Thanks,
//Jim