Re: [OpenIndiana-discuss] Nwam interfaces and aliases
If you're not planning on moving this computer between several wireless networks, you might be as well off using physical:default instead of physical:nwam ... On my laptop, I run nwam, but on the servers that use wire connections I use non-nwam, and generally if they're going to sit still for a long time, I even make them static IP's. adding and removing virtual interfaces with nwam is a bit of a ball-ache, adding them with ipadm/dladm is easy :) Jon On 27 February 2014 11:32, jimkli...@cos.ru jimkli...@cos.ru wrote: Hello all, I am still a newb with nwam and ipadm, and recently failed to add an alias ipv4 interface to an nwam-managed interface (needed to add an address in a specific subnet to contact a factory-defaulted device, while the default address is from dhcp). The old ifconfig addif said it added the alias but nothing happened. The dmesg logs revealed that nwam instantly killed the address it did not set up. Adding with ipadm also failed for some syntax reason. Maybe the examples from internet are obsolete or are for oracle solaris. Ultimately i created a vnic and ifconfig'ed that. But i'm still curious if a proper CLI-friendly method exists. Thanks, Jim Typos courtesy of my Samsung Mobile ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Nwam interfaces and aliases
Jim, can you be more specific on the syntax errors? What did nwamcfg complain about? Cheers Stefan Von: jimkli...@cos.ru [jimkli...@cos.ru] Gesendet: Donnerstag, 27. Februar 2014 12:32 An: openindiana-discuss@openindiana.org Betreff: [OpenIndiana-discuss] Nwam interfaces and aliases Hello all, I am still a newb with nwam and ipadm, and recently failed to add an alias ipv4 interface to an nwam-managed interface (needed to add an address in a specific subnet to contact a factory-defaulted device, while the default address is from dhcp). The old ifconfig addif said it added the alias but nothing happened. The dmesg logs revealed that nwam instantly killed the address it did not set up. Adding with ipadm also failed for some syntax reason. Maybe the examples from internet are obsolete or are for oracle solaris. Ultimately i created a vnic and ifconfig'ed that. But i'm still curious if a proper CLI-friendly method exists. Thanks, Jim Typos courtesy of my Samsung Mobile ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Nwam interfaces and aliases
I actually don't think that using NWAM is a matter of potential device mobility. I started using NWAM all over the place and am generally quite happy. Simple and scriptable, just works so far. Especially now that I have understood how to add DNS to the equation. :-) Cheers Stefan Von: Jonathan Adams [t12nsloo...@gmail.com] Gesendet: Donnerstag, 27. Februar 2014 12:38 An: Discussion list for OpenIndiana Betreff: Re: [OpenIndiana-discuss] Nwam interfaces and aliases If you're not planning on moving this computer between several wireless networks, you might be as well off using physical:default instead of physical:nwam ... On my laptop, I run nwam, but on the servers that use wire connections I use non-nwam, and generally if they're going to sit still for a long time, I even make them static IP's. adding and removing virtual interfaces with nwam is a bit of a ball-ache, adding them with ipadm/dladm is easy :) Jon On 27 February 2014 11:32, jimkli...@cos.ru jimkli...@cos.ru wrote: Hello all, I am still a newb with nwam and ipadm, and recently failed to add an alias ipv4 interface to an nwam-managed interface (needed to add an address in a specific subnet to contact a factory-defaulted device, while the default address is from dhcp). The old ifconfig addif said it added the alias but nothing happened. The dmesg logs revealed that nwam instantly killed the address it did not set up. Adding with ipadm also failed for some syntax reason. Maybe the examples from internet are obsolete or are for oracle solaris. Ultimately i created a vnic and ifconfig'ed that. But i'm still curious if a proper CLI-friendly method exists. Thanks, Jim Typos courtesy of my Samsung Mobile ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Nwam interfaces and aliases
I taught myself nwam for my laptop ... and I'm probably more unusual in that I run an OpenLDAP replica on my laptop and use LDAP for login (overridden automount to point to localhost for selected users, syncs automatically on seeing the home network) but I have to say that NWAM gets in the way if you just want to temporarily plumb up an interface on 192.168.0.99 or 192.168.1.99 to talk to some random router/print server and change the IP address. On our servers, we have had a couple of OI boxes that would DHCP fine for a month, then one day just set the IP address to 0.0.0.0, reboot fixed it, setting static IP fixed it permanently. On our Static IP VPN boxes I have nwam turned off to make my life easier with the Solaris 10 guys in our office, ipadm and dladm are a lot easier to convert them to than teaching nwam. Jon On 27 February 2014 12:24, Stefan Müller-Wilken stefan.mueller-wil...@acando.de wrote: I actually don't think that using NWAM is a matter of potential device mobility. I started using NWAM all over the place and am generally quite happy. Simple and scriptable, just works so far. Especially now that I have understood how to add DNS to the equation. :-) Cheers Stefan Von: Jonathan Adams [t12nsloo...@gmail.com] Gesendet: Donnerstag, 27. Februar 2014 12:38 An: Discussion list for OpenIndiana Betreff: Re: [OpenIndiana-discuss] Nwam interfaces and aliases If you're not planning on moving this computer between several wireless networks, you might be as well off using physical:default instead of physical:nwam ... On my laptop, I run nwam, but on the servers that use wire connections I use non-nwam, and generally if they're going to sit still for a long time, I even make them static IP's. adding and removing virtual interfaces with nwam is a bit of a ball-ache, adding them with ipadm/dladm is easy :) Jon On 27 February 2014 11:32, jimkli...@cos.ru jimkli...@cos.ru wrote: Hello all, I am still a newb with nwam and ipadm, and recently failed to add an alias ipv4 interface to an nwam-managed interface (needed to add an address in a specific subnet to contact a factory-defaulted device, while the default address is from dhcp). The old ifconfig addif said it added the alias but nothing happened. The dmesg logs revealed that nwam instantly killed the address it did not set up. Adding with ipadm also failed for some syntax reason. Maybe the examples from internet are obsolete or are for oracle solaris. Ultimately i created a vnic and ifconfig'ed that. But i'm still curious if a proper CLI-friendly method exists. Thanks, Jim Typos courtesy of my Samsung Mobile ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Nwam interfaces and aliases
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@n54l:~# ifconfig bge0 addif 10.94.56.100/24 up Created new logical interface bge0:1 root@n54l:~# ifconfig bge0:1 ifconfig: status: SIOCGLIFFLAGS: bge0:1: no such interface root@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@n54l:~# ipadm show-addr ADDROBJ TYPE STATEADDR lo0/v4static 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/v6static 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@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@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@n54l:~# dladm create-vnic -t -l bge0 vnic1 root@n54l:~# ifconfig vnic1 plumb 10.94.56.100/24 up root@n54l:~# ifconfig vnic1 vnic1: flags=1100843UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4 mtu 1500 index 6 inet 10.94.56.100 netmask ff00 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 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
